Book Image

UML 2.0 in Action: A project-based tutorial

Book Image

UML 2.0 in Action: A project-based tutorial

Overview of this book

Most books about UML describe it almost in its entirety. Inevitably you're left with only a superficial knowledge of the range of UML elements, without a deep and intuitive understanding of how to apply UML as a whole to real world design problems. This book doesn't set out to cover all of UML, but instead pulls together those parts of UML with immediate practical relevance and presents them as part of a coherent process for using UML in your actual development projects.This book is designed to be read while you work on a real project. After an initial review of the essentials of UML and the design process, it begins with the modeling of a business system and its business processes, in this case an airport. Then the IT system intended to serve that business process is described and analysed. Finally the integration of the system into the production environment is covered in detail. The book can be used in two ways: it can be read through as a thorough grounding in how UML really works in practice; in addition it can be used as stand alone guide to that particular aspect of your own project. Both result in an intuitive understanding of how to actually use UML.
Table of Contents (11 chapters)

5.5 The Static View

The static view describes the structure of business objects that are sent as message arguments from the sender to the receiver of the message (also see Section 5.2, Messages in UML).

The following points should be taken into consideration when modeling business objects:

  • It is important to pay attention to semantic integrity. The structure and content of business objects have to be clear and easy to understand for all involved parties.

  • Information has to be coherent and all involved parties should be able to interpret it.

  • Business objects should be reusable.

  • Business objects have to be complete, so that they satisfy even rarely occurring demands and there is no room for ambiguity.

Different requirements and different modeling approaches lead to different structures of business objects. It is not possible to fulfill all demands simultaneously. The structure and scope of a business object is always a compromise; the ideal business object can never be found.

5.5.1 Elements of the...