MBSAP Methodology Overview

Abstract

In this chapter, we introduce and summarize the MBSAP methodology that is the core topic of the book. First, we present the basic principles on which the methodology is based, expanding the discussion of MBSE from Chaps. 1 and 2, and we relate our approach to traditional Systems Engineering (SE) constructs such as the “Vee” diagram that is familiar to generations of system engineers. We expand on the key aspects of transitioning from a traditional document-centric approach to one that is model-centric, and we emphasize the fact that MBSE using MBSAP is not a fundamentally different SE process. Next, we give a high-level overview of MBSAP, and we summarize the flow of the methodology from initial requirements analysis and conceptual thinking to a final physical system implementation, following the levels of abstraction defined in the architecture taxonomy in Chap. 1. We address the crucial subject of model structure and present the Viewpoints and Perspectives that together provide the organizing principles of MBSAP. Many such structures are possible, but our experience is that the organization shown here delivers consistently good results across a wide range of system categories. Because of the importance of system stakeholders in determining the success or failure of a system development, we provide a discussion of the essentials of stakeholder interaction, especially using the architecture as a tool for dialog and analysis. We then introduce a hierarchy of modeling and simulation as an integral element of architecture development and refinement. We discuss the reality that architecture development is often constrained by the need to conform to customer policies and mandates, and we lay out a set of preliminary activities that are essential preparation for an effective architecture effort. Finally, we complete this introduction to MBSAP by reviewing a number of alternative methodologies and showing that to a great extent, MBSAP is consistent with them while stressing a rigorous succession of architecting activities with defined artifacts and metrics. Chapter objective: the reader will be able to describe the fundamental motivation for MBSE, its benefits when applied to a general SE process, and the background, goals, scope, products, and overall process of the MBSAP methodology, including stakeholder interactions.