Difference between revisions of "Requirement (glossary)"
| Line 1: | Line 1: | ||
| − | ''<blockquote>Statement that identifies a product* or process operational, functional, or design characteristic or constraint, which is unambiguous, testable or measurable, and necessary for product or process acceptability. (ISO/IEC 2007) *includes product or | + | ''<blockquote>Statement that identifies a [[Product (glossary)|product]]* or [[Process (glossary)|process]] [[Operational (glossary)|operational]], functional, or [[Design (glossary)|design]] characteristic or [[Constraint (glossary)|constraint]], which is unambiguous, testable or measurable, and necessary for product or process acceptability. (ISO/IEC 2007) |
| + | |||
| + | *includes product, [[Service (glossary)]], or [[Enterprise (glossary)]]. </blockquote>'' | ||
====Source==== | ====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 | + | 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=== | ===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 stakeholder acceptability.” (INCOSE. 2010) | + | 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 [[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. | ||
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
Revision as of 14:18, 14 September 2011
Statement that identifies a product* or process operational, functional, or design characteristic or constraint, which is unambiguous, testable or measurable, and necessary for product or process acceptability. (ISO/IEC 2007)
- includes product, service , or enterprise .
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 stakeholder acceptability.” (INCOSE. 2010)
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.