Overview

If language is not correct, then what is said is not what is meant.

( Confucius)

UML had originally been developed to create models for software systems. The word unified stands for the claim that the language can be used for software systems of a large number of different domains from business and economics systems to the development of standard software products to technical systems, such as an airbag control. The language uses controlled extension mechanisms (stereotypes) to let you adapt it to your domain, so that UML actually lives up to that claim.

At the latest since the introduction of Version 2.0, the term unified has had a more ample meaning. Since then, the target groups include not only the large number of different software development domains, but also neighboring disciplines, such as business process modeling [33] and systems engineering. Again, UML lives up to the claim to be truly unified. Of course there are limits. For example, UML is suitable for systems engineering. However, Systems Modeling Language (SysML) is much more closer to systems engineering, as you will see further on in this book.

UML is not a Babylonian language. You shouldn't give in to your inclination to try expressing everything in UML. However, to make sure you can maintain a complete model altogether, for example, you can integrate a general element a "placeholder" in your model. The details of this placeholder are described outside the model. One good example is requirements that are usually described...