1 / 24

Free Mini Course: Applying SysML with MagicDraw

Free Mini Course: Applying SysML with MagicDraw. UML reused by SysML (UML4SysML). UML 2. SysML. Not required by SysML. SysML’s extensions to UML. What is SysML?. OMG System Modeling Language (SysML) Developed by OMG and INCOSE, and AP233. Adopted by OMG in May ‘06

dorie
Download Presentation

Free Mini Course: Applying SysML with MagicDraw

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. Free Mini Course: Applying SysML with MagicDraw

  2. UML reused by SysML (UML4SysML) UML 2 SysML Not required by SysML SysML’s extensions to UML What is SysML? • OMG System Modeling Language (SysML) • Developed by OMG and INCOSE, and AP233. Adopted by OMG in May ‘06 • Realized as UML subset • http://www.omgsysml.org

  3. What is SysML? • Modeling language that includes 9 diagrams • Dedicated for modeling complex systems that may include: • hardware, • software, • information, • personnel, • procedures, and • facilities. • Being implemented by different tools vendors

  4. SysML Diagram Behavior Diagram Requirement Diagram Structure Diagram Activity Diagram Sequence Diagram State Machine Diagram Use Case Diagram Block Definition Diagram Internal Block Diagram Package Diagram The same as in UML 2 Modified from UML 2 Parametric Diagram New diagram type SysML Diagrams

  5. System Requirements & Business Analysis System Analysis & Design Evaluation & Optimization (V&V) Detailed Design: Software & Hardware System Integration System Implementation SysML in the System Development Process Requirements diagram Use Case Diagram Activity diagram Package diagram Block Definition diagram Activity diagram Sequence diagram State diagram Package diagram Block Definition diagram Internal Block diagram Parametric diagram Sequence diagram State diagram Requirements diagram Use Case diagram Block Definition diagram Internal Block diagram Package diagram

  6. Why Modeling Is Important? • Modeling helps to improve design quality, reduce errors and avoid ambiguity. • Modeling helps to improve communications. • Modeling helps to manage complex systems development: • helps to separate different concerns, • allows hierarchical modeling, • facilitates impact analysis of requirements and design changes, • supports incremental development.

  7. A Case Study: Analyzing User Needs • Analyze user needs by identifying user roles –actors– and associating them to theiruse cases. • With MagicDraw you can document use cases and generate use case documentation from model.

  8. A Case Study: Defining System Requirements • Show system requirements and their relationships with other elements. • Create Use Case diagram to specify functional requirements.

  9. A Case Study: Structural System Decomposition • Prepare package diagramto group your model elements into packages, views and viewpoints. • Establish dependencies between packages and/or model elements within that package. • Viewpoints provide insight to a model using another principle.

  10. A Case Study: Defining Structural Blocks • Show system structureas block components with their properties, operations and relationships.

  11. A Case Study: Modeling Block Structure • Describe the system-containing blocksinternal structure. Show parts, ports and connectors.

  12. A Case Study: Designing Control and Data Flows • Model system behaviorand the way how these behaviors are related. • Describe control and data flow, displaycontinuousbehaviors and continuous data flows

  13. A Case Study: Designing Communications • Model component interactionsfor use case scenarios in order tofind out new methodsin existing blocks or evenblockswith specific responsibilities

  14. A Case Study: Designing State-Based System Behavior • Represent blocklife cycle. • Define system behavioras sequences of states that a component or interaction experience in response to events.

  15. A Case Study: Modeling System Constraints • Model system constraintsbetween structural elements. • Model constraints blocks to capture equations. Use parametric diagrams to represent a usage of the constraints in an analysis context.

  16. A Case Study: Mapping Logical to Physical Model Elements • Represent general relationships that map one model element to another. • Create diagram or dependency matrix to represent allocations!

  17. Learn MagicDraw Features! Increase efficiency of tool usage by learning how to: • Organize your model elements and hyperlink them for easy navigation • Prepare model content diagrams for easy model navigation • Reuse model element in multiple diagrams with different level of details • Document your use case models and generate use case specification • Create system documentation following style guidelines and using layout tools • Validate the model you have created • Decompose large models into independent modules and profiles • Compare model versions and find out changes in model and diagrams • Evaluate your model by calculating model metrics …and much more!

  18. Sample MagicDraw Feature: Comparison of Two Model Versions (1) Added element Deleted elements Modified element – a diagram

  19. Sample MagicDraw Feature: Comparison of Two Model Versions (2) Find out modified parts in diagrams!

  20. Ways to Learn • Choose the most effective way to learn: • Send one or two employees to anopen enrollmentclass! • Order onsite trainingwhen purchasing new MagicDraw licenses! • Consider adding one of our professional services consultants as anon-staff mentorin your first MagicDraw project! • Ask for afree one hour tourfor new functionality demo!

  21. Leading Instructor • Darius has been working with No Magic since 1998. He took part as Java developer in multiple international projects. Darius has developed a modeling case study MagicLibrary and leaded numerous MagicDraw UML training courses and consultations worldwide. He also taught industrial courses on Requirements Management with UML, Software Design with UML, and Java/J2EE Programming. Darius received PhD from Vytautas Magnus University, where he teaches courses Software Development Methodology and Software Engineering. Darius participates frequently in various conferences and gives talks on UML and other software development topics. He holds the following professional certificates: • Microsoft Certified Professional • Sun Certified Programmer for the Java 2 Platform 1.4 • OMG-Certified UML Professional Advanced Dr. Darius Šilingas MagicDraw Training Leader darius.silingas@nomagic.com

  22. Other Instructors • Our world-wide instructor group contains people who all have the following characteristics: • Have experience in software development • Have applied UML in multiple industrial projects • Are experts of MagicDraw UML • Have good communication skills • Are customer-oriented • Believe in modeling • Most of our trainers are either • The best people from MagicDraw development group • The best independent consultants working with MagicDraw • Visit www.magicdraw.com/trainers for trainers description.

  23. Where to Look for More Info Do you need MagicDraw training for just yourself or several employees? Want MagicDraw training for a small group but want to get away? • We are offering you regular open enrollment classes in the USA, Europe, and Asia • Check the online schedule www.magicdraw.com/training for locations and dates • Onsite training is available anywhere in the world with the possibility to customize course to meet best your needs! • Contact training group: training@magicdraw.com • Register online at www.magicdraw.com/registration

  24. The End • Thank You for Attention! • Let’s Keep In Touch: • training@nomagic.com

More Related