Difference between revisions of "Architecting (glossary)"

From SEBoK
Jump to: navigation, 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.3, released 30 October 2020'''</center>" to "<center>'''SEBoK v. 2.4, released 17 May 2021'''</center>")
 
(27 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) ''Process of conceiving, defining, expressing, documenting, communicating, certifying proper implementation of, maintaining and improving an architecture throughout a system’s life cycle'' (ISO/IEC/IEEE 2011)</blockquote>
  
====Source====
+
<blockquote>(2) ''The architecting process sometime involves the use of heuristics to establish the form of architectural options before quantitative analyses can be applied. Heuristics are design principles learned from experience.'' (Rechtin 1990)</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) ISO/IEC/IEEE. 2011. Systems and software engineering - Architecture description. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE), ISO/IEC/IEEE 42010.
 +
 
 +
(2) Rechtin, E. 1990. ''Systems Architecting: Creating & Building Complex Systems.'' Upper Saddle River, NJ, USA: Prentice-Hall.
  
 
===Discussion===
 
===Discussion===
Discussion as to why this is the "consensus" definition for the SEBoK.
+
None.
  
 
[[Category:Glossary of Terms]]
 
[[Category:Glossary of Terms]]
 +
 +
<center>'''SEBoK v. 2.4, released 17 May 2021'''</center>

Latest revision as of 08:01, 6 May 2021

(1) Process of conceiving, defining, expressing, documenting, communicating, certifying proper implementation of, maintaining and improving an architecture throughout a system’s life cycle (ISO/IEC/IEEE 2011)

(2) The architecting process sometime involves the use of heuristics to establish the form of architectural options before quantitative analyses can be applied. Heuristics are design principles learned from experience. (Rechtin 1990)

Source

(1) ISO/IEC/IEEE. 2011. Systems and software engineering - Architecture description. Geneva, Switzerland: International Organization for Standardization (ISO)/International Electrotechnical Commission (IEC)/Institute of Electrical and Electronics Engineers (IEEE), ISO/IEC/IEEE 42010.

(2) Rechtin, E. 1990. Systems Architecting: Creating & Building Complex Systems. Upper Saddle River, NJ, USA: Prentice-Hall.

Discussion

None.

SEBoK v. 2.4, released 17 May 2021