A standard defines agreed rules, terms, criteria, or practices for creating, assessing, or operating systems and work products consistently.
In requirements engineering, it can define processes, document structures, terminology, quality criteria, and required evidence. Therefore, teams gain comparable results and clearer handovers.
For software requirements, IEEE 830 influenced the traditional structure of a Software Requirements Specification. Meanwhile, ISO/IEC/IEEE 29148 provides modern guidance for requirements processes and information items across the lifecycle.
ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288 describe lifecycle processes. In addition, ISO/IEC 25010 defines system and software quality characteristics. ISO 9241-210 supports human-centred design, while ISO/IEC 29110 addresses very small entities. Moreover, ISO 9001 influences quality management, identification, and traceability.
Regulated industries use additional guidance. For example, aviation projects may apply DO-178C/ED-12C. Medical device software often uses IEC 62304. Rail projects may follow CENELEC-related rule sets. Furthermore, telecommunications projects frequently use publications from ITU-T and ETSI.
No single standard fits every project. Therefore, teams should identify applicable publications, resolve overlaps, and document justified deviations.
Effective application converts external guidance into practical project rules for artifacts, terminology, attributes, approvals, reviews, and compliance evidence.
« Back to Glossary Index