Requirements Engineering Workflows#
For a detailed explanation of workflows and their role within the process model, please refer to the Introduction.
Create/Maintain Stakeholder requirements and SW-Platform AoU
|
status: valid
|
||||
Stakeholder requirements and SW-Platform Assumptions of Use (AoU) can be created during a change request. Any contributor can create a stakeholder requirement (or AoU) and propose it for approval. |
|||||
Create/Maintain Feature requirements
|
status: valid
|
||||
Depending on the stakeholder requirements feature requirements can be derived. This can be done by any contributor and will be approved by a project lead. If needed safety and security managers can provide support. |
|||||
Create/Maintain Feature AoUs
|
status: valid
|
||||
Based on the safety concept on feature level, feature AoUs can be derived. See also Workflow for Creating and Linking Assumption of Use (AoU) |
|||||
Create/Maintain Component requirements
|
status: valid
|
||||
Create/Maintain Component AoUs
|
status: valid
|
||||
Based on the safety concept on component level, component AoUs can be derived. See also Workflow for Creating and Linking Assumption of Use (AoU) |
|||||
Create/Maintain Process and Tool Requirements
|
status: valid
|
||||
Based on the process descriptions (which comply to standards) and/or stakeholder requirements process and tool requirements are derived. |
|||||
Monitor/Verify Requirements
|
status: valid
|
||||
The requirements are monitored and verified. The inspection shall be implemented as integral part of the review in version management tool. |
|||||