Overview

People who speak too many languages usually don't say much in any of them.

( Peter Ustinov)

Together, the stereotypes discussed in this chapter form the SYSMOD engineering profile required for the SYSMOD approach discussed in this book (Chapter 2). You will most likely introduce additional stereotypes and define an individual profile in your own projects. Depending on the domain, such as aeronautics, for example, and the development process or model simulation used, each project requires its own modeling vocabulary in the form of stereotypes and profiles. The SYSMOD profile is generic, forming a good starting platform for your own project-specific profiles.

The profile extends the SysML language. If you want to use UML only, rather than SysML, you have to additionally use the SysML stereotypes on which this profile depends. For example, the domain stereotype is a specialization of the SysML stereotype block which, in turn, is an extension of the UML element class.

The UML extension mechanism for stereotypes is discussed in Section 3.10.2. Each good SysML/UML tool supports this form of language extension. Ideally, the profile can be developed independently and used for your respective project model.

Many modeling tools come with various stereotypes. Unfortunately, they are not always explained and often mixed among the pure SysML/UML elements so that it is difficult for developers to see whether they are looking at a pure language element or a stereotype. The situation in the literature is similar. This is why I knowingly paid...