Uml
Uml
Uml
Contents
Why model ? Principles of modeling What is UML ? Conceptual Model of the UML Building Blocks Rules Common Mechanisms
Introduction to UML
Why Model ?
Analyse the problem-domain simplify reality capture requirements visualize the system in its entirety specify the structure and/or behaviour of the system Design the solution document the solution - in terms of its structure, behaviour, etc.
Introduction to UML
Principles of Modeling
Every model may be expressed at different levels of precision - the same model can be scaled up (or down) to
different granularities.
What is UML ?
UML - Unified Modeling language UML is a modeling language, not a methodology or process Fuses the concepts of the Booch, OMT, OOSE methods Developed by Grady Booch, James Rumbaugh and Ivar Jacobson at Rational Software. Accepted as a standard by the Object Management Group (OMG), in 1997.
Introduction to UML
More on UML...
UML is a modeling language for visualising, specifying, constructing and documenting the artifacts of software systems. Visualising - a picture is worth a thousand
words; a graphical notation articulates and unambiguously communicates the overall view of the system (problem-domain).
Introduction to UML
More on UML...
Specifying - UML provides the means to model
precisely, unambiguously and completely, the system in question.
Introduction to UML
More on UML...
Documenting - every software
project involves a lot of documentation from the inception phase to the deliverables. UML provides the notations for documenting some of these artifacts
Introduction to UML
Building Blocks
Things
Diagrams
Relationships
Class Diagram Object Diagram Use Case Diagram Behaviour Diagram Implementation Diagram
Introduction to UML
Structural Things
The nouns of UML models; usually the static parts of the system in question.
Class - an abstraction of a set of things in the problemdomain that have similar properties and/or functionality. Notation: customer
Introduction to UML
Introduction to UML
Notation:
Introduction to UML
Behavioral Things
The verbs of UML models; usually the dynamic parts of the system in question.
Introduction to UML
Introduction to UML
Grouping Things
The organisational part of the UML model; provides a higher level of abstraction (granularity).
Notation:
Accounts Department
Introduction to UML
Annotational Things
The explanatory part of the UML model; adds information/meaning to the model elements.
Notation:
Introduction to UML
Relationships
Articulates the meaning of the links between things.
Introduction to UML
Relationships (contd.)
Introduction to UML
Relationships (contd.)
Introduction to UML
Diagrams
The graphical presentation of the model. Represented as a connected graph - vertices (things) connected by arcs (relationships). UML includes nine diagrams - each capturing a different dimension of a software-system architecture. Class Diagram Statechart Diagram Object Diagram Activity Diagram Use Case Diagram Component Diagram Sequence Diagram Deployment Diagram Collaboration Diagram
CDAC (Formerly NCST)
Introduction to UML
More on Diagrams...
Introduction to UML
More on Diagrams...
Introduction to UML
More on Diagrams...
Introduction to UML
Dimensions...
. . .of Software Architecture
Structural Implementation View View Class Diagrams Object Diagrams Component Diagrams
User View
Sequence Diagrams Deployment Diagrams Collaboration Diagrams Statechart Diagrams Activity Diagrams Behavioral Environment View View
CDAC (Formerly NCST)
Introduction to UML
Rules
Specify what a well-formed model should look like. The UML has semantic rules for Names Scope Visibility Integrity Execution
Introduction to UML
Common Mechanisms
Mechanisms/elements that apply consistently throughout the language: Specifications Adornments (Notes) Common Divisions Extensibility Mechanisms Stereotypes Tagged values Constraints
Introduction to UML
Adornments
Adorn the model - i.e., enhance the model. Adds to the meaning and/or semantics of the element to which it pertains. Notes are the mechanism provided by UML for adorning a model:
graphical symbol to render constraints, comments, etc. a note that renders only a comment has no semantic impact on the element it is adorning; at most adds meaning to it and/or provides guidelines for implementation.
Introduction to UML
Stereotypes
Used to create new building blocks from existing blocks. New building blocks are domain-specific. A particular abstraction is marked as a stereotype and this stereotype is then used at other places in the model to denote the associated abstraction.
Notation: metaclass
Introduction to UML
Tagged Values
Used to add to the information of the element (not of its instances). Stereotypes help create new building blocks; tagged values help create new attributes. Commonly used to specify information relevant to code generation, configuration management, etc.
Notation: {version=1.4}
Introduction to UML
Constraints
Used to create rules for the model. Rules that impact the semantics of the model, and specify conditions that must be met. Can apply to any element in the model attributes of a class, relationship, etc.
Notation: { incomplete, disjoint }
Introduction to UML
Summary
Modeling captures the system in its entirety, along with the different dimensions of its complexity. Facilitates quick and efficient analysis and design and helps communicate the overall system architecture unambiguously. Principles of modeling lay down that: model must be chosen well model should encapsulate different granularities models can make simplifying assumptions, but not hide important facts no single model can capture all dimensions of the complexity
Introduction to UML
Summary
UML (Unified Modeling Language) is a language that helps analyse and design solutions for softwareintensive systems Developed by Booch, Rumbaugh and Jacobson at Rational Software; subsequently adopted as an open standard by the Object Management Group in 1997. UML is a modeling language for visualising, specifying, constructing and documenting the artifacts of a software system. It is a modeling language and not a methodology or a process.
Introduction to UML
Summary
The conceptual model of the UML comprises the Building Blocks of UML, its Rules and certain Common Mechanisms that are applicable across the entire language. The Building Blocks comprise Things, Relationships and Diagrams. Things are of grouped into 4 categories: structural things, behavioral things, grouping things and annotational things.
Introduction to UML
Summary
Structural things describe the static part of the model and are of seven types: class, interface, collaboration, use case, active class, component, node. Behavioral things describe the dynamic part of the model and are of two types: interaction and state machine.
Packages are included under Grouping things, and Notes under Annotational things
Relationships link things to each other and are of four types: Dependency, Association, Generalisation and Realization.
Introduction to UML
Summary
Diagrams are essentially connected graphs - a set of vertices (things) connected by arcs (relationships). There are several types of diagrams, each one capturing a different dimension of the systems complexity. Diagrams are of nine types: Class Diagram, Object Diagram, Use Case Diagram, Sequence Diagram, Collaboration Diagram, Statechart Diagram, Activity Diagram, Implementation Diagram, Deployment Diagram. The UML has semantic rules for Names of classifiers, Scope of these names, Visibility of these names, and the Integrity and Execution of the model.
Introduction to UML
Summary
Certain common mechanisms apply uniformly across the model. There are four such mechanisms: Specifications, Common Divisions, Adornments, Extensibility Mechanisms. Notes are the most common adornments used, that add to the meaning of a classifier. Extensibility mechanisms include Stereotypes, Tagged values and constraints.
Introduction to UML
References
The Unified Modeling Language User Guide
Grady Booch, James Rumbaugh, Ivar Jacobson Addison-Wesley (International Student Edition)
UML Distilled
Martin Fowler (with Kendall Scott) Addison-Wesley