Systems Modeling Language (SysML) Tutorial

1 OMG Systems Modeling Language (OMG SysML )TutorialSeptember, 2009 Sanford FriedenthalAlan MooreRick Steiner(emails included in references at end)Copyright 2006-2009 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 Available Specification in Nov 08 Revision task force for in process Multiple vendor implementations available This Tutorial is based on the omg SysML available specification (formal/2007-09-01)

2 This Tutorial , the specifications, papers, and vendor info can be found on the omg SysML Website at Refer to A Practical Guide to SysML by Friedenthal, Moore, and Steiner for Language details and reference4/15/2008 Copyright 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 notintended to make you a Systems modeler!

3 You must usethe 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 Class ExerciseMotivation & Background4/15/2008 Copyright 2006-2008 by Object Management Practices for Describing Systems Specifications Interface requirements system design Analysis &

4 Trade-off Test plansMoving from Document centric to Model centric PastFuture4/15/2008 Copyright 2006-2008 by Object Management ModelingStartShiftAccelerateBrakeEngineT ransmissionTransaxleControlInputPowerEqu ationsVehicleDynamicsMassPropertiesModel StructuralModelSafetyModelCostModelRequi rementsIntegrated system Model Must Address Multiple Aspects of a system 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

5 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 Complexity4/15/2008 Copyright 2006-2008 by Object Management at Multiple Levels of the system <TITLE> system Design<TITLE> <META http-equiv="REFRESH"<!--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)

6 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/ActionInf or m at ion Char acte r izat ionSe nding No d eRe ceiving No d eCr iticalFor m atClassLate ncy.

7 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 ingHostCEPYesBinary IAW IDDS ecret xx secs/xx secsxx %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 ingHostCEPYesBinary IAW IDDS ecret xx secs/xx secsxx %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 ackingHostCEPYesBinary IAW IDDS ecret xx secs/xx secsxx %Respond w hen requested OP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsID

8 Change s to s uppor t data fusion and composite trackingHostCEPYesBinary IAW IDDS ecret xx secs/xx secsxx % OP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsNavigation data to suppor t data fusion and composite trackingHostCEPYesBinary IAW IDDS ecret xx secs/xx secsxx %REF:CEC SRS and Host Nav. 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 ackingHostCEPYesBinary IAW IDDS ecret xx secs/xx secsxx %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-HostYesBinary IAW IDDS ecret xx secs/xx secsxx %Changes sent immediatelyOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsComposite Track State Update

9 To support data fusion and com posit e t r ackingCEPHostYesBinary IAW IDDS ecret xx secs/xx secsxx %REF: CEC IDDs for each hostOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsAss ociate d M e asur em e nt Reports to support data fusion and com posite tr ack ingCEPHostYesBinary IAW IDDS ecret xx secs/xx secsxx %REF: CEC A-spec Table 3- 3. SPY onlyOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsIFF As signm e nts to suppor t data fus ion and com pos ite tr ack ingCEPHostYesBinary IAW IDDS ecret xx secs/xx secsxx %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 CEPHostYesBinary IAW IDDS ecret xx secs/xx secsxx %When assigned or changedOP Com m Op Inf oPr ovide SA/Suppor t Engage m e ntsSensor cues to support data

10 Fusion and composite trackingCEPHostYesBinary IAW IDDS ecret xx secs/xx secsxx %REF: CEC A-spec Table 3- 3. 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 R