The Method Framework for Engineering System Architectures docx

© 2009 by Taylor & Francis Group, LLC The Method Framework for Engineering System Architectures © 2009 by Taylor & Francis Group, LLC AUERBACH PUBLICATIONS www.auerbach-publications.com To Order Call: 1-800-272-7737 • Fax: 1-800-374-3401 E-mail: orders@crcpress.com Optimizing Human Capital with a Strategic Project Office J. Kent Crawford and Jeannette Cabanis-Brewin 978-0-8493-5410-6 The Business Value of IT Michael D.S. Harris, David Herron, and Sasia Iwanicki 978-1-4200-6474-2 Best Practices in Business Technology Management Stephen J. Andriole 978-1-4200-633-2 Effective Software Maintenance and Evolution Stanislaw Jarzabek 978-0-8493-3592-1 Interpreting the CMMI ® , Second Edition Margaret Kulpa and Kent Johnson 978-1-4200-6502-2 Global Engineering Project Management M. Kemal Atesmen 978-1-4200-7393-5 Manage Software Testing Peter Farrell-Vinay 978-0-8493-9383-9 Programming Languages for Business Problem Solving Shouhong Wang and Hai Wang 978-1-4200-6264-9 Patterns for Performance and Operability Chris Ford, Ido Gileadi, Sanjiv Purba, and Mike Moerman 978-1-4200-5334-0 The Handbook of Mobile Middleware Paolo Bellavista and Antonio Corradi 978-0-8493-3833-5 Managing Global Development Risk James M. Hussey and Steven E. Hall 978-1-4200-5520-7 Implementing Electronic Document and Record Management Systems Azad Adam 978-0-8493-8059-4 Leading IT Projects: The IT Managers Guide Jessica Keyes 978-1-4200-7082-8 A Standard for Enterprise Project Management Michael S. Zambruski 978-1-4200-7245-7 The Art of Software Modeling Benjamin A. Lieberman 978-1-4200-4462-1 The Complete Project Management Office Handbook, Second Edition Gerard M. Hill 978-1-4200-4680-9 Building Software: A Practitioner's Guide Nikhilesh Krishanmurthy and Amitabh Saran 978-0-8493-7303-9 Software Engineering Foundations Yingxu Wang 978-0-8493-1931-0 Service Oriented Enterprises Setrag Knoshafian 978-0-8493-5360-4 Effective Communications for Project Management Ralph L. Kliem 978-1-4200-6246-5 Software Testing and Continuous Quality Improvement, Third Edition William E. Lewis 978-1-4200-8073-3 The ROI from Software Quality Khaled El Emam 978-0-8493-3298-2 Software Sizing, Estimation, and Risk Management Daniel D. Galorath and Michael W. Evans 978-0-8493-3593-8 Six Sigma Software Development, Second Edition Christine B. Tayntor 978-1-4200-4462-3 Elements of Compiler Design Alexander Meduna 978-1-4200-6323-3 Determining Project Requirements Hans Jonasson 978-1-4200-4502-4 Practical Guide to Project Planning Ricardo Viana Vargas 978-1-4200-4504-8 Service-Oriented Architecture James P. Lawler and H. Howell-Barber 978-1-4200-4500-0 Building a Project Work Breakdown Structure Dennis P. Miller 978-1-4200-6969-3 Building and Maintaining a Data Warehouse Fon Silvers 978-1-4200-6462-9 Other Auerbach Publications in Software Development, Software Engineering, and Project Management © 2009 by Taylor & Francis Group, LLC Donald G. Firesmith with Peter Capell Dietrich Falkenthal Charles B. Hammons DeWitt Latimer Tom Merendino The Method Framework for Engineering System Architectures AN AUERBACH BOOK CRC Press is an imprint of the Taylor & Francis Group, an informa business Boca Raton London New York © 2009 by Taylor & Francis Group, LLC Auerbach Publications Taylor & Francis Group 6000 Broken Sound Parkway NW, Suite 300 Boca Raton, FL 33487‑2742 © 2009 by Taylor & Francis Group, LLC Auerbach is an imprint of Taylor & Francis Group, an Informa business No claim to original U.S. Government works Printed in the United States of America on acid‑free paper 10 9 8 7 6 5 4 3 2 1 International Standard Book Number‑13: 978‑1‑4200‑8575‑4 (Hardcover) This book contains information obtained from authentic and highly regarded sources. Reasonable efforts have been made to publish reliable data and information, but the author and publisher cannot assume responsibility for the valid‑ ity of all materials or the consequences of their use. The authors and publishers have attempted to trace the copyright holders of all material reproduced in this publication and apologize to copyright holders if permission to publish in this form has not been obtained. If any copyright material has not been acknowledged please write and let us know so we may rectify in any future reprint. Except as permitted under U.S. Copyright Law, no part of this book may be reprinted, reproduced, transmitted, or uti‑ lized in any form by any electronic, mechanical, or other means, now known or hereafter invented, including photocopy‑ ing, microfilming, and recording, or in any information storage or retrieval system, without written permission from the publishers. For permission to photocopy or use material electronically from this work, please access www.copyright.com (http:// www.copyright.com/) or contact the Copyright Clearance Center, Inc. (CCC), 222 Rosewood Drive, Danvers, MA 01923, 978‑750‑8400. CCC is a not‑for‑profit organization that provides licenses and registration for a variety of users. For orga‑ nizations that have been granted a photocopy license by the CCC, a separate system of payment has been arranged. Trademark Notice: Product or corporate names may be trademarks or registered trademarks, and are used only for identification and explanation without intent to infringe. Library of Congress Cataloging‑in‑Publication Data The method framework for engineering system architectures / Donald G. Firesmith … [et al.]. p. cm. Includes bibliographical references and index. ISBN 978‑1‑4200‑8575‑4 (alk. paper) 1. Computer architecture. 2. System design. I. Firesmith, Donald G., 1952‑ QA76.9.A73M46 2008 004.2’2‑‑dc22 2008043271 Visit the Taylor & Francis Web site at http://www.taylorandfrancis.com and the Auerbach Web site at http://www.auerbach‑publications.com © 2009 by Taylor & Francis Group, LLC v Concise Table of Contents Preface xxvii 1 Introduction 1 2 System Architecture Engineering Challenges 13 3 System Architecture Engineering Principles 39 4 MFESA: An Overview 49 5 MFESA: e Ontology of Concepts and Terminology 81 6 Task 1: Plan and Resource the Architecture Engineering Effort 137 7 Task 2: Identify the Architectural Drivers 153 8 Task 3: Create the First Versions of the Most Important Architectural Models 171 9 Task 4: Identify Opportunities for the Reuse of Architectural Elements 191 10 Task 5: Create the Candidate Architectural Visions 205 11 Task 6: Analyze Reusable Components and eir Sources 219 12 Task 7: Select or Create the Most Suitable Architectural Vision 233 13 Task 8: Complete the Architecture and Its Representations 245 14 Task 9: Evaluate and Accept the Architecture 257 15 Task 10: Maintain the Architecture and Its Representations 279 16 MFESA Method Components: Architectural Workers 293 17 MFESA: e Metamethod for Creating Endeavor-Specific Methods 339 18 Architecture and Quality 355 19 Conclusions 397 © 2009 by Taylor & Francis Group, LLC vi  Concise Table of Contents Appendix A: Acronyms and Glossary 415 Appendix B: MFESA Method Components 431 Appendix C: List of Guidelines and Pitfalls 441 Appendix D: Decision-Making Techniques 449 Annotated References/Bibliography 459 © 2009 by Taylor & Francis Group, LLC vii Contents List of Figures xvii List of Tables xxi Foreword xxiii Preface xxvii 1 Introduction 1 1.1 To Begin … 1 1.2 Why is Book Is Needed 2 1.3 Why System Architecture Is Critical to Success 4 1.4 Why System Architecture Engineering Is Critical to Architecture 9 1.5 A Common System Architecture Engineering Method Is Insufficient 11 2 System Architecture Engineering Challenges 13 2.1 Introduction 13 2.2 General Systems Architecture Engineering Challenges 13 2.3 Challenges Observed in System Architecture Engineering Practice 23 2.3.1 Industry Has a Poor Architecture Engineering Track Record 24 2.3.2 Many Architecture Defects Are Found during Integration and Testing 24 2.3.3 Processes Are Inconsistent in Practice 25 2.3.4 Architectural Representations Are Often Missing, Incomplete, Incorrect, or Out of Date 25 2.3.5 Architectural Models Are Treated as the Sole Architectural Representations 26 2.3.6 Architectural Models Are Often Not Understandable 26 2.3.7 Architecture Engineering Underemphasizes Specialty Engineering Focus Areas 27 2.3.8 How Good Is “Good Enough”? 27 2.3.9 Because We Lack Sufficient Adequately Trained and Experienced Architects, ey Must Sometimes Perform Tasks for Which ey Are Unqualified 28 © 2009 by Taylor & Francis Group, LLC viii  Contents 2.3.10 Architects Use Multiple Inconsistent Architecture Engineering Methods 29 2.3.11 Architecture Engineering Methods Are Incompletely Documented 29 2.3.12 Architects Rely Too Much on Architectural Engineering Tools 29 2.3.13 e Connection between the Architecture and the Design It Drives Is Weak 30 2.4 Challenges Observed in Systems Architecture Engineering Methods 30 2.4.1 Current System Architecture Engineering Methods Are Incomplete 31 2.4.2 Current Methods Do Not Scale Up 31 2.4.3 Current Methods Assume “Greenfield” Development 31 2.4.4 Current Methods Overemphasize Architecture Development over Other Tasks 31 2.4.5 Current Methods Overemphasize Functional Decomposition for Logical Structures 32 2.4.6 Current Methods Overemphasize Physical Decomposition for Physical Structures 32 2.4.7 Current Methods Are Weak on Structure, View, and Focus Area Consistency 32 2.4.8 Current Methods Codify Old Processes 33 2.4.9 Current Methods Emphasize the Waterfall Development Cycle 33 2.4.10 Current Methods Confuse Requirements Engineering with Architecture Engineering 33 2.4.11 Current Methods Underemphasize Support for the Quality Characteristics 34 2.4.12 Current Methods Assume at “One Size Fits All” 35 2.4.13 Current Methods Produce Only a Single Architectural Vision 35 2.4.14 Current Methods Overly Rely on Local Interface Specifications 36 2.4.15 Current Methods Lack an Underlying Ontology 36 2.4.16 Current Methods Confuse Architecture and Architecture Representations 36 2.4.17 Current Methods Excessively Emphasize Architectural Models over Other Architectural Representations 36 2.4.18 Current Methods Overemphasize the Points of View of Different Types of Experts 37 2.5 Reasons for Improved Systems Architecture Engineering Methods 37 2.6 Summary of the Challenges 38 3 System Architecture Engineering Principles 39 3.1 e Importance of Principles 39 3.2 e Individual Principles 40 3.3 Summary of the Principles 47 4 MFESA: An Overview 49 4.1 e Need for MFESA 49 4.2 MFESA Goal and Objectives 51 4.3 What Is MFESA? 51 4.3.1 Ontology 52 © 2009 by Taylor & Francis Group, LLC Contents  ix 4.3.2 Metamodel 52 4.3.3 Repository 56 4.3.3.1 Method Components: Tasks 57 4.3.3.2 Method Components: Architectural Workers 60 4.3.4 Metamethod 61 4.4 Inputs 61 4.5 Outputs 66 4.6 Assumptions 66 4.6.1 e Number and Timing of System Architecture Engineering Processes 67 4.7 Relationships with Other Disciplines 67 4.7.1 Requirements Engineering 68 4.7.2 Design 71 4.7.3 Implementation 71 4.7.4 Integration 71 4.7.5 Testing 71 4.7.6 Quality Engineering 72 4.7.7 Process Engineering 72 4.7.8 Training 72 4.7.9 Project/Program Management 73 4.7.10 Configuration Management 73 4.7.11 Risk Management 74 4.7.12 Measurements and Metrics 74 4.7.13 Specialty Engineering Disciplines 75 4.8 Guidelines 76 4.9 Summary 78 4.9.1 MFESA Components 79 4.9.2 Goal and Objectives 79 4.9.3 Inputs 79 4.9.4 Tasks 79 4.9.5 Outputs 80 4.9.6 Assumptions 80 4.9.7 Other Disciplines 80 4.9.8 Guidelines 80 5 MFESA: e Ontology of Concepts and Terminology 81 5.1 e Need for Mastering Concepts and eir Ramifications 81 5.2 Systems 81 5.3 System Architecture 92 5.4 Architectural Structures 95 5.5 Architectural Styles, Patterns, and Mechanisms 100 5.6 Architectural Drivers and Concerns 102 5.7 Architectural Representations 106 5.8 Architectural Models, Views, and Focus Areas 109 5.9 Architecture Work Products 122 5.10 Architectural Visions and Vision Components 125 5.11 Guidelines 126 © 2009 by Taylor & Francis Group, LLC x  Contents 5.12 Pitfalls 131 5.13 Summary 135 6 Task 1: Plan and Resource the Architecture Engineering Effort 137 6.1 Introduction 137 6.2 Goal and Objectives 137 6.3 Preconditions 138 6.4 Inputs 138 6.5 Steps 140 6.6 Postconditions 141 6.7 Work Products 142 6.8 Guidelines 144 6.9 Pitfalls 146 6.10 Summary 151 6.10.1 Steps 151 6.10.2 Work Products 151 6.10.3 Guidelines 152 6.10.4 Pitfalls 152 7 Task 2: Identify the Architectural Drivers 153 7.1 Introduction 153 7.2 Goal and Objectives 153 7.3 Preconditions 154 7.4 Inputs 155 7.5 Steps 156 7.6 Postconditions 159 7.7 Work Products 159 7.8 Guidelines 160 7.9 Pitfalls 162 7.10 Summary 168 7.10.1 Steps 168 7.10.2 Work Products 168 7.10.3 Guidelines 169 7.10.4 Pitfalls 169 8 Task 3: Create the First Versions of the Most Important Architectural Models 171 8.1 Introduction 171 8.2 Goal and Objectives 173 8.3 Preconditions 174 8.4 Inputs 174 8.5 Steps 175 8.6 Postconditions 176 8.7 Work Products 177 8.8 Guidelines 177 8.9 Pitfalls 183 8.10 Summary 187 8.10.1 Steps 187 8.10.2 Work Products 188 [...]... well as the architecture of individual systems, their subsystems, and systems of systems Note that this book is about system architectures, not enterprise architectures It is also about software architectures to the extent that they are part of and significantly affect system architectures The following three terms and their definitions will help the reader understand the scope of this book: 1 System. .. And they also concurrently prepared for and developed the evidence that if the system were developed to the given architecture, it would support the operational concept, satisfy the requirements, and be buildable within the budgets and schedules in the plans Further, they checked the consistency of the interfaces of the elements so that if the developers complied with the interface specifications, the. .. architecture engineering method components† for creating methods for effectively and efficiently engineering high-quality architectures for software-intensive systems and their subsystems.‡ NN Provide a more complete look at system architecture engineering than that which is commonly seen in industry and academia NN Thereby open readers’ eyes to the very large scale of architecture engineering, including the. .. produce the stronger and more flexible architectures that our world is going to need Barry Boehm TRW Professor of Software Engineering Director of the Center for Systems and Software Engineering (CSSE) University of Southern California © 2009 by Taylor & Francis Group, LLC Preface Goals and Objectives The goals of this reference book are to: NN Document the Method Framework for Engineering System Architectures. .. scope of MFESA is the engineering of system (and by implication subsystem) architectures There are many books about enterprise architectures but this is not one of them, even 1 © 2009 by Taylor & Francis Group, LLC 2    The Method Framework for Engineering System Architectures though businesses, government, and military enterprises can be construed as extremely large systems Similarly, there are many... resulting quality of the system architecture and its representations, and the corresponding quality of the resulting system A good system architecture is critical to project success, and system architecture engineering is critical to engineering a good system architecture MFESA will help system architects use effective, efficient, and appropriate methods for engineering their system s architectures * A... Falkenthal (The MITRE Corp.) Charles B Hammons (SEI) DeWitt T Latimer IV (U.S Air Force) Tom Merendino (SEI) © 2009 by Taylor & Francis Group, LLC Chapter 1 Introduction 1.1  To Begin … This is the reference book for the Method Framework for Engineering System Architectures (MFESA), and as its name implies, MFESA helps system architects use system architecture engineering to create system architectures. .. primarily developed to produce methods for engineering the system architectures of software-intensive systems, it can also be used to engineer the software architectures of systems, their subsystems, and their software architectural components xxvii © 2009 by Taylor & Francis Group, LLC xxviii    Preface NN The components of the MFESA: −− A cohesive and consistent ontology defining the fundamental concepts... critical effect on the achievement of the system s performance and quality as well as the cost and schedule of the system s development and maintenance It is also becoming widely understood that the documented method used to engineer a system s architecture has a significant impact on the effectiveness and efficiency of the corresponding process performed to engineer the system s architecture, the resulting... and how they collaborate to meet the requirements) 2 System architecture engineering (SAE): the subdiscipline of systems engineering consisting of all architectural work units performed by architecture workers to develop and maintain architectural work products (including system or subsystem architectures and their representations) Note that system architecture engineering is part of system engineering . within the budgets and schedules in the plans. Further, they checked the consistency of the interfaces of the elements so that if the developers complied with the interface specifications, the. Hammons DeWitt Latimer Tom Merendino The Method Framework for Engineering System Architectures AN AUERBACH BOOK CRC Press is an imprint of the Taylor & Francis Group, an informa business Boca Raton. Observed in Systems Architecture Engineering Methods 30 2.4.1 Current System Architecture Engineering Methods Are Incomplete 31 2.4.2 Current Methods Do Not Scale Up 31 2.4.3 Current Methods Assume