ABSTRACT
This chapter introduces all Unified Modeling Language diagrams in version 2.5. The UML, however, does not dictate the sequence in which the diagrams can be produced. That sequencing is the responsibility of a software development process. The nature of the UML diagrams is understood as follows: structural versus behavioural and Static versus dynamic. The state machine diagram of the UML has the ability to represent time precisely and in a real-time fashion. Deployment diagrams are structural and static in nature. Unlike all other diagrams in the UML, deployment diagrams are the only "hardware" diagrams in UML. A package is a collection of logically cohesive artifacts and diagrams of the UML. Package diagrams therefore only show the top view–a bird's-eye view–of the system organization. Timing diagrams were introduced in the later versions of the UML. The underlying metamodel of the UML allows it to be applied to various situations.
