DocumentCode
1143334
Title
Architectural Organizational Patterns
Author
Booch, Grady
Volume
25
Issue
3
fYear
2008
Firstpage
18
Lastpage
19
Abstract
To set the context for the discussion that follows, there are some fundamentals worth repeating. The author talked about each of these to some degree in previous columns, so let me summarize here: 1) all architecture is design, but not all design is architecture. A system\´s architecture is defined by its significant design decisions, where in the author\´s experience, "significant" is measured by the cost of change. 2) Most architectures are accidental; some are intentional. 3) Every software-intensive system has an architecture, forged from the hundreds of thousands of small decisions made every day. 4) The code is the truth, but not the whole truth. Most architectural information is preserved in tribal memory. 5) All well-structured software-intensive systems are full of patterns.
Keywords
object-oriented programming; software architecture; architectural organizational patterns; design decisions; software-intensive system; tribal memory; Books; Costs; Design engineering; Process control; Product design; architectural patterns; organizational pattern; risk confrontation;
fLanguage
English
Journal_Title
Software, IEEE
Publisher
ieee
ISSN
0740-7459
Type
jour
DOI
10.1109/MS.2008.56
Filename
4497757
Link To Document