Sign up & Download
Sign in

Architectural Organizational Patterns

by G Booch
IEEE Software (2008)

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.

Cite this document (BETA)

Sign up today - FREE

Mendeley saves you time finding and organizing research. Learn more

  • All your research in one place
  • Add and import papers easily
  • Access it anywhere, anytime

Start using Mendeley in seconds!

Already have an account? Sign in

Readership Statistics

9 Readers on Mendeley
by Discipline
 
 
by Academic Status
 
33% Ph.D. Student
 
22% Student (Master)
 
11% Post Doc
by Country
 
22% United States
 
22% Brazil
 
11% Germany