Difference between revisions of "Architecting (glossary)"
Line 1: | Line 1: | ||
− | <blockquote>(1) ''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) | + | <blockquote>(1) ''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)</blockquote>'' |
− | <blockquote>(2) ''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>(2) ''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==== | ||
− | (1)ANSI/IEEE. 2000. [[IEEE 1471 |''Recommended practice for architectural description for software-intensive systems'']]. New York, NY: American National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers (IEEE), ANSI/IEEE 1471-2000. | + | (1) ANSI/IEEE. 2000. [[IEEE 1471 |''Recommended practice for architectural description for software-intensive systems'']]. New York, NY: American National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers (IEEE), ANSI/IEEE 1471-2000. |
(2) Rechtin, E. 1990. ''Systems Architecting: Creating & Building Complex Systems.'' Upper Saddle River, NJ, USA: Prentice-Hall. | (2) Rechtin, E. 1990. ''Systems Architecting: Creating & Building Complex Systems.'' Upper Saddle River, NJ, USA: Prentice-Hall. |
Revision as of 16:52, 11 September 2012
(1) 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)
(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) ANSI/IEEE. 2000. Recommended practice for architectural description for software-intensive systems. New York, NY: American National Standards Institute (ANSI)/Institute of Electrical and Electronics Engineers (IEEE), ANSI/IEEE 1471-2000.
(2) Rechtin, E. 1990. Systems Architecting: Creating & Building Complex Systems. Upper Saddle River, NJ, USA: Prentice-Hall.
Discussion
None.
SEBoK Discussion
Please provide your comments and feedback on the SEBoK below. You will need to log in to DISQUS using an existing account (e.g. Yahoo, Google, Facebook, Twitter, etc.) or create a DISQUS account. Simply type your comment in the text field below and DISQUS will guide you through the login or registration steps. Feedback will be archived and used for future updates to the SEBoK. If you provided a comment that is no longer listed, that comment has been adjudicated. You can view adjudication for comments submitted prior to SEBoK v. 1.0 at SEBoK Review and Adjudication. Later comments are addressed and changes are summarized in the Letter from the Editor and Acknowledgements and Release History.
If you would like to provide edits on this article, recommend new content, or make comments on the SEBoK as a whole, please see the SEBoK Sandbox.
blog comments powered by Disqus