TABLE OF CONTENTS This chapter provides essential rules, principles, and style guidelines for composing UML component or implementation models within the context of the roadmap, including component diagrams and their elements. Component modeling is concerned with modeling the implementation dimension of a system how a system is implemented 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 roadmap concerning the implementation aspect of implementation models.
A component diagram depicts the implementation of an entity using components and their relationships, that is, its implementation-time configuration. Generally, a component diagram only has a type form and not an instance form; however, "degenerate" deployment diagrams are used to show component instances. An entity is a classifier, for example, a system, subsystem, or class. Both component and deployment diagrams are called implementation diagrams.
An artifact is a physical element of information that is produced or consumed by a software development process, including models, source files, object files, executable files, scripts, and so forth. An artifact is depicted as a stereotyped classifier. An artifact may have features. An artifact should be named using a noun phrase and described in a way that captures the artifact's characteristics.
A classifier may be stereotyped with...
