Requirements Engineering Work Products#
Stakeholder Requirements
|
status: valid
|
||||
Technical requirements from a stakeholder viewpoint on SW-platform level, contain “assumed Technical Safety Requirements” in SW-Platform SEooC development. |
|||||
Feature Requirements
|
status: valid
|
||||
Feature requirements describe in a more detailed way the functionality which will fulfill a set of stakeholder requirements. A “feature” itself represents a set of requirements. It describes the interaction of the components to form a feature. It shall also be the basis for integration testing on platform level. |
|||||
Component Requirements
|
status: valid
|
||||
SW Requirements for components, broken down from feature requirements to the realizing component. These include configuration specification. |
|||||
SW-Platform Assumptions of Use
|
status: valid
|
||||
SW Safety Requirements for the user of the platform, exportable requirements for the user to integrate in their requirements management system. |
|||||
Feature Assumptions of Use
|
status: valid
|
||||
SW Safety Requirements for the user of the feature, exportable requirements for the user to integrate in their req mgt system. |
|||||
Component Assumptions of Use
|
status: valid
|
||||
SW Safety Requirements for the user of the component, exportable requirements for the user to integrate in their req mgt system. |
|||||
Process/Tool Requirements
|
status: valid
|
||||
Process and Tool requirements describe activities needed to be executed in the development process either manually or automated (i.e. tool supported). Tool requirements (if derived from process requirements) are more detailed as those are also the basis for tool (qualification) testing. |
|||||
Requirements Inspection
|
status: draft
|
||||
Depends on requirements management tooling, expect text based requirements. Review done with inspection checklist. This checklist may be integrated in requirements/version management tooling. |
|||||