You are previewing SysML Distilled: A Brief Guide to the Systems Modeling Language.
O'Reilly logo
SysML Distilled: A Brief Guide to the Systems Modeling Language

Book Description

The Systems Modeling Language (SysML) extends UML with powerful systems engineering capabilities for modeling a wider spectrum of systems and capturing all aspects of a system’s design.  SysML Distilled is the first clear, concise guide for everyone who wants to start creating effective SysML models.

(Drawing on his pioneering experience at Lockheed Martin and NASA, Lenny Delligatti illuminates SysML’s core components and provides practical advice to help you create good models and good designs. Delligatti begins with an easy-to-understand overview of Model-Based Systems Engineering (MBSE) and an explanation of how SysML enables effective system specification, analysis, design, optimization, verification, and validation. Next, he shows how to use all nine types of SysML diagrams, even if you have no previous experience with modeling languages. A case study running through the text demonstrates the use of SysML in modeling a complex, real-world sociotechnical system.

Modeled after Martin Fowler’s classic UML Distilled, Delligatti’s indispensable guide quickly teaches you what you need to know to get started and helps you deepen your knowledge incrementally as the need arises. Like SysML itself, the book is method independent and is designed to support whatever processes, procedures, and tools you already use.

Coverage Includes

  • Why SysML was created and the business case for using it

  • Quickly putting SysML to practical use

  • What to know before you start a SysML modeling project

  • Essential concepts that apply to all SysML diagrams

  • SysML diagram elements and relationships

  • Diagramming block definitions, internal structures, use cases, activities, interactions, state machines, constraints, requirements, and packages

  • Using allocations to define mappings among elements across a model

  • SysML notation tables, version changes, and sources for more information

  • Table of Contents

    1. Title Page
    2. Copyright Page
    3. Praise for SysML Distilled
    4. Contents
    5. Foreword by Rick Steiner
    6. Foreword by Richard Soley
      1. Technology Take-Up Takes Time
    7. Preface
      1. Who Should Read This Book?
      2. Structure of the Book
    8. Acknowledgments
    9. About the Author
    10. Chapter 1. Overview of Model-Based Systems Engineering
      1. 1.1. What Is MBSE?
      2. 1.2. The Three Pillars of MBSE
      3. 1.3. The Myth of MBSE
      4. Summary
    11. Chapter 2. Overview of the Systems Modeling Language
      1. 2.1. What SysML Is—and Isn’t
      2. 2.2. Yes, SysML Is Based on UML—but You Can Start with SysML
      3. 2.3. SysML Diagram Overview
      4. 2.4. General Diagram Concepts
      5. Summary
    12. Chapter 3. Block Definition Diagrams
      1. 3.1. Purpose
      2. 3.2. When Should You Create a BDD?
      3. 3.3. The BDD Frame
      4. 3.4. Blocks
      5. 3.5. Associations: Another Notation for a Property
      6. 3.6. Generalizations
      7. 3.7. Dependencies
      8. 3.8. Actors
      9. 3.9. Value Types
      10. 3.10. Constraint Blocks
      11. 3.11. Comments
      12. Summary
    13. Chapter 4. Internal Block Diagrams
      1. 4.1. Purpose
      2. 4.2. When Should You Create an IBD?
      3. 4.3. Blocks, Revisited
      4. 4.4. The IBD Frame
      5. 4.5. BDDs and IBDs: Complementary Views of a Block
      6. 4.6. Part Properties
      7. 4.7. Reference Properties
      8. 4.8. Connectors
      9. 4.9. Item Flows
      10. 4.10. Nested Parts and References
      11. Summary
    14. Chapter 5. Use Case Diagrams
      1. 5.1. Purpose
      2. 5.2. When Should You Create a Use Case Diagram?
      3. 5.3. Wait! What’s a Use Case?
      4. 5.4. The Use Case Diagram Frame
      5. 5.5. Use Cases
      6. 5.6. System Boundary
      7. 5.7. Actors
      8. 5.8. Associating Actors with Use Cases
      9. 5.9. Base Use Cases
      10. 5.10. Included Use Cases
      11. 5.11. Extending Use Cases
      12. Summary
    15. Chapter 6. Activity Diagrams
      1. 6.1. Purpose
      2. 6.2. When Should You Create an Activity Diagram?
      3. 6.3. The Activity Diagram Frame
      4. 6.4. A Word About Token Flow
      5. 6.5. Actions: The Basics
      6. 6.6. Object Nodes
      7. 6.7. Edges
      8. 6.8. Actions, Revisited
      9. 6.9. Control Nodes
      10. 6.10. Activity Partitions: Allocating Behaviors to Structures
      11. Summary
    16. Chapter 7. Sequence Diagrams
      1. 7.1. Purpose
      2. 7.2. When Should You Create a Sequence Diagram?
      3. 7.3. The Sequence Diagram Frame
      4. 7.4. Lifelines
      5. 7.5. Messages
      6. 7.6. Destruction Occurrences
      7. 7.7. Execution Specifications
      8. 7.8. Constraints
      9. 7.9. Combined Fragments
      10. 7.10. Interaction Uses
      11. Summary
    17. Chapter 8. State Machine Diagrams
      1. 8.1. Purpose
      2. 8.2. When Should You Create a State Machine Diagram?
      3. 8.3. The State Machine Diagram Frame
      4. 8.4. States
      5. 8.5. Transitions
      6. 8.6. Pseudostates
      7. 8.7. Regions
      8. Summary
    18. Chapter 9. Parametric Diagrams
      1. 9.1. Purpose
      2. 9.2. When Should You Create a Parametric Diagram?
      3. 9.3. Blocks, Revisited
      4. 9.4. The Parametric Diagram Frame
      5. 9.5. Constraint Properties
      6. 9.6. Constraint Parameters
      7. 9.7. Value Properties
      8. 9.8. Binding Connectors
      9. Summary
    19. Chapter 10. Package Diagrams
      1. 10.1. Purpose
      2. 10.2. When Should You Create a Package Diagram?
      3. 10.3. The Package Diagram Frame
      4. 10.4. Notations for Namespace Containment
      5. 10.5. Dependencies Between Packages
      6. 10.6. Importing Packages
      7. 10.7. Specialized Packages
      8. 10.8. Shades of Gray: Are You Looking at a Package Diagram, or a Block Definition Diagram?
      9. Summary
    20. Chapter 11. Requirements Diagrams
      1. 11.1. Purpose
      2. 11.2. When Should You Create a Requirements Diagram?
      3. 11.3. The Requirements Diagram Frame
      4. 11.4. Requirements
      5. 11.5. Requirements Relationships
      6. 11.6. Notations for Requirements Relationships
      7. 11.7. Rationale
      8. Summary
    21. Chapter 12. Allocations: Cross-Cutting Relationships
      1. 12.1. Purpose
      2. 12.2. There’s No Such Thing as an Allocation Diagram
      3. 12.3. Uses for Allocation Relationships
      4. 12.4. Notations for Allocation Relationships
      5. 12.5. Rationale
      6. Summary
    22. Appendix A. SysML Notation Desk Reference
    23. Appendix B. Changes Between SysML Versions
    24. Bibliography