Chapter 2

Chapter 2 - Chapter 2. MBSAP Methodology Overview John M....

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
2-1 Chapter 2. MBSAP Methodology Overview John M. Borky Copyright 2009-2010. All rights reserved. No portion of this document may be reproduced or distributed without the consent of the author.
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2-2 Chapter 2. MBSAP Methodology Overview "Tho’ this be madness, yet there’s method in’t.” Shakespeare Basic Principles In this and the next several chapters, we describe the MBSAP methodology that is the heart of our approach to architecture. First, we introduce the structure and activities of the methodology as a whole, then, in subsequent chapters, focus on the details of the succes- sive stages of the process. We have evolved our approach by drawing on best practices of the system engineering and architecture communities and on lessons learned in a number of earlier architecture development efforts. Many of the individual elements of MBSAP have been developed, used, and published by various workers. * The contribution to the field that this book seeks to make is the adaptation and integration of carefully selected concepts and methods into a coherent and comprehensive architecture strategy. Although the discussion frequently refers to “system architecture” and “system engineering,” it should be understood that MBSAP applies to any complex, information-intensive entity, including an enterprise combining multiple nodes and systems. In tackling information system challenges, it quickly becomes apparent that architec- ture and system engineering are inseparable. Indeed, we take the position that system en- gineering (SE) processes for systems and enterprises like those of interest in this book must be rooted in architecture. SE is concerned with things like requirements analysis and allocation; trade studies involving performance, cost, schedule and supportability; risk management; integration and test; configuration management; and other aspects of achieving an optimized and operationally satisfactory mission solution. Architecture fur- nishes the central organizing principle for these SE activities because it is the authorita- tive representation of the system or enterprise design at any point in time. Architecture models provide the subject matter for trade studies, configuration management, timing and performance assessment, resource load balancing, safety analysis, and a host of other SE tasks. This concept of architecture-centric (also widely referred to as model-driven) SE represents a profound change from traditional thinking in which architecture was usually treated as simply an artifact produced by SE, often consisting of little more than block diagrams of the final design. Today, it is widely realized that architecture is the heart of the development process and that it is critical to all phases of translating custom- er requirements into effective solutions.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 21

Chapter 2 - Chapter 2. MBSAP Methodology Overview John M....

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online