Embed Size (px)
DESCRIPTION
Systems Modeling Language (SysML) Overview. April 20, 2005. Sanford Friedenthal SysML Cochair [email protected] (703) 293-5557. SE Practices for Describing Systems. Future. Past. Specifications Interface requirements System design Analysis & Trade-off Test plans. - PowerPoint PPT Presentation
Citation preview
1
Systems Modeling LanguageSystems Modeling Language(SysML) Overview(SysML) Overview
April 20, 2005April 20, 2005
Sanford FriedenthalSanford FriedenthalSysML CochairSysML [email protected]@lmco.com(703) 293-5557(703) 293-5557
Systems Modeling Language2
SE Practices for Describing SystemsSE Practices for Describing Systems
• SpecificationsSpecifications
• Interface requirementsInterface requirements
• System designSystem design
• Analysis & Trade-offAnalysis & Trade-off
• Test plansTest plans
Moving from Document centric to Model centric Moving 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
Systems Modeling Language3
Why Model Based Approach ?Why Model Based Approach ?
• Improved communicationsImproved communications
• Reduced ambiguityReduced ambiguity
• Reduced errorsReduced errors
• More complete representationMore complete representation
• Enhanced knowledge captureEnhanced knowledge capture
Systems Modeling Language4
Unified Modeling Language (UML)Unified Modeling Language (UML)• UMLUML
– Is a visual modeling languageIs a visual modeling language– Is not a methodologyIs not a methodology– Defacto standard for SW level OO modelingDefacto standard for SW level OO modeling
• Visual Modeling Language = Notation + SemanticsVisual Modeling Language = Notation + Semantics– Semantics = meaningSemantics = meaning– Notation = representation of meaningNotation = representation of meaning
Systems Modeling Language5
UML/SysML StatusUML/SysML Status• UML V2.0 UML V2.0
– Updated version of UML that offers significant capability for Updated version of UML that offers significant capability for systems engineering over previous versionssystems engineering over previous versions
– Adopted in June 2003/Finalized in 2005Adopted in June 2003/Finalized in 2005
• UML for Systems Engineering (SE) RFPUML for Systems Engineering (SE) RFP– Established the requirements for a system modeling languageEstablished the requirements for a system modeling language– Issued by the OMG in March 2003Issued by the OMG in March 2003
• SysML SysML – Industry Response to the UML for SE RFPIndustry Response to the UML for SE RFP– Addresses most of the requirements in the RFPAddresses most of the requirements in the RFP– V1.0 expected to begin adoption in 2005V1.0 expected to begin adoption in 2005
Systems Modeling Language6
SysML PartnersSysML Partners• IndustryIndustry
– American Systems, BAE SYSTEMS, Boeing, Deere & American Systems, BAE SYSTEMS, Boeing, Deere & Company, EADS Astrium, Eurostep, Israel Aircraft Company, EADS Astrium, Eurostep, Israel Aircraft Industries, Lockheed Martin, Motorola, Northrop Industries, Lockheed Martin, Motorola, Northrop Grumman, oose.de, Raytheon, THALESGrumman, oose.de, Raytheon, THALES
• GovernmentGovernment– DoD/OSD, NASA/JPL, NISTDoD/OSD, NASA/JPL, NIST
• VendorsVendors– Artisan, Ceira, EmbeddedPlus, Gentleware, IBM, I-Logix, Artisan, Ceira, EmbeddedPlus, Gentleware, IBM, I-Logix,
PivotPoint Technology, Popkin, Project Technology, PivotPoint Technology, Popkin, Project Technology, 3SL, Telelogic, Vitech3SL, Telelogic, Vitech
• Liaisons/Other OrganizationsLiaisons/Other Organizations– AP-233, CCSDS, EAST, INCOSE, RosettaAP-233, CCSDS, EAST, INCOSE, Rosetta
Systems Modeling Language7
SystemSystemSystemSystem
SysML ScopeSysML Scope
Req’tsAnalysis
ArchDesign
Verify &Validate
Systems Engineering Process, Methods, & Artifacts
Component Specific Methods (e.g. HW, SW)
SystemSystem
SubsystemSubsystem
Item 1Item 1 Item NItem N
Subsystem
Applies to Each Level of the System Hierarchy
Applies to Each Level of the System Hierarchy
SoSSoS
CustomerReq’ts
System Solutions
Item 1Item 1 Item NItem N
EvalAltern
Development Life CycleDevelopment Life Cycle
SystemSystemHierarchyHierarchy
Systems Modeling Language8
SysML Diagram TaxonomySysML Diagram Taxonomy
SysML Diagram
StructureDiagram
BehaviorDiagram
Use CaseDiagram
ActivityDiagram
AssemblyDiagram
SequenceDiagram
State MachineDiagram
TimingDiagram
ParametricDiagram
RequirementDiagram
ClassDiagram
Modified from UML 2
New diagram type
Derived from UML 2 Derived from UML 2 Composite StructureComposite Structure
Systems Modeling Language9
A Few Sample DiagramsA Few Sample Diagrams
Systems Modeling Language10
Assemblies, Parts, Ports, Connectors Assemblies, Parts, Ports, Connectors & Flows& Flows
asm: ABC System
Part2:Part1:
AssemblyAssembly
ConnectorConnectorPortPort
Item FlowItem Flow
Systems Modeling Language11
Continuous SystemsContinuous Systems
« interruptibleRegion»
Driving
Braking
Monitor Traction
TurnKey On
« continuous »
Dri
ve
rB
rak
eS
ys
tem
AB
S
BrakePressure
«ControlOperator»
Enable on BrakePressure > 0
« continuous »
ModulationFrequency
IgnitionOff
Systems Modeling Language12
Sequence Diagram with ReferenceSequence Diagram with Reference
seq: Continue
:A :B :C
refQuestion
altok
notOK
yes
no
seq: Question
:A :B
alt
ok
notOK
ask
DoSth
nonono
Derived from UML 2 SuperstructureDerived from UML 2 Superstructure
Systems Modeling Language13
State Machine DiagramState Machine Diagram
s-m:VehicleSystemOperateState
Operate
Start
Terminate
Vehicle On
Neutral
Forward
Reverse
engine on
Shift [gearSelect=reverse]
Shift [gearSelect=neutral]
Shift [gearSelect=forward]
Shift [gearSelect=neutral]
ignition off
engine off
ignition on
Systems Modeling Language14
Requirement Diagram Showing Requirement Diagram Showing Requirements FlowdownRequirements Flowdown
Vehicle System Use Cases
«requirement»Power Subsystem Specification
«requirement»Vehicle System Specification
req: VehicleSystemReqtsFlowdown
Vehicle System Design
Drive Vehicle
Driver
«system»Vehicle
«assembly»Power Train
«assembly»Brakes
«trace»
«satisfy»«derive»
Power Subsystem Design(Alternative = V6)
«assembly»Engine
«assembly»Transmission
«satisfy»«rationale»
Ref: Trade-Off Analysis
«trace»
«rationale»Ref: Statement of Work
Id: 102text: System shall ..criticallity: H
«criticalRequirement»VehicleAcceleration
id: 111text: System shall ..
«requirement»R111
id: 337text: Powersubsystem shall …
«requirement»R337
id: 340text: Powersubsystem shall ..
«requirement»R340
«document»Market Needs
System shallaccelerate from 0 -60 mph in lest than8 seconds under thespecified conditions
«testCase»Engine Horsepower Test
«verify»
Systems Modeling Language15
Related Standards EffortsRelated Standards Efforts
Systems Modeling Language16
Standard UML Profile for DoDAFStandard UML Profile for DoDAF• Recent initiative started through the OMGRecent initiative started through the OMG
• PurposePurpose– Develop standard representations of DoDAF Develop standard representations of DoDAF
products using UML/SysMLproducts using UML/SysML
• BenefitsBenefits– Improved communicationsImproved communications– Architecture model reuse and maintainabilityArchitecture model reuse and maintainability– Model interoperability among toolsModel interoperability among tools
• OMG TimelineOMG Timeline– Plan to issue req’ts for the standard in late ’05 or Plan to issue req’ts for the standard in late ’05 or
early ‘06early ‘06
Systems Modeling Language17
SysML / AP-233 AlignmentSysML / AP-233 Alignment
ISO 10303/AP-233 NEUTRAL SE
DATA EXCHANGEFORMAT
ElectricalCAE
MechanicalCAD
SW DevEnvironment
SystemsEngineering
EngineeringAnalysis
TestingTools
PlanningTools
AlgorithmDesign
SysMLTools
Systems Modeling Language18
ImplementedImplementedby Toolsby Tools
Modeling Methods SADTSADTHH
PPOOSEOOSE OtherOther
Interchange Standards MOF/XMIMOF/XMI STEP/AP-233STEP/AP-233 OtherOther
Architecture Frameworks
FEAFFEAF Zachman FWZachman FWDoDAFDoDAF MDAMDA
Modeling & SimulationStandards
UML/SysMLUML/SysML IDEF0IDEF0 OtherOtherHLAHLAModeling Simulation
ProcessStandards EIA 632EIA 632 CMMI *CMMI *ISO 15288ISO 15288 IEEE 1220IEEE 1220
Systems Engineering Standards Systems Engineering Standards & Architecture Frameworks& Architecture Frameworks
CADMCADMMOF/XMIMOF/XMI STEP/AP-233STEP/AP-233
DoDAFDoDAF
UML/SysMLUML/SysML
Systems Modeling Language19
SummarySummary• SysML is a general purpose language that supports SysML is a general purpose language that supports
the specification, analysis, design, & verification of the specification, analysis, design, & verification of complex systemscomplex systems
• SysML is being developed in conjunction with related SysML is being developed in conjunction with related systems engineering and architecture framework systems engineering and architecture framework standardsstandards– Part of the OMG Model Driven Architecture Part of the OMG Model Driven Architecture
StandardsStandards– ISO AP-233 data interchange standardISO AP-233 data interchange standard– UML Profile for DoDAF initiativeUML Profile for DoDAF initiative
• Planned adoption of SysML v1.0 to begin end of 2005Planned adoption of SysML v1.0 to begin end of 2005
Systems Modeling Language20
ReferencesReferences• UML for SE RFPUML for SE RFP
– OMG doc# ad/03-03-41OMG doc# ad/03-03-41
• SysML V0.9 (refer to www.sysml.org)SysML V0.9 (refer to www.sysml.org)– OMG Doc # ad/05-01-03OMG Doc # ad/05-01-03
• [UML2 2003] UML 2 Superstructure (Final Adopted Specification)[UML2 2003] UML 2 Superstructure (Final Adopted Specification)– OMG doc# OMG doc# ptc/03-08-02ptc/03-08-02
• [UML2 2003] UML 2 Infrastructure (Final Adopted Specification)[UML2 2003] UML 2 Infrastructure (Final Adopted Specification)– OMG doc# OMG doc# ptc/03-09-15ptc/03-09-15
• INCOSE 2004 Symposium Paper “INCOSE 2004 Symposium Paper “Extending UML to Support a Systems Extending UML to Support a Systems Modeling Language” – S. Friedenthal, C. KobrynModeling Language” – S. Friedenthal, C. Kobryn
• INCOSE 2003 Symposium Paper “Extending UML from Software to Systems” INCOSE 2003 Symposium Paper “Extending UML from Software to Systems” – S. Friedenthal, R. Burkhart– S. Friedenthal, R. Burkhart
• INCOSE Insight (June 2004)INCOSE Insight (June 2004)
• [Bock 2003] "UML 2 Activity Model Support for Systems Engineering [Bock 2003] "UML 2 Activity Model Support for Systems Engineering Functional Flow Diagrams," Journal of INCOSE Systems Engineering, vol. 6, Functional Flow Diagrams," Journal of INCOSE Systems Engineering, vol. 6, no. 4, October 2003 – C. Bock no. 4, October 2003 – C. Bock
Systems Modeling Language21
Further InfoFurther Info
• WebWeb– www.sysml.orgwww.sysml.org
• ChairsChairs– Cris KobrynCris Kobryn
• [email protected]; [email protected]@telelogic.com; [email protected]– Sandy FriedenthalSandy Friedenthal
• [email protected]; [email protected]; [email protected]@sysml.org
