A Combat Support Agency Defense Information Systems Agency

A Combat Support Agency Defense Information Systems Agency A Combat Support Agency Model Based Systems Engineering and Systems Modeling Language Do. DAF Plenary January 5, 2012 Chris Gedo Chief, Architecture Branch Enterprise Engineering Directorate christopher. n. gedo 2. civ@mail. mil

Overview A Combat Support Agency • Motivation • Model Based Systems Engineering (MBSE) Overview • Architecting with MBSE • Systems Modeling Language (Sys. ML) relationship to the Do. D Architecture Framework (Do. DAF) • DISA’s transition to MBSE & Sys. ML 2

Motivation A Combat Support Agency • Develop an integrated architecture for critical portions of the Global Information Grid (GIG) – Comprehensive • Includes all essential capabilities • Applies to all Do. D Components – Based on rigorous Systems Engineering principles • Such as those espoused by Do. D 5000, INCOSE, etc. • Traditional development practices have not produced the desired results for complex, large scale IT problems – Current artifacts do not routinely address critical analysis details • Imprecise descriptions lead to different interpretations of the artifacts – Focus is on generating artifacts rather than the underlying data • Improved techniques could facilitate better analysis We Need to Understand How Systems Work 3

MBSE Overview A Combat Support Agency • Models use common data sets – Provides a consistent view of the architecture – Can lead directly to system specifications & test plans – Reduces systems integration and testing risks – Promotes traceability – Makes it possible to identify gaps and overlaps – Facilitates model reuse and integration • Uses a standards-based modeling language – Defines architectures that can be simulated with standard tools – Models can be used with many standards compliant automation tools Integrated Architectural Model Requirements Structure • Automation tools are used to generate artifacts – Less labor intensive to generate & update http: //www. incose. org/Products. Pubs/products/sevision 2020. aspx Behavior Parametric 4

Architecting With Model Based Systems Engineering (MBSE) A Combat Support Agency • Use existing, proven architecting process • Create models rather than developing documents • Use automation tools to generate routine artifacts directly from the models • Sys. ML provides 9 different types of diagrams to represent the architecture, which can be used to develop solutions • • • 4 behavioral 4 Structural 1 Cross-Cutting 5

Systems Modeling Language A Combat Support Agency http: //www. omg. org/cgi-bin/doc? dtc/2001 -07 -02 • International Council on Systems Engineering (INCOSE) defined the Unified Modeling Language (UML) for Systems Engineering strategy in January 2001 • INCOSE partnered with the Object Management Group (OMG) in July 2001 to develop the language • OMG published Systems Modeling Language (Sys. ML) version 1. 0 specification in June 2006 • Sys. ML v 1. 0 specification defines 9 types of diagrams that map directly to Do. DAF models • Reports can be generated from the Sys. ML models that are consistent with Do. DAF matrix artifacts 6

Sys. ML Relationship to Do. DAF http: //www. omg. org/cgi-bin/doc? dtc/2001 -07 -02 A Combat Support Agency • 26 Do. DAF models map directly to the 9 Sys. ML diagram types – Do. DAF models are indicated in the red text below • 26 Do. DAF matrix artifacts (e. g. , TV-1) are reports that can be generated directly from Sys. ML models OV-1, DIVs OV-2, 4, 5 a SV-1, 2, CVs, SOV-1, 2 [15] OV-2, EV-2, SV-2 [3] Cross-Cutting Diagrams Structural Diagrams Internal Block Diagram [IBD] Block Definition Diagram [BDD] Package Diagram [PKG] Parametric Diagram [PD] View (OV, SV) Containers Sys. ML Diagrams Requirements Diagram [REQ] SV-7 [1] OV-6 b SV-10 b [3] OV-5 b SV-4, SOV-5 [3] Behavioral Diagrams Use Case Diagram [UC] Activity Diagram [AD] State Machine Diagram [SMD] Sequence Diagram [SD] OV-6 c SV-10 c [3] 7

Do. DAF Data Elements A Combat Support Agency • Do. DAF Meta. Model (DM 2) defines Do. DAF data elements and the relationships among them • The Unified Profile for Do. DAF/MODAF (UPDM) is a Sys. ML profile that makes it possible to develop Sys. ML models using Do. DAF or MODAF terminology – UPDM Domain Metamodel (DMM) defines UPDM elements and the relationships among them – UPDM includes an element by element mapping between DM 2 and the UPDM DMM * Do. DAF-DM 2 Term UPDM Profile element *Sample Mapping from UPDM Spec activity. Part. Of. Capability Activity. Part. Of. Capability activity. Part. Of. Project. Type Activity. Part. Of. Project activity. Performable. Under. Condition instance of a Measure Actual. Measurement Organization Actual. Organization port. Part. Of. Performer Implicit in Sys. ML activity. Consumes. Resource Conveyed tag on System and Function. Edges, implicit through direction 8

DISA’s Transition to MBSE A Combat Support Agency • Actions to date – Trained the Enterprise Engineering staff on MBSE/Sys. ML – Updating our internal systems engineering processes – Developing a common data structure so that models representing individual capabilities can be integrated – Developed a standard template for documenting DISA capabilities – Completed initial set of pilot projects to produce models & Sys. ML artifacts for the 2012 version of the GIG Convergence Master Plan (GCMP) • Planned actions – – Transition remaining DISA programs & projects Update future versions of the GCMP with Sys. ML artifacts Continue training DISA & Do. D personnel Develop all new capabilities using MBSE 9

A Combat Support Agency Questions? Thank you for your attention 10

www. disa. mil