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")
 
(26 intermediate revisions by 5 users not shown)
Line 1: Line 1:
''<blockquote>(1a) The [[Requirement (glossary)|requirements]] for a system that can provide the [[Service (glossary)|services]] needed by [[User (glossary)|users]] and other [[Stakeholder (glossary)|stakeholders]] in a defined [[Environment (glossary)|environment]].'' (ISO/IEC, 2008, section 6.4.1)</blockquote>
+
<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>(1b) The Stakeholder Requirements definition process identifies [[Stakeholder (glossary)|stakeholders]], of classes of stakeholders, involved with the system throughout its [[Life Cycle (glossary)|life cycle]], and their needs, expectations and desires.  It transforms these into a common set of stakeholder requirements that express the intended interaction the system will have  with its operational environment and that are the reference against which each resulting operational service is [[Validation (glossary)|validated]]'' (ISO/IEC,2008, section 6.4.1) </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===
 +
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.
  
===Source===
+
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.  
(1) ISO/IEC. 2008. ''Systems and Software Engineering - System Life Cycle Processes''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electronical Commission (IEC), ISO/IEC 15288:2008 (E).  
 
  
 
===Discussion===
 
===Discussion===
Both definitions are taken from the introduction to the Stakeholder Requirements Definition process, there is no formal definition of the term "Stakeholder Requirement" in the standard.
+
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 requirements in Systems Engineering see the [[Stakeholder Needs and Requirements]] article.
+
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]]
  
{{DISQUS}}
+
<center>'''SEBoK v. 2.10, released 06 May 2024'''</center>

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