Difference between revisions of "Architecting (glossary)"
(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 - "SEBoK v. 2.9, released 20 November 2023" to "SEBoK v. 2.10, released 06 May 2024") |
||
| (35 intermediate revisions by 11 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <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> | |
| − | + | <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> | |
| − | + | ||
| + | ===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=== | ||
| − | + | None. | |
[[Category:Glossary of Terms]] | [[Category:Glossary of Terms]] | ||
| + | |||
| + | <center>'''SEBoK v. 2.10, released 06 May 2024'''</center> | ||
Latest revision as of 21:54, 2 May 2024
(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.