ISO/IEC/IEEE 29148 Standard
ISO/IEC/IEEE 29148:2018 — ISO/IEC/IEEE International Standard — Systems and software engineering — Life cycle processes — Requirements engineering is the latest international standard describing requirements engineering processes for development of software and hardware products and systems.
It obsoletes the well known standard for software requirements specifications: IEEE 830-1998 — IEEE Recommended Practice for Software Requirements Specifications.
Document Templates
To create a new document based on the ISO/IEC/IEEE 29148 standard, click Project and select Add Document. In the New Document dialog, choose Predefined, and then select one of the following requirements specifications:
- ISO 29148: Stakeholder Requirements Specification (StRS) describing stakeholder requirements,
- ISO 29148: System Requirements Specification (SyRS) describing system requirements,
- ISO 29148: Software Requirements Specification (SRS) describing software requirements.
- ISO 29148: Business Requirements Specification (BRS) describing business or mission requirements, or
- ISO 29148: System Operational Concept (OpsCon) describing stakeholder needs.
These Document Templates preserve structure of sections provided in the standard and define requirements attributes supporting the requirements process described in the standard.
Instructions
The standard provides detailed information about the requirements engineering process for software and system products and we strongly recommend it as the primary source of information for using the templates in your projects.
If you create a new document from one of the templates above then the application displays detailed guidance from the standard in the Instructions pane:
Another useful source of information is the Guide to the Systems Engineering Body of Knowledge (SEBoK) by the Body of Knowledge and Curriculum to Advance Systems Engineering (BKCASE) governed by the International Council on Systems Engineering (INCOSE), the Systems Engineering Research Center (SERC) and the IEEE Computer Society.
Attributes
| Name | Identifier | Type | Description |
|---|---|---|---|
| Id | id | string | Unique identifier within the document |
| Heading | heading | string | Short name of the document section or the requirement |
| Text | text | xhtml | Intent of the requirement |
| Owner | owner | string | The person or element of the organization that maintains the requirement |
| Priority | priority | enum | Requirements importance for the stakeholder relative to the whole project |
| Source | source | string | Source of the requirements, e.g., name of the person who raised the requirement or reference to a related standard |
| Rationale | rationale | xhtml | Explanation of the reason why the requirement is needed |
| Difficulty | difficulty | enum | Assumed difficulty of the requirement |
| Type | type | enum | Type of the document object — Section, Information, Functional Requirement, Non-functional Requirement |
| Status | status | enum | Requirements status supporting your workflow |
| Verification Method | verMethod | enum | Verification method — Test, Demonstration, Inspection or Analysis |
Example
Check the Software Requirements Specification (SRS) document in the Example Project or Example SRS:
