UNIT-3 OOAD SEM-4

Q-1 what are the Elements of Use Case Diagrams explain in details.
 Use case diagrams are used to gather the requirements of a system including internal and
external influences.
 These requirements are mostly design requirements.
 So when a system is analyzed to gather its functionalities use cases are prepared and
actors are identified.

Elements of use case diagram:

1. Actor:
 An actor describes any entity (or entities) that perform certain roles in a given system.
 The different roles the actor represents are the actual business roles of users in a given
system.
 An actor in a use case diagram interacts with a use case.
 For example, for banking application, a customer entity represents an actor in the
application.
 Similarly, the person who provides service at the counter is also an actor.
 An actor is shown as a stick figure in a use case diagram depicted "outside" the system
boundary, as shown in the below figure.

2. Use case:
 A use case in a use case diagram is a visual representation of separate business functionality
in a system.
 As the first step in identifying use cases, you should list the discrete business functions in
your problem statement.
 It provides the process of the system.
 Each of these business functions can be classified as a potential use case.
 A use case is shown as an ellipse in a use case diagram.

1
UNIT-3 OOAD SEM-4

3. System boundary:

 A system boundary defines the scope of what a system will be.

 A system cannot have infinite functionality.
 So, it follows that use cases also need to have definitive limits defined.
 A system boundary of a use case diagram defines the limits of the system.
 The system boundary is shown as a rectangle across all the use cases in the system.

 The figure shows the system boundary of the clinic application.

 The use cases of this system are enclosed in a rectangle.
 Note that the actors in the system are outside the system boundary.

4. Relationships between Use-Cases:

A relationship between two use cases is basically a dependency between the two use
cases.
Defining a relationship between two use cases is the decision of the modeler of the use case
diagram.

 Include:

When one use case is represent as using the functionality of another use case in a diagram, this
relationship between the use cases is named as an include relationship.

In an include relationship, a use case includes the functionality described in another use case as a part of
its process flow.

An include relationship is depicted with a directed arrow having a dotted shaft.

2
UNIT-3 OOAD SEM-4

Ex.: one would not confirm the patient record without making an appointment.

 The stereotype "<<include>>" identifies the relationship as an include relationship.

 Extend:

 In an extend relationship between two use cases, the child use case adds to the existing
functionality and characteristics of the parent use case.
 An extend relationship is depicted with a directed arrow having a dotted shaft, similar to the
include relationship.
 The stereotype "<<extend>>" identifies the relationship as an extend relationship.

5. Relationship between Actors:

The only relationship allowed between actors on use case diagram is Generalization.
This is useful in defining overlapping roles between actors.

3
UNIT-3 OOAD SEM-4

Q-2 Explain Class diagram in details.

The class diagram is a static diagram.

It represents the static view of an application.

Class diagram is not only used for visualizing, describing and documenting
different part of a system but also for constructing executable code of the
software application.

The class diagram describes the attributes and operations of a class on the
system.

The class diagrams are generally used in the modeling of object oriented
systems because they are the only UML diagrams which can be drawing directly
with object oriented languages.

Purpose:

The purpose of the class diagram is to model the static view of an

application.

Analysis and design of the static view of an application.

* Elements:
1. Class

A class is a collection of Objects, attributes and operations.

Examples of classes are passengers, planes, or tickets.

2. Attribute

An attribute of a class represents a characteristic of a class.

4
UNIT-3 OOAD SEM-4

Characteristics of a passenger, for example, are name and age.

3. Generalization

Generalization is a relationship between two classes: a general class and a special

class:

4. Association

An association represents a relationship between two classes:

An association indicates that objects of one class have a relationship with objects
of another class.

5. Multiplicity
A multiplicity allows for statements about the number of objects that are involved
in an association.

6. Aggregation
An aggregation is a special case of an association, It provide whole/part
relationship.

In aggregation, if Whole is destroyed, its part will not destroy.

5
UNIT-3 OOAD SEM-4

Q-3 Explain Object Diagram in details.

 Object diagrams are derived from class diagrams so object diagrams are
dependent upon class diagrams.
 Object diagrams represent an example of a class diagram.
 The basic concepts are similar for class diagrams and object diagrams.
 The difference is that a class diagram represents an abstract model consisting
of classes and their relationships. But an object diagram represents an
instance at a particular moment which is concrete in nature.
 Object diagrams are used to give a set of objects and their relationships as an
instance.
 It means the object diagram is more close to the actual system behavior .the
purpose of the object diagram can be summarized as:
 Object relationships of a system.
 Static view of an interaction.
 Understand object behavior and their relationship from practical
perspective.

6
UNIT-3 OOAD SEM-4

Object Diagram for Customer Order:

7
UNIT-3 OOAD SEM-4

Q-4 Explain Benefits of Use Case diagram.

The use case diagram provides a comprehensive summary of the whole
software system in a single illustration.
Another major advantage of use case modeling is that it requires the
identification of exceptional scenarios for the use cases.
This helps in discovering understated alternate requirements in the system.
The use case model can be utilized in several other part of software
development as well, e.g. Cost Estimation, Project Planning, Test Case Preparation
and User Documentation.
Use cases help ensure that the correct system is developed by capturing the
requirements from the user's point of view.
Use cases can help manage the complexity of large projects by decomposing
the problem into major functions (i.e., use cases) and by specifying applications
from the users' perspective.
Use cases provide a good basis for the verification of the higher-level
models
Use cases can serve as the basis for the estimating, scheduling, and
validating effort.
Use cases are reusable within a project.
Use cases have proved to be easily understandable by business users.
Use case specifications don't use a special language.
They can be written in a variety of styles to suit the particular needs of the
project.
Use cases allow us to tell stories. It is very easy to describe a use case in a
concrete way by turning it into a story or scenario.
Use cases are concerned with the interactions between the user and the
system.
Use Cases allow you to capture the user’s need by focusing on a task that the
user needs to do.
Use Cases help you define the right functionalities.
The Use cases help ensure that the correct system is developed by capturing
the requirements from the user's point of view.
Use Cases are easy to read.