Objectives

In this lesson, you will learn to:

• Identify the need and scope of UML

• Specify the notations for creating the UML diagrams
• Identify the various views of software systems

Lesson 1B /
UML and Requirements Modeling Slide 1 of
26
Overview of UML
• Unified Modeling Language (UML) is a standard language for creating blueprint
that depicts structure and design of the software system.
• You can use UML for modeling systems that can range between enterprise
information systems to distributed Web-based applications.
• There are several tools available, such as Rational Rose, Jude, AgroUML, and
Poseidon, which you can use to design software systems by using UML.

Lesson 1B /
UML and Requirements Modeling Slide 2 of
26
Evolution of UML
• During the mid 1970s and late 1980s:
• Object-oriented modeling languages were developed for analysis and
design of the software.
• The most prominently used languages were:
• Booch’s Booch’93
• Jacobson’s Object Oriented Software Engineering (OOSE)
• Rumbaugh’s Object Modeling Technique-2 (OMT).
• In October 1994, the unification of Booch’93, OMT, and OOSE led to the
release of version 0.9 and 0.91 of UML.

Lesson 1B /
UML and Requirements Modeling Slide 3 of
26
Scope of UML
• Rational Software Corporation defines UML as follows: “The Unified Modeling
Language (UML) is a language for specifying, constructing, visualizing, and
documenting the artifacts of a software-intensive system.”
• Artifacts include requirements, architecture, design in terms of classes, objects
or interfaces, source code, tests, prototypes, and the software releases of a
software system.
• A software-intensive system includes high-end enterprise solutions, such as:
• Banking services
• Distributed Web-based services
• Medical systems
• Insurance

Lesson 1B /
UML and Requirements Modeling Slide 4 of
26
Building Blocks of UML
• UML building blocks include:
• Basic UML constituents: Include the static, dynamic, grouping, and a
notational constituents of UML.
• Relationships: Depict the relations between various constituents of a UML
model.
• Diagrams: Represent the various artifacts of a system graphically.

Lesson 1B /
UML and Requirements Modeling Slide 5 of
26
Defining UML Notations
• UML provides the following nine diagrams to represent the structure and
design of a software system:
• Use case diagrams
• Class diagrams
• Object diagrams
• Collaboration diagrams
• Sequence diagrams
• State diagrams
• Activity diagrams
• Component diagrams
• Deployment diagrams

Lesson 1B /
UML and Requirements Modeling Slide 6 of
26
Defining Use Case Diagrams
• A use case diagram:
• Depicts the various operations that a system performs.
• Contains use cases, actors, and their relationships.

Lesson 1B /
UML and Requirements Modeling Slide 7 of
26
Defining Class Diagrams
• A class diagram represents a set of classes, interfaces, and their relationships.

Lesson 1B /
UML and Requirements Modeling Slide 8 of
26
Defining Object Diagrams
• An object diagram represents an instance of a class diagram.

Lesson 1B /
UML and Requirements Modeling Slide 9 of
26
Defining Collaboration Diagrams
• Collaboration diagrams represent interaction between objects in the form of
messages.

Lesson 1B /
UML and Requirements Modeling Slide 10 of
26
Defining Sequence Diagrams
• Sequence diagrams represent interaction between objects in the form of
messages ordered in sequence by time.

Lesson 1B /
UML and Requirements Modeling Slide 11 of
26
Defining State Diagrams
• A state diagram shows how a class reacts when an event occurs.

Lesson 1B /
UML and Requirements Modeling Slide 12 of
26
Defining Activity Diagrams
• Activities are a representation of various operations
performed by a class.
• An activity diagram depicts the flow of control from
one activity to another.

Lesson 1B /
UML and Requirements Modeling Slide 13 of
26
Defining Component Diagrams
• You combine packages or individual entities to form components.
• A component diagram depicts various components and their dependencies.

Lesson 1B /
UML and Requirements Modeling Slide 14 of
26
Defining Deployment Diagrams
• A deployment diagram shows the physical placement of components in nodes
over a network.

Lesson 1B /
UML and Requirements Modeling Slide 15 of
26
Associating UML Diagrams with UML
Modeling Techniques
• The four modeling techniques are:
• Requirements modeling: Involves depicting the requirements using use
case diagrams.
• Static modeling: Involves depicting the static constituents of the software
system using the class and object diagrams.
• Dynamic modeling: Involves depicting the behavior of static constituents
using the following diagrams:
• Collaboration diagram
• Sequence diagram
• Activity diagram
• State diagram
• Architectural modeling: Involves depicting the architecture of the software
system into multiple tiers, such as presentation, business, and resource.
Lesson 1B /
UML and Requirements Modeling Slide 16 of
26
Viewing a Software System
Architecture
• The architecture of a software system is defined as an arrangement of the
static and dynamic constituents in a model.
• The various views of a software system are:
• Use case view: Indicates the functionalities that the system offers to each
stakeholder.
• Design view: Focuses on the static and dynamic representation of the
system.
• Process view: Represents various processes executing in a system at a
given instance of time.
• Implementation view: Represents the physical system including files and
components required to assemble the system.
• Deployment view: Represents the hardware components on which the
software system will execute.

Lesson 1B /
UML and Requirements Modeling Slide 17 of
26
The Role of UML in SDLC
• Diagrams developed using UML serve as key documents in each phase of
SDLC.
• The following table lists the UML diagrams that the end users can use in the
requirement analysis phase:

Diagram Role of a Diagram in the Requirement Analysis Phase

Use case Depicts the various users of the system and how they are
going to use the system to meet the requirement objectives

Class Depicts the classes and their dependencies for the primary
requirements of the system
Sequence and Depicts the sequence of steps performed in a process
Collaboration
Activity Depicts the specific activities that are required to understand
the functional requirements of the system
Lesson 1B /
UML and Requirements Modeling Slide 18 of
26
The Role of UML in SDLC
• The following table lists various UML diagrams that you can use in the design
phase:

Diagram Role of a Diagram in SDLC phase

Class Depicts the classes, their attributes and operations, and the
relationship between classes
Sequence Depicts the sequence of interactions between the various objects
of the system
Package Depicts the various classes that are grouped together depending
on their functionality
Deployment Depicts the layout of the software components over the network

State Depicts the state of an object on the occurrence of an event

Component Depicts the components required for executing system

Lesson 1B /
UML and Requirements Modeling Slide 19 of
26
The Role of UML in SDLC
• You use the use case diagram in the test phase.
• The use case diagram depicts the test cases on the basis of which the system
is tested.

Lesson 1B /
UML and Requirements Modeling Slide 20 of
26
Summary
In this lesson, you learned that:

• Unified Modeling Language (UML) is a standard language for creating

blueprint that depicts structure and design of the software system. It is used
to specify, visualize, construct, and document the artifacts of a software
system.
• The building blocks of UML consist of basic constituents, relationships, and
diagrams. The basic constituents include structural, behavioral, grouping,
and annotional constituents.
• The UML diagrams enable you to visualize the software system by graphical
representation of the various constituents.
• The nine UML diagrams are use case, class, object, collaboration, sequence,
state, activity, component, and deployment diagrams.
• The architecture of a software system can be viewed from the different
perspectives of the stakeholders.
• UML diagrams are used in the analysis and design phases of SDLC.
Lesson 1B /
UML and Requirements Modeling Slide 21 of
26