| |
| |
| Foreword | |
| |
| |
| Preface | |
| |
| |
| |
| Simple Analogy | |
| |
| |
| The Perfect Analogy. Finally, a Cognitive Map | |
| |
| |
| The Analogy Reveals the Missing Ingredient Architecture | |
| |
| |
| The Analogy Confers Clarity of Role and Purpose | |
| |
| |
| It All Begins with a Client and an Architect | |
| |
| |
| With the Analogy, Words Are Meaningful | |
| |
| |
| With the Analogy, Processes Are Predictable | |
| |
| |
| The Analogy Brings Order to Complexity and Flexibility. Conclusion | |
| |
| |
| |
| World Without Architects | |
| |
| |
| The Paradox of the Software Industry | |
| |
| |
| The March of the Notorious | |
| |
| |
| The Federal Aviation Administration | |
| |
| |
| Internal Revenue Service Tax System Modernization (TSM) | |
| |
| |
| Conclusion | |
| |
| |
| |
| What Is Architecture? Technology: The Common Thread of Architecture | |
| |
| |
| Many Definitions of the Indefinable. Utilitas, Venustas, Firmitas | |
| |
| |
| The Mystery of Design. The Lesson of St. Peter's: Harmony and Unity | |
| |
| |
| The Quality Without a Name. Conclusion | |
| |
| |
| |
| A Pithy History of Architecture | |
| |
| |
| The Greek Ideal | |
| |
| |
| Architects: Anonymous Craftsmen and Superstars | |
| |
| |
| Modern Architecture: Rise and Demise | |
| |
| |
| The Architect as Social Philosopher | |
| |
| |
| Architecture and the Third Wave. Conclusion | |
| |
| |
| |
| The Roles of Software Construction | |
| |
| |
| Architect, Builder, Engineer, Scientist. Guiding Principles | |
| |
| |
| Software Architects Decide How the Structure Will Look and Act | |
| |
| |
| Software Engineers Make the Structure Sound | |
| |
| |
| Developers Build the Structure | |
| |
| |
| Computer Scientists Further Knowledge | |
| |
| |
| The Role of the Client | |
| |
| |
| Defining, Not Limiting. An Indelicate, but Trenchant, Illustration of the Roles of Construction. Conclusion | |
| |
| |
| |
| The Role of the Software Architect | |
| |
| |
| The Role of the Architect Begins with the Client | |
| |
| |
| The Architect as Client Advocate and Design Champion | |
| |
| |
| The Art of Listening. The Art of Observation | |
| |
| |
| The Art of Strategy | |
| |
| |
| The Pyramid in Paris | |
| |
| |
| Conclusion | |
| |
| |
| |
| The Phases of Architecture-Driven Software Construction | |
| |
| |
| Two Overall Phases. Architectural Phases, with Caveats | |
| |
| |
| The Design Is Not the Deliverable. Caution: These Design Phases Are Not Linear | |
| |
| |
| The Building Phases. Conclusion: The Party Phase | |
| |
| |
| |
| The Architectural Plan | |
| |
| |
| The Characteristics of an Architectural Plan | |
| |
| |
| Good Architects, Good Plans | |
| |
| |
| Why Have Plans at All? The Levels of the Plan | |
| |
| |
| Conclusion | |
| |
| |
| |
| Educating Software Architects. Second Wave Education, Third Wave Needs | |
| |
| |
| Still Another Crisis | |
| |
| |
| We Are What We Do. What Is the Profile of a Computer Scientist? | |
| |
| |
| Architecture Education. Establishing Software Architecture Education | |
| |
| |
| Can Design Be Taught? | |
| |
| |
| Conclusion | |
| |
| |
| |
| Venturing to Call Ourselves Architects | |
| |
| |
| What Is a Profession? Client Expectations | |
| |
| |
| A Standard Body of Knowledge | |
| |
| |
| Education. Identity | |
| |
| |
| A Code of Ethics and Standards | |
| |
| |
| Where to Begin | |
| |
| |
| Index | |