TABLE OF CONTENTS This chapter provides essential rules, principles, and style guidelines for composing UML deployment or environment models within the context of the roadmap, including deployment diagrams and their elements. Deployment modeling is concerned with the environment dimension of a system how the implementation or implemented system resides in its environment and is used for system, subsystem, and class implementation within the roadmap to capture in an implementation model how the construct is packaged or implemented and how it resides in its environment. An implementation model consists of component and deployment diagrams and their model elements. Our goal, in this chapter, is to gain more depth in understanding the UML notation and the road-map concerning the environment aspect of implementation models.
A deployment diagram depicts how an implementation or implemented entity resides in its environment using nodes and their relationships, that is, its run-time configuration. Generally, a component that does not exist at run-time because it is compiled away does not appear on a deployment diagram. An entity is a classifier, for example, a system, subsystem, or class. Both component and deployment diagrams are called implementation diagrams.
A node is a resource in the execution environment on which components reside. A node is depicted as a three-dimensional cube figure. A node should be named using a noun phrase and described in a way that captures the node's characteristics.
Figure 9.1 shows a generic node for the Project Management System, and Figure 9.2 shows a specific node for the Project...
