model based systems engineering · · 2017-05-19model based systems engineering ... abstraction...

Model Based Systems Engineering

and How it Aids DoD Acquisition & Systems Engineering

Dwayne [email protected]

Enterprise DevelopmentSystems and Software Engineering DirectorateOffice of the Under Secretary of Defense (A&T)

24 OCT 2006

Briefing Objectives

Vision for Model-Based Systems Engineering (MBSE)• Primarily from INCOSE’s perspective

How MBSE enables better and faster system trade-offs and related DoD acquisition decisions• From my perspective

INCOSE Vision 2020Model-Based Systems Engineering (MBSE)

Highlights fromMBSE Workshop

July 7, 2006

Definitions• Model

– A representation of one or more concepts that may be realized inthe physical world. Models are represented in many forms including graphical, mathematical, and physical prototypes.

– Typical systems engineering models may include behavioral, structural, geometric, performance, and other engineering analysis models.

• Model based systems engineering (MBSE)– Model based systems engineering is the formalized application

of modeling to support system requirements, design, analysis, verification and validation beginning in the conceptual design phase, and continuing throughout development and later life cycle phases.

MBSE Benefits• MBSE enhances the ability to capture, analyze, share, and manage the

information associated with the complete specification of a product, resulting in the following benefits: – Improved communications among the development stakeholders (e.g.

the customer, program management, systems engineers, hardware and software developers, testers, and specialty engineering disciplines).

– Increased ability to manage system complexity by enabling a system model to be viewed from multiple perspectives, and to analyze the impact of changes.

– Improved product quality by providing an unambiguous and precise model of the system that can be evaluated for consistency, correctness, and completeness.

– Enhanced knowledge capture and reuse of the information by capturing information in more standardized ways and leveraging built in abstraction mechanisms inherent in model driven approaches. This in-turn can result in reduced cycle time and lower maintenance costs to modify the design.

– Improved ability to teach and learn systems engineering fundamentals by providing a clear and unambiguous representation of the concepts.

MBSE Drivers

• Information technology explosion– Networking– Computing power– Storage capacity

• Evolving profile of the Systems Engineer– Chat generation adaptive to rapid change in

technology and information

MBSE State of Practice Factors

• MBSE applications– What are the applications/uses of MBSE?

• Model scope– What is the scope that the system model is intended to represent

(e.g. system to component, ilities, life cycle, …) ?• Model quality and robustness

– How adequately does the model represent the real world concepts?

• Modeling standards – What industry standards support MBSE?

• MBSE process, methods, tools, and training– What is the process infrastructure for MBSE?

MBSE State of Practice - 2006• Practiced in pockets across industry

– Functional modeling with some executable behavior– Performance simulation models

• MBSE not fully integrated into SE process • SoS and System models not integrated with

hardware, software, ilities• Use of architecture frameworks gaining steam

(e.g. DODAF, MODAF) for SoS/Enterprise modeling

• MBSE standards emerging (SysML, AP233, BPMN, UPDM, ..)

MBSE State of Practice - 2010• Commonly practiced across broad range of industry• Standards based MBSE tools • Modeling methods matured• Integrated models from SoS down to hardware and

software• Enhanced integration between architecture models,

behavior execution, simulation, and engineering analysis• Some model reuse• Modeling metrics defined to assess “model goodness” • MBSE standards increasing in precision and leveraging

model and data management standards• MBSE certification underway

MBSE State of Practice - 2020• MBSE extends to domains beyond engineering to support complex

predictive and affects-based modeling that includes integration of engineering models with scientific and phenomenology models, social, economic, and political models, and human behavioral models

• Use of domain specific languages and visualization that enable the systems engineer to focus on abstract modeling of the user domain

• Modeling standards based on a firm mathematical foundation that support high fidelity simulation and real world representations

• Extensive reuse of model libraries, taxonomies, and design patterns • Standards that support integration and management across a

distributed model repository• Highly reliable and secure data exchange via published interfaces • Systems engineering workflow supported by standard “SE services”

to access model information (e.g. requirements trace)

Potential Challenges

• Evolution of standards to meet evolving needs

• Availability of model driven methods• Availability of interoperable modeling tools

– Tool interoperability and standards support• Availability of model driven training• Stakeholder/User acceptance of model

driven approach

RecommendationsFor Advancing MBSE

• Research– Mathematical foundation for modeling semantics – Application of data mining/search/pattern recognition methods to architecture engineering including use of

semantic web– Metrics and value of MBSE

• Promote use of modeling tools – INCOSE tool fairs including model and data exchange demos– Increase emphasis on simulation and engineering analysis

• Promote and advance MBSE process and methods– Identify and capture MBSE best practices– Identify modeling metrics– Add human centric to systems engineering methods (human to machine, human to human)– Establish criteria/guidelines for selecting and organizing models

• Promote and advance standards for MBSE– OMG SysML– AP233– OMG model interchange and model management– Architecture frameworks (UML Profile for DODAF/MODAF)– Integration between SysML and simulation standards

• Education in MBSE– MBSE certification

• Specifications• Interface requirements• System design• Analysis & Trade-off• Test plans

SE Practice Transitioning from Document centric to Model centricSE Practice Transitioning from Document centric to Model centric

AirplaneATC Pilot

Request to proceed

Authorize

Power-up

Initiate power-up

Direct taxiway

Report Status

Executed cmds

Initiate Taxi

PastPast FutureFuture

Transition to MBSE

Summary• MBSE offers significant benefits to enhance communications, manage complexity, improve product quality,

enhance knowledge capture, and improve the ability to teach SE • Systems engineering is in the early state of transition from a document centric to a model centric

approach, and is expected to advance rapidly over the next 15 years.• The current state of MBSE practice in 2006 is immature and practiced in an ad-hoc manner. MBSE standards

are emerging (OMG SysML, XMI, AP233, BPMN, Architecture Frameworks). • The projected state of MBSE practice in 2010 is that the MBSE methods and tools will be significantly more

mature based on implementation of standards and lessons learned. Architecture modeling for enterprise and SOS applications will be common place. The integration of the system models with the hardware and software models and engineering analysis models will be substantially improved.

• The projected state of MBSE practice in 2020 will extend MBSE to modeling domains beyond engineering models to support complex predictive and affects-based modeling. This will include integration of the engineeringmodels with scientific and phenomenology models, social, economic, and political models, and human behavioral models, The key characteristics of MBSE in 2020 include:

– Domain specific languages and visualization that enable the systems engineer to focus on abstract modeling of the user domain– Modeling standards based on a firm mathematical foundation that support high fidelity simulation and real world representations– Extensive reuse of model libraries, taxonomies, and design patterns – Standards that support integration and management across a distributed model repository– Highly reliable and secure data exchange via published interfaces

• INCOSE and the SE community should promote research, and advances in MBSE process and methods, tools, education, and standards to facilitate the transition to MBSE and achieve the desired benefits

In MBSE, SE Processes Must Leverage M&S

System Alternative (A)

f1 f2

&

d1

f3

&

d2

d3

system/subsystemalternative

2.0 3.01.0

1.1 1.2 41 4.2 4.3

4.0

function form

External Requirements traceability,

rationale

analysisneeds Analysis

Plan

closed form discrete event network

analysis specification

- purpose- scope-criteria

Analytical Models

System Modelperformance estimates

“instant” System Documentation &

Specifications

view-point

The “Working Fluid” of SE becomes the system model, not the document

How MBSE Aids DoD Acquisition & Systems Engineering

Transforming AcquisitionReversing the Trend

Tim

e to

Acq

uire

(yea

rs) Commercial

Technology Period

1010

2020

3030

00

DoD Acquisition Cycles

Over HistoryOver History

?F-15

F-22

UAV?

Responsive Acquisition?Responsive Acquisition?

Acquisition Cycles Now ExceedCommercial

Technology Periods

“Now, when I was secretary of defense . . . a quarter of a century ago . . . the reality was that the acquisition period was about half of what it is today . . . technology is advancing about four times as fast as it used to. Now how in the world can we expect to live in a circumstance like that?”

31 Jan 2002National Defense University

… we have taken important steps that will help us to produce improved capability on time and within budget by re-energizing our approach to systems engineering. This critical discipline has always contributed significantly to effective program management at every level and will receive sustained emphasis during my tenure.

Testimony of The Honorable Kenneth J. Krieg, USD(AT&L), before US Committee on Armed Services,

September 27, 2005

…… we have taken important steps that will help us we have taken important steps that will help us to to produce improved capability on time and within produce improved capability on time and within budget by rebudget by re--energizing our approach to systems energizing our approach to systems engineeringengineering. This critical discipline has always . This critical discipline has always contributed significantly to effective program contributed significantly to effective program management at every level and will receive management at every level and will receive sustained emphasis during my tenure.sustained emphasis during my tenure.

Testimony of The Honorable Kenneth J. Krieg, USD(AT&L), before US Committee on Armed Services,

September 27, 2005

… and Revitalization of Systems Engineering

Top 10 Emerging Systemic Issues

Major contributors to poor program performance

• Sustainment costs not fully considered (short-sighted)• Supportability considerations traded

10. Maintainability/Logistics

• Architecture, design/development discipline• Staffing/skill levels, organizational competency (process)

9. Software• Breadth, depth, resources8. Test Planning• Realism, compression7. Schedule

• Competing budget priorities, schedule-driven• Contracting issues, poor technical assumptions

6. Acquisition Strategy

• Ambitious growth curves, unrealistic requirements• Inadequate “test time” for statistical calculations

5. Reliability• Inadequate Government program office staff4. Staffing

• Lack of a rigorous approach, technical expertise• Process compliance

3. Systems Engineering

• Creep/stability• Tangible, measurable, testable

2. Requirements

• IPT roles, responsibilities, authority, poor communication• Inexperienced staff, lack of technical expertise

1. Management

Areas where MBSE might help

SE Issue – Poor Communications

TestersTesters

Developers/Developers/Integrators/Integrators/SustainersSustainers

VendorsVendors

RegulatorsRegulators

CustomersCustomers

Project Project ManagersManagers

MBSE can facilitate Improved Communications through use of technical data that is more precise and semantically

comparable with other taxonomies

SE’s Interface with many other system stakeholders over the life cycle

Technical Baseline(as a model)

SE Issue – Tangible, Measurable and Testable

MBSE should provide greater traceability of solutions to requirements and insight into technical risks

Technical Performance Measurements (TPMs) and technical baselines must be precise and comparable

SE Issue – Poor Technical Assumptions

<TITLE>System Design<TITLE><META http-equiv="REFRESH"<SCRIPT src="/virtual/2000/code<LINK rel="stylesheet" href="/<SCRIPT language="javascript"

Data ProcessingTerminalHardware


TCIM

Voice CommHardware includes

MSE


MSE

Operator InterfaceHardware


Force LevelControl System


Power Generationand Distribution


EPLRS or SINGARSTerminal


JTIDSTerminal

JTIDSTerminal

TCIM

PLGR (GPS)

PLGR(GPS)

Software

Software

A2C2 Subsystem

ABMOC Subsystem

Power

Power

Power

Power

Power

Power

Power

Voice & TADIL-B Data

Power

Power

Power

Power

Power

Power

Power


Tech Support System EntryPrimary Key

TSS_Entry_Number [PK1]Non-Key Attributes

Windows_VersionTSS_Description

CustomerPrimary Key

Customer_ID [PK1]Non-Key Attributes

Customer_NamePurchase_ContactCustomer_Address

Software LicensePrimary Key

Serial_Number [PK1]Non-Key Attributes

Technical_Contact

Client CallPrimary Key

Serial_Number [PK1] [FK]

LocationPrimary Key

Status [PK1] [FK]

Software ReleasePrimary Key

Version_Number [PK1]

StatusPrimary Key

Status [PK1]

owns

consists of

is subject to

creates

currently hasis a

CEC Information Exchange Requirements - Classified SECRET w hen filled in1 2 3 4 5 6 7 8 9 10 11

Rationale/UJTL Num ber Event/Action Inform ation Characterization Sending Node

Receiving Node

Critical Form at Class Latency: SA/Eng Support

Message Error Rate

Rem arks

OP 5.1.1 Comm Op InfoProvide SA/Support Engagem ents

Radar m easurem ents to support data fusion com posite tracking

Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %REF: CEC A-spec Table 3-3 and Host reqm ts


IFF measurem ents to support data fusion and composite tracking

Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %

OP 5.1.1 Comm Op Info Provide SA/Support Engagem ents

IFF interrogation requests to support data fusion and com posite tracking

Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % Respond when requested


ID Changes to support data fusion and composite tracking

Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx %


Navigation data to support data fusion and composite tracking Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % REF:CEC SRS and

Host Nav. spec


Engagem ent Support Requests to support data fusion and com posite tracking

Host CEP Yes Binary IAW IDD Secret xx secs/xx secs xx % AEGIS only


Track number managem ent to support data fusion and com posite tracking

Host-CEP CEP-Host Yes Binary IAW IDD Secret xx secs/xx secs xx %Changes sent im m ediately


Composite Track State Update to support data fusion and com posite tracking

CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx %REF: CEC IDDs for each host


Associated Measurem ent Reports to support data fusion and com posite tracking

CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx %REF: CEC A-spec Table 3-3. SPY only


IFF Assignm ents to support data fusion and composite tracking

CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx % When assigned or changed


ID recom mendations to support data fusion and com posite tracking

CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx %When assigned or changed


Sensor cues to support data fusion and composite tracking CEP Host Yes Binary IAW IDD Secret xx secs/xx secs xx %

REF: CEC A-spec Table 3-3. SPY only

Correlating Tracks

On entry / match state vectorsDo / corr state vectorsDo / corr LPEDo / corr PIPDo / corr RCSDo / corr CIDOn exit / corr BMDS Track #

corr fail / is new BMDS Trackcorr success / is corr BMDS Track

Receiving Network Track FileData

On entry / receive file dataDo / store track dataOn exit / request matching data

Receiving BMDS Track FileData

On entry / receive file dataDo / store track data

Idle

Session Activated

BMDS Track File Request Sent ( Request) / Pull BMDS Track Files

Network Track File Received ( File Data ) [ number tracks> 0 ] / Input Network Track

Correlation Complete ( CorrelationResults ) [ set not null ] / Send Results

BMDS Track File DataReceived ( File Data ) /

Correlate Tracks

/ initialize

Track Management Module Correlation Module HICTrack FileNetwork InterfaceModule

Verify CID,Correlation, and

Assoicated TrackData

RequestPossible

BMDS TrackFile Matches

MonitorCorrelation

Process

Correlate Tracks

Attempt toCorrelate withBMDS Track

Send BMDSTrack Data to

JDN

Create NewBMDS Track

Send TrackFile Data

Update TrackFile Data

Track Management Module Correlation Module HICTrack FileNetwork InterfaceModule

CorrelationPossible

Network Track MSG

Prepared Track MSG

Track MSG Data

BMDS Track Data

BMDS Track Display

BMDS Track Data

no

yes

Correlation Results

Track Data

BMDS Track Data

Track File Request

Track DataTrack Data



TCIM


MSE


MSE









JTIDSTerminal

JTIDSTerminal

TCIM

PLGR (GPS)

PLGR(GPS)

Software

Software

A2C2 Subsystem

ABMOC Subsystem

Power

Power

Power

Power

Power

Power

Power


Power

Power

Power

Power

Power

PowerPower


FAAD C3I

AMDPCS

Patriot ICC

MCE (CRC)AWACS

MCE (CRC)

MCE (CRC)

LINK 16LINK 16

LINK 16

LINK 16

<<entity>>Network Track

owning elementReceived Date-Timelocal track number

receive ()store ()update ()send ()

<<interface>>Network Interface Module

buffer capacity/msg data

receive msg ()parse msg ()route msg data ()build msg ()send msg ()

Correlation Module

algorithm/tracks to be correlatedcorrelation datadecorrelation data

correlate tracks ()decorrelate tracks ()retrieve track data ()send track data ()

Track Mangement Module

/current tracks/associated track data/CID data

assign CID ()recommend CID ()retrieve track file data ()display track file data ()

<<entity>>Track File

Track NumberCID/State Vector/Date-Time

send track data ()

<<entity>>BMDS Track

/associated data/history

create ()update ()destroy ()retrieve ()

HIC

JDN

manages

0..*

1..*

interface for

1

1..*

correlates

0..*

1

communicates with

1

1

uses 1..*

1..*

received from

1

0..*

<<derived>>traces to

11

Receive NetworkTrack File

13

Manage BMDSTrack File Data

12

Correlate TrackFiles

Track Mangement S/W Module

NetworkInterface S/W

Correlation S/WModule

Correlated Track

Network Plan

NetworkTrack Data

CID Criteria

Network Track Data

JDN

HIC

BMDS Track

AMDPCS

FAAD C3I

ACDS (CVN)

DDG-51 AEGIS Destroyer

F-15C

AWACS F/A-18

MCE

TAOM

RIVET JOINT

CG

Patriot ICC

E-2C

SIAP Functional

Allocated

Physical

Technical Baseline Documentation

MBSE should minimize unclear or inconsistent data by improved data management and data sharing

These are often caused by unclear or inconsistent data contained in the numerous program documents and technical databases that are maintained individually

Technical Baseline(as a model)

SE Issue – Sustainment not Fully Considered or Traded

MBSE should facilitate earlier and better trade-offs between competing requirements and ALL design considerations

PMs are responsible for Total Life Cycle Systems Management

SE Issue – Rigorous and Disciplined Approach

TPMsProvide Objective

Entry & ExitCriteria

•Measure degree to which system requirements are met in terms of performance, cost, schedule, and progress in implementing risk handling

•Are critical to balancing cost & performance throughout the life cycle

•Basis for trade-off analysis

•Provide management insight

•Inform Reviews & Decisions

MBSE should provide a technical baseline that is measurable and permits more timely evaluation of key system characteristics

because it continuously evolves

DoD’s SE approach is centered on measurable results and timely reviews

SE Issue – Inadequate “Test Time”

MS “B” MS “C”MS “A”

ConceptRefinement

System Dev/Demonstration Production

ConceptDecision

Full RateProd

O&STechnology Development

MS “B” MS “C”MS “A”

TrainingTest

Component Design

Design

Feedback

Component Integration & Test

User Rqmts & Concept of Operations

System Requirements & Architecture

Procure, Fabricate, & Assemble Parts

System Integration & Test

RecursiveProcesses

RecursiveProcesses

System Demonstration &

Validation

NotionalM&Suse

Enablingthe

SystemsEngineering

Process

CampaignMissionEngagementEngineering Cost, etc

Source: Initial Draft Acquisition M&S Business Plan - August 4, 2006

MBSE should enable greater use of M&S to permit earlier and continuous evaluation of solutions

Ideally, M&S is used across the acquisition life cycle

MBSE is a focus area that is part of INCOSE Vision 2020 for SE

MBSE benefits are directly applicable to improving the practice of SE in DoD• Improved communications• Integrating consideration of total system life cycle needs• Early and continuous evaluation• More rigorous & disciplined reviews• More timely trade-offs and decisions

MBSE is not new, but most applications to-date have been limited in scope

Broader application of MBSE requires some emerging enablers• Data & modeling standards• Alignment with SE ‘process’ standards• Interoperable tool support• Application experience

- Real benefits and limitations - Refinement needed

Summary

Questions?

Key MBSE Enablers –Related Data & Modeling Standards Activities

Open Standards• SysML - Object Management Group SE DSIG

– Standard language and notation for modelling all types of systems– Model interchange with AP233

• AP233 (ISO 10303-233)- Defines a neutral information model for complex systems engineering

concerns to exchange systems engineering data with other data models• GEIA-927

- Facilitates the exchange of complex systems data concepts between product data domains

• UPDM (UML Profile for DoDAF & MODAF)– Define standardized architecture framework views & viewpoints– Data interchange with other architecture data sets, such as CADM, M3

& IDEAS schemasStandards-based Tool Interoperability Framework & Demos • Assists vendors to built interoperable SE tools using these standards

- NIST-DoD sponsored plug-fest

Facilitating Improved Total Life Cycle Systems Management

MBSE shared data should enable balancing design and support decisions that affect the total life cycle

model based systems engineering · · 2017-05-19model based systems engineering ... abstraction...

Documents