1 / 29

SysML Awareness

SysML Awareness. John Davies BSc, PhD, CEng, FIET. Objectives. Why am I here? To raise awareness of the SysML To show you some of the features of SysML To try and explain the benefits of using the SysML. But I am not an expert I am not a tool vendor I think SysML is important.

merrill
Download Presentation

SysML Awareness

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SysML Awareness John Davies BSc, PhD, CEng, FIET.

  2. Objectives • Why am I here? • To raise awareness of the SysML • To show you some of the features of SysML • To try and explain the benefits of using the SysML. • But • I am not an expert • I am not a tool vendor • I think SysML is important

  3. Introduction: • What is it ? • The Systems Modelling Language • What is it used for ? • Modelling System Designs ! • What is it like ? • A bit like UML (The Unified Modelling Language)

  4. History • Since late 90’s – UML has become a widely used as a general purpose visual modelling language with software engineers, • Up to then it had a Software focus • In 2003 the Object Management Group (OMG) decided to pursue UML for systems engineering, with a request for proposals. • The SysML group were successful, proposing a language based on UML 2.0. • Currently SysML 1.0 is in its approval loop

  5. Where to find SysML

  6. SysML Goals: • To provide a “standard modelling language for systems engineering • Allow systems engineers to: • Analyse, Specify, Design, and Verify complex systems. • To improve communications between: • Engineering Disciplines, i.e. Systems, Software, Hardware • Engineering Tools • To use UML 2.0 as much as possible and avoid making unnecessary changes.

  7. Who is involved in defining SysML • American Systems Corporation • ARTISAN Software Tools • BAE SYSTEMS • The Boeing Company • Ceira Technologies • Deere & Company • EADS Astrium GmbH • EmbeddedPlus Engineering • Eurostep Group AB • Gentleware AG • I-Logix, Inc. • International Business Machines • International Council on Systems Engineering • Israel Aircraft Industries • Lockheed Martin Corporation • Motorola, Inc. • Northrop Grumman • oose.de Dienstleistungen für innovative Informatik GmbH • PivotPoint Technology Corporation • Raytheon Company • Telelogic AB • THALES

  8. Basic System Design • Define the system boundary/context • Identify what the system has to do • Identify the major parts of the system • Identify/allocate which part does what • Check that the parts working together achieve the overall needs of the system

  9. Why is System Engineering/Design different to Software Engineering/Design? • Starts from ‘Woolly ideas’ – ‘Concepts’ • Low level of ‘design maturity’ • Need to work with • Context • Partitioning – to sub-systems • High-level Functionality • Allocation • Interfaces At an early stage • Need to deal with trade-offs • Need to consider ‘physical’ aspects – eg Submarines • Need to cover performance, reliability, - ‘ilities’.

  10. Satisfies Satisfies Where does SysML fit in Systems of Systems Architecture Modelling Supports Models SysML System Design UML Models Software Design

  11. From UML to SysML. • UML • collation of Object-Oriented methods and diagrams • UML 2.0 • improved, better defined, meta-model • Standard application/extension mechanisms ‘Profiles’ • SysML • Defined ‘Profile’ for Systems Engineering • Uses sub-set of ‘Standard’ UML 2.0 plus specific extensions for Systems Engineering

  12. UML 1.x Diagrams Diagram Structure Behaviour Class Component Object Activity Use Case State Machine Deployment Package Interaction Sequence Communication UML 1.x

  13. UML 2.0 Diagrams SysML Diagram Structure Behaviour Class Component Object Activity Use Case State Machine Composite Structure Deployment Package Interaction Sequence Communication UML 1.x UML 2.0 Interaction Overview Timing

  14. SysML Diagrams SysML Diagram Structure SysML: Parametric Behaviour SysML: Requirements Activity Use Case State Machine SysML: Block Definition SysML Internal Block Package Interaction UML 1.x Sequence UML 2.0 SysML:

  15. New Diagrams • Requirements Diagrams • Requirements hierarchies • Requirements tracing diagrams • Overlap with Requirements Management Tools – but may be needed on some projects • ‘Two-way’ exchange with Requirements Management Tools • Parametric Diagrams • Parameter equations/ Constraints /Parameter limits • E.g Time to react to an incoming threat • Detection/Identification: power/time/resolution • Assessment/allocation/fire control • Weapon fire/transit time to target • Range/speed of target • Block Diagrams • Structure diagram for System Elements • Can use for different structures • Physical structure • System/sub-system structure • Security structure • Etc.

  16. Extended Diagrams • Activity Diagram • Allocation added - identify ‘who does what’ • Timing Diagram • Allocation added - as above • State Machine Diagram • Can have more than one machine on the diagram

  17. Standard – Use Case DiagramsWhat the system needs to do.

  18. Extended Activity DiagramsSwim-lanes to identify who does what.

  19. New Block Diagram – System Architecture

  20. New Requirements Diagram.

  21. New Parametric Diagrams.

  22. Some Issues • What ‘level’ to use SysML • Illustration • Supporting information • Complete specification • How to show • ‘This is the general overview’ • and ‘This is the refined/detailed view’ • in the same model • Which diagrams to use on a specific project • Don’t need to use them all • But need to get a ‘complete picture’ • How to link to other Systems Activities

  23. Tool Suppliers • Established tool vendors for UML • Artisan Studio • Telelogic – Tau G2 • Sparx Systems • ….. • All support ‘most’ in SysML • Some generalised diagrams can be applied for specific use

  24. In Conclusion • SysML is the emergent standard for Systems Design • Version 1.0 awaiting approval • Tool support available • from Standard UML 2.0 tool vendors • System Design is not all of Systems Engineering • but SysML will improve things…

  25. Thank you

More Related