Capturing requirements
Requirements are used as the basis for all development tasks in a systems engineering project. All team members and stakeholders participate in gathering and evaluating system engineering requirements.
About this task
There are two types of systems engineering requirements:
- Stakeholder requirements are typically outlined as general capabilities for a system and often originate from external sources, such as set of requirements documents. These documents also include the business requests of clients and customers. Agreed upon requirements and requests are consolidated into a single requirements document, or specification structure. If requirements change, or new ones are conceived, the specification must be updated so that all requirements are accurately described. Then, agreed upon requirements and requests are combined into a consistent requirements specification.
- System requirements are derived from stakeholder requirements and describe what the system must do based on the requirements. System requirements describe specific functions necessary within a system to "satisfy" each stakeholder requirement. A system requirement must map to at least one use case.
- Roles:
- Stakeholders
- Systems engineers
- Artifacts:
- Requirements documents
- External requirement sources
Procedure
- Import the system and stakeholder requirements from your external sources (Microsoft word, for example) into DOORS® .
- In DOORS , use the "satisfy" dependency to link each system requirement to a stakeholder requirement.
- Export the system requirements from DOORS into Rhapsody .