Difference between revisions of "Requirement (glossary)"
(Text replacement - "\[\[\s*([^]]*)\s*\(glossary\)\s*\|\s*([^]]+)\]\]" to "{{Term|$1 (glossary)|$2}}") |
m (Text replacement - "<center>'''SEBoK v. 2.0, released 1 June 2019'''</center>" to "<center>'''SEBoK v. 2.1, released 31 October 2019'''</center>") |
||
Line 13: | Line 13: | ||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
− | <center>'''SEBoK v. 2. | + | <center>'''SEBoK v. 2.1, released 31 October 2019'''</center> |
Revision as of 15:04, 24 October 2019
Statement that identifies a
(ISO/IEC 2007)
*includes product,
Source
ISO/IEC. 2007. Systems and Software Engineering -- Recommended Practice for Architectural Description of Software-Intensive Systems. Geneva, Switzerland: International Organization for Standards (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 42010:2007.
Discussion
A requirement is “a statement that identifies a system, product or process characteristic or constraint, which is unambiguous, clear, unique, consistent, stand‐alone (not grouped), and verifiable, and is deemed necessary for
INCOSE. 2010. Systems Engineering Handbook: A Guide for System Life Cycle Processes and Activities. Version 3.2.1. San Diego, CA, USA: International Council on Systems Engineering (INCOSE), INCOSE-TP-2003-002-03.2.1: 362.