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

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

Dec 17, 2015

Download

Documents

Randell Hodges
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: ® Integrating System Architecture & Engineering Applications Using Open Systems David Price OSJTF SoS Architecture Modeling Meeting September 22, 2005.

®

Integrating System Architecture & Engineering

Applications Using Open Systems

David PriceOSJTF SoS Architecture Modeling

MeetingSeptember 22, 2005

Page 2: ® 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 Focus Individual System Focus

Boundaries

Interactions

Modules Interfaces

Boundary

System-of-Systems Architecture

Increasingly, architectures are used as basis for programmatic decisionsThis increases importance of their consistency, precision and scalability

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

®

System BSystem A

Collaborative System-of-Systems Engineering

Modules Interfaces

BoundaryBoundaries

Modules Interfaces

System-of-systems engineering requires: • Use of robust modeling techniques for describing systems architectures • And, Greater collaboration and tool interoperability

Request

Response

SystemModel

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

®

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

SystemModel

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

®

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

SystemModel

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

®

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

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

®

Request

Response

SystemModel

DoD ArchitectureRepository System

DOD CADM

Operational

Systems

Technical

DODAF

Any SE Tool

specifies requirements for

ISO STEP-enabledDownstream Tool

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

®

Request

Response

SystemModel

Demo : Executable Architectures

Create Activity Breakdown in MindMap Tool

OV-6bBuild StateMachine(UML)

Transfer to UMLTool Thru AP233Pipeline

OV-5Operational

Activity Model(UML)

Transfer to SimulatorThru AP233 Pipeline

SimulationTool

(SVM)

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

®

Contact Information• David Price

[email protected]– +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