Systems Modeling Language (SysML) Overvie · Systems Modeling Language (SysML) Overview SysML Merge...
Transcript of Systems Modeling Language (SysML) Overvie · Systems Modeling Language (SysML) Overview SysML Merge...
Systems Modeling Language (SysML)Overview
SysML Merge Team (SMT)March 16, 2006
**Draft**
SMT Chair: Sanford [email protected]
These slides are in process of development by the SMT team and aresubject to change as the SysML specification is finalized. Please checkfor current SysML status at syseng.omg.org.
2
Caveatn This material is based on Draft V0.99
of the SysML specification and is stillsubject to change prior to adoption
3
Topicsn Motivation & Backgroundn Diagram Overviewn SysML Modeling as Part of an SE Processn SysML in a Standards Frameworkn Transitioning to SysMLn Summary
Motivation & Background
5
SE Practices for Describing Systems
n Specifications
n Interface requirements
n System design
n Analysis & Trade-off
n Test plans
Moving from Document centric to Model centricMoving 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
6
Model Based Engineering Benefitsn Improved communicationsn Improved design quality
n Reduced errors and ambiguityn More complete representation
n Reduced maintenance costsn Enhanced knowledge capture
7
System-of-Systems
Boundaries
Interactions
Modeling Needed to Manage System ComplexityModeling Needed to Manage System Complexity
8
Stakeholders Involvedin System Acquisition
TestersTesters
Developers/Developers/IntegratorsIntegrators
VendorsVendors
RegulatorsRegulators
CustomersCustomers
ProjectProjectManagersManagers
Modeling Needed to Improve CommunicationsModeling Needed to Improve Communications
9
What is SysML?n A graphical modeling language in response to the UML
for Systems Engineering RFP developed by the OMG,INCOSE, and AP233n a UML Profile that represents a subset of UML 2 with
extensions
n Supports the specification, analysis, design, verificationand validation of systems that include hardware,software, data, personnel, procedures, and facilities
n Supports model and data interchange via XMI and theevolving AP233 standard (in-process)
SysML is Critical Enabler for Model Driven SESysML is Critical Enabler for Model Driven SE
10
UML/SysML Status
n UML V2.0n Updated version of UML that offers significant capability for
systems engineering over previous versionsn Finalized in 2005 (formal/05-07-04)
n UML for Systems Engineering (SE) RFPn Established the requirements for a system modeling languagen Issued by the OMG in March 2003
n SysMLn Industry Response to the UML for SE RFPn Addresses most of the requirements in the RFPn Current version 0.99 and expected to begin adoption in April ‘06n Being implemented by 5 vendors
11
SysML Merge Team (SMT)nIndustry & Government
n American Systems, BAE SYSTEMS, Boeing,Deere & Company, EADS-Astrium, Eurostep,Lockheed Martin, Motorola, NIST, NorthropGrumman, oose.de, Raytheon, THALES
nVendorsn Artisan, EmbeddedPlus, Gentleware, IBM, I-Logix,
Mentor Graphics, PivotPoint Technology, SparxSystems, Telelogic, Vitech Corp
nAcademian Georgia Institute of Technology
nLiaison Organizationsn INCOSE, AP233 WG
Diagram Overview
13
Relationship Between SysML and UML
UML 2
UML 2Reuse(1, 2)
UMLreused by
SysML
UMLnot required
by SysML(UML -
UML4SysML)
SysMLextensions to
UML
SysML
14
SysML Diagram Taxonomy
15
4 Pillars of SysML –ABS ExampleStructure Behavior
Requirements Parametrics
req [package] VehicleSpecifications[Requirements Diagram - Braking Requirements]
Braking SubsystemSpecification
Vehicle SystemSpecification
id: 102text: The vehicle shall stopfrom 60 mph within 150 fton a clean dry surface.
«requirement»StoppingDistance
id: 337text: Braking subsystemshall prevent wheel lockupunder all braking conditions.
«requirement»Anti-LockPerformance
«traceReqt»
bdd [block] Anti-LockController [Block Definition Diagram]
«block»TractionDetector
«block»Brake
Modulator
«block»Library::Electro-Hydraulic
Valve
«block»Library::
ElectronicProcessor
«block»BrakingSystem::
Anti-LockController
d1 m1
definition
ibd [block] Anti-LockController[Internal Block Diagram]
d1:TractionDetector
m1:BrakeModulator
:modulatorinterface
use
sd ABS_ActivationSequence [Sequence Diagram]
d1:TractionDetector
m1:BrakeModulator
detTrkLos()
modBrkFrc()
sendSignal()
modBrkFrc(traction_signal:boolean)
sendAck()
interactionstm TireTraction [State Diagram]
«state»Gripping
«state»Slipping
LossOfTraction
RegainTraction
statemachine
act PreventLockup [Activity Diagram]
tractionLossFlow:
tractionLossFlow:«activity»
DetectLossOfTraction
«activity»Modulate
BrakingForce
activity/function
par [constraintBlock] StraightLineVehicleDynamics
«constraint»Accelleration
Equation[F = ma]
«constraint»VelocityEquation
[a = dv/dt]
«constraint»DistanceEquation
[v = dx/dt]
«constraint»BrakingForce
Equation[f = (tf*bf)*(1-tl)]
tf bftl
f
F
m
aa
v
v
x
16
par [constraintBlock] StraightLineVehicleDynamics
«constraint»Accelleration
Equation[F = ma]
«constraint»VelocityEquation
[a = dv/dt]
«constraint»DistanceEquation
[v = dx/dt]
«constraint»BrakingForce
Equation[f = (tf*bf)*(1-tl)]
tf bftl
f
F
m
aa
v
v
x
req [package] VehicleSpecifications[Requirements Diagram - Braking Requirements]
Braking SubsystemSpecification
Vehicle SystemSpecification
id: 102text: The vehicle shall stopfrom 60 mph within 150 fton a clean dry surface.
«requirement»StoppingDistance
id: 337text: Braking subsystemshall prevent wheel lockupunder all braking conditions.
«requirement»Anti-LockPerformance
«traceReqt»
req [package] VehicleSpecifications[Requirements Diagram - Braking Requirements]
Braking SubsystemSpecification
Vehicle SystemSpecification
id: 102text: The vehicle shall stopfrom 60 mph within 150 fton a clean dry surface.
«requirement»StoppingDistance
SatisfiedBy«block»Anti-LockController
id: 337text: Braking subsystemshall prevent wheel lockupunder all braking conditions.
«requirement»Anti-LockPerformance
«traceReqt»
par [constraintBlock] StraightLineVehicleDynamics
«constraint»Accelleration
Equation[F = ma]
«constraint»VelocityEquation
[a = dv/dt]
«constraint»DistanceEquation
[v = dx/dt]
«constraint»BrakingForce
Equation[f = (tf*bf)*(1-tl)]
tf bftl
f
F
m
aa
v
v
x
«value»Vehicle.position
«value»Vehicle.weight
«value»Tire.friction
«value»DutyCycle
«value»Braking.force
par [constraintBlock] StraightLineVehicleDynamics
«constraint»Accelleration
Equation[F = ma]
«constraint»VelocityEquation
[a = dv/dt]
«constraint»DistanceEquation
[v = dx/dt]
«constraint»BrakingForce
Equation[f = (tf*bf)*(1-tl)]
tf bftl
f
F
m
aa
v
v
x
«value»Vehicle.position
«value»Vehicle.weight
«value»Tire.friction
«value»DutyCycle
«value»Braking.force
ibd [block] Anti-LockController[Internal Block Diagram]
d1:TractionDetector
m1:BrakeModulator
:modulatorinterface
act PreventLockup [Activity Diagram]
tractionLossFlow:
tractionLossFlow:«activity»
DetectLossOfTraction
«activity»Modulate
BrakingForce
ibd [block] Anti-LockController[Internal Block Diagram]
allocatedFrom «activity»DetectLossOf Traction
d1:TractionDetector
allocatedFrom «activity»Modulate BrakingForce
m1:BrakeModulator
allocatedFrom«connector»tractionLossFlow:
c1:modulatorInterface
act PreventLockup [Swimlane Diagram]
tractionLossFlow:
«allocate»:TractionDetector
«allocate»:BrakeModulator
tractionLossFlow:«activity»
DetectLossOfTraction
«activity»Modulate
BrakingForce
allocatedTo«connector»c1:modulatorInterface
req [package] VehicleSpecifications[Requirements Diagram - Braking Requirements]
Braking SubsystemSpecification
Vehicle SystemSpecification
VerifiedBy«interaction»MinimumStoppingDistance
id: 102text: The vehicle shall stopfrom 60 mph within 150 fton a clean dry surface.
«requirement»StoppingDistance
SatisfiedBy«block»Anti-LockController
id: 337text: Braking subsystemshall prevent wheel lockupunder all braking conditions.
«requirement»Anti-LockPerformance
«traceReqt»
Cross Connecting Model ElementsStructure Behavior
Requirements Parametrics
ibd [block] Anti-LockController[Internal Block Diagram]
allocatedFrom «activity»DetectLossOf Traction
d1:TractionDetector
allocatedFrom «activity»Modulate BrakingForce
m1:BrakeModulator
allocatedFrom«connector»tractionLossFlow:
c1:modulatorInterface
satisfies«requirement»Anti-LockPerformance
ibd [block] Anti-LockController[Internal Block Diagram]
allocatedFrom «activity»DetectLossOf Traction
d1:TractionDetector
valuesDutyCycle: Percentage
allocatedFrom «activity»Modulate BrakingForce
m1:BrakeModulator
allocatedFrom«connector»tractionLossFlow:
c1:modulatorInterface
satisfies«requirement»Anti-LockPerformance
valuebinding
allocation
satisfy
verify
17
req [package] VehicleSpecifications[Requirements Diagram - Braking Requirements]
Braking SubsystemSpecification
Vehicle SystemSpecification
VerifiedBy«interaction»MinimumStoppingDistance
id: 102text: The vehicle shall stopfrom 60 mph within 150 fton a clean dry surface.
«requirement»StoppingDistance
SatisfiedBy«block»Anti-LockController
id: 337text: Braking subsystemshall prevent wheel lockupunder all braking conditions.
«requirement»Anti-LockPerformance
«traceReqt»
par [constraintBlock] StraightLineVehicleDynamics
«constraint»Accelleration
Equation[F = ma]
«constraint»VelocityEquation
[a = dv/dt]
«constraint»DistanceEquation
[v = dx/dt]
«constraint»BrakingForce
Equation[f = (tf*bf)*(1-tl)]
tf bftl
f
F
m
aa
v
v
x
«value»Vehicle.position
«value»Vehicle.weight
«value»Tire.friction
«value»DutyCycle
«value»Braking.force
ibd [block] Anti-LockController[Internal Block Diagram]
allocatedFrom «activity»DetectLossOf Traction
d1:TractionDetector
valuesDutyCycle: Percentage
allocatedFrom «activity»Modulate BrakingForce
m1:BrakeModulator
allocatedFrom«connector»tractionLossFlow:
c1:modulatorInterface
satisfies«requirement»Anti-LockPerformance
Cross Connecting Model ElementsStructure Behavior
Requirements
act PreventLockup [Swimlane Diagram]
tractionLossFlow:
«allocate»:TractionDetector
«allocate»:BrakeModulator
tractionLossFlow:«activity»
DetectLossOfTraction
«activity»Modulate
BrakingForce
allocatedTo«connector»c1:modulatorInterface
Parametrics
satisfy
verify
valuebinding
allocation
SysML Modeling as Partof the SE Process
19
System Development Process
SystemModelingActivities
Integrated ProductDevelopment (IPD) isessential to improve
communications
A Recursive V processthat can be applied tomultiple levels of the
system hierarchy
ComponentModelingActivities
20
Typical Systems Modeling Activities
SynthesizePhysical
Architecture
DefineSystem
Requirements
DefineLogical
ArchitectureOptimize &Evaluate
Alternatives
Validate &VerifySystem
AnalyzeNeeds Major SE Development Activities
Common Subactivities
•Engr Analysis Models•Trade studies
•Test cases/procedures
•Mission use cases/scenarios•Enterprise model
•System use cases/scenarios•Elaborated context•Req’ts diagram
•Logical architecture
•Node diagram•HW, SW, Data architecture
21
SysML Diagram Taxonomy
22
Capturing Requirements in the Model
ArtisanArtisanToolTool
23
Requirements Breakdown
Containment Used to Model the Content of a SpecificationContainment Used to Model the Content of a Specification
24
Requirements Relationships
Use of Derive, Satisfy, Verify, & Refine RelationshipsUse of Derive, Satisfy, Verify, & Refine Relationships
25
Problem and Rationale
Problem and Rationale can be attached to anyProblem and Rationale can be attached to anyModel Element to Capture Issues and DecisionsModel Element to Capture Issues and Decisions
26
SysML Diagram Taxonomy
27
Operational Use Cases
28
Activitiesn Activities used to specify flow of I/O
and controln SysML extensions to Activities
n Support for continuous flow modelingn Alignment of activities with Enhanced
Functional Flow Block Diagram
29
SysML EFFBD Profile
AligningAligning SysMLSysML with Classical Systems Engineering Techniqueswith Classical Systems Engineering Techniques
EFFBD - Enhanced Functional Flow Block Diagram
30
Activity Modeling with Swimlanesn allocation of parts via swim lanes
«ext
erna
l»«a
ttrib
ute»
perf
orm
ingD
ept:
Dep
artm
ent»
Cus
tom
erA
cctg
Dep
artm
ent
Ord
er D
epar
tmen
t
FillOrder
ShipOrder
SendInvoice
AcceptPayment
CloseOrder
Make Payment
[orderaccepted]
Invoice
ReceiveOrder
31
Distill Water Activity Diagram(Continuous Flow Modeling)
Representing Distiller Example inRepresenting Distiller Example in SysMLSysMLUsing Continuous Flow ModelingUsing Continuous Flow Modeling
32
Interactionsn Sequence diagrams provide representation for
message based behaviorn represents flow of control
n Sequence diagrams provide key mechanismsfor representing complex behaviorn reference sequencesn control logicn lifeline decomposition
33
Black Box Interaction (Drive)
UML 2 Sequence Diagram More ScalableUML 2 Sequence Diagram More Scalableby Supporting Control Logic and Reference Sequencesby Supporting Control Logic and Reference Sequences
34
Black Box Sequence (StartVehicle)
Simple Black Box InteractionSimple Black Box Interaction
References Lifeline DecompFor White Box Interaction
35
White Box Sequence (StartVehicle)
Decomposition of Black BoxDecomposition of Black BoxInto White Box InteractionInto White Box Interaction
36
State Machinesn Supports event based behavior
(generally asynchronous)n Transition with event, guard, actionn State with entry, exit and do-activityn Can include nested sequential or concurrent
statesn Can send/receive signals to communicate
between blocks during state transitions, etc
37
Operational States (Drive)
38
SysML Diagram Taxonomy
39
Blocksn Used to express structure of system
n Backbone description of system hierarchyn Either white- or black-box descriptionn Includes internal relationships and connectivity
in addition to system decomposition
40
Power Subsystem Breakdown
Block Definition Diagram Used to Specify SystemBlock Definition Diagram Used to Specify SystemHierarchy and ClassificationHierarchy and Classification
41
Power Subsystem IBD
Internal Block Diagram Used to Specify InterconnectionInternal Block Diagram Used to Specify InterconnectionAmong Parts in Context of Enclosing BlockAmong Parts in Context of Enclosing Block
Part
Connector
EnclosingBlock
42
Parametricsn Used to express constraints (equations) between
value propertiesn Provides support to engineering analysis (e.g.
performance, reliability, etc)n Constraint block captures equations
n Expression language can be formal (e.g. MathML, OCL…) or informal
n Computational engine is defined by applicable analysistool and not by SysML
n Parametric diagram represents the usage of theconstraints in an analysis contextn Binding of constraint usage to value properties of blocks
(e.g. vehicle mass bound to F= m * a)
ParametricsParametrics Enable Integration of EngineeringEnable Integration of EngineeringAnalysis with Design ModelsAnalysis with Design Models
43
Defining Vehicle Dynamics
Defining Reusable Equations forDefining Reusable Equations for ParametricsParametrics
44
Evaluating Vehicle Dynamics
Using the Equations in a Parametric Diagram toUsing the Equations in a Parametric Diagram toConstrain the Value PropertiesConstrain the Value Properties
45
Evaluating Measures of Effectiveness
MOEMOE’’ss and objective function provide flexible support forand objective function provide flexible support fortrade study analysis that is fully integrated withtrade study analysis that is fully integrated with parametricsparametrics
46
Allocationsn Provides general relationship to map one
model element to anothern Includes specific subclasses of allocation with
constraints on their usagen Behavioraln Structuraln Flow
n Explicit allocation of activities to swim lanes(e.g. activity partitions)
n Graphical and/or tabular representations
47
Different Allocation Representations(Tabular Representation Not Shown)
Explicit Allocation ofActivity to Swim Lane
Allocate Relationship
Callout NotationCompartment Notation
48
View/ViewpointViewpoint captures stakeholder concerns
•express concerns as requirements
•construction rules describe view which satisfies reqts
View describes system from a particular viewpoint
Relationship between Viewpoints
SysML in a Standards Framework
50
Systems Engineering Standards &Architecture Frameworks
SADTSADT
ProcessStandards
Modeling &SimulationStandards
ModelingMethods
FEAF Zachman FWDoDAF
HPHP
ArchitectureFrameworks
Other
UML/SysMLUML/SysMLIDEF0
InterchangeStandards STEP/AP233STEP/AP233MOF/XMI CADM
MDA
MATHMLHLAModeling Simulation & Analysis
ImplementedImplementedBy ToolsBy Tools
EIA 632 CMMIISO 15288 IEEE 1220
OOSE
51
ISO/IEC 15288System Life Cycle ProcessesEnterprise Processes
5.3.2Enterprise Environment
Management Process
5.3.3Investment
Management Process
5.3.6Resource
Management Process
5.3.5Quality
Management Process
5.3.4System Life Cycle
Processes Management
5.2.3Supply Process
5.2.2Acquisition Process
Agreement Processes
Project Processes
5.4.2Project Planning Process
5.4.3Project Assessment
Process
5.4.6Risk Management
Process
5.4.5Decision-Making Process
5.4.4Project Control Process
5.4.8Information Management
Process
5.4.7Configuration Management
Process
Technical Processes5.5.2
Stakeholder ReqtsDefinition Process
5.5.3Reqts Analysis Process
5.5.6Integration Process
5.5.5Implementation Process
5.5.8Transition Process
5.5.7Verification Process
5.5.9Validation Process
5.5.10Operation Process
5.5.11Maintenance Process
5.5.12Disposal Process
5.5.4Architectural Design Process
52
Example Standards-basedTool Integration
••----------------------------------------------------------------
•.....•.....•.....
SV4 OV2
OV7 TV2
••----------------------------------------------------------------
•.....•.....•.....AP233/XMI
AP233/XMI
Systems ModelingTool
Model/DataInterchange
Other SE EngineeringTools
EngineeringRepository
53
Participating SysML Tool Vendors
n Artisann EmbeddedPlusn IBMn I-Logixn Sparx Systemsn Telelogicn Vitech
54
UML Profile for DoDAF/MODAFStandardization
n Current initiative underway to developstandard profile for representing DODAFand MODAF productsn Requirements for profile issued Sept 05n Final submissions expected Dec ‘06
n Multiple vendors and users participatingn Should leverage SysML
55
Tool Support
Project ManagementIMP/IMS, Process Modeling (ISDM)
CM
/DM
Prod
uct D
ata
Man
agem
ent
Req
uire
men
ts M
anag
emen
t
Engi
neer
ing
Perf
orm
ance
Ana
lysi
s
Ris
k &
Opp
ortu
nity
Man
agem
ent
Verif
icat
ion
& V
alid
atio
n
Mea
sure
men
t
SoS / DoDAF
System ModelingSysML
Software ModelingUML 2.0
Hardware ModelingVHDL, Verilog Sp
ecia
lty E
ngin
eerin
g
56
Summaryn SysML sponsored by INCOSE/OMG with broad
industry and vendor participationn SysML provides general purpose modeling
language to support specification, analysis,design and verification of complex systemsn Subset of UML 2 with extensions
n Multiple vendor implementations announcedn Adoption expected to begin in April 2006n Standards based modeling approach for SE
expected to improve communications, toolinteroperability, and design quality
57
References
n UML for SE RFPn OMG doc# ad/03-03-41
n SysML specification v0.99n http://syseng.omg.org/SysML.htm
n UML 2 Superstructuren OMG doc# formal/05-07-04
n UML 2 Infrastructuren OMG doc# ptc/04-10-14