Skip to main content
View Cart

A Practical Guide to SysML

The Systems Modeling Language

  • 1st Edition - July 24, 2008
  • Latest edition
  • Authors: Sanford Friedenthal, Alan Moore, Rick Steiner
  • Language: English

Systems engineers must understand how all the parts of a digital system work together, including hardware AND software. SysML is the first design language to cover both hardware… Read more

Early spring sale

Nurture your knowledge

Grow your expertise with up to 25% off trusted resources.

Shop now

Description

Systems engineers must understand how all the parts of a digital system work together, including hardware AND software. SysML is the first design language to cover both hardware and software, allowing engineers to consider how all the parts of a system will successfully interact, from the very beginning of a project. This can prevent huge problems and delays down the line. Therefore, SysML use is becoming a widespread phenomenon, and many companies, especially in the defense, automotive, aerospace, medical device and telecommunications industries, are already using SysML, or are planning to switch over in the near future. Until now, little consolidated information has been available on the market regarding SysML. However, this book changes all that! It provides the hundreds of thousands of new users with a comprehensive guide to SysML, including a full description of the language itself, detailed instructions on how to implement it, exercises to help readers gain practical experience working with SysML, and extensive, real-world examples of actual successful projects, demonstrating all the benefits SysML can provide.

Key features

  • The authoritative guide for understanding and applying SysML
  • Authored by the foremost experts on the language
  • Language description, examples, and quick reference guide included

Readership

Systems Engineers and Software Engineers, Designers and Programmers, Particularly the intersection between these two groups, often termed "Systems Software Engineers"

Table of contents

Part I Introduction1 Systems Engineering Overview1.1 Motivation for Systems Engineering1.2 The Systems Engineering Process1.3 Typical Application of the Systems Engineering Process1.4 Multi-Disciplinary Systems Engineering Team1.5 Codifying Systems Engineering Practice through Standards1.6 Summary1.7 Questions2 Model-Based Systems Engineering2.1 Contrasting the Document-Based and Model-Based Approach2.2 Modeling Principles2.3 Summary2.4 Questions3 SysML Language Overview3.1 SysML Purpose and Key Features3.2 SysML Diagrams Overview3.3 Using SysML in Support of MBSE3.4 A Simple Example Using SysML for an Automobile Design3.5 Summary3.6 QuestionsPart II Language Description4. SysML Language Architecture4.1 The OMG SysML Language Specification4.2 The Architecture of the SysML Language4.3 SysML Diagrams4.4 The Surveillance System Case Study4.5 Chapter Organization for Part II4.6 Questions5 Organizing the Model with Packages5.1 Overview5.2 The Package Diagram5.3 Defining Packages Using a Package Diagram5.4 Organizing a Package Hierarchy5.5 Showing Packageable Elements on a Package Diagram5.6 Packages as Namespaces5.7 Importing Model Elements into Packages5.8 Showing Dependencies Between Packageable Elements5.9 Specifying Views and Viewpoints5.10 Summary5.11 Questions6 Modeling Structure with Blocks6.1 Overview6.2 Modeling Blocks on a Block Definition Diagram6.3 Modeling the Structure and Characteristics of Blocks Using Properties6.4 Modeling Block Interfaces Using Ports and Flows6.5 Modeling Block Behavior6.6 Modeling Classification Hierarchies Using Generalization6.7 Summary6.8 Questions7 Modeling Constraints with Parametrics7.1 Overview7.2 Using Constraint Expressions to Represent System Constraints7.3 Encapsulating Constraints in Constraint Blocks to Enable Reuse7.4 Using Composition to Build Complex Constraint Blocks7.5 Using a Parametric Diagram to Bind Parameters of Constraint Blocks7.6 Constraining Value Properties of a Block7.7 Capturing Values in Block Configurations7.8 Constraining Time-Dependent Properties to Facilitate Time-Based Analysis7.9 Using Constraint Blocks to Constrain Item Flows7.10 Describing an Analysis Context7.11 Modeling Evaluation of Alternatives and Trade Studies7.12 Summary7.13 Questions8 Modeling Flow-Based Behavior with Activities8.1 Overview8.2 The Activity Diagram8.3 Actions—The Foundation of Activities8.4 The Basics of Modeling Activities8.5 Using Object Flows to Describe the Flow of Items Between Actions8.6 Using Control Flows to Specify the Order of Action Execution8.7 Handling Signals and Other Events8.8 Advanced Activity Modeling8.9 Relating Activities to Blocks and Other Behaviors8.10 Modeling Activity Hierarchies using Block Definition Diagrams8.11 Enhanced Functional Flow Block Diagram (EFFBD)8.12 Executing Activities8.13 Summary8.14 Questions9 Modeling Message-Based Behavior with Interactions9.1. Overview9.2. The Sequence Diagram9.3. The Context for Interactions9.4. Using Lifelines to Represent Participants in an Interaction9.5. Exchanging Messages Between Lifelines9.6. Representing Time on a Sequence Diagram9.7. Describing Complex Scenarios Using Combined Fragments9.8. Using Interaction References to Structure Complex Interactions9.9. Decomposing Lifelines to Represent Internal Behavior9.10. Summary9.11. Questions10 Modeling Event-Based Behavior with State Machines10.1 Overview10.2 State Machine Diagram10.3 Specifying States in a State Machine10.4 Transitioning Between States10.5 State Machines and Operation Calls10.6 State Hierarchies10.7 Contrasting Discrete versus Continuous States10.8 Summary10.9 Questions11 Modeling Functionality with Use Cases11.1 Overview11.2 Use Case Diagram11.3 Using Actors to Represent the Users of a System11.4 Using Use Cases to Describe System Functionality11.5 Elaborating Use Cases with Behaviors11.6 Summary11.7 Questions12. Modeling Text-Based Requirements and Their Relationship to Design12.1 Overview12.2 Requirement Diagrams12.3 Representing a Text Requirement in the Model12.4 Types of Requirements Relationships12.5 Representing Cross-Cutting Relationships in SysML Diagrams12.6 Depicting Rationale for Requirement Relationships12.7 Depicting Requirements and Their Relationships in Tables12.8 Modeling Requirement Hierarchies in Packages12.9 Modeling a Requirements Containment Hierarchy12.10 Modeling Requirement Derivation12.11 Asserting a Requirement Is Satisfied12.12 Verifying that a Requirement Is Satisfied12.13 Reducing Requirements Ambiguity Using the Refine Relationship12.14 Using the General-Purpose Trace Relationship12.15 Summary12.16 Questions13. Modeling Cross-Cutting Relationships with Allocations13.1 Overview13.2 Allocation Relationship13.3 Allocation Notation13.4 Types of Allocation13.5 Planning for Reuse: Specifying Definition and Usage in Allocation13.6 Allocating Behavior to Structure Using Functional Allocation13.7 Connecting Functional Flow with Structural Flow Using Functional Flow Allocation13.8 Modeling Allocation Between Independent Structural Hierarchies13.9 Modeling Structural Flow Allocation13.10 Evaluating Allocation Across a User Model13.11 Taking Allocation to the Next Step13.12 Summary13.13 Questions14 Customizing SysML for Specific Domains14.1 Overview14.2 Defining Model Libraries to Provide Reusable Constructs14.3 Defining Stereotypes to Extend Existing SysML Concepts14.4 Extending the SysML Language Using Profiles14.5 Applying Profiles to User Models in Order to Use Stereotypes14.6 Applying Stereotypes When Building a Model14.7 Summary14.8 QuestionsPart III Modeling Examples15 Water Distiller Example Using Functional Analysis15.1 Stating the Problem15.2 Defining the Model-Based Systems Engineering Approach15.3 Organizing the Model15.4 Establishing Requirements15.5 Modeling Behavior15.6 Modeling Structure15.7 Analyzing Peformance15.8 Modifying the Original Design15.9 Summary15.10 Questions16. Residential Security System Example Using the Object-Oriented Systems Engineering Method (OOSEM)16.1 Method Overview16.2 Residential Security Example Overview and Project Setup16.3 Applying the Method to Specify and Design the System16.4 Summary16.5 QuestionsPart IV Transitioning to Model-Based Systems Engineering17. Integrating SysML into a Systems Development Environment17.1 Understanding System Model’s Role in a Systems Development Environment17.2 Integrating the System Modeling Tool with Other Tools17.3 Data Exchange Mechanisms in an Integrated Systems Development Environment17.4 Selecting a System Modeling Tool17.5 Summary17.6 Questions18. Deploying SysML into an Organization18.1 Improvement Process18.2 Summary18.3 Questions

Product details

  • Edition: 1
  • Latest edition
  • Published: July 24, 2008
  • Language: English

About the authors

SF

Sanford Friedenthal

Sanford Friedenthal. Sanford Friedenthal is an industry leader and independent consultant in model-based systems engineering (MBSE). He was formerly a Technical Fellow at Lockheed Martin, where he led the effort to enable Model-Based Systems Development (MBSD) and other advanced practices across the company. Dr. Friedenthal has been a leader of the industry standards effort through the Object Management Group (OMG) and INCOSE to develop the Systems Modeling Language (OMG SysML ®) that was adopted by the OMG in 2007. He is co-author of ‘A Practical Guide to SysML’ and ‘Architecting Spacecraft with SysML’. Dr. Friedenthal more recently co-led the effort to develop the next generation of SysML (v2) and co-chairs the OMG Systems Modeling Community (SMC) to further advance systems modeling practices.
Affiliations and expertise
MBSE Consultant, Reston, VA USA

AM

Alan Moore

Alan Moore is an Architecture Modeling Specialist at The MathWorks. He has extensive experience in the development of real-time and object-oriented methodologies and their application. Alan was co-chair of the OMG's Real-time Analysis and Design Working Group and served as the language architect during the development of SysML.
Affiliations and expertise
Architecture Modeling Specialist, The MathWorks, Ltd.

RS

Rick Steiner

Rick Steiner is an independent consultant focusing on pragmatic application of systems engineering modeling techniques. He culminated his 29 year career at Raytheon as an Engineering Fellow, Raytheon Certified Architect and INCOSE Expert Systems Engineering Professional (ESEP).

Mr. Steiner has been an advocate, consultant, and instructor of model driven systems development for over 20 years. He has served as chief engineer, architect, or lead system modeler for several large scale electronics programs, incorporating the practical application of the OOSEM methodology and generation of Department of Defense Architecture Framework (DoDAF) artifacts from complex system models.

Mr. Steiner has been a key contributor to both the original requirements for SysML and the development of SysML specification. While his main technical contribution has been in the area of allocations, requirements, and the sample problem, Mr. Steiner has also served as co-chair of the SysML Revision Task Force (RTF). He continues to provide frequent tutorials and workshops on SysML and model driven engineering topics at INCOSE events, NDIA conferences, and other corporate engagements.

Affiliations and expertise
Independent Consultant, San Diego, California

View book on ScienceDirect

Read A Practical Guide to SysML on ScienceDirect