Integrating System Architecture & Engineering Applications Using Open Systems

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

2. Individual System Focus System-of-Systems Focus Boundary Interactions Interfaces Modules Boundaries System-of-Systems Architecture Increasingly, architectures are used as basis for programmatic decisionsThis increases importance of their consistency, precision and scalability 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

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

4. System-of-systems engineering requires • Greater collaboration and tool interoperability, and … • Using robust modeling techniques for describing systems architectures Request System Model Response 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

5. System-of-systems engineering requires • Greater collaboration and tool interoperability, and … • Using robust modeling techniques for describing systems architectures Request System Model Response 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

6. 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 www.exff.org/ap233 Web site • 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

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

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

9. Contact Information • David Price • david.price@eurostep.com • +44 20 7221 7307 • exff Systems Engineering • http://www.exff.org/ap233 • AP233 • NASA AP233 Page at http://step.jpl.nasa.gov/AP233/ • DoDAF • DoD NII Archive at http://www.defenselink.mil/nii/doc • SysML • SysML Partners Page at http://www.sysml.org • OMG SysEng SIG at http://syseng.omg.org/ • The International Council on Systems Engineering • INCOSE at http://www.incose.org