16
An Overview
Unified
Modeling
Language
- a set of graphic notation techniques to create visual models of object-oriented software-intensive systems.
- used to specify, visualize, modify, construct and document the artifacts of an object-oriented software-intensive system under development.
Colimay
Lizardo
Macandili
Mangilin
Two Views of System Model
Static view <Structural>
emphasizes the static structure of the system using objects, attributes, operations and relationships.
Dynamic view <Behavioral>
emphasizes the dynamic behavior of the system by showing collaborations among objects and changes to the internal states of objects.
Categorized Hierarchy of UML Diagrams
Structure
Structure Diagram
Diagram
emphasize the things that must be present in the system being modeled
Behaviour
Behavior Diagram
Diagram
emphasize what must happen in the system being modeled
Class
Component
Class Diagram
Diagram
the main building block of object oriented modelling
represent both the main objects, interactions in the application and the classes to be programmed.
Component Diagram
Object
Diagram
-depicts how components are wired together to form larger components and or software systems.
They are used to illustrate the structure of arbitrarily complex systems.
Object Diagram
Diagram
a diagram that shows a complete or partial view of the structure of a modeled system at a specific time.
Profile
Activity
Composite
Profile Diagram
Activity Diagram
Use Case
Diagram
- graphical representations of workflows of stepwise activities and actions with support for choice, iteration and concurrency.
- diagram shows the overall flow of control.
-operates at the metamodel level to show stereotypes as classes with the <<stereotype>> stereotype, and profiles as packages with the<<profile>> stereotype. The extension relation (solid line with closed, filled arrowhead) indicates what metamodel element a given stereotype is extending.
Structure
Deployment
Diagram
Use Case Diagram
Composite Structure Diagram
graphical representation of a user's interaction with the system and depicting the specifications
a type of static structure diagram, that shows the internal structure of a class and the collaborations that this structure makes possible.
Diagram
portray the different types of users of a system and the various ways that they interact with the system
Package
Deployment Diagram
Diagram
models the physical deployment of artifacts on nodes
Package Diagram
Diagram
depicts the dependencies between the packages that make up a model.
Interaction
State
Diagram
Interaction Diagram
emphasize the flow of control and data among the things in the system being modeled.
Machine
Diagram
Sequence
State Machine Diagram
a significantly enhanced realization of the mathematical concept of a finite automaton in computer science applications as expressed in the Unified Modeling Language (UML) notation.
Communication
Sequence Diagram
Diagram
a kind of interaction diagram that shows how processes operate with one another and in what order
shows object interactions arranged in time sequence
Interaction
Communication Diagram
models the interactions between objects or parts in terms of sequenced messages. Communication diagrams represent a combination of information taken from Class, Sequence, and Use Case Diagrams describing both the static structure and dynamic behavior of a system.
Diagram
Overview
Interaction Overview Diagram
Timing
similar to the activity diagram both visualizing a sequence of activities. The difference is that the individual activity in the interaction overview diagram is pictured as a frames, which can contain interaction - or sequence diagrams
Diagram
Timing Diagram
Diagram
used to explore the behaviors of objects throughout a given period of time. A timing diagram is a special form of a sequence diagram. The differences between timing diagram and sequence diagram are the axes are reversed so that the time is increased from left to right and the lifelines are shown in separate compartments arranged vertically.