Difference between revisions of "Architecting (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>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).</blockquote>'' |
====Source==== | ====Source==== | ||
| − | + | Rechtin,E. 1990. Systems architecting: Creating & building complex systems. Upper Saddle River, NJ, USA: Prentice-Hall. | |
===Discussion=== | ===Discussion=== | ||
Revision as of 01:05, 17 May 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
Discussion as to why this is the "consensus" definition for the SEBoK.