Difference between revisions of "System Requirement (glossary)"
m (Text replacement - "SEBoK v. 2.9, released 20 November 2023" to "SEBoK v. 2.10, released 06 May 2024") |
|||
| (21 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
| − | ''<blockquote>(1a) A statement that transforms the | + | ''<blockquote>(1a) ''A statement that transforms the stakeholder, user-oriented view of desired capabilities into a technical view, of a solution that meets the operational needs of the user.'' (ISO/IEC/IEEE, 2015, section 6.4.2) </blockquote> |
| − | ''<blockquote>(1b) The Requirement | + | ''<blockquote>(1b) The System Requirement Definition process creates a set of measurable system requirements that specify, from the supplier’s perspective, what characteristics, attributes, and functional and performance requirements the system is to possess, in order to satisfy stakeholder requirements. |
| + | '' (ISO/IEC/IEEE, 2015, section 6.4.2) </blockquote> | ||
===Source=== | ===Source=== | ||
| − | (1) ISO/IEC. | + | (1) ISO/IEC/IEEE. 2015. ''Systems and Software Engineering - System Life Cycle Processes''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2015 (E). |
===Discussion=== | ===Discussion=== | ||
| − | Both definitions are | + | Both definitions are modified from the introduction to the Requirements Analysis process, there is no formal definition of the term "system requirement" in the standard. |
| − | + | The term (engineered system) has been substituted for the word (product) in definition 1a to better align with the terminology used in the SEBoK. | |
| − | For a full discussion of the role and importance of system requirements in | + | For a full discussion of the role and importance of system requirements in systems engineering see the [[System Requirements|System Requirements]] article. |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| − | + | <center>'''SEBoK v. 2.10, released 06 May 2024'''</center> | |
Latest revision as of 23:17, 2 May 2024
(1a) A statement that transforms the stakeholder, user-oriented view of desired capabilities into a technical view, of a solution that meets the operational needs of the user. (ISO/IEC/IEEE, 2015, section 6.4.2)
(1b) The System Requirement Definition process creates a set of measurable system requirements that specify, from the supplier’s perspective, what characteristics, attributes, and functional and performance requirements the system is to possess, in order to satisfy stakeholder requirements. (ISO/IEC/IEEE, 2015, section 6.4.2)
Source
(1) ISO/IEC/IEEE. 2015. Systems and Software Engineering - System Life Cycle Processes. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE). ISO/IEC/IEEE 15288:2015 (E).
Discussion
Both definitions are modified from the introduction to the Requirements Analysis process, there is no formal definition of the term "system requirement" in the standard.
The term (engineered system) has been substituted for the word (product) in definition 1a to better align with the terminology used in the SEBoK.
For a full discussion of the role and importance of system requirements in systems engineering see the System Requirements article.