Feature Security Work Products List#
[Your Feature Name] Security WPs
|
status: draft
security: YES
safety: ASIL_B
|
||||
Attention
The above directive must be updated according to your Feature.
Modify
Your Feature Nameto be your Feature NameModify
idto be your Module Name in upper snake case preceded bydoc__and succeeded by_security_wpAdjust
statusto bevalidAdjust
safetyandtagsaccording to your needs
Tailoring#
Additional to the tailoring in the SW platform project as defined in the project’s Platform Security Plan we define here the additional tailoring on feature level.
Excluded for this feature are additionally the following work products (and their related requirements):
<work product/requirement> - <Argumentation why it is not needed or replaced by another work product or activity.>
Security Work products List#
Work product Id |
Link to process |
Process status |
Link to WP |
|---|---|---|---|
valid |
|||
valid |
|||
valid |
|||
valid |
|||
valid |
|||
valid |
|||
valid |
<Link to WP> |
Attention
The above table must be updated according to your feature security planning.
Fill the work producs links
Feature Security Package#
To create the security package (according to Security Package Automated ...) the following documents and work products status have to go to “valid” (after the relevant verification were performed).
Feature Documents Status#
For all the work product documents the status can be seen by following the “Link to WP”. A summary of the status is also documented in the project’s documentation management plan.
See <add here the section reference to the documentation management plan>
Feature Requirements Status#
ID |
Status |
|---|---|
invalid |
Feature AoU Status#
ID |
Status |
|---|---|
invalid |
Feature Architecture Status#
ID |
Status |
|---|---|
invalid |
|
invalid |