Course: Practical systems engineering with the OMG's Systems Modeling Language (SysML) and the MD SysML Plugin for MagicDraw UML.
This content area is UNDER CONSTRUCTION or MIGRATION
A hands-on Webel IT course and workshop held over 5-days.
Contents of: Course: Practical systems engineering with the OMG's Systems Modeling Language (SysML) and the MD SysML Plugin for MagicDraw UML.
- About UML Parsing Analysis and SysML Parsing Analysis for document-driven systems engineering
- People who could benefit from this course:
- Engineers and Technicians developing complex electrical, mechanical, optical, acoustic, radar, and mechatronic systems requiring graphical systems engineering tool support.
- Logistics and Acquisition Managers interested in graphical tracking of systems elements.
- Requirements Analysts, Systems Analysts, Constraints Analysts, and Systems Architects interested in integrated systems engineering tool support and graphical engineering.
- Scientists interested in graphical associative analysis, modelling, and simulation of systems such as scientific beam instruments, complex natural systems, and taxonomies.
- Technical Project Managers interested in highly traceable systems engineering and strongly process-driven development for wide range of existing development methodologies.
- Day 1 | Overview of UML2 and SysML for systems engineering | MagicDraw UML and the MD SysML Plugin |
- Overview of UML2+ and SysML1+ for systems engineering
- Why graphical, associative, port-based, and patch-based "synthesis engineering" is (potentially) so powerful.
- Graphical engineering + Text-based engineering: the best of both worlds
- What is Associative engineering ?
- What UML is and how and why it has been traditionally used “just” for software engineering.
- UML2 Connector: Example: Home Entertainment System progressively "connected up"
- Why UML does not handle some systems engineering tasks and physical systems well.
- UML2 Components: very useful for systems engineering, but NOT formally in SysML.
- What SysML is and why you should consider it for your systems engineering projects.
- Anatomy of the SysML Block element
- Overview of the SysML Diagrams (and the UML Diagrams they are adapted from).
- Some example systems used in this course:
- Example: the SysML specification's Hybrid Sports Utility Vehicle (HSUV)
- Example: port-based engineering example: a modular home entertainment system
- Example: signal processing: the Drancing real-time synthesis accelerometer music system.
- Example: MagicDraw UML and MD SysML: the MagicCastle system.
- Example: the participants' own domain-specific workshop case study.
- Aspects of UML2 useful for systems engineering, and how SysML builds on them
- Ownership of Elements: Packages, Models, and Components as Namespaces.
- UML Classes, UML Properties, and Class Diagrams.
- UML Ports, Connectors, and the EncapulatedClassifier
- The UML Interface as Operations and/or data contract: not only for software systems.
- The UML2 “ball and socket” notation: providing/requiring Interface contracts via Ports
- MagicDraw UML: Interfaces provided/required by predefined Port classes
- Service orientation: MD UML: Class with Ports providing/requiring Interfaces
- Architectural “Dependency wiring” of Interface contracts in MagicDraw UML
- Example: Using an "instance" of a Class with Ports in a higher level system
- UsageContext: plan connections first using architectural Dependency wiring
- Structure compartments in MagicDraw UML Class Diagrams and "hybrid" diagrams
- UML2 Composite Structure diagrams
- The “fork/lollipop” notation for provided/required Interfaces.
- "To Frame or not to Frame ? That is the question !"
- UML InformationFlows for conveying information.
- UML DataTypes as conveyed data tokens
- Power features of MagicDraw UML and the MD SysML Plugin
- SysML stereotypes and MD SysML additional stereotypes
- logical vs. physical in MagicDraw UML 15
- MD SysML: active validation
- UML2 (and the UML specifications) vs. MagicDraw UML vs. MD SysML
- The UML2 Metamodel, the UML specification, and how to (not) read it.
- The UML2 Metamodel in MagicDraw UML specification dialogs.
- The UML2 Metaclasses in MagicDraw UML (and what they are not).
- UML2 Comments: a real and very useful Element (that is stored in the project "repository") !
- UML2 Artifacts: very useful for systems engineering, but NOT formally in SysML.
- UML2 Components: very useful for systems engineering, but NOT formally in SysML.
- UML2 Constraints: defining them, representing them
- UML2 InstanceSpecifications and value Slots: representing value states of systems
- Day 2 | SysML: history, specification, metamodel | structure, flow, quantity, value, configuration, context, time, space |
- Overview of the SysML specification and the OMG's revision process
- The SysML diagrams, elements, profiles, stereotypes, and notations
- Representing structure: the SysML Block, Ports, Connectors
- Representing physical, industrial, and financial quantities in SysML
- Representing value state and modes of complex systems in SysML
- Block definitions for PropertySpecificTypes as instance value carriers
- Example: BirthdayParty BDD: Block and value Property definitions for Definition View
- Example: BirthdayParty IBD
- Example: Child breathes in before inflating Balloon more
- Progressive initialisation of value state using the UML2 Property.defaultValue (in SysML1.1 "initial values")
- Why UML2 InstanceSpecifications can't be used generally for SysML "instance/object views"
- Mathematical Constraints analysis in SysML
- Day 3 | Behavior, State, Requirements, Allocation | Process Management, Project Management, Human Management |
- Modelling Behavior and State in SysML
- SysML extends UML2 Activities and Activity Diagrams
- Why you should always (and I really mean always) use explicit Pins on Activities
- [Advanced] Activities as Classes and “Activity decomposition”.
- [Advanced] Swimlane Allocation
- SysML1.0 adds no additional stereotypes to UML2 StateMachines
- Use Cases in SysML
- Using SysML Requirements
- The normative SysML Requirement
- The very useful non-normative SysML requirement extensions
- Deriving one Requirement from another with SysML DerivedReqt
- Refining descriptions of Requirements with other element types using SysML Refine
- The SysML Satisfy relationship: tracing fulfillment of Requirements
- The SysML Verify relationship, TestCase, and VerdictKind
- [Non-standard] on applying the SysML «requirement» Stereotype to UML2 Components.
- HOWTO elicit SysML Requirements and how to relate them to other elements.
- HOWTO callout SysML requirements metadata into UML notes in MagicDraw UML
- HOWTO use hyperlinks and related elements in MagicDraw to trace between source
- Using SysML for Project Management
- Combining SysML with your favourite systems engineering process
- Modelling development process with Activities
- Hyperlinking from Artifacts to external documents and resources
- Using Stereotypes to carry project metadata
- Stereotype driven development process
- Recording the status of elements and test results as “tagged values”
- Tracking human resources and working groups using Actors
- Generating model reports using MagicDraw UML and MD SysML
- Day 4 | SysML review, MD SysML tips, fun examples, questions | The UML- and SysML Parsing analysis recipes |
- More TIPS for using SysML in MD SysML
- Exploit the powerful hyperlinking and diagram icon facilities of MagicDraw for easy cross-navigation between elements, packages, models and diagrams
- Really very tricky MagicDraw UML tricks
- TIP: Use a BlockPackage or BlockModel to group a Block and supporting elements
- On combining UML and SysML to get the best of both worlds in SysML tools
- SysML Review and Question time
- Every diagram of the SysML Hybrid Sports Utility Vehicle sample problem from the SysML specification (in MD SysML)
- The MD SysML BeerMachine with value state and other fun and interesting examples
- The UML- and SysML Parsing Analysis recipes for sentence-by-sentence systems engineering
- From engineering documents in natural language to understandable SysML models.
- Exercise: choose a source text document (usually a technical description of your system) from your own domain.
- Exercise: choose an interesting source article from the Wikipedia and represent it as a hyperlinked Artifact and source text Stereotype for wrapper Components
- To make the recipe work you need the UML2 Component (not officially in SysML)
- The UML2 Component as logical and graphical «wrapper»
- Hyperlinked “focus diagrams” for «wrapper» Components
- HOWTO trace participation in logical «wrapper» Components: "unwrapping"
- Motto: In MagicDraw UML the Display Related Elements feature is your very good friend.
- Tracing automatically generated ComponentRealizations
- Tracing manually created Dependencies FROM «wrapper» Components TO analysis elements
- HOWTO separate parsing analysis elements and «source» text «wrapper» Components in Models from systems elements in Packages
- Day 5 | Workshops | SysML Parsing Analysis of your own technical document into SysML models | Team presentations, group discussion |
- Workshop | morning | SysML Parsing Analysis of a document of your choice in MD SysML |
- Participants are encouraged to model from their own team, role, and domain perspectives
- There will be the opportunity for freestyle diagramming to prepare a presentation of results.
- Workshop | afternoon | team presentations followed by discussions of each team's SysML models | conclusion |
Gallery group:
Galleries index: Systems Modeling Language (SysML) - Login to post comments
The Doctor is in the house
Drancing air synth for Wiimotes
Tag and Keyword Cloud
Syndicate
