ISO IEC IEEE 29148:2018 pdf free

ISO IEC IEEE 29148:2018 pdf free.Systems and software engineering一Life cycle processes一Requirements engineering
Defining requirements begins with stakeholder needs (or goals, or objectives) that are refined and evolve before arriving as valid stakeholder requirements. Initial stakeholder concerns do not serve as stakeholder requirements, since they often lack definition, analysis and possibly consistency and feasibility. Using the Concept of Operations to aid the understanding of the stakeholder concerns at the organizational level and the System Operational Concept from the system perspective, requirements engineering leads stakeholders from those initial, often latent needs to a set of objectively adequate,structured and more formal statements of stakeholder requirements and goals. These statements are well-formed and meet the characteristics of 5.2.4, 5.2.5, and 5.2.6.
When the system of interest is a system element at the second or lower level in the overall system structure, it is also necessary to identify stakeholder needs and requirements at that level. These needs do not just apply to the topmost system in the system structure. There could be additional stakeholders that are not discovered until lower level architecture or design decisions are made.
The stakeholder-owned system requirements are then transformed into lower level system element requirements for the system-of-interest. Where risk due to technology or complexity is significant,requirements are genuinely changing because of change of need, or requirements were never properly defined in the first place, this transformation may involve significant iteration. The same processes are also applied recursively to lower physical level system elements that themselves are subject to design and development, generating again lower-level system element requirements in the process.
Clause 6 details the processes to perform stakeholder and system requirements definition. Clauses 7,8,and 9 contain further guidance on information items associated with documenting the requirements.
Annex A provides requirements for the content of a System Operational Concept and Annex B provides guidelines for the content of a Concept of Operations.
NOTE See ISO/IEC 26551 for additional guidance on requirements development techniques, including requirements reuse.ISO IEC IEEE 29148 pdf download.