OOSE PRACTICAL FILE

MCA – 01

GURU NANAK INSTITUTE OF MANAGEMENT STUDIES

PUNJABI BAGH, NEW DELHI- 110026

MCA – 01

OOSE PRACTICAL FILE

GURU NANAK INSTITUTE OF MANAGEMENT STUDIES

PUNJABI BAGH, NEW DELHI- 110026

SUBMITTED TO – MR. NILESH KUMAR DOKANIA

SUBMITTED BY – JATIN KUMAR

ROLL NO – 70213004423
 1- Write SRS of the following: 1) Library management system 2)Banking system
3)Hotel management system

2- Prepare DFD (0 & 1 Levels) of the following : 1) Library management system

2)Banking system 3)Hotel management system
3- Draw Use Case diagram for EXAMINATION PORTAL
4- Draw Use Case diagram for RAILWAY RESERVATION SYSTEM.
5- Draw Use Case diagram for LIBRARY MANAGEMENT SYSTEM
6- Draw Use Case diagram for AIRLINE RESERVATION SYSTEM
7- Draw Use Case diagram for HOTEL MANAGEMENT SYSTEM
8- Draw ER/EER diagram for EXAMINATION PORTAL
9- Draw ER/EER diagram for RAILWAY RESERVATION SYSTEM.
10- Draw ER/EER diagram for LIBRARY MANAGEMENT SYSTEM
11- Draw ER/EER diagram for AIRLINE RESERVATION SYSTEM
12- Draw ER/EER diagram for HOTEL MANAGEMENT SYSTEM
13- Draw use case of an ATM system with at least 3 different actors that interact with
system.
14- Draw sequence and collaboration diagram for Library Management System.
15- Draw sequence and collaboration diagram for Airline Reservation System.
16- Draw sequence and collaboration diagram for Railway Reservation System.
17- Draw sequence and collaboration diagram for Examination Portal.
18- Draw sequence and collaboration diagram for an Hotel Management System,.
19- Draw class diagram of an ATM system.
20- Draw class diagram for Hospital Management System.
21- Draw class diagram for Library Management System.
22- Draw class diagram for Airline Reservation System.
23- Draw class diagram for a ticket distributor for a train system.
24- Draw activity diagram for ATM.
25- Draw activity diagram for AIRLINE RESERVATION SYSTEM.
26- Draw activity diagram for LIBRARY MANAGEMENT SYSTEM.
27- Draw activity diagram for HOTEL MANAGEMENT SYSTEM.
28- Draw a state chart diagram for HOTEL MANAGEMENT SYSTEM.
29- Draw a state chart diagram for AIRLINE RESERVATION SYSTEM.
30- Draw deployment diagram for AIRLINE RESERVATION SYSTEM.
31- Draw deployment diagram for HOSPITAL MANAGEMENT SYSTEM.
Question 01- Write SRS of the following:
Library management system INTRODUCTION

With the increase in the number of readers, better management of libraries

system is required. The Library management system focuses on improving the
management of libraries in a city or town. “What If you can check whether a
book is available in the library through your phone
?” or “what if instead of having different library cards for different libraries you
can just have one ?” or “you can reserve a book or issue a book from your
phone sitting at your home!”.

1.1 PURPOSE-

The purpose of the project is to maintain the details of books and library
members of different libraries. The main purpose of this project is to maintain a
easy circulation system between clients and the libraries, to issue books using
single library card, also to search and reserve any book from different available
libraries and to maintain details about the user (fine, address, phone
number).Moreover, the user can check all these features from their home.

1.2 SCOPE-

Manually updating the library system into an android based application so that
the user can know the details of the books available and maximum limit on
borrowing from their computer and also through their phones.

The System provides information's like details of the books, insertion of new
books, deletion of lost books, limitation on issuing books, fine on keeping a
book more than one month from the issued date.

1. 3-Definition, Acronyms, Abbreviation:

JAVA -> platform independenc

SQL -> Structured query Language

DFD -> Data Flow Diagram

CFD -> Context Flow Diagram

ER -> Entity Relationship

IDE -> Integrated Development Environment

SRS -> Software Requirement Specification

2. OVERALL DESCRIPTION

2.1 PRODUCT PRESPECTIVE

The proposed Library Management System will take care of the current book
detail at any point of time. The book issue, book return will update the current
book details automatically so that user will get the update current book details.

2.2 SOFTWARE REQUIREMENT

Front end: Android developer tool Advance java

Back end: •MySQL

2.3 HARDWARE REQUIREMENT

Android version 2.3 ginger bread(minimum, android user’s)

2GB ram
1.2 GHz processor Intel
i5
Windows 7/8/8.1/10
2.4.1 FUNCTIONAL REQUIREMENT

R.1:Register

Description : First the user will have to register/sign up. There are two different
type of users.

The library manager/head : The manager have to provide details about

the name of library, address, phone number, email id.

Regular person/student : The user have to provide details about his/her

name of address, phone number, email id.

R.1.1: Sign up

Input: Detail about the user as mentioned in the description.

Output: Confirmation of registration status and a membership number and

password will Regenerated and mailed to the user.
Processing: All details will be checked and if any error are found then an error
message is displayed else a membership number and password will be
generated.

R.1.2 : Login

Input: Enter the membership number and password provided.

Output : User will be able to use the features of software.

R.2 : Manage books by user

R.2.1 : Books issued.

Description : List of books will be displaced along with data of return.

R.2.2 : Search

Input : Enter the name of author's name of the books to be issued.

Output : List of books related to the keyword.

R.2.3 : Issues book

State : Searched the book user wants to issues.

Input : click the book user wants.

Output : conformation for book issue and apology for failure in issue.

Processing : if selected book is available then book will be issued else error will
be displayed.

R.2.4 : Renew book

State : Book is issued and is about to reach the date of return.

Input : Select the book to be renewed.

Output : conformation message.

Processing : If the issued book is already reserved by another user then error
message willbe send and if not then conformation message will be displayed.

R.2.5 : Return

Input ; Return the book to the library.

Output : The issued list will be updated and the returned book will be listed out.

R.2.6 ; Reserve book

Input ; Enter the details of the book.

Output : Book successfully reserved.

Description : If a book is issued by someone then the user can reserve it ,so that
later the user can issue it.

R.2.6 Fine

Input : check for the fines.

Output : Details about fines on different books issued by the user.

Processing : The fine will be calculated, if it crossed the date of return and the
user did not renewed if then fine will be applied by Rs 10 per day.

R.3.1.1 Add books

Input : Enter the details of the books such as names ,author ,edition, quantity.

Output : confirmation of addition.

R.3.1.2 Remove books

Input : Enter the name of the book and quantity of books.

Output : Update the list of the books available.

2.4.2 Non Functional Requirements

•Usability Requirement-The system shall allow the users to access the system
from the phone using android application. The system uses a android
application as an interface. Since all users are familiar with the general usage of
mobile app, no special training is required. The system is user friendly which
makes the system easy.

•Availability Requirement-The system is available 100% for the user and is used
24 hrs a day and 365 days a year. The system shall be operational 24 hours a
day and 7 days a week.

•Efficiency Requirement-Mean Time to Repair (MTTR) - Even if the system

fails, the system will be recovered back up within an hour or less.
 •Accuracy-The system should accurately provide real time information taking
into consideration various concurrency issues. The system shall provide 100%
access reliability.

•Performance Requirement-The information is refreshed depending upon

whether some updates have occurred or not in the application. The system shall
respond to the member in not less than two seconds from the time of the request
submittal. The system shall be allowed to take more time when doing large
processing jobs. Responses to view information shall take no longer than 5
seconds to appear on the screen.

•Reliability Requirement-The system has to be 100% reliable due to the

importance of data and the damages that can be caused by incorrect or
incomplete data. The system will run 7 days a week, 24 hours a day.

2.5 USER CHARACTERSTICS

We have 3 levels of users :

User module: In the user module, user will check the availability of the books.

Issue book

Reserve book

Return book

Fine details

Library module:

Add new book

Remove books

Update details of book

Administration module: The following are the sub module in the administration
module :

Register user

Entry book details

Book issue

2.6 CONSTRAINTS

Any update regarding the book from the library is to be recorded to have update
& correct values, and any fine on a member should be notified as soon as
possible and should be correctly calculated.

2) Banking system

INTRODUCTATION

This document gives detailed functional and nonfunctional requirements for the
bank management system. This product will support online banking transaction.
The purpose of this document is that the requirements mentioned in it should be
utilized by software developer to implement the system.

1.1 Purpose

Online banking system provides is specifically developed for internet banking

for Balance Enquiry, Funds Transfer to another account in the same bank,
Request for cheque book/change of address/stop payment of cheques, Mini
statements (Viewing Monthly and annual statements).

The Traditional way of maintaining details of a user in a bank was to enter the
details and record them. Every time the user need to perform some transactions
he has to go to bank and perform the necessary actions, which may not be so
feasible all the time. It may be a hard-hitting task for the users and the bankers
too. The project gives real life understanding of Internet banking and activities
performed by various roles in the supply chain. Here, we provide an automation
for banking system through Internet. Internet banking system project captures
activities performed by different roles in real life banking which provides
enhanced techniques for maintaining the required in- formation up-to-date,
which results in efficiency. The project gives real life understanding of Internet
banking and activities performed by various roles in the supply chain.

1.2 Scope

This Product will automate of banking transaction process. This Project

investigates the entry threshold for providing a new transaction service channel
via the real options approach, where the entry threshold is established by using
an Internet banking system designed for the use of normal users(individuals),
Industrialists, Entrepreneurs, Educational Institutions(Financial sections),
Organizations and Academicians under transaction rate uncertainty.

1.3 Overview

The system provides easy solution to banks.

Overview: The SRS will include two sections, namely:

Overall Description: This section will describe major components of the system,
interconnections, and external interfaces.

Specific Requirements: This section will describe the functions of actors,

their roles in the system and the constraints faced by system.

2. General description

2.1 Product Perspective: The client will have client interface in which he can
interact with the banking sys- tem. It is a web based interface which will be the
web page of the banking application. Starting a page is
displayed asking the type of customer he is whether ordinary or a
corporate customer. Then the page is redirected to login page where the user can
enter the login details. If the login particulars are valid then the user is taken to a
home page where he has the entire transaction list that he can perform with the
bank. All the above activities come under the client interface.

The administrator will have an administrative interface which is a GUI so that

he can view the entire system. He will also have a login page where he can
enter the login particulars so that he can perform all his a ctions. This
administrative interface provides different environment such that he can
maintain data- base & provide backups for the information in the database. He
can register the users by providing them with
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 10

username, password & by creating account in the database. He can view the
cheque book request & perform action to issue the cheque books to the clients.

2.2 Software Interface:

Front End Client: The system is a web based application clients are requiring
using modern web browser such as Mozilla Firefox 1.5, PHP.

* Web Server: The web application will be hosted on one of the apache server.

* Back End: We use backend as MY SQL.

3. Functional Specifications -This section provides the functional overview of

the product. The project will require the PHP as a front end and at the back end
the database MYSQL will be running. Various functional modules that can be
implemented by the product will be

1. Login

2. Validation

3. Get balance information

4. Withdrawal of money

5. Transfer Money

6. Customer info.

3.1 Login: Customer logins by entering customer name & a login pin.

3.2 Validation: When a customer enters the ATM card, its validity must
be ensured. Then customer is allowed to enter the valid PIN. The
validation can be for following conditions

Validation for lost or stolen card When card is already reported as lost or stolen
then the message “Lost/Stolen card!!!”.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 11

Validation for card’s expiry date if the card inserted by the customer has crossed
the expiry date then the system will prompt “Expired Card”.

Validation for PIN

After validating the card, the validity of PIN must be ensured. If he/she fails to
enter valid code for three times then the card will not be returned to him. That
means the account can be locked. The counter for number of logins must be
maintained Get balance information:

This system must be networked to the bank’s computer. The updated database of
every customer is maintained with bank. Hence the balance information of
every account is available in the database and can be displayed to the customer.

3.3 Payment of Money: A customer is allowed to enter the amount which

he/she wishes to withdraw. If the entered amount is less than the available
balance and if after withdraw if the minimum required balance is maintained
then allow the transaction.

3.4 Transfer of Money: The customer can deposit or transfer the desired
amount of money.

3.5 Transaction Report: The bank statement showing credit and debit
information of corresponding account must be printed by the machine.

3.6 Technical Issues-This product will work on client-server architecture. It will

require an internet server and which will be able to run PHP applications. The
product should support some commonly used browsers such as Internet
Explorer, Mozilla Firefox.

4. Interface Requirements

4.1 GUI- This is interface must be highly intuitive or interactive because there
will not be an assistance for the user who is operating the System. At most of
the places help desk should be provided for user convenience. The screens
appearing should be designed in such a manner that it can draw User attraction
towards the new plans for the customers. Also the pin and password
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 12

confidentiality should be maintained, This can be done by using asterisks at the

password panel.

Proper security messages should be displayed at most of the places.

4.2 Hardware Interface

Various interfaces for the product could be

1. Touch screen/Monitor

2. Keypad

3. Continuous battery backup

4. Printer which can produce the hard copy.

5. Interface that connects the device to bank’s computer.

6. An interface that can count currency notes.

4.3 Software Interface

1. Any windows operating system.

2. The PHP must be installed. For the database handling MYSQL must be
installed. These products are open source products.

3. The final application must be packaged in a set up program, so that the

products can be easily installed on machines. This application must be
networked to corresponding banks.

4. Performance Requirements

The system should be compatible enough to hold the general traffic.

It should not get hang or show some other problems arising out due to large no
of concurrent users . The system should be fast enough to meet the customer
The high and low temperature should not affect the performance of the device.
An uninterrupted transaction must be performed.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 13

6.Constraints

* The information of all the users must be stored in a database that is

accessible by the On- line

Banking System.

* The Online Banking System is connected to the computer and is running

all 24hours a day.

* The users access the Online Banking System from any computer that
has Internet browsing capabilities and an Internet connection.

*The users must have their correct usernames and passwords to enter into the
Online Banking System.

Design Constraints:

* Software Language Used -The languages that shall be used for coding
Online Banking System are c , c++ , java , and HTML. For working on the
coding phase of the Online job portal System Web
Sphere Application Server/WebSphere Application Server CE Server needs
to be installed.

*Database design

In our database design, we give names to data flows, processes and data stores.
Although the names are descriptive of data, they do not give details .So
following DFD, our interest is to build some details of the contents of data
flows, processes and data store. A data dictionary is a structured repository of
data about data .It is a set of rigorous definitions of all DFD data elements and
data structures .

7. Performance

7.1 Security -The banking system must be fully accessible to only authentic
user.

It should require pin for entry to a new environment.

7.2 Reliability-The application should be highly reliable and it should generate

all the updated information in correct order.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 14

7.3 Availability-Any information about the account should be quickly available

from any computer to the authorized user. The previously visited customer’s
data must not be cleared.

7.4 Maintainability-The application should be maintainable in such a manner

that if any new requirement occurs then it should be easily incorporated in an
individual module.

7.5 Portability-The application should be portable on any windows based

system. It should not be machine specific.

3)Hotel management system Purpose

The Software Requirements Specification (SRS) will provide a detailed

description of the requirements for the Hotel Management System (HMS).
This SRS will allow for a complete understanding of what is to be expected
from the newly introduced system which is to be constructed. The clear
understanding of the system and its’ functionality will allow for the correct
software to be developed for the end user and will be used for the development
of the future stages of the project. This SRS will provide the foundation for the
project. From this SRS, the Hotel Management System can be designed,
constructed, and finally tested.

This SRS will be used by the system development team which is constructing
the HMS and the hotel end users. The Project team will use the SRS to fully
understand the expectations of this HMS to construct the appropriate software.
The hotel end users will be able to use this SRS as a “test” to see if the
constructing team will be constructing the system to their expectations. If it is
not to their expectations the end users can specify how it is not to their liking
and the team will change the SRS to fit the end users’ needs.

Document Conventions

The document is prepared using Microsoft Word 2013 and has used the font
type 'Times New Roman'. The fixed font size that has been used to type this
document is 12pt with 1.5 line spacing. It has used the bold property to set the
headings of the document. Use case scenario is written according to Alistair
Cockburn’s template. UML diagrams have been created according to UML 2.0
standards. Standard IEEE template is the template used to organize the
appearance of the document and its flow.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 15

Intended Audience and Reading Suggestions

The intended audience of this document would be owner and specific employees
like Manager and Receptionist of Hotel Gayana, and project team with the
objective to refer and analyze the information. The SRS document can be used
in any case regarding the requirements of the project and the solutions that have
been taken. The document would final provide a clear idea about the system that
is building.

Brief outline of the document is,

1. Overall Description

2. System Features

3. External Interface Requirements

4. Non Functional Requirements

Product Scope

The introducing software, Hotel Management System which is going to be

implemented for Hotel Gayana will automate the major operations of the hotel.
The Reservation System is to keep track in room and hall reservation and check
availability. The Room Management System is for manage all room types room
services. The Inventory Control System will keep track in all inventories of the
hotel and guest details will handled by guest management. Administration
department will monitor the all .There is three End Users for HMS. The End
Users are Owner, Manager and Receptionist. Owner can access to all system
functionalities without any restrictions. Manager can access to all system
functionalities with limited restrictions. Receptionist can only access to the
Reservation management section. To keep restrictions for each End User levels
HMS can create different Login functions.

The objectives of the automated Hotel Management System is to simplify the

day to day processes of the hotel. The system will be able to handle many
services to take care of all customers in a quick manner. As a solution to the
large amount of file handling happening at the hotel, this software will be used
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 16

to overcome those drawbacks. Safety, easiness of using and most importantly

the efficiency of information retrieval are some benefits the development team
going to present with this system. The system should be user appropriate, easy
to use, provide easy recovery of errors and have an overall end user high
subjective satisfaction. Overall Description
Product Perspective-

The Hotel Management System is a new self-contained software product which

will be produced by the project team in order to overcome the problems that
have occurred due to the current manual system. The newly introduced system
will provide an easy access to the system and it will contain user friendly
functions with attractive interfaces. The system will give better options for the
problem of handling large scale of physical file system, for the errors occurring
in calculations and all the other required tasks that has been specified by the
client. The final outcome of this project will increase the efficiency of almost all
the tasks done at the Hotel in a much convenient manner.

Product Functions:-

Make Reservations

Search Rooms

Add Payment

Issue Bills

Manage Guest (Add, Update Guest)

Manage Room Details (Add, Update, Delete)

Manage Staff (Add, Update, Delete, View)

Manage Inventory (Add, Edit, Delete)

Set Rates

Retrieve Reports (Staff payment, Income)

Manage Users (Add, Update, Delete)

Taking Backups
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 17

E-mail notifications

Functional Requirements

Project Documentation-Project Documentation section reveals the all the

details about documents created by the project team so far of this project. It
includes project charter and project proposal.

Project charter: - This document provides the basic information about the team
members their responsible in developing functions, the background of the client
and the nature of the main problem identified

Project Proposal: - The proposal of the project consists with the problems that
are identified with the client, and the solutions that are going to implement using
the proposed system.

User Documentation-

User manual provide to the client will give a clear idea in interacting with the
system. It will be written in a simple understandable language concealing the
inner complexity of the system. A hard copy of the user manual will be
delivered to the client with the delivery of system.

5 Activity Diagrams

Add new Hotel Room

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 18

Edit Hotel Room

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 19

Make Reservation
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 20

Take Backup

Search
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 21

Delete a user

Add Payment
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 22

Other Nonfunctional Requirements Performance Requirements-

Performance requirements define acceptable response times for system

functionality. Although the system is developed suiting for the least system
performances, the performance of the system will highly depend on the
performance of the hardware and software components of the installing
computer. When consider about the timing relationships of the system the load
time for user interface screens shall take no longer than two seconds. It makes
fast access to system functions. The log in information shall be verified within
five seconds causes’ efficiency of the system. Returning query results within
five seconds makes search function more accurate.

Safety Requirements

There are several user levels in hotel management system, Access to the various
subsystems will be protected by a user log in screen that requires a user name
and password. This gives different views and accessible functions of user levels
through the system. Maintaining backups ensure the system database security.
System can be restoring in any case of emergency.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 23

Security Requirements

Customer Service Representatives and Managers and owner will be able to log
in to the Hotel Management System. Customer Service Representatives will
have access to the Reservation/Booking and subsystems. Managers will have
access to the Management subsystem as well as the Reservation/Booking
subsystems. Owner has the maximum privilege to all subsystems. Access to the
various subsystems will be protected by a user log in screen that requires a user
name and password.

Software Quality Attributes

Availability: - The system shall be available during normal hotel operating hours

Correctness: - extent to which program satisfies specifications, fulfills user’s

mission objectives

Efficiency: - How much less number of resources and time are required to
achieve a particular task through the system.

Flexibility: - Ability to add new features to the system and handle them
conveniently.

Integrity: - How the system would insecure the information in the system and
how it avoids the data losses. Referential integrity in database tables and
interfaces

Maintainability: - How easy is to keep the system as it is and correct defects

with making changes.

Portability: - The Hotel Management System shall run in any Microsoft

Windows environment

Reliability: - Specify the factors required to establish the required reliability of

the software system at time of delivery. Mean time between failures and mean
time to recovery

Reusability: - What is the ability to use the available components of the system
in other systems as well.

Testability: - Effort needed to test to ensure performs as intended

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 24

Usability: - How easily a person can be taken the benefits of the system and the
user friendliness.

Robustness: – Strength of the system to handle system functions accurately and

maintain the database without facing to unexpected failures

Maintainability: – What design, coding standards must be adhered to exclusions

created

Other Requirements

When the system is completely developed and submitted to the client, few
sessions will be required to make the users of the system understand about the
functionality of it and some time to adapt to the system. After those sessions, it’s
required that a member from the development team should spend sometime in
the system background for an agreed time period. That time period will be used
in identifying new bugs that could not be reached in the earlier phases of the
development process.

Q2- Prepare DFD (0 & 1 Levels) of the following:

Library management system

DFD depicts the flow of information and the transformation applied when a data
moves in and out from a system. The overall system is represented and
described using input, processing and output in the DFD. The inputs can be:

➢ Book request when a student requests for a book.

➢ Library card when the student has to show or submit his/her identity as a
proof.
The overall processing unit will contain the following output that a system will
produce or generate:
Book will be the output as the book demanded by the student will be given to
them.
Information of demanded 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.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 25

LEVEL 0-

LEVEL 01-

At this level, the system has to show or exposed with more details of processing.
The processes that are important to be carried out are:

➢ Book delivery
➢ Search by topic
List of authors, List of Titles, List of Topics, the bookshelves from which books
can be located are some information that is required for these processes. Data
store is used to represent this type of information.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 26

2) Banking system

Level 0-

Explanation :
➢ Transaction Request/Loan Request –
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 27

In this customer provides the specific details to initiate or support a

transaction and the customer can apply for a loan through the system.

➢ Manager –
The manager can access and manage any request as well as input
commands to change or update Employee Record Database. A Manager
manages the employees of the bank as well as either accepts or rejects
any Loan Request and hence inputs details to update the corresponding
databases as Customer Record and Employee Record Database.

➢ Cashier –
It responds actively to any Transaction Request and assists the Manager.
The cashier can also resolve any query from the Customer and provide
immediate help to the Customer. However, a Cashier cannot access any
database independently.

➢ Bank Headquarter –
It acts as an entity that controls all the branches of the Bank. The entity
can access all the databases, and it also controls the operations of the
Manager. The Bank can modify or eliminate any policies as well as create
new policies for the Online Banking System.

➢ Customer Record –
It stores all the non-personal details of an individual who is a Customer of
any specific branch of the Bank. As an individual initiates a request to
open an account in the Bank, Customer Records creates a new entry that
is unique and specific to the Customer only. This record is accessible by
Managers or Employees of the Banks as and when required.

➢ Employee Record –
It stores the record of all the Employees at the Bank. The record can be
accessed but not modified by the Customer of the Bank. The record can
be modified by either the Manager of a Branch or by the Bank itself.

➢ Account Details –
It stores the personal details of every individual Customer. It can be
accessed/modified by the Customer only. The Bank cannot modify the
personal details of the Customer.
RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 28
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 29

Level 01-

Processes:
➢ Account Management System –
In this Customer can access all the services offered by the Bank by
adding his details. As the Customer avails any services as a transaction or
a loan, then the required data flows to Transaction Management System
or the Loan Management System respectively. Any Customer can print
the activity status of the account which fetches information from all the
available databases using the Generate Customer Report System.

➢ Transaction Management System –

It helps the Customer to add/transfer money to another account. The
Cashier may execute or help execute the transaction process on behalf of
the Bank where the Bank updates all the corresponding details related to
the Customer following a successful transaction.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 30

➢ Loan Management System –

It is used by the Customer to apply or request a Loan from the Bank. The
Manager can access the LoanDetails database to either accept or deny the
request for the Loan. The Bank has the access to modify the Loan
Management System as the Bank can set or modify any policies of the
Loan offered by the Bank.

➢ Online Banking System –

It provides other services like insurance, bill payments, etc.

3) Hotel management system

The Data Flow Diagram (DFD) represents the flow of data and the
transformations in Hotel management system. These transformations occurs as
data enters and exits a system. In the DFD, input, processing, and output are
used to represent and define the overall system.

Hotel Management System DFD Level 0 (Context Diagram)-

The hotel management system level 0 represents a single process with external
entities using the abstract view mechanism. This DFD Level 0 depicts the
overall structure as a single bubble. It comes with incoming/outgoing indicators
showing input and output data.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 31

DFD for Hotel Management System Level 1

Next to the context diagram is the level 1 data flow diagram.

The content of Hotel management system DFD level 1 is gotten from the
context diagram and is broken down into sub processes. System’s DFD Level 1
reveals further processing information. The actors that are going to use this
system and the sub-processes of Hotel Management were shown here.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 32

Q3- Draw Use Case diagram for EXAMINATION PORTAL

EXAMINATION PORTAL- USE CASE DIAGRAM

This Use Case Diagram is a graphic depiction of the interactions among the
elements of Examination Management System. It represents the methodology
used in system analysis to identify, clarify, and organize system requirements of
Examination Management System. The main actors of Examination
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 33

Management System in this Use Case Diagram are: Super Admin, System User,
Examiner, Student, who perform the different type of use cases such as Manage
Students, Manage Examinations, Manage Marks, Manage Courses, Manage
Papers, Manage Faculties, Manage Users and Full Examination Management
System Operations.

Q4- Draw Use Case diagram for RAILWAY RESERVATION SYSTEM.

Use case diagram- Railway reservation system

It represents the methodology used in system analysis to identify, clarify, and

organize system requirements of Railway Reservation System. The main actors
of Railway Reservation System in this Use Case Diagram are:
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 34

Super Admin, System User, Ticket Agent, Customers, who perform the different
type of use cases such as Manage Train, Manage Ticket, Manage Booking,
Manage Customer, Manage Payment, Manage Train Route, Manage Train
Schedule, Manage Users and Full Railway Reservation System Operations.
Major elements of the UML use case diagram of Railway Reservation System
are shown on the picture below.
The relationships between and among the actors and the use cases of Railway
Reservation System:

• Super Admin Entity: Use cases of Super Admin are Manage Train, Manage
Ticket, Manage Booking, Manage Customer, Manage Payment, Manage Train
Route, Manage Train Schedule, Manage Users and Full Railway Reservation
System Operations
• System User Entity: Use cases of System User are Manage Train, Manage
Ticket, Manage Booking, Manage Customer, Manage Payment, Manage Train
Route, Manage Train Schedule
• Ticket Agent Entity: Use cases of Ticket Agent are Book Tickets, Search
Vacant Seats, Collect Payment

• Customers Entity: Use cases of Customers are Search Trains, Book Tickets,
Make Payments
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 35

Q5- Draw Use Case diagram for LIBRARY MANAGEMENT SYSTEM

Some scenarios of the system are as follows :

❖ User who registers himself as a new user initially is regarded as staff or

student for the library system.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 36

❖ For the user to get registered as a new user, registration forms are
available that is needed to be fulfilled by the user.
❖ After registration, a library card is issued to the user by the librarian. On
the library card, an ID is assigned to cardholder or user.
❖ After getting the library card, a new book is requested by the user as per
there requirement.
❖ After, requesting, the desired book or the requested book is reserved by
the user that means no other user can request for that book.
❖ Now, the user can renew a book that means the user can get a new due
date for the desired book if the user has renewed them.
❖ If the user somehow forgets to return the book before the due date, then
the user pays fine. Or if the user forgets to renew the book till the due
date, then the book will be overdue and the user pays fine.
❖ User can fill the feedback form available if they want to.

Q6- Draw Use Case diagram for AIRLINE RESERVATION SYSTEM

This system is the subsystem of the airline reservation system. The actors are
passengers, admins, and the banks that are the organizations. The passenger is
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 37

concerned with multiple use cases like login, check for availability, book ticket,
etc. The book ticket use case is in relation to the choose seat use case. The
admin cancels tickets, updates flight schedules. The bank sees the payment use
cases.

Q7- Draw Use Case diagram for HOTEL MANAGEMENT SYSTEM

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 38

Hotel Management System General Use Case Diagram – This diagram shows
the general processes or functions that the system could do that are based on the
transactions done by the customer and the admin or employee about checking in
or out of the hotel.
The use case diagrams depict the system’s main components as well as the flow
of information between them.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 39

Q8- Draw ER/EER diagram for EXAMINATION PORTAL

This ER (Entity Relationship) Diagram represents the model of Examination

Management System Entity. The entity-relationship diagram of Examination
Management System shows all the visual instrument of database tables and the
relations between Examinations, Courses, Students, Faculties etc. It used
structure data and to define the relationships between structured data groups of
Examination Management System functionalities. The main entities of the
Examination Management System are Students, Examinations, Marks, Courses,
Papers and Faculties
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 40

Q9- Draw ER/EER diagram for RAILWAY RESERVATION SYSTEM.

This ER (Entity Relationship) Diagram represents the model of Railway

Reservation System Entity. The entity-relationship diagram of Railway
Reservation System shows all the visual instrument of database tables and the
relations between Ticket, Customer, Train, Train Route etc. It used structure data
and to define the relationships between structured data groups of Railway
Reservation System functionalities. The main entities of the Railway
Reservation System are Train, Ticket, Booking, Customer, Payment and Train
Route.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 41

Q10- Draw ER/EER diagram for LIBRARY MANAGEMENT SYSTEM

❖ The system keeps track of the staff with a single point authentication
system comprising login Id and password.
❖ Staff maintains the book catalog with its ISBN, Book title, price(in INR),
category(novel, general, story), edition, author Number and details.
❖ A publisher has publisher Id, Year when the book was published, and
name of the book.
❖ Readers are registered with their user_id, email, name (first name, last
name), Phone no (multiple entries allowed), communication address. The
staff keeps track of readers.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 42

❖ Readers can return/reserve books that stamps with issue date and return
date. If not returned within the prescribed time period, it may have a due
date too.
❖ Staff also generate reports that has readers id, registration no of report,
book no and return/issue info.

Q11- Draw ER/EER diagram for AIRLINE RESERVATION SYSTEM

Airline Reservation System ER Diagram Based on the image above, the

EntityRelationship diagram for Airline Reservation system tables includes the
following: customer, admin, airline ticket, reservation, transaction, schedule,
and reports.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 43

Q12- Draw ER/EER diagram for HOTEL MANAGEMENT SYSTEM

The ER Diagram for hotel management system in dbms reveals the relationships
of the hotel management entities within the project database. This describes the
logical structure of the system’s database or data storage. It is done by
identifying the hotel management process entities, their properties, and the
interactions between them.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 44

Q13- Draw use case of an ATM system with at least 3 different actors that
interact with system.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 45

Q14- Draw sequence and collaboration diagram for Library Management

System.

Collaboration diagram-

Sequence diagram-
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 46

Q15- Draw sequence and collaboration diagram for Airline Reservation System.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 47

Collaboration diagram-

Sequence –
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 48

Q16- Draw sequence and collaboration diagram for Railway Reservation

System.

Sequence diagram-
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 49

Collaboration -

Q17- Draw sequence and collaboration diagram for Examination Portal.

Collaboration diagram –
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 50

Sequence diagram –

Q18- Draw sequence and collaboration diagram for an Hotel Management

System ,.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 51

Sequence diagram-

Collaboration diagram-
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 52

Q19- Draw class diagram of an ATM system.

A class diagram for ATM in UML is a series of boxes and connectors. All you
need to make your own class ATM diagram is a collection of shapes, some
connecting links, and an idea of what your ATM system and financial
transactions might look like.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 53

Q20- Draw class diagram for Hospital Management System.

The above is the Class Diagram for Hospital Management

System represents. It is also denoted by the Hospital domain Model Diagram.
The Domain Model for Hospital Management System is depicted by multiple
class diagrams.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 54

The diagram gives you a brief idea about the Hospital management process that
has small but important substructures such as staff structure, hospital structure,
patient treatment terminology, and relationship with patients.

• Patient Class: To superviseall the operations of Patient

• Doctors Class: To superviseall the operations of Doctors
• Bill Class: To superviseall the operation bills
• Receptionist Class: To superviseall the Appointments

Q21- Draw class diagram for Library Management System.

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 55

❖ Library Database: Our library database lists all the items in the inventory.
It also allows librarians to add, update, delete, search and display
information about each book.
❖ Librarian: The librarian class gives each librarian an ID number.
❖ Members: The member class gives each member a unique ID. It also
shows the date of membership, the maximum number of books they
might check out, and the members’ names and addresses.
❖ Transaction: The transaction class gives each translation a unique ID. It
lists the member’s ID and the books checked out and their due date.
❖ Bill: The bill class issues a bill for overdue books, with a unique bill
number and the date along with the member’s ID and the amount owed.
❖ Book: The book class lists all the information about each book–title,
subject, identification number, edition, and subject.
❖ Author: The author class shows the name and biography of each author.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 56

Q22- Draw class diagram for Airline Reservation System.

Airlines Reservation System Class Diagram describes the structure of a Airlines

Reservation System classes, their attributes, operations (or methods), and the
relationships among objects.

The main classes of the Airlines Reservation System are Airlines, Reservation,
Passenger, Ticket Booking, Employee, Airline Enquiry Classes of Airlines
Reservation System.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 57

Q23- Draw class diagram for a ticket distributor for a train system.
 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 58

Q24- Draw activity diagram for ATM.

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 59

Q25-Draw activity diagram for AIRLINE RESERVATION SYSTEM.

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 60

Q26-Draw activity diagram for LIBRARY MANAGEMENT SYSTEM.

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 61

Q27-Draw activity diagram for HOTEL MANAGEMENT SYSTEM.

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 62

Q28-Draw a state chart diagram for HOTEL MANAGEMENT SYSTEM.

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 63

Q29-Draw a state chart diagram for AIRLINE RESERVATION SYSTEM.

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 64

Q30-Draw deployment diagram for AIRLINE RESERVATION SYSTEM.

 RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 65

Q31-Draw deployment diagram for HOSPITAL MANAGEMENT SYSTEM.

RyanSteveBraganza
5 0 1 1 3 0 0 4 4 2 1 | 66