integrated modeling: adopting architecture frameworks for

Aurelijus Morkevicius

Integrated modeling: Adopting Architecture Frameworks

for Model-based Systems Engineering

“Copyright © 2014 by No Magic Inc.

Published and used by The SSSE and INCOSE with permission.”

The author or assignee retains the copyright to the materials.

Speaker

Dr. Aurelijus Morkevičius,

[email protected]

Solution Architect @ No Magic Europe

Works with companies such as BMW, Deutsche Bahn,

General Electric, Kongsberg Defense and Aerospace,

SKA, INDRA, Amadeus etc.

Chairman and one of the leading architects for the

current OMG UPDM standard development group

2 2 © 2014 No Magic, Inc. Exclusively for No Magic Use

mailto:[email protected]

Some History about No Magic

3 3

Contents

I. Why Architectural Framework is Key to MBSE

Success

II. Things that get solved if using

Architectural Framework

III. Architectural Frameworks in Practise

IV. Summary

4 © 2014 No Magic, Inc. Exclusively for No Magic Use

4

MBSE is about driving

systems engineering by

modeling & models

MBSE is SE!

5

Getting Value from Models and Modeling

Manage Complexity

Preserve knowledge

Reuse

Automate

6

Picture MODEL ≠

© 2014 No Magic, Inc. Exclusively for No Magic Use 6

Manage Complexity

© 2014 No Magic, Inc. Exclusively for No Magic Use

The data collected by the SKA in a single

day would take nearly two million years

to playback on an ipod

© SKA 2014

The SKA will use enough optical fibre to

wrap twice around the Earth!

The SKA central computer will have the

processing power of about one hundred

million PCs

SysML is critical

enabler for MBSE

8

What is SysML?

• OMG Systems Modeling Language (SysML) is a graphical

modeling language for specification, analysis and design,

verification and validation of systems.

• Modeling language that includes 9 diagrams

• Dedicated for modeling complex systems that may

include hardware, software, information, personnel,

procedures, and facilities.


SysML is neither a

modeling methodology

nor a framework

10

The modeling language

is just the language,

and must be combined

with a methodology to

be useful

11

Need for a Framework

• This opens discussions of:

how to structure the model

what views to build

which artifacts to deliver

and in what sequence

Every company deals with the same issue differently. Some use: defense architecture frameworks: DoDAF, NAF, MODAF

MBSE methods: OOSEM, Harmony, SYSMOD, FAS; however, saying there is no need for an architectural framework just doesn’t work.


You always end-up using an

architecture framework

whether you want one or

not, or whether you intend

to or not

13

If there is no Framework

14

System Requirements

& Business Analysis

System Analysis

& Design

Detailed Design:

Software & Hardware

Evaluation &

Optimization (V&V)

System

Integration

System

Implementation

Requirements diagram

Use Case Diagram

Activity diagram

Sequence Diagram

Package diagram

Block Definition diagram

Activity diagram

Sequence diagram

State diagram

Package diagram


Internal Block diagram

Parametric diagram

Sequence diagram

State diagram


Internal Block diagram

Package diagram

Requirements diagram

Use Case diagram

Parametric diagram

Activity Diagram

Sequence Diagram



15

System Engineering Standards

16

Sanford Friedenthal, Alan Moore, Rick Steiner, A Practical Guide to SysML The Systems Modeling Language


17 17

Ontology

ISO/IEC/IEEE42010, DoDAF

© 2014 No Magic, Inc. Exclusively for No Magic Use

EA Framework

• Conventions, principles and best practices for the

description of architectures established within a specific

domain of application and/or community of stakeholders

• Usually EA Framework consists of:

• Set of Views and Viewpoints

• Set of Presentation Artifacts

• Ontology (Metamodel) or

recommendations for modeling languages


Viewpoints

Capability

Operational

Scenario

Capability

Configuration


EA Frameworks: Future

Ian Bailey <[email protected]>


Where to read more?

www.nafdocs.org


http://www.nafdocs.org/

UPDM is critical

enabler to integrate

AFs with SysML

22

What is UPDM?

• UPDM is Unified Profile for DoDAF, MODAF, and NAF

• UPDM is NOT a new Architectural Framework

• UPDM is not a methodology or a process

• UPDM is an enterprise modeling language

• UPDM was developed by members

of the OMG with help from

industry and government

domain experts


UPDM

UML SysML

SoaML

BPMN

SysML – AF integration point

SysML


Capability

Operational

Scenario

Contents


Success




IV. Summary

25


What Sometimes Happens in Modeling Practice

26

~450 Actions ~950 Control Flows

Some facts about the project: Model-driven development

50 engineers working 4 years

2000+ diagrams

30 modules


MBSE Pitfalls: unmanaged abstractions

A. Unmanaged abstractions Ambiguous understanding

Duplicating information

Dependence on technical platform


Raise level of abstraction

MBSE Pitfalls: disintegrated model

C. Disintegrated model

Difficult to maintain

Duplicated/redundant information


Make model a single

source of data

MBSE Pitfalls: too complex diagrams

B. Too complex diagrams

Ambiguous understanding

Hides incompleteness issues

Model = Diagram & View = Diagram


Use different views to

represent model data

(view >= diagram)

MBSE Pitfalls: different roles are not

involved

D. Different roles are not involved

Gap between cross-functional teams

Single aspect oriented model


Bring different roles

together

Systems

Engineers

Product/Project

Managers

Software

Engineers

Requirements

Engineers

The Recipe for Success

think BIG

start SMALL

and EVOLVE


31

EA Framework for Unsuccessful Project

Scott W. Ambler www.ambysoft.com/surveys/

0%

7%

13%

27%

60%

D/MODAF

TOGAF

Zachman

Don't know

Created their

own


Contents


Success




IV.Summary


34

Successfully adopted MBSE with EA

Frameworks

Most experience is generic and does not depend on a

particular modeling domain


35

Submarine Warfare Federated Tactical System (SWFTS)

• A Common Combat System Deployed Across Multiple Fleets

• USN: • Los Angeles (SSN 688), • Ohio (SSGN 726), • Seawolf (SSN 21), • Virginia (SSN 774), • Ohio Replacement (SSBN)

• RAN: • Collins (SSG 73)

• Federates Multiple Subsystems from Multiple Program Offices and Vendors

• SWFTS Manages Subsystem Interfaces and System I&T

MBSE Solution for

Copyright © 2013: PennWell Corporation

http://c4i.gmu.edu/events/reviews/2011/slides/8-Mitchell-slides.pdf

http://c4i.gmu.edu/events/reviews/2011/slides/8-Mitchell-slides.pdf

• Manage the complexity faced by systems engineers

• Manage High Variability Between SWFTS Platforms

• Maximize Reuse Between Baselines • Improve the quality and efficiency of the baseline

configuration process

• Adopt MBSE to Enable a More Efficient

Systems Engineering Process

• Provide Intuitive MBSE tools for Engineers

to Develop Complex Systems with Maximum Reuse

• Adopt UPDM and SysML modeling languages • Train Systems Engineers in MBSE Technologies

and Tools

• Hierarchy of Models Supporting TEAM

SUBMARINE Engineering • Reduced Duplication and Inconsistency of

Element Definitions • Developed Libraries and Catalogs to Improve the

Quality and Efficiency of The Baseline Configuration Process

Solutions

Results ROI

Context

• 13% Savings to SE from MBSE

• 25% in Capability Definition • Another 10% over DOORS in Baseline Management

• Savings Seen in 4th Year • 2 Years to Implement Model • 1 Year Transition Overlap with Current Process

• Manage The Complexity Faced by Systems engineers

• Manage High Variability Between SWFTS Platforms

• Maximize Reuse Between Baselines • Improve the Quality and Efficiency of the Baseline

Configuration Process

Challenges

Copyright 2012 Net Resources International, a trading division of SPG Media Limited

Workflow in Defence

Contracting

Authority

Contractor/

Sub-Contractor


Contents


Success




IV.Summary


39

Top 4 Benefits Architectural

Frameworks provide

1. Raise level of abstraction

2. Make model a single source of data

3. Use different views to represent model

data (view >= diagram)

4. Bring different roles together

40

The Recipe # 1 for Success

41

A good beginning makes a good end!

41

The End

Thank You for Attention!

Questions???

Let’s Keep in Touch!

Aurelijus Morkevicius

Solution Architect @ No Magic Europe

Mobile: +370 612 10621

e-mail: [email protected]

LinkedIn: http://www.linkedin.com/pub/aurelijus-morkevicius/42/645/549


42





http://www.linkedin.com/pub/aurelijus-morkevicius/42/645/549



integrated modeling: adopting architecture frameworks for

Documents