Difference between revisions of "Stakeholder Needs and Requirements (glossary)"

From SEBoK
Jump to navigation Jump to search
m (Text replacement - "SEBoK v. 2.9, released 20 November 2023" to "SEBoK v. 2.10, released 06 May 2024")
 
(39 intermediate revisions by 8 users not shown)
Line 1: Line 1:
''<blockquote>(1) A formally drafted [[Service (glossary)|service]], objective or [[Capability (glossary)|capability]] that is desired or expected from the future system by a [[stakeholder(glossary)]].
+
<blockquote>(1a)'' Stakeholder needs include elicitation of needs, wants, desires, expectations and perceived constraints of identified stakeholders.  Needs concentrate on system purpose and behavior, and are described in the context of the operational environment and conditions.'' (ISO/IEC/IEEE 15288, 2023, Section 6.4.2)</blockquote>
</blockquote>''
 
  
''<blockquote>(2) Equivalent to expectation.</blockquote>''
+
<blockquote>(1b)'' Stakeholder requirements are transformed from the stakeholder needs to objectively adequate, structured and more formal statements.'' (ISO/IEC/IEEE 29148, 2018, Section 5.2.3)</blockquote>
 +
 +
<blockquote>(1c)'' Stakeholder requirements express the intended interaction the system will have with its operational environment and that are the reference against which each resulting operational capability is validated. The stakeholder requirements are defined considering the context of the system of interest with the interoperating systems and enabling systems. This also includes consideration of laws and regulations, environmental restrictions, and ethical values.'' (ISO/IEC/IEEE 15288, 2023, Section 6.4.2)</blockquote>
  
====Source====
+
===Source===
This definition was developed for the SEBoK version 0.5. ‘’Note to reviewers’’: If you are aware of a more authoritative definition, please provide this information in your review.
+
ISO/IEC/IEEE. 2023. ''[[ISO/IEC/IEEE 15288|Systems and Software Engineering -- System Life Cycle Processes]]''. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions / Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2023.  
 +
 
 +
ISO/IEC/IEEE. 2018. ''[[ISO/IEC/IEEE 29148|Systems and software engineering — Life cycle processes — Requirements engineering]]''. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions / Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 29148:2018.  
  
 
===Discussion===
 
===Discussion===
There is currently no discussion for this term.  This will be completed for SEBoK version 1.0.
+
Both definitions are taken from the introduction to the "Stakeholder Requirements Definition Process" in ISO/IEC 15288; there is no formal definition of the term "stakeholder requirement" in the standard.
 +
   
 +
For a full discussion of the role and importance of stakeholder needs in systems engineering see the [[Stakeholder Needs Definition]] article.
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
  
 
+
<center>'''SEBoK v. 2.10, released 06 May 2024'''</center>
 
 
{{DISQUS}}
 

Latest revision as of 22:34, 2 May 2024

(1a) Stakeholder needs include elicitation of needs, wants, desires, expectations and perceived constraints of identified stakeholders. Needs concentrate on system purpose and behavior, and are described in the context of the operational environment and conditions. (ISO/IEC/IEEE 15288, 2023, Section 6.4.2)

(1b) Stakeholder requirements are transformed from the stakeholder needs to objectively adequate, structured and more formal statements. (ISO/IEC/IEEE 29148, 2018, Section 5.2.3)

(1c) Stakeholder requirements express the intended interaction the system will have with its operational environment and that are the reference against which each resulting operational capability is validated. The stakeholder requirements are defined considering the context of the system of interest with the interoperating systems and enabling systems. This also includes consideration of laws and regulations, environmental restrictions, and ethical values. (ISO/IEC/IEEE 15288, 2023, Section 6.4.2)

Source

ISO/IEC/IEEE. 2023. Systems and Software Engineering -- System Life Cycle Processes. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions / Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 15288:2023.

ISO/IEC/IEEE. 2018. Systems and software engineering — Life cycle processes — Requirements engineering. Geneva, Switzerland: International Organisation for Standardisation / International Electrotechnical Commissions / Institute of Electrical and Electronics Engineers. ISO/IEC/IEEE 29148:2018.

Discussion

Both definitions are taken from the introduction to the "Stakeholder Requirements Definition Process" in ISO/IEC 15288; there is no formal definition of the term "stakeholder requirement" in the standard.

For a full discussion of the role and importance of stakeholder needs in systems engineering see the Stakeholder Needs Definition article.

SEBoK v. 2.10, released 06 May 2024