CST205 OBJECT ORIENTED
PROGRAMMING USING
JAVA
MODULE 1
Object Modeling Using Unified
Modeling Language (UML)
Unified Modeling Language (UML)
UML (Unified Modeling Language) is a general-purpose,
graphical modeling language in the field of Software Engineering
UML is used to specify, visualize, construct, and document the
artifacts (major elements) of the software system
UML is a visual language for developing software blue prints
(designs). A blue print or design represents the model.
For example, while constructing buildings, a designer or
architect develops the building blueprints. Similarly, we can also
develop blue prints for a software system.
UML is the most commonly and frequently used language for
building software system blueprints
UML is not a programming language, it is rather a visual
language
UML
The UML has the following features:
1. It is a generalized modeling language.
2. It is distinct from other programming languages like C+
+, Python, etc.
3. It is interrelated to object-oriented analysis and design.
4. It is used to visualize the workflow of the system.
5. It is a pictorial language, used to generate powerful
modeling artifact
Diagrams in UML can be broadly classified as:
◦ Structure Diagrams : Capture static aspects or
structure of a system
◦ Behavior Diagrams: Capture dynamic aspects or
behavior of the system
1. USE CASE MODEL / USE CASE DIAGRAM
The purpose of a use case diagram in UML is to
demonstrate the different ways that a user might
interact with a system.
It captures the dynamic behavior of a live system.A use
case diagram can summarize the details of your
system's users (also known as actors) and their
interactions with the system.
To build a use case diagram, we will use a set of
specialized symbols and connectors
A use case diagram doesn't go into a lot of detail, but it
depicts a high-level overview of the relationship
between use cases, actors, and systems.
PURPOSE OF USE CASE DIAGRAM
Developed in early stages of development
Specify the context of a system
Capture the requirements of a system
Validate a system architecture
Drive implementation and generate test
cases
Developed by analysts together with
domain experts
A use-case model is a model of how different types
of users interact with the system to solve a problem
Use case diagram components
• Actors: The users that interact with a system. An
actor can be a person, an organization, or an outside
system that interacts with your application or system.
They must be external objects that produce or
consume data.
• System: A specific sequence of actions and
interactions between actors and the system. A system
may also be referred to as a scenario
• Goals: The end result of most use cases. A
successful diagram should describe the activities and
variants used to reach the goal.
Use case diagram symbols and notation
1. Use cases
• Horizontally shaped ovals that represent the
different uses(system function) that a user
might have
• A use case represents a distinct functionality
of a system, a component, a package, or a
class
Each Actor must be linked to a usecase,
while some use cases may not be linked to
actors
2. Actors
•Stick figures that represent the people actually
employing the use cases.
• A user is the best example of an actor
• One actor can be associated with multiple use
cases in the system.
Actor triggers use cases
Actor has a responsibility toward a system(inputs)
and Actor has expectations from the system
(outputs)
User can play different roles
Eg:A professor can be an instructor as well as a
researcher.
3. Associations
• A line between actors and use cases
• In complex diagrams, it is important to
know which actors are associated with which
use cases.
4. System boundary boxes
• A box that sets a system scope to use cases
• All use cases outside the box would be
considered outside the
scope of that system.
5. Packages
• A UML shape that allows you to put different
elements into groups
• Just as with component diagrams, these
groupings are represented as file folders.
PURPOSES OF USE CASE DIAGRAM
Used to gather the requirements of a system.
Used to get an outside view of a system.
Identify the external and internal factors
influencing the system.
Show the interaction among the requirements
and actors
Association between Actor and a
use case.
An actor must be associated with at least one use case
An actor can be associated with multiple use cases
Multiple actors can be associated with a single use case
Extend Relationship Between Two Use
Cases
