® Integrating System Architecture & Engineering Applications Using Open Systems David Price OSJTF SoS Architecture Modeling Meeting September 22, 2005

® SoSs typical characteristics: Not managed or funded under a singular authority Composed of complex systems that provide independent functionality Hard to bound Distributed over time and space Dynamically assembled, ‘on-the-fly’ by operational commanders Compete with other SoSs for the same resources Relatively short lifecycle, compared to traditional systems System-of-Systems FocusIndividual System Focus Boundaries Interactions Modules Interfaces Boundary System-of-Systems Architecture Increasingly, architectures are used as basis for programmatic decisions This increases importance of their consistency, precision and scalability

® System BSystem A Collaborative System-of-Systems Engineering Modules Interfaces Boundary Boundaries Modules Interfaces System-of-systems engineering requires: Use of robust modeling techniques for describing systems architectures And, Greater collaboration and tool interoperability Request Response System Model

® Our Focus is on SE Standards Enable communication between SEs and the tools they use –Approach described in white paper : Using Systems Engineering Standards In an Architecture Framework –Influenced by DoD, INCOSE, ISO STEP and OMG communities System-of-systems engineering requires Greater collaboration and tool interoperability, and … Using robust modeling techniques for describing systems architectures Request Response System Model

® Standards and SE data DoDAF - DoD Architecture Framework –Defines standardized views of systems information –CADM = Core Architecture Data Model INCOSE - International Council on Systems Engineering –Model-Driven System Design Working Group Model-Driven SE Semantic Dictionary and Concept Model Group work results in SysML/AP233 and alignment activity SysML - from Object Management Group –Provide a standard modelling language and notation for systems engineers AP233 Systems Engineering - ISO –Defines a neutral information model for complex systems engineering structures

® DoDAF System-of-systems engineering requires Greater collaboration and tool interoperability, and … Using robust modeling techniques for describing systems architectures Request Response System Model DoDAF tells SEs what kinds of models to create DoDAF does not require a specific tool or notation IDEF, UML, etc. all OK Some SE tools are tailored for DoDAF support Is a US DOD standard

® SysML System-of-systems engineering requires Greater collaboration and tool interoperability, and … Using robust modeling techniques for describing systems architectures Request Response System Model SysML is OMG standard language and notation for SEs to use SE tools will implement and conform to SysML SEs will understand SysML concepts and terminology SysML can be used by SEs to create systems architectures following DODAF

® AP233 Systems Engineering AP233 = ISO standard specifying communications pipeline between Systems Engineering tools and databases Designed to be neutral vs DODAF, MODAF, SysML, UML, IDEF, other SE tools, … which are more specific As part of ISO STEP series, AP233 links to standards with a vast scope –AP stands for “Application Protocol” APs are very formal and strict – intended to prevent ambiguity in data exchange APs define the types of data to be exchanged and the structure of that data –There are 40+ STEP Application Protocols –AP233, like all new modular APs, is built from reusable information model “modules” for compatibility across application domains System-of-systems engineering requires Greater collaboration and tool interoperability, and … Using robust modeling techniques for describing systems architectures Request Response System Model

® DoDAF CADM/AP233 Project Purpose –Evaluate feasibility of system architecture data exchange using emerging ISO AP233 Systems Engineering standard Not a fully validated design effort –Provide a body of work that future efforts can build upon Phase 1 and 1a Scope –SV-1, SV-2, SV-3, SV-4, SV-10b, OV-5, OV-6b, TV-1 subset –Delivered via Web sitewww.exff.org/ap233 Phase 2 includes all remaining products –Plus AP233 High Level API –Plus Extras such as: SysML/AP233 State Machine translation specification SysML Requirement/Systems Allocation demo

® AP233 Scope requirements text-based property-based breakdowns static structure PDM analysis rules behaviour product structure system sub-system functional breakdown WBS verification & validation function-based model presentation config control security risk measurement person & org completed future work Legend state-based

® Proving this path

® Implemented by Tools Modeling Methods SADTHPOOSEOther Interchange Standards MOF/XMISTEP/AP-233 Other Architecture Frameworks FEAF Zachman FW DoDAFMoDAF Modeling & Simulation Standards UML/SysMLIDEF0OtherHLA ModelingSimulation Process Standards EIA 632 CMMI * ISO IEEE 1220 Context Diagram for Systems Engineering Standards DoDAF UML/SysML MOF/XMI CADM STEP/AP-233 This shows only one thread through these standards, others are necessary as well.

® Request Response System Model DoD Architecture Repository System DOD CADM Operational Systems Technical DODAF Any SE Tool specifies requirements for ISO STEP-enabled Downstream Tool

® Request Response System Model Demo : Executable Architectures Create Activity Breakdown in MindMap Tool OV-6b Build State Machine (UML) Transfer to UML Tool Thru AP233 Pipeline OV-5 Operational Activity Model (UML) Transfer to Simulator Thru AP233 Pipeline Simulation Tool (SVM)

® Contact Information David Price – –exff Systems Engineering AP233 –NASA AP233 Page at DoDAF –DoD NII Archive at SysML –SysML Partners Page at –OMG SysEng SIG at The International Council on Systems Engineering –INCOSE at