For this, readers should refer to RUP’s project management discipline and Bittner’s book just cited.
UML
Knowledge of the basics of UML is assumed. Readers should be familiar with the basic structure and behavioral diagrams in UML, and should know the pieces that make up the diagrams. They should have knowledge of the basic entities of UML such as classes, operations, use cases.21
SysML
This book assumes basic knowledge of SysML.22
The most important parts of SysML to be considered in this book are:
Requirements modeling
Structure modeling with blocks
Parametrics
The use of SysML is not required to get benefits from MDSD; however, MDSD is optimized by using SysML semantics and capabilities. SysML was created with the intent to provide richer semantics for systems than UML provides. Some of the central issues that MDSD addresses were drivers behind important semantics in SysML. We will provide discussion of these as they occur in this book.
How the book is organized
This chapter provides an introduction to MDSD. Chapter 2 covers definitions, design points and key concepts, while Chapters 3, 4, and 5 cover the core of MDSD. Chapter 6 discusses model structure and use of Rational Systems Developer to create MDSD artifacts. Chapter 7 gives an overview of those SysML concepts required for MDSD, and suggestions for using SysML with MDSD. These can be read independently, while Chapters 2, 3, 4, and 5 stand as a virtual unit.
21There is no lack of material available on UML. A good starting point might be Martin Fowler, UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3rd edition, 2003. The standard references are James Rumbaugh, Ivar Jacobsen, and Grady Booch, Unified Modeling Language Reference Manual, 2004, and Grady Booch, James Rumbaugh, and Ivar Jacobsen, Unified Modeling Language User Guide, 2005
22The Object Management Group developed and manages the SysML specification: http://www.omgsysml.org
16Model Driven Systems Development with Rational Products
