Difference between revisions of "Requirement (glossary)"
Jump to navigation
Jump to search
(Created page with '''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow ...') |
|||
| Line 1: | Line 1: | ||
| − | ''<blockquote> | + | ''<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)/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 Electronical Commission (IEC), ISO/IEC 42010:2007. | |
===Discussion=== | ===Discussion=== | ||
Revision as of 15:10, 18 May 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)/blockquote>
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 Electronical Commission (IEC), ISO/IEC 42010:2007.
Discussion
Discussion as to why this is the "consensus" definition for the SEBoK.