Difference between revisions of "Requirement (glossary)"
m (Text replacement - "<center>'''SEBoK v. 1.9.1, released 16 October 2018'''</center>" to "<center>'''SEBoK v. 2.0, released 1 June 2019'''</center>") |
(Text replacement - "\[\[\s*([^]]*)\s*\(glossary\)\s*\|\s*([^]]+)\]\]" to "{{Term|$1 (glossary)|$2}}") |
||
Line 1: | Line 1: | ||
− | ''<blockquote>Statement that identifies a | + | ''<blockquote>Statement that identifies a {{Term|Product (glossary)|product}}* or {{Term|Process (glossary)|process}} {{Term|Operational (glossary)|operational}}, functional, or {{Term|Design (glossary)|design}} characteristic or {{Term|Constraint (glossary)|constraint}}, which is unambiguous, testable or measurable, and necessary for product or process acceptability.'' (ISO/IEC 2007)</blockquote> |
− | <blockquote>*includes product, | + | <blockquote>*includes product, {{Term|Service (glossary)|service}}, or {{Term|Enterprise (glossary)|enterprise}}.</blockquote> |
===Source=== | ===Source=== | ||
Line 7: | Line 7: | ||
===Discussion=== | ===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 | + | 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 {{Term|Stakeholder (glossary)|stakeholder}} acceptability.” (INCOSE 2010) |
INCOSE. 2010. ''[[INCOSE Systems Engineering Handbook|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. | INCOSE. 2010. ''[[INCOSE Systems Engineering Handbook|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. |
Revision as of 21:56, 2 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.