PivotPoint FAQ: What is Agile MBSE™?

Agile MBSE™ Process Features

It is essential that an Agile MBSE Process approach strives to meet or exceed the following goals:

Architecture-Centric Agile MBSE Process Features

• Architecture-centric: The Agile MBSE process must emphasize a precise and complete System-of-Systems Architecture Model (SSADM) as the primary work artifact throughout the System Development Life Cycle (SDLC). i.e., SAM = system architecture "truth" (cf. Agile Manifesto). The SSADM should be organized using an scalable and simulatable Enterprise Architecture Framework (EAF; see below);
• Pattern- & framework-based for reuse: The Agile MBSE process must be based on proven pragmatic Requirement Analysis, System Analysis, System Design and Architecture patterns that ensure system architecture integrity and consistency, and promote reuse within and across enterprise system models. These simulatable architectural "patterns-of-patterns" constitute a bona fide Executable Enterprise Architecture Framework (EAF; e.g., ISO/IEC 42010, DoDAF, TOGAF) with multiple Views/Viewpoints for the various system stakeoholders. An excellent example of an EAF designed to support Agile MBSE is PivotPoint's Agile MBSE 6D EAF.
• Support full SDLC with rigorous V&V: The Agile MBSE process must provide comprehensive support of all SDLC phases (Requirements, System Analysis, System Design, Implementation, System Integration &Testing);
• Requirements-driven: All System Analysis, System Design, and Implementation elements on the "Left Side" of the System V-Model must directly or indirectly trace to System Functional and Non-Functional Requirements;
• Test-driven: All System Test Cases on the "Right Side" of the System V-Model must exhaustively test the System Design and Implementation using "black-box" and "white-box" Test Cases at the Unit, Integration, and System levels;
• Scalable: The Agile MBSE Process must scale recursively to accommodate Systems-of-Systems of arbitrary complexity;
• Simulatable: The Agile MBSE process must be capable must be capable of Dynamic Simulation (a.k.a. Dynamic System Simulation) of all SysML Behavior diagrams (Activities, Sequences, State Machines) and Mathematical Modeling & Simulation (a.k.a. Mathematical ModSim, Mathematical M&S, Parametric Simulation) of all Parametric diagrams;
• Integrate SE & Agile MBSE best practices: The Agile MBSE process must be capable of enhancing proven traditional Systems Engineering best practices and integrating them with evolving Agile MBSE best practices.

Agile MBSE Process Features

• Quick, Regular Process Cadence: Short iterative, incremental Agile "Sprints" allow System-of-Systems Architecture & Design work artifacts to adapt to changing business and mission Requirements;
• Proactive Testing: Test Cases are continuously refined to identify problems early in SDLC, especially Test Cases for Software Components;
• Frequent Peer-to-Peer Reviews: Frequent personal interactions and informal peer-to-peer reviews streamline communications and reduce misunderstandings.

In addition, it is desirable that an Agile MBSE Process achieves the following goals:

• Straightforward & systematic: The Agile MBSE process should be explained in a straightforward and systematic manner, so that it is easy for Systems Engineers to learn and apply;
• Promote the use of open standards: The Agile MBSE process should support open standards for system architecture modeling and tool interoperability. These open standards include, but are not limited to SysML, UML 2, XMI, and AP233. These open standards should be used to specify the System-of-Systems Architecture & Design Model (SSADM) and to serve as a lingua franca among Systems Engineers and other stakeholders (Software Engineers, Electrical Engineers, Mechanical Engineers, Customers, etc.).