Derived Requirement (glossary): Difference between revisions
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 ...') |
No edit summary |
||
| Line 1: | Line 1: | ||
''<blockquote> | ''<blockquote>Constraint stated during the design activities which arise as a result of the selected solution (for example, a necessary mean or resource related to a technology, or an interface between two components of different sub-systems). (Faisandier 2011 (expected--not yet published)) </blockquote>'' | ||
====Source==== | ====Source==== | ||
Faisandier, A. 2011 (expected--not yet published). ''Engineering and Architecting Multidisciplinary Systems''. TBD: TBD. | |||
===Discussion=== | ===Discussion=== | ||
Revision as of 14:26, 17 May 2011
Constraint stated during the design activities which arise as a result of the selected solution (for example, a necessary mean or resource related to a technology, or an interface between two components of different sub-systems). (Faisandier 2011 (expected--not yet published))
Source
Faisandier, A. 2011 (expected--not yet published). Engineering and Architecting Multidisciplinary Systems. TBD: TBD.
Discussion
Discussion as to why this is the "consensus" definition for the SEBoK.