Model Based Systems Engineering using SysML 4th...

Model Based Systems Engineering using SysML

4th MODPROD Workshop on Model-Based Product Development

February 10, 2010

Sanford FriedenthalLockheed [email protected]

Topics

Model-based Systems Engineering (MBSE) Motivation and Scope

System Modeling Using SysML

System Model as an Integration Framework

SysML-Modelica Integration

SysML Status

Summary

MBSE Motivation and Scope

SE Practices for Describing Systems

Specifications

Interface requirements

System design

Analysis & Trade-off

Test plans

Moving from Document centric to Model centric Moving from Document centric to Model centric

PastPast FutureFuture

Model-based Systems Engineering (MBSE)

Formalizes the practice of systems development through use of modelsBroad in scope– Integrates with multiple

modeling domains across life cycle from system of systems to component

Results in quality/productivity improvements & lower risk– Rigor and precision– Communications among

system/project stakeholders– Management of complexity

Life Cycle Support

Vert

ical

Inte

grat

ion

© Copyright Lockheed Martin Corporation All Rights Reserved


•• DocumentDocument--Based System EngineeringBased System Engineering::

•• ModelModel--Based System Engineering:Based System Engineering:

System Description

Where is truth? Document

1 A<B

Document 2

A=B

Document 3

A>B

Model Repository

Inconsistencies within and among documents

Model enforces consistency

System Modeling Using SysML

System Modeling

Start Shift Accelerate Brake

Engine Transmission Transaxle

ControlInput

PowerEquations

VehicleDynamics

MassProperties

ModelStructuralModel

SafetyModel

CostModel

Requirements

Integrated System Model Must AddressIntegrated System Model Must AddressMultiple Aspects of a SystemMultiple Aspects of a System

What is SysML?A graphical modeling language in response to the UML for Systems Engineering RFP developed by the OMG, INCOSE, and AP233– a UML Profile that represents a subset of UML 2 with

extensions

Supports the specification, analysis, design, verification, and validation of systems that include hardware, software, data, personnel, procedures, and facilities

Supports model and data interchange via XML Metadata Interchange (XMI®) and the evolving AP233 standard (in-process)

SysML is Critical Enabler for MBSESysML is Critical Enabler for MBSE

SysML Diagram Taxonomy

SysML Diagram

StructureDiagram

BehaviorDiagram

Use CaseDiagram

ActivityDiagram

Internal BlockDiagram

Block DefinitionDiagram

SequenceDiagram

State MachineDiagram

ParametricDiagram

RequirementDiagram

Modified from UML 2

New diagram type

Package Diagram

Same as UML 2

definition use

4 Pillars of SysML – ABS Example1. Structure 2. Behavior

3. Requirements 4. Parametrics

sd ABS_ActivationSequence [Sequence Diagram]

d1:TractionDetector

m1:BrakeModulator

detTrkLos()

modBrkFrc()

sendSignal()

modBrkFrc(traction_signal:boolean)

sendAck()

interactionstate machine

stm TireTraction [State Diagram]

Gripping Slipping

LossOfTraction

RegainTractionactivity/function

SysML Model Used to Elaborate System and Component Requirements

System Model as anIntegration Framework

Modeling Domains

MBSE Must Integrateacross Modeling Domains

Ops/Mission Analysis

System Design

AlgorithmDevelopment

SoftwareDesign

HardwareDesign

Human System Integration

PerformanceSimulation

EngineeringAnalysis

ManufacturingLogisticsSupport

Integration& Test


Using System Architecture Modelas an Integration Framework

System Architecture Model

Req’ts Allocation &Design Integration

Software ModelsHardware Models

Q

QSET

CLR

S

R

∫G(s)U(s)

Analysis Models Verification Models


. . . . .

UC

. . . . .

UC

UC

System Level• Derives Subsystems• Allocates Requirements to Subsystems

Element Level• Derives Hardware and Software Components• Allocates Requirements to Components

Sub-System 1

Spec

SubSystem 2

Spec

System 1Spec

System 2Spec

. . .

UC

SW Comp 1

Spec

A-Spec

B-Spec

Mission Concept of Operations

Using the System Architecture Modelto Flowdown Requirements

Trade Studies, Simulation, Specification Reviews, etc.

Trade Studies, Simulation, Specification Reviews, etc.

Trade Studies, Simulation, Specification Reviews, etc.SW

Comp XSpec

. . .

Component Design & Implementation Level

UC

Comp 1Software

Comp XSoftware

. . .

System-of-System Level• 1st Level Of Decompositions• How Our System Contributes to

the Overall Mission

Behavior,Structure &

Requirements


Requirements


Requirements

(from John Watson/LMCSysML Info Days presentation)


Complete Subsystem Specs

Analyze System Services

Analyze System Level Requirements

Analyze Subsystem Collaboration to Satisfy the System Services

Derive and Allocate Requirements to Subsystem

Identify the Subsystem

Continue?No

Incorporate Additional Analysis as Needed

System Decomposition Process using SysML

SatComms

Forward Message from Regional Command

Forward Message to Regional Cmd


Weapon

Fire Weapon

Correct Course

Weapon System

Receive Order

Evaluate Engagement

Start Enagement

Terminate Engagement

Monitor Weapon

Send Guidance Command

[Correction Needed]

Send Status Change

[Status Change]

Weapon Intercept?[No]

SatComms




Weapon

Fire Weapon

Correct Course

Weapon System

Receive Order

Evaluate Engagement

Start Enagement


Monitor Weapon


[Correction Needed]

Send Status Change

[Status Change]


SatComms




Weapon

Fire Weapon

Correct Course

Weapon System

Receive Order

Evaluate Engagement

Start Enagement


Monitor Weapon


[Correction Needed]

Send Status Change

[Status Change]


SatComms




Weapon

Fire Weapon

Correct Course

Weapon System

Receive Order

Evaluate Engagement

Start Enagement


Monitor Weapon


[Correction Needed]

Send Status Change

[Status Change]


[Correction Needed][Status Change]

[No]

The Subsystem shall ....The Subsystem shall ....Derived

Requirements

SatComms




Weapon

Fire Weapon

Correct Course

Weapon System

Receive Order

Evaluate Engagement

Start Enagement


Monitor Weapon


[Correction Needed]

Send Status Change

[Status Change]


SatComms




Weapon

Fire Weapon

Correct Course

Weapon System

Receive Order

Evaluate Engagement

Start Enagement


Monitor Weapon


[Correction Needed]

Send Status Change

[Status Change]


SatComms




Weapon

Fire Weapon

Correct Course

Weapon System

Receive Order

Evaluate Engagement

Start Enagement


Monitor Weapon


[Correction Needed]

Send Status Change

[Status Change]


SatComms




Weapon

Fire Weapon

Correct Course

Weapon System

Receive Order

Evaluate Engagement

Start Enagement


Monitor Weapon


[Correction Needed]

Send Status Change

[Status Change]


[Correction Needed][Status Change]

[No]

Trade Studies, R&D, Simulation, Specification Reviews, etc.

Input

Yes

. . . . .

UC

. . . . .

UC

(from John Watson/LMCSysML Info Days presentation)


System Architecture Model to Support Tradeoff Analysis

System Architecture Model

CostReliability

∫G(s)U(s)

PerformanceSubsystem Alternative1 Alternative2 Alternative3Sensor Sensor1 Sensor2 Sensor3Processor Processor1 Processor2 Processor3Control Control1 Control2 Control3

Criteria Weight Alt 1 Alt 2 Alt 3Performance 0.5 7 5 5Reliability 0.2 4 6 5Cost 0.3 3 5 8Effectiveness 5.2 4.2 5.9

Alt 2 Alt 3

Optimization

AnalysisResults


SysML-Modelica Integration

Integrating SysML with SimulationGIT* Project

ModelicaModelicaLexical RepresentationLexical Representation(auto(auto--generated from SysML)generated from SysML)

[Johnson, 2008 [Johnson, 2008 -- Masters Thesis]Masters Thesis]

* Georgia Institute of Technology

SysML-Modelica Working Group

Initiated December 2008 at OMG SE DSIG Meeting

Objective:– Leverage the strengths of both SysML and Modelica by integrating

them to create a more expressive and formal MBSE language.– Define a formal Transformation Specification: a SysML4Modelica

profile and a mapping between the profile and Modelica

Members from both SysML and Modelica Community

Plan– Submit Transformation Spec to OMG at June 2010 meeting

Working Group Site– http://www.omgwiki.org/OMGSysML/doku.php?id=sysml-

modelica:sysml_and_modelica_integration21

– Yves Bernard– Roger Burkhart– Hans-Peter de Koning– Sandy Friedenthal– Peter Fritzson

– Nerijus Jankevicius– Alek Kerzhner– Chris Paredis (Chair)– Nicolas Rouquette– Wladimir Schamai

SysML-Modelica Transformation

22

Transformation SpecificationPart I — IntroductionPart II — SysML4Modelica profilePart III — Modelica meta-modelPart IV — SysML-Modelica mappingAnnex A – Robotic Sample Problem

Classes in SysML4Modelica

23

Robot Model from Modelica Standard Library

24

mot

or to

rque

25

Robot Context Diagram

26

Robot Internal Block Diagram

27

Actuator Internal Block Diagram

28

Computing Overall Robot Effectiveness

29

Trajectory Error Analysis

30

Creating the SysML4Modelica Model

31

SysML4Modelica Analytical Model

SysML Status

OMG SysML™ StatusSpecification– OMG Beta Specification in May ’06– Available Specification v1.0 in Sept ’07– Available Specification v1.1 in Nov ‘08– Revision task force for v1.2 in Dec ‘09– Revision task force for v1.3 in process

Adoption– Multiple vendor implementations available– Increasing number of early adopters across industry– Being introduced into academia– Books available (4)– SysML Certification being developed– DISR Emerging Standard (March 26, 2009)

Information can be found on the OMG SysML Website at http://www.omgsysml.org/

SummaryMBSE is a key practice to advance complex systems developmentStandards such as SysML and Modelica are critical enablers of MBSEMultiple tool vendors implementing SysMLSystem architecture model and standards based approach facilitate integration across modeling domainsSysML-Modelica Integration provides synergistic capability for system design and analysisGrowing interest and application of MBSE

Model Based Systems Engineering using SysML 4th...

Documents

Transcript of Model Based Systems Engineering using SysML 4th...