Rayat Shikshan Sanstha’s

KARMAVEER DHAURAO PATIL COLLEGE,VASHI,

[Autonomous College)

Rearcredited NAAC with Grade ’A+’(CGPA 3.53) | ISO 9001:2008 Certified

Institute ‘Best College’ Award by University of Mumbai

DEPARTMENTOF INFORMATIONTECHNOLOGY

CERTIFICATE
This Is To Certify That, Tanmay Chandrakant Mane Student of TYBSc.IT
Class From Karmaveer Bhaurao Patil College, Vashi [Autonomous], Navi
Mumbai Has Satisfactorily Completed The Practical Course In Subject
SOFTWARE PROJECT MANAGEMENT As per The Syllabus Lind By The
University Of Mumbai During The Academic Year 2023-24.

ROLL NO:. 237802

EXAM NO:237802

TEACHER:Poonam Rawale EXAMINER HEAD

Date: Department Of Information Technology

Name: Tanmay Mane Roll no:237802 Batch:B2

SR.NO. DATE TITLE SIGN
Draw Class diagram for ATM machine.
1(A)

Draw a class diagram using starUML

1(B) for the scenario.

Study and implement the use case

2(A) diagram for ATM machine.

Study and implement the use case

2(B) diagram for LIBRARY
management System.

Study and implement the Entity

3 relationship diagram for LIBRARY
management System.

Study and implement the Sequence

4(A) diagram for issue book.

Study and implement the Sequence

4(B) diagram for return book.

Study and implement the statechart

5(A) diagram for library management
system.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Study and implement the statechart
5(B) diagram for online food order system.

Study and implement the Data flow

6(A) diagram for library management
system.

Study and implement the Data flow

6(B) diagram for ATM machine.

Study and implement the

7(A) collaboration diagram for library
management.

Study and implementation of

7(B) collaboration diagram for ATM.

Study and implementation of activity

8(A) diagram for ATM cash withdrawal.

Study and implementation of activity

8(B) diagram for online food order system.

Study and implementation of

9 Component Diagram for Hospital
Management System.

Name: Tanmay Mane Roll no:237802 Batch:B2

10 Study and implementation of
deployment Diagram for library
Management System.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:1(A)

Aim: Draw Class diagram for ATM Machine.An automated teller machine(ATM)
or the automatic banking subsystem that provides bank customers with access to
financial transactions in a public space without the need for cashier,clerk or bank
teller.Customer uses bank ATM to check balances of his/her bank accounts,deposit
funds,withdraw cash and/or transfer funds which are the generalization alternative
of ATM transactions use case.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

Explanation:

Classes:

ATM: Represents the ATM machine itself. It will have methods to handle

customer transactions and communicate with the Bank class for processing.

● Attributes: location, atm number,managed by

● Methods: transactions(),identifies()
Bank: Represents the bank that manages customer accounts and transactions.
The ATM will communicate with this class to process the transactions.
● Methods: management(),maintenance()
● Customer: Represents a bank customer who uses the ATM.
● Attributes: name, ac number, address,dob,debit card

Relationships:

● The ATM class will have an association with the Bank class to
communicate with the bank for processing transactions.
● The ATM class will also have an association with the Customer
class, representing that customers interact with the ATM.

Implementation:

● The specific types of transactions, such as Deposit, Withdrawal, and

Transfer, can be represented as subclasses of a Transaction class. This
Transaction class will be a generalization of these specific transaction
types.

Transaction: Represents a general transaction that can be of different types

(Deposit, Withdrawal, Transfer).

● Methods: execute transactions()

Name: Tanmay Mane Roll no:237802 Batch:B2

 Deposit: Represents a deposit transaction. It will inherit from the
Transaction class and override the execute transactions() method.

Withdrawal: Represents a withdrawal transaction. It will inherit from the

Transaction class and override the execute transactions() method.

Transfer: Represents a funds transfer transaction. It will inherit from the

Transaction class and override the execute transactions() method.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:1(B)
Aim: Draw a class diagram using StarUMI, for the scenario given below. This
scenario shows an inheritance hierarchy of a series of classes and their subclasses.
It's for an imaginary application that must model different kinds of vehicles such as
bicycles, motor bikes and cars. All Vehicles have some common attributes (speed
and color) and common behavior (tumLeft, turnRight). Bicycle and Motor Vehicle
are both kinds of Vehicle and are therefore shown to inherit from Vehicle. To put
another way, Vehicle is the superclass of both Bicycle and Motor Vehicle. In our
model Motor Vehicles have engines and license plates. Attributes have been added
accordingly, along with some behavior that allows us to examine those attributes.
Motor Vehicles is the base class of both MotorBike and Car, therefore these
classes not only inherit the speed and color properties from Vehicle, but also the
additional attributes and behavior from MotorVehicle. Both MotorBike and Car
have additional attributes and behavior which are specific to those kinds of
objects.

Name: Tanmay Mane Roll no:237802 Batch:B2

Diagram:

Explanation:
All Vehicles have some common attributes (speed and color) and common
behavior (turnLeft, turnRight) Bicycles and MotorVehicle are both kinds of
Vehicle and are therefore shown to inherit from vehicles. To put this another way,
vehicles are the superclass of both Bicycles and MotorVehicle In our model
MotorVehicles have engines and license plates. Attributes have been added
accordingly, along with some behavior that allows us to examine those attributes
MotorVehicles is the base class of both MotorBike and Car, therefore these classes
not only inherit the speed and color properties from Vehicle, but also the
additional attributes and behavior from MotorVehicle Both MotorBike and Car
have additional attributes and behavior which are specific to those kinds of object.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:2(A)

Aim: Study and implementation of use case diagram for ATM system.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

Explanation:

This UML diagram shows the use cases of an ATM system. A use case is a
description of how a system interacts with its external actors to achieve a specific
goal. An actor is a role that a person or entity plays when using the system. A
system is a collection of components that work together to provide some
functionality.

The diagram has two actors: the operator and the customer. The operator is
responsible for maintaining and shutting down the ATM system. The customer is
the person who uses the ATM system to perform various transactions with their
bank account.
The diagram has six use cases: transactions, withdrawal, transfer, deposit,
inquiry, and system shutdown. Transactions is an abstract use case that
represents any kind of transaction that a customer can perform with the ATM
system.
Withdrawal, transfer, deposit, and inquiry are concrete use cases that inherit from
transactions. They specify the details of how a customer can withdraw money,
transfer money, deposit money, or inquire about their balance using the ATM
system. System shutdown is a use case that describes how the operator can shut
down the ATM system when it is not in use.

The diagram also shows the relationships between the actors and the use cases,
and between the use cases themselves. A solid line with an arrow indicates an
association relationship, which means that an actor can initiate or participate in a
use case. A dashed line with an arrow indicates an extended relationship, which
means that a use case can be extended by another use case under some condition.
A dashed line with a triangle indicates a generalized relationship, which means
that a use case is a specialization of another use case.

For example, the diagram shows that the customer is associated with transactions,
which means that the customer can initiate or participate in any transaction. The
diagram also shows that withdrawal extends transactions with the condition "pin
invalid", which means that withdrawal is a special kind of transaction that can be
extended by another use case when the customer enters an invalid pin. The
diagram also shows that withdrawal generalizes transactions, which means that
withdrawal is a more specific kind of transaction than transactions

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:2(B)

Aim: Study and implementation of use case diagram for library management.

Diagram:

Explanation:
This UML Diagram is a flowchart for a library management system. It is
divided into three sections: User, Staff/Student, and Librarian. The User section
includes processes such as filling up membership forms, getting a library card,
and providing feedback. The Staff/Student section includes processes such as
requesting a new book, registering online.The Librarian section includes
processes such as manages books, manages database of members.The
rectangles in the flowchart represent different processes, while the oval shapes
represent decision points. The arrows show the flow of the process and the
direction of the decision.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No 3

Aim: Study and implementation of Entity Relationship Diagram.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

Explanation:
ER diagram is known as Entity-Relationship Diagram, it is used to analyze the
structure of the Database. It shows relationships between entities and their
attributes. An ER Model provides a means of communication.

Entities and their Attributes-

● Book Entity : It has authno,title, edition,book id, price is the primary key.
● Publisher Entity : It has publisher name & address.
● Author Entity: It has first & last name.
● Transaction Entity: It has book id,transaction id,transaction name,etc.
● Student Entity: It has class,Name,roll no,etc is the primary key.

There are few data types used in the diagram which are integers which are used for
id,class,contact no & time. The varchar used for name,author,type,& location.

Relationship between Entities-

● A reader can reserve N books but one book can be reserved by only
one reader. The relationship 1:N.
● A publisher can publish many books but a book is published by only
one publisher. The relationship 1:N.
● Library keeps track of readers. The relationship is M:N.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:4A

Aim: Study and implementation of Sequence Diagrams in a Book issue of Library

Management System.

Diagram:

Explanation: Sequence diagrams are also known as behavioral diagrams. It shows

the interactions between the objectsAbove is the Sequence Diagram of the Book
issue from the Library.

Name: Tanmay Mane Roll no:237802 Batch:B2

Actor:This is at the top of the sequence diagram and represents an object
interacting with the system. Here the Student is the actor.

Lifeline: Lifelines represent the objects that participate in an interaction. Here, our
lifeline is a Student, Librarian,Book and Transaction. The dotted vertical line
denotes the longevity of the respective lifelines.

Synchronous message: This Colored headed arrow (→)denotes the message

sent to an object.

Asynchronous message: This triangle headed arrow(→) denotes the reply from
the
object. It is used to indicate that the message receiver is done processing the
message and is returning control over to the message caller.

Activation Bar: The activation bar is the box placed on the lifeline. It is used to
indicate that an object is active during an interaction between two objects.
The length of the rectangle indicates the duration of the objects staying active.

Our first interaction is when the student requests a book to the librarian it passes a
message as the book name to User Librarian checks availability of the book in the
system, if the book is available the librarian will give a message as the book is
available. The librarian will then check no. of books & issue a book to the student.
The librarian will add student & book details in the transaction session. Then the
librarian will update the book status & update student records in the system.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:4B

Aim:Study and implementation of Sequence Diagrams in a Book return of Library

Management System.

Diagram:

Explanation:
Our first interaction will be when a student of the library requests to return a book
to a librarian. The message requests to return a book labeled. Arrow will point
towards the librarian. The librarian checks the condition and due date of the book
If the book is verified to be in bad condition or expired due date then the user is
liable to pay a fine. It displays a message using an asynchronous arrow with the
label 'pay fine' to the user.When the user pays fine the librarian enters it in the
transaction database and the book is returned successfully.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:5A

Aim:Study and implementation of Statechart diagrams of ATM machines.

Diagram:

Explanation: State Transition Diagram are also known as Dynamic models. It is a

type of diagram that is used to represent different transition (changing) states of a
System. It is generally used to graphically represent all possible transition states a
system can have and model such systems.The System consists of various states that
are being represented using various symbols in the state transition diagram.

Name: Tanmay Mane Roll no:237802 Batch:B2

Basic components of a statechart diagram –
1. Initial state – We use a black filled circle represent the initial state of a Systeor
a class.

2. Transition – We use a solid arrow to represent the transition or change of

control from one state to another. The arrow is labelled with the event
which causes the change in state.

3. State – We use a rounded rectangle to represent a state. A state represents the.

conditions or circumstances of an object of a class at an instant of time.

4. Final state – We use a filled circle within a circle notation to represent the
final state in a state machine diagram.

Name: Tanmay Mane Roll no:237802 Batch:B2

When the customer inserts the bank or credit card in the ATM’s card reader, the
entry action i.e readcard is performed by the ATM machine. If the card is not valid
then the machine will perform exit action. After the card is being read
successfully, the ATM machine will ask for a Pin. Then the customer enters the
pin and the ATM machine then reads the pin. If the pin entered is not valid then
the machine will perform an exit action. If the pin entered is valid, then the
machine further processes towards the transaction. After successful transaction,
machine undergoes the exit action i.e., eject card that discharges the customer’s
card.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:5B

Aim:Study and implementation of Statechart diagrams of Library Management

System.

Diagram:

Explanation:
When the member enquiry about a book in the library,the entry action i.e check the
availability of the book, if book is not available it will show the book not available
& if book is available the librarian will check for validate member card. If the card
is not valid it will perform a register member card. After the card is valid the
librarian will check no.of issued book & issue a book to the member. Then the
librarian adds the book & member details in the system & updates the status. When
the due date of book comes the member return the book & then librarian updates
the book status.After successful process, it undergoes the exit action.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:6A

Aim:Study and implementation of Data flow diagram of ATM System.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

A data flow diagram (DFD) maps out the flow of information for any process or
system. It uses defined symbols like rectangles, circles and arrows, plus short text
labels, to show data inputs, outputs, storage points and the routes between each
destination.
The symbols depict the four components of data flow diagrams:

1. External entity: an outside system that sends or receives data,

communicating with the system being diagrammed. They are the sources and
destinations of information entering or leaving the system.

2. Process: any process that changes the data, producing an output. A short label
is used to describe the process.

3. Data store: Files or repositories that hold information for later use, such as a
database table or a membership form. Each data store receives a simple label.

4. Data flow: The route that data takes between the external entities, processes
and data stores. It portrays the interface between the other components and is
shown with arrows, typically labeled with a short data name.

A data flow diagram can divide into levels.DFD levels are numbered 0, 1 or 2, and
occasionally go to even Level 3 or beyond. The necessary level of detail depends
on the scope of what you are trying to accomplish.
DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole
system or process being analyzed or modeled.

Name: Tanmay Mane Roll no:237802 Batch:B2

DFD Level 1 provides a more detailed breakout of pieces of the Context Level
Diagram. You will highlight the main functions carried out by the system.
DFD Level 2 then goes one step deeper into parts of Level 1. It may require more
text to reach the necessary level of detail about the system’s functioning.

The overall processing unit will contain the following output that a system will
generate:

Level 0 DFD: It’s a basic overview of the whole process being analyzed.Users,
the main process, and data flow make up its parts.It shows the entities that interact
with a system and defines the border between the system and its environment.

Level 1 DFD: At this level, the system has to be shown with more details of
processing.The three different processes: customer information management,
transaction information management, and release cash and receipts.Firstly, the
flow of data starts from the machine and the card holders. Then the system caters
to the transaction.

Level 2 DFD:Then goes one step deeper into parts of Level 1. It includes the sub-
processes from level 1 as well as the data that flows.may require more text to reach
the necessary level of detail about the system’s functioning. The processes that are
included are: customer database, transaction database Cash & receipts,customer &
transaction information & customer

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:6B

Aim: Study and implementation of Data flow diagram of Library Management

System.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

The overall processing unit will contain the following output that a system will
generate:

Level 0 DFD: It’s a basic overview of the whole process being analyzed.
Books will be the output as the book demanded by the student will be given to
them.Information of the book should be displayed by the library information
system that can be used by the student while selecting the book which makes it
easier for the student.

Level 1 DFD: At this level, the system has to be shown with more details of
processing.The processes that are important to be carried out are:
Book delivery, Authors, Titles, List of Topics,Student,etc.

Level 2 DFD:Then goes one step deeper into parts of Level 1. The processes that
are to be carried out: Get the book, Search the book & update the book borrowed.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:7A

Aim:Study and implementation of Collaboration diagram of Book issue & return

in library.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

Explanation:
The collaboration diagram is used to show the relationship between the objects in a system.
Both the sequence and the collaboration diagrams represent the same information but
differently. Instead of showing the flow of messages, it depicts the architecture of the object
residing in the system as it is based on object-oriented programming.

Components:
1. Objects: The representation of an object is done by an object symbol with its name and
class underlined, separated by a colon.
In the collaboration diagram, objects are utilized in the following ways:
○ The object is represented by specifying their name and class.
○ It is not mandatory for every class to appear.
○ A class may constitute more than one object.
○ In the collaboration diagram, firstly, the object is created, and then its class is
specified.
○ To differentiate one object from another object, it is necessary to name them.
2. Actors: In the collaboration diagram, the actor plays the main role as it invokes the
interaction. Each actor has its respective role and name. In this, one actor initiates the
use case.
3. Links: The link is an instance of association, which associates the objects and actors. It
portrays a relationship between the objects through which the messages are sent. It is
represented by a solid line. The link helps an object to connect with or navigate to
another object, such that the message flows are attached to links.
Messages: It is a communication between objects which carries information and includes a
sequence number, so that the activity may take place. It is represented by a labeled arrow,
which is placed near a link. The messages are sent from the sender to the receiver, and the
direction must be navigable in that particular direction. The receiver must understand the
message.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No: 8A
Aim: Study and implementation of activity diagram for ATM Machine System.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

Explanation:
An activity diagram is a type of UML (Unified Modeling Language) diagram used
to visually represent the flow of activities or processes within a system.

Activities: Activities are represented by rounded rectangles and symbolize

tasks,actions, or operations that occur within the system. They can represent high-
level processes or detailed sub-processes.

Transitions: Arrows with labels connecting activities indicate the flow or sequence
of activities. These transitions show the order in which activities are
performed.

Decision Points (Diamonds): Decision points, represented by diamonds, are used

to model conditional logic or branching in the process flow. Depending on the
condition evaluated at a decision point, the flow can follow different paths.

Fork and Join Nodes: Fork nodes, typically represented as bars, indicate that
multiple activities can occur in parallel. Join nodes, also represented as bars, show
where parallel flows converge back into a single flow

Initial Node: The initial node (a solid circle) represents the starting point of the
activity diagram. It indicates where the process begins.

Final Node: The final node (a solid circle with a border) represents the endpoint of
the activity diagram, indicating where the process ends.

Swimlanes: Swimlanes are used to group activities by the responsible entity or

role. They are often represented as vertical or horizontal partitions and help clarify
who is responsible for each activity.

Name: Tanmay Mane Roll no:237802 Batch:B2

Name: Tanmay Mane Roll no:237802 Batch:B2
 Practical No: 8A
Aim: Study and implementation of activity diagram for Food Ordering System.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

Explanation: This is the Activity UML diagram of Food Ordering System which
shows the flows between the activity of Order, Delivery, Food Item, Category,
Payment.
● Admin User can search Order, view description of a selected Order,
add Order, update Order and delete Order
● Its shows the activity flow of editing, adding and updating of Delivery
● User will be able to search and generate report of Food Item,
Category, Payment
● All objects such as ( Order, Delivery, Payment) are interlinked.
● Its shows the full description and flow of Order, Category, Payment, Food
Item, Delivery

Name: Tanmay Mane Roll no:237802 Batch:B2

 PRACTICAL NO : 9

AIM : Study and implementation of component diagram for Hospital Management

System Server.

DIAGRAM:

Name: Tanmay Mane Roll no:237802 Batch:B2

Explanation :
● Package:
1) Staff database:Database contains the two components Doctor and Nurse.
2) Patient database:Database contains the two components private patient
and general patient.
3) User interface:Database contains the two components Website and Software.
4) Utility:Databases contain only one component, which is Data processing.
5) HMS operation details:Package is dependent on the component Hospital
Management System Server.

● Component:
1) Hospital management database:Database stores all the information of the
hospital management.
2) Doctor:Components contain all the details of the doctors of the hospital.
3) Nurse:Component contains all the details of the nurses of the hospital.
4) Private patient:Components contain the details of private patient of the hospital.
5) General patient:Components contain the details of the general patient of the
hospital.
6) Website:Components have the hospital website.
7) Software:Components contain the software of the hospital.
8) Data processing: Component Hospital Management System Server is dependent
on the Data processing component.
● Dependency:
1) The component Hospital management System Server is dependent on the
component of the Hospital management Database.
2) The component Hospital Management System Server is dependent on the
Package of Staff Database.
3) The component Hospital management System Server is dependent on the
Package of Patient Database.
4) The package User interface is dependent on the Hospital Management
System Server.
5) The Component Hospital Management System Server is dependent on the Utility
Package.
6) The HMS operation details package is dependent on the Hospital
Management System Server.

Name: Tanmay Mane Roll no:237802 Batch:B2

 Practical No:10

Aim : Study and implementation of deployment diagram for Library Management

System.

Diagram:

Name: Tanmay Mane Roll no:237802 Batch:B2

Explaination :
1. Node:
A) Database Server is the node for the component books.
B) Application Server is the node for both library information and
books information.
C) Web server is the node for both borrow book and return book
component. D)Member1,Member2,Member3 are three independent nodes.

2. Component:
1) Books is the component of the database server,Which keeps the record
of all books of library.
2) Library information and books information are the components of the
application server,Which keeps the information of all the books and library.
3) Borrow book and return book are the components of web server
node,which keeps the record of books borrowed and returned books.

3. Communication Path:
1)Database server and application server are connected via connection.
2)Application server and web server are connected via connection.
3)Web server and Member1,Member2 are connected via private network.

Name: Tanmay Mane Roll no:237802 Batch:B2