Difference between revisions of "Physical Architecture (glossary)"

From SEBoK
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 ...')
 
m (Text replacement - "<center>'''SEBoK v. 2.6, released 13 May 2022'''</center>" to "<center>'''SEBoK v. 2.6, released 20 May 2022'''</center>")
 
(31 intermediate revisions by 10 users not shown)
Line 1: Line 1:
''<blockquote>A comprehensive, integrated plan that identifies the acquisition approach and describes the business, technical, and support strategies that management will follow to manage program risks and meet program objectives. The Acquisition Strategy should define the relationship between the acquisition phases and work efforts, and key program events such as decision points, reviews, contract awards, test activities, production lot/delivery quantities, and operational deployment objectives. (DAU February 19, 2010)</blockquote>''
+
<blockquote>(1) ''A physical architecture is an arrangement of physical elements (system elements and physical interfaces) which provides the design solution for a product, service, or enterprise, and is intended to satisfy logical architecture elements and system requirements. It is implementable through technologies.'' (ISO/IEC 2010)</blockquote>
  
====Source====
+
<blockquote>(2) ''An arrangement of physical elements which provides the design solution for a consumer product or life-cycle process intended to satisfy the requirements of the functional architecture and the requirement baseline.'' (ISO/IEC 2007)</blockquote>
DAU. February 19, 2010. ''Defense Acquisition Guidebook (DAG)''. Ft. Belvoir, VA, USA: Defense Acquisition University (DAU)/U.S. Department of Defense (DoD).  
+
 
 +
===Source===
 +
(1) Adapted from ISO/IEC. 2010. ''Systems and Software Engineering, Part 1: Guide for Life Cycle Management''. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 24748-1:2010.
 +
 
 +
(2) 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 FDIS 42010:2007.  
  
 
===Discussion===
 
===Discussion===
Discussion as to why this is the "consensus" definition for the SEBoK.
+
Definition (1) comes from the terms "design architecture" provided in ISO/IEC/IEEE 24748 - 4. It is adapted here to be consistent current terminology, in particular with [[Logical Architecture (glossary) |logical architecture]].
 +
 
 +
Definition (2) comes from ISO/IEC/IEEE 42010:2007 that is replaced by version 2011 in which this definition has been withdrawn.
 +
 
 +
For a full discussion of the role and importance of physical architecture in systems engineering see the [[Physical Architecture Model Development]] article.
 +
 
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
 +
 +
<center>'''SEBoK v. 2.6, released 20 May 2022'''</center>

Latest revision as of 19:30, 19 May 2022

(1) A physical architecture is an arrangement of physical elements (system elements and physical interfaces) which provides the design solution for a product, service, or enterprise, and is intended to satisfy logical architecture elements and system requirements. It is implementable through technologies. (ISO/IEC 2010)

(2) An arrangement of physical elements which provides the design solution for a consumer product or life-cycle process intended to satisfy the requirements of the functional architecture and the requirement baseline. (ISO/IEC 2007)

Source

(1) Adapted from ISO/IEC. 2010. Systems and Software Engineering, Part 1: Guide for Life Cycle Management. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC), ISO/IEC 24748-1:2010.

(2) 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 FDIS 42010:2007.

Discussion

Definition (1) comes from the terms "design architecture" provided in ISO/IEC/IEEE 24748 - 4. It is adapted here to be consistent current terminology, in particular with logical architecture.

Definition (2) comes from ISO/IEC/IEEE 42010:2007 that is replaced by version 2011 in which this definition has been withdrawn.

For a full discussion of the role and importance of physical architecture in systems engineering see the Physical Architecture Model Development article.

SEBoK v. 2.6, released 20 May 2022