A Practical Guide to SysML: The Systems Modeling Language

by Sanford Friedenthal, Rick Steiner, Alan Moore

A Practical Guide to SysML, Third Edition, fully updated for SysML version 1.4, provides a comprehensive and practical guide for modeling systems with SysML. With their unique perspective as leading contributors to the language, Friedenthal, Moore, and Steiner provide a full description of the language along with a quick reference guide and practical examples to help you use SysML.

The book begins with guidance on the most commonly used features to help you get started quickly. Part 1 explains the benefits of a model-based approach, providing an overview of the language and how to apply SysML to model systems. Part 2 includes a comprehensive description of SysML that provides a detailed understanding that can serve as a foundation for modeling with SysML, and as a reference for practitioners. Part 3 includes methods for applying model-based systems engineering using SysML to specify and design systems, and how these methods can help manage complexity. Part 4 deals with topics related to transitioning MBSE practice into your organization, including integration of the system model with other engineering models, and strategies for adoption of MBSE.

Learn how and why to deploy MBSE in your organization with an introduction to systems and model-based systems engineering Use SysML to describe systems with this general overview and a detailed description of the Systems Modeling Language Review practical examples of MBSE methodologies to understand their application to specifying and designing a system Includes comprehensive modeling notation tables as an appendix that can be used as a standalone reference

Genres: Reference

599 pages, Kindle Edition

First published July 24, 2008

Reviews

[Bob S. · Rating 5 out of 5]

This was a well-written and informative book. I'm very comfortable with the UML, which has a large overlap with SysML, so the language was easy to pick up. This book was also a moderately entertaining read, in the sense that the examples used were uncommon, given my background in business computer systems; example systems included an automotive sub-system, a water distiller system, as well as surveillance and security systems. I can't even count the number of times I have read texts where the illustrative example was either an account (e.g. bank account) or retail system. Not only did these examples keep the presentation fresh, they really showed off the advantages of SysML.

My purpose in reading this book was essentially to learn what SysML was, why there was a need for it (when we already have UML), and, to a lesser extent, look at an example of a language defined via UML profile. From the Business Analyst perspective, what I found was surprisingly useful.

First, SysML doesn't bother to re-invent the UML. This is an advantage of defining a language by extension. A useful subset of UML is incorporated, mostly as is. To this, SysML adds some missing by essential properties and elements. For example SysML adds support for parametric modeling, so, with the proper tool support, simulations can validate that design options will satisfy constraints.

Most importantly (from a BA perspective), Requirements are added as first-class elements of the model. SysML adds notation for relationships to Requirements, such as containment, satisfaction, and verification. The SysML abstract syntax is as good a starting point for maintaining requirements traceability as I have seen.

This book will prove useful to many types of readers. Obviously those involved in traditional System Engineering projects (airplane design, weapons systems, etc.) will find this a valuable introduction/referance on SysML. Systems modeling is often widely applied, but in an ad hoc fashion, so I would also encourage those in various disciplines to check this book out; SysML could potentially foster cross-disciplinary understanding, but it certainly could inform readers from various systems sub-disciplines (Biology, Geology, Sociology, etc.) of best practices for modelers.

Finally I recommend this book to those within my own field of Business Analysis. Although UML is suficient for modeling many parts of the systems we analyze, it fails to capture some elements of our domain, most notably Requirements. I also have supplemented the UML in my own practice with Data Flow Diagrams (DFDs), especially for defining project scope (the context diagram). This book is the first that I have seen to present a credible alternative notation for this usage, the Internal Block Diagram.

[George Anderson · Rating 3 out of 5]

Necessary reference book for the Sysml language. I found it necessary to read other books to gain more clarity in my understanding of the subject. Sadly very few seem to actually use Sysml but everyone talks about it as if they do.

[Doug · Rating 4 out of 5]

The prose is not deftly written like some other treatments of the topic, but the critical points and details about the language are crystal clear. I'll let you know how good it really is after I get the results of my certification exam back.

[Christian D'Amico · Rating 3 out of 5]

Good book but I don’t necessarily enjoy the order that the topics are presented.

[Zhi Han]

I found only the first part interesting and worth reading. The second part is long and should be used as a reference.