Experiment No.

SEMESTER: VI DATE OF DECLARATION: 22/3/2021

SUBJECT: SE LAB DATE OF SUBMISSION: 12/4/2021

NAME OF THE STUDENT: REENA KALE ROLL NO.: 23

To Identify scenarios & develop UML Use case and Class Diagram for the
AIM
project.

LEARNING The student will learn to identify scenarios & develop use case, activity and
OBJECTIVE sequence Diagram for the project.

The students will be able to understand the software engineering concepts

LEARNING and prepare the problem statement & proposed solution for the selected case
OUTCOME
study

CSL601.1: Students will be able to understand the software engineering

COURSE concepts and prepare the problem statement & proposed solution for the
OUTCOME
selected case study

PO1: Apply the knowledge of mathematics, science, engineering

fundamentals, and an engineering specialization to the solution of complex
engineering problems.

PO9: Function effectively as an individual, and as a member or leader in

PROGRAM
diverse teams, and in multidisciplinary settings.
OUTCOME
PO10: Communicate effectively on complex engineering activities with the
engineering community and with society at large, such as, being able to
comprehend and write effective reports and design documentation, make
effective presentations, and give and receive clear instructions.

BLOOM'S Knowledge
TAXONOMY
LEVEL Understand

A UML use case diagram is the primary form of system/software

requirements for a new software program underdeveloped. Use cases specify
the expected behavior (what), and not the exact method of making it happen
(how). Use cases once specified can be denoted both textual and visual
THEORY
representation (i.e. use case diagram). A key concept of use case modeling is
that it helps us design a system from the end user's perspective. It is an
effective technique for communicating system behavior in the user's terms by
specifying all externally visible system behavior.

1
A use case diagram is usually simple. It does not show the detail of the use
cases:

● It only summarizes some of the relationships between use cases,

actors, and systems.
● It does not show the order in which steps are performed to achieve the
goals of each use case.

Purpose of Use Case Diagram

Use case diagrams are typically developed in the early stage of development
and people often apply use case modeling for the following purposes:

● Specify the context of a system

● Capture the requirements of a system
● Validate a systems architecture
● Drive implementation and generate test cases
● Developed by analysts together with domain experts

A UML Activity diagram is another important diagram in UML to describe

the dynamic aspects of the system. Activity diagram is basically a flowchart
to represent the flow from one activity to another activity. The activity can be
described as an operation of the system.The control flow is drawn from one
operation to another. This flow can be sequential, branched, or concurrent.
Activity diagrams deal with all types of flow control by using different
elements such as fork, join, etc.

Purpose of an activity diagram

● Draw the activity flow of a system.

● Describe the sequence from one activity to another.
● Describe the parallel, branched and concurrent flow of the system.

UML Sequence Diagrams are interaction diagrams that detail how

operations are carried out. They capture the interaction between objects in the
context of a collaboration. Sequence Diagrams are time focused and they
show the order of the interaction visually by using the vertical axis of the
diagram to represent time, what messages are sent and when.

Purpose of Sequence Diagram

● Model high-level interaction between active objects in a system

● Model the interaction between object instances within a collaboration
that realizes a use case
● Model the interaction between objects within a collaboration that
realizes an operation
● Either model generic interactions (showing all possible paths through
the interaction) or specific instances of a interaction (showing just one
path through the interaction)

2
LAB EXERCISE Activity Diagram:

3
Sequence Diagram:

4
Use case Diagram:

Name of the Group:

Group Details:
Sr. No. Roll No. Name of the Batch Name of the student

1 16 A Fabian Gomes

2 23 A Reena Kale

3 27 A Gavin Koli

5
REFERENCES https://creately.com/diagram/example/jqyuajsx1/Ambulance%20Servic
es
https://bohatala.com/ambulance-management-system/
https://slideplayer.com/slide/10985665/