A Practical Guide to SysML: The Systems Modeling Language

by Sanford Friedenthal, Alan Moore, Rick Steiner

A Practical Guide to The Systems Modeling Language is a comprehensive guide to SysML for systems and software engineers. It provides an advanced and practical resource for modeling systems with SysML. The source describes the modeling language and offers information about employing SysML in transitioning an organization or project to model-based systems engineering. The book also presents various examples to help readers understand the OMG Systems Modeling Professional (OCSMP) Certification Program. The text is organized into four parts. The first part provides an overview of systems engineering. It explains the model-based approach by comparing it with the document-based approach and providing the modeling principles. The overview of SYsML is also discussed. The second part of the book covers a comprehensive description of the language. It discusses the main concepts of model organization, parametrics, blocks, use cases, interactions, requirements, allocations, and profiles. The third part presents examples that illustrate how SysML supports different model-based procedures. The last part discusses how to transition and deploy SysML into an organization or project. It explains the integration of SysML into a systems development environment. Furthermore, it describes the category of data that are exchanged between a SysML tool and other types of tools, and the types of exchange mechanisms that can be used. It also covers the criteria that must be considered when selecting a SysML. Software and systems engineers, programmers, IT practitioners, experts, and non-experts will find this book useful.*The authoritative guide for understanding and applying SysML*Authored by the foremost experts on the language*Language description, examples, and quick reference guide included

Genres: Reference

576 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.

[Zhi Han]

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