Difference between revisions of "Architecting (glossary)"
Wikiexpert (talk | contribs) m (Removed protection from "architecting ") |
m (Text replacement - "<center>'''SEBoK v. 2.2, released 15 May 2020'''</center>" to "<center>'''SEBoK v. 2.3, released 30 October 2020'''</center>") |
||
(18 intermediate revisions by 8 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> | |
− | Rechtin, E. 1990. ''Systems Architecting: Creating & Building Complex Systems.'' Upper Saddle River, NJ, USA: Prentice-Hall. | + | |
+ | ===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.3, released 30 October 2020'''</center> | |
− |
Revision as of 12:35, 25 September 2020
(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.