Systems Modeling Language (SysML) Tutorial

1 OMG Systems Modeling Language (OMG SysML ) Tutorial19 June 2008 revbSanford FriedenthalAlan MooreRick Steiner(emails included in references at end)Copyright 2006-2008 by Object Management and used by INCOSE and affiliated societies with 2006-2008 by Object Management SysML Specification Specification status Adopted by OMG in May 06 Available Specification in Sept 07 Revision task force for in July 07 This Tutorial is based on the OMG SysML available specification (formal/2007-09-01) This Tutorial , the specifications, papers, and vendor info can be found on the OMG SysML Website at 2006-2008 by Object Management & Intended AudienceAt the end of this Tutorial , you should have an awareness of: Motivation of model-based Systems engineering approach SysML diagrams and Language concepts How to apply SysML as part of a model based SE process Basic considerations for transitioning to SysMLThis course is not intended to make you a Systems modeler!

2 You must use the Audience: Practicing Systems Engineers interested in system Modeling Software Engineers who want to better understand how to integrate software and system models Familiarity with UML is not required, but it helps4/15/2008 Copyright 2006-2008 by Object Management Motivation & Background Diagram Overview and Language Concepts SysML Modeling as Part of SE Process Structured Analysis Distiller Example OOSEM Enhanced Security system Example SysML in a Standards Framework Transitioning to SysML Summary Motivation & Background4/15/2008 Copyright 2006-2008 by Object Management Practices for Describing Systems Specifications Interface requirements system design Analysis & Trade-off Test plansMoving from Document centric to Model centric Moving from Document centric to Model centric PastPastFutureFuture4/15/2008 Copyright 2006-2008 by Object Management ModelingStartShiftAccelerateBrakeEngineT ransmissionTransaxleControlInputPowerEqu ationsVehicleDynamicsMassPropertiesModel StructuralModelSafetyModelCostModelRequi rementsIntegrated system Model Must Address Multiple Aspects of a SysteIntegrated

3 system Model Must Address Multiple Aspects of a system m 4/15/2008 Copyright 2006-2008 by Object Management Based Systems Engineering Benefits Shared understanding of system requirements and design Validation of requirements Common basis for analysis and design Facilitates identification of risks Assists in managing complex system development Separation of concerns via multiple views of integrated model Supports traceability through hierarchical system models Facilitates impact analysis of requirements and design changes Supports incremental development & evolutionary acquisition Improved design quality Reduced errors and ambiguity More complete representation Supports early and on-going verification & validation to reduce risk Provides value through life cycle ( , training) Enhances knowledge capture4/15/2008 Copyright 2006-2008 by Object Management Needed to Manage system ComplexityModeling Needed to Manage system Complexity4/15/2008 Copyright 2006-2008 by Object Management at Multiple Levels of the system <TITLE> system Design<TITLE> <META http-equiv="REFRESH"<!

4 --CSSDATA:966533483--> <SCRIPT src="/virtual/2000/code<LINK rel="stylesheet" href="/<SCRIPT Language ="javascript"Data ProcessingTerminalHardwareData ProcessingTerminalHardwareTCIMV oice CommHardware includesMSEV oice CommHardware includesMSEO perator InterfaceHardwareOperator InterfaceHardwareForce LevelControl SystemForce LevelControl SystemPower Generationand DistributionPower Generationand DistributionEPLRS or SINGARST erminalEPLRS or SINGARST erminalJTIDST erminalJTIDST erminalTCIMPLGR (GPS)PLGR(GPS)SoftwareSoftwareA2C2 SubsystemABMOC SubsystemPowerPowerPowerPowerPowerPowerP owerVoice & TADIL-B DataPowerPowerPowerPowerPowerPowerPowerV oice & TADIL-B DataTech Support system EntryPrimary KeyTSS_Entry_Number [PK1]Non-Key AttributesWindows_VersionTSS_Description CustomerPrimary KeyCustomer_ID [PK1]Non-Key AttributesCustomer_NamePurchase_ContactC ustomer_AddressSoftware LicensePrimary KeySerial_Number [PK1]Non-Key AttributesTechnical_ContactClient CallPrimary KeySerial_Number [PK1] [FK]LocationPrimary KeyStatus [PK1] [FK]Software ReleasePrimary KeyVersion_Number [PK1]StatusPrimary KeyStatus [PK1]ownsconsists ofis subject tocreatescurrently hasis aCEC Infor m ation Exchange Requir e m ents - Class ifie d SECRET w hen filled in1234567891011 Rationale/UJTL Num berEvent/ActionInfor m ation Char acte r izationSe nding No d eRe ceiving No d eCr iticalFor m atClassLatency.

5 SA/Eng SupportMessage Error RateRe m ar k sOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsRadar measurements to suppor t data fus ion com posite tr ack ingHostCEPYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %REF: CEC A-spec Table 3- 3 and Hos t r e qm t sOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsIFF m e as ur em e nts to suppor t data fus ion and com pos ite tr ack ingHostCEPYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %OP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsIFF inte r r ogation re que sts to suppor t data fus ion and com posit e t r ackingHostCEPYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %Respond when requested OP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsID Change s to s uppor t data fusion and composite trackingHostCEPYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx % OP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsNavigation data to suppor t data fusion and composite trackingHostCEPYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %REF:CEC SRS and Host Nav.

6 SpecOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsEngagement Support Requests to support data fusion and com posit e t r ackingHostCEPYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %AEGIS onlyOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsTrack number management to suppor t data fus ion and com posit e t r ackingHost-CEP CEP-HostYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %Changes sent immediatelyOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsComposite Track State Update to support data fusion and com posit e t r ackingCEPHostYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %REF: CEC IDDs for e ach hostOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsAssociated Measurement Reports to support data fusion and com posite tr ack ingCEPHostYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %REF: CEC A-spec Table 3-3. SPY onlyOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsIFF A s s ignm e nts to suppor t data fus ion and com pos ite tr ack ingCEPHostYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %When assigned or changedOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsID recommendations to suppor t data fus ion and composit e t r acking CEPHostYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %When assigned or changedOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsSensor cues to support data fusion and composite trackingCEPHostYe sBinar y IAW IDDSe cr etxx s ecs/xx se csxx %REF: CEC A-spec Table 3-3.

7 SPY onlyCorrelating TracksOn 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 TrackReceiving Network Track FileDataOn entry / receive file dataDo / store track dataOn exit / request matching dataReceiving BMDS Track FileDataOn entry / receive file dataDo / store track dataIdleSession ActivatedBMDS Track File Request Sent ( Request) / Pull BMDS Track FilesNetwork Track File Received ( File Data ) [ number tracks> 0 ] / Input Network TrackCorrelation Complete ( CorrelationResults ) [ set not null ] / Send ResultsBMDS Track File DataReceived ( File Data ) /Correlate Tracks/ initializeTrack Management ModuleCorrelation ModuleHICT rack FileNetwork InterfaceModuleVerify CID,Correlation, andAssoicated TrackDataRequestPossibleBMDS TrackFile MatchesMonitorCorrelationProcessCorrelat e TracksAttempt toCorrelate withBMDS TrackSend BMDST rack Data toJDNC reate NewBMDS TrackSend TrackFile DataUpdate TrackFile DataTrack Management ModuleCorrelation ModuleHICT rack FileNetwork InterfaceModuleCorrelationPossibleNetwor k Track MSGP repared Track MSGT rack MSG DataBMDS Track DataBMDS Track DisplayBMDS Track DatanoyesCorrelation ResultsTrack DataBMDS Track DataTrack File RequestTrack DataTrack DataData ProcessingTerminalHardwareData ProcessingTerminalHardwareTCIMV oice CommHardware includesMSEV oice CommHardware includesMSEO perator InterfaceHardwareOperator InterfaceHardwareForce LevelControl SystemForce LevelControl SystemPower Generationand DistributionPower Generationand DistributionEPLRS or SINGARST erminalEPLRS or SINGARST erminalJTIDST erminalJTIDST erminalTCIMPLGR (GPS)PLGR(GPS)

8 SoftwareSoftwareA2C2 SubsystemABMOC SubsystemPowerPowerPowerPowerPowerPowerP owerVoice & TADIL-B DataPowerPowerPowerPowerPowerPowerPowerV oice & TADIL-B DataFAAD C3 IAMDPCSP atriot ICCMCE (CRC)AWACSMCE (CRC)MCE (CRC)LINK 16 LINK 16 LINK 16 LINK 16<<entity>>Network Trackowning elementReceived Date-Timelocal track numberreceive ()store ()update ()send ()<<interface>>Network Interface Modulebuffer capacity/msg datareceive msg ()parse msg ()route msg data ()build msg ()send msg ()Correlation Modulealgorithm/tracks to be correlatedcorrelation datadecorrelation datacorrelate tracks ()decorrelate tracks ()retrieve track data ()send track data ()Track Mangement Module/current tracks/associated track data/CID dataassign CID ()recommend CID ()retrieve track file data ()display track file data ()<<entity>>Track FileTrack NumberCID/State Vector/Date-Timesend track data ()<<entity>>BMDS Track/associated data/historycreate ()update ()destroy ()retrieve () * *interface * *1communicates * *received *<<derived>>traces to11 Receive NetworkTrack File13 Manage BMDST rack File Data12 Correlate TrackFilesTrack Mangement S/W ModuleNetworkInterface S/WCorrelation S/WModuleCorrelated TrackNetwork PlanNetworkTrack DataCID CriteriaNetwork Track DataJDNHICBMDS TrackAMDPCSFAAD C3 IACDS (CVN)DDG-51 AEGIS DestroyerF-15 CAWACSF/A-18 MCETAOMRIVET JOINTCGP atriot ICCE-2 CSIAPO perational ModelsSystem ModelsComponent Models4/15/2008 Copyright 2006-2008 by Object Management Involved in system AcquisitionTestersTestersDevelopers/Deve lopers/IntegratorsIntegratorsVendorsVend orsRegulatorsRegulatorsCustomersCustomer sProject Project ManagersManagersModeling Needed to Improve CommunicationsModeling Needed to Improve Communications4/15/2008 Copyright 2006-2008 by Object Management is SysML?

9 A graphical modelling 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 Model Driven SE SysML is Critical Enabler for Model Driven SE 4/15/2008 Copyright 2006-2008 by Object Management is SysML (cont.) Is a visual Modeling Language that provides Semantics = meaning Notation = representation of meaning Is not a methodology or a tool SysML is methodology and tool independent4/15/2008 Copyright 2006-2008 by Object Management Status UML V2 Updated version of UML that offers significant capability for Systems engineering over previous versions Issued in 2005 with on-going minor revisions UML for Systems Engineering (SE) RFP Established the requirements for a system Modeling Language Issued by the OMG in March 2003 SysML Industry Response to the UML for SE RFP Adopted by OMG in May 06 Diagram Overview & Language Concepts4/15/2008 Copyright 2006-2008 by Object Management Between SysML and UMLUML 2 UMLreused bySysML(UML4 SysML)UMLnot requiredby SysML(UML -UML4 SysML)SysMLextensionsto UML(SysMLProfile)

10 SysMLSysML Extensions-Blocks-Item flows-Value properties-Allocations-Requirements-Para metrics-Continuous 2006-2008 by Object Management Diagram TaxonomySysML DiagramStructureDiagramBehaviorDiagramUs e CaseDiagramActivityDiagramInternal BlockDiagramBlock DefinitionDiagramSequenceDiagramState MachineDiagramParametricDiagramRequireme ntDiagramModified from UML 2 New diagram typePackage DiagramSame as UML 24/15/2008 Copyright 2006-2008 by Object Management Pillars of SysML ABS Example1. Structure2. Behavior3. Requirements4. Parametricssd ABS_ActivationSequence [Sequence Diagram]d1:TractionDetectorm1:BrakeModul atordetTrkLos()modBrkFrc()sendSignal()mo dBrkFrc(traction_signal:boolean)sendAck( )interactionstate machinestm TireTraction [State Diagram]GrippingSlippingLossOfTractionRe gainTractionactivity/function4/15/2008 Copyright 2006-2008 by Object Management Diagram Frames Each SysML diagram represents a model element Each SysML Diagram must have a Diagram Frame Diagram context is indicated in the header: Diagram kind (act, bdd, ibd, sd, etc.)