Difference between revisions of "Functional Architecture (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>An arrangement of functions and their sub-functions and interfaces (internal and external) which defines the execution sequencing, conditions for control or data-flow and the performance requirements to satisfy the requirements baseline. (ISO/IEC 2007)</blockquote>'' |
====Source==== | ====Source==== | ||
| − | + | ISO/IEEE. 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 17:48, 17 May 2011
An arrangement of functions and their sub-functions and interfaces (internal and external) which defines the execution sequencing, conditions for control or data-flow and the performance requirements to satisfy the requirements baseline. (ISO/IEC 2007)
Source
ISO/IEEE. 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.