Difference between revisions of "Architecting (glossary)"

From SEBoK
Jump to: navigation, search
Line 1: Line 1:
''<blockquote>The activities of defining, documenting, maintaining, improving, and certifying proper implementation of an architecture (IEEE 1471-2000 IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, 3.3). The architecting [[Process (glossary)|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>''
+
''<blockquote>The activities of defining, documenting, maintaining, improving, and certifying proper implementation of an [[Architecture (glossary)|architecture]] (IEEE 1471-2000 IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, 3.3). The architecting [[Process (glossary)|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>''
  
 
====Source====
 
====Source====

Revision as of 17:33, 16 September 2011

The activities of defining, documenting, maintaining, improving, and certifying proper implementation of an architecture (IEEE 1471-2000 IEEE Recommended Practice for Architectural Description of Software-Intensive Systems, 3.3). 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

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

Discussion

There is currently no discussion for this term. This will be completed for SEBoK version 1.0.