SOFTWARE ENGINEERING LAB MANUAL

Case Studies

1. Banking System

2. Hotel management system

3. Inventory Control System

4. Library management system

5. Railway Reservation System

4. Library management system

1. Problem Statement:

The library management system aims to revolutionize the way libraries operate by leveraging
technology to enhance accessibility and efficiency. With the proliferation of mobile devices, there is a
growing demand for library services that can be accessed remotely. Therefore, the system will provide a
user-friendly platform for patrons to search for and borrow books using their mobile phones.
Additionally, it will streamline the library management process, making it easier for library staff to
manage resources and serve patrons effectively.

2. SRS Document:

1. Introduction:

The Library Management System (LMS) is a software solution designed to modernize and streamline
library operations. By harnessing the power of technology, the system aims to provide patrons with
convenient access to library resources while simplifying administrative tasks for library staff. This
document outlines the requirements and specifications for the development of the LMS.

2. Purpose:

The purpose of the LMS is to:

 Maintain accurate records of library resources, including books and periodicals.

 Facilitate seamless borrowing and returning of library materials for registered patrons.

 Enable patrons to search for and reserve books remotely using a mobile application.

 Provide library staff with tools to efficiently manage inventory, issue library cards, and track user
activity.

 Enhance the overall user experience by offering intuitive interfaces and convenient access to
library services.

3. Scope:
The LMS will encompass the following key features:

 User Registration: Patrons can register for library membership and receive a unique
identification card.

 Book Search and Reservation: Patrons can search for books by title, author, or category and
reserve them for pickup.

 Borrowing and Returning: Patrons can borrow books from the library by scanning their library
card and return them at their convenience.

 Inventory Management: Library staff can add new books, update existing records, and remove
lost or damaged items from the inventory.

 Feedback Submission: Patrons can provide feedback on library services and suggest new
acquisitions.

4. Definitions, Acronyms, and Abbreviations:

 LMS: Library Management System

 RFID: Radio-Frequency Identification

 API: Application Programming Interface

 UI: User Interface

 UX: User Experience

5. References:

This document follows the IEEE Software Requirements Specification format.

6. Technologies and Tools:

 Frontend: HTML, CSS, JavaScript

 Backend: Java, Servlets, JSP

 Database: MySQL

 Mobile Development: Android Studio

 Version Control: Git

 IDE: IntelliJ IDEA, Eclipse

7. Overview:

The SRS document is divided into two sections:

 Overall Description: Describes the system components and their interconnections.

 Specific Requirements: Outlines the roles and functions of the system actors.
8. Overall Description:

8.1 Product Perspective:

The LMS will maintain real-time records of library resources, updating them automatically upon book
issuance and return. It will integrate seamlessly with existing library infrastructure and provide a user-
friendly interface for both patrons and staff.

8.2 Software Interface:

The frontend will be developed using HTML, CSS, and JavaScript, while the backend will be powered by
Java and MySQL. The mobile application will be built using Android Studio, ensuring compatibility with a
wide range of devices.

8.3 Hardware Interface:

The system will interact with RFID scanners for book identification and barcode readers for library card
authentication. It will also utilize standard computer hardware for server deployment.

8.4 User Characteristics:

The system will cater to three levels of users:

 Patrons: Can search for and reserve books, borrow and return library materials, and provide
feedback on services.

 Library Staff: Can manage inventory, issue library cards, and perform administrative tasks.

 Administrators: Oversee system operations, register users, and maintain database integrity.

8.5 Constraints:

Users must have access to a computer or mobile device with an internet connection to utilize the system
effectively.

8.6 Assumptions and Dependencies:

Users are assumed to have basic computer literacy and proficiency in the English language.
3. ER Diagram

Entities:

 Book: Attributes: ISBN (Primary Key), Title, Author, Genre, Published Year, Copies Available, etc.

 Readers: Attributes: User ID (Primary Key), Name, Email, Address, Phone Number, etc.

 Staff: Attributes: Staff ID (Primary Key), Name, etc.

 Authentication System: Attributes: Login ID (Primary Key) and Password

 Publisher: Attributes: Publisher ID (Primary Key) , Year of Publication, Name, etc.

 Reports: Attributes: Reg No(Primary Key), User ID, Book No, Issue/Return

Relationships:

1. Borrow (Association between Readers and Book):

 A Reader can borrow multiple books.

  A Book can be borrowed by multiple Readers.

 Attributes: Borrow Date, Return Date

2. Manage (Association between Staff and Book):

 A Staff member manages the catalogue, which includes adding, updating, or removing
books.

 A Book is managed by a Staff member.

 Attributes: Management Date, Operation Type (Add/Update/Remove)

3. Issue (Association between Staff and Readers):

 A Staff member issues library cards to Readers.

 A Reader can have only one Staff member issuing their card.

 Attributes: Issue Date, Expiry Date

4. Authenticate (Association between Authentication System and Staff/Readers):

 The Authentication System authenticates Staff and Readers during the login process.

 Attributes: Last Login Date, Login Attempts

5. Publisher (Association between Book and Publisher):

 A Book is published by a Publisher.

 A Publisher can have multiple books.

 Attributes: Publication Date

6. Manages (Association Between Staff and Report):

 A Report is generated for transactions involving Readers and Books.

 Attributes: Generation Date, Report Type (Issue/Return)

4. Data flow Diagrams
5. Use Case diagrams
OR
6. Activity Diagram
7. Sequence Diagram

8. Collaboration Diagram
9. Class diagram
5. Railway Reservation System
Problem Statement:

The existing manual system for railway ticket reservation is time-consuming and inefficient. With the
increasing number of passengers, there is a need for an automated online reservation system to
streamline the process. Our project aims to develop software for an Online Railway Reservation System
that allows users to conveniently book and manage their tickets from the comfort of their homes.

SRS Document:

1.0 Introduction:

The manual ticket reservation process is slow and limited in capacity. To address this, we propose an
Online Railway Reservation System that allows users to book tickets online. This system leverages
modern programming and database techniques to simplify the reservation process and accommodate
the growing demand for railway tickets.

1.1 Purpose:

The purpose of the system is to automate the ticket reservation process and improve efficiency. By
providing an online interface for ticket booking, the system reduces the time and effort required for
reservation. It also enhances security and accuracy by digitizing passenger information and ticket
records.

1.2 Scope:

 The system enables users to register and book tickets online, eliminating the need for manual
reservation.

 Railway authorities can use the system to manage ticket bookings and process applications more
efficiently.

 The system facilitates communication between passengers and administrators, providing

updates on application status and verification requirements.

1.3 Definitions, Acronyms, and Abbreviations:

 Passenger: An individual who wishes to obtain a railway ticket.

 PNR: Passenger Name Record, used to identify and manage passenger information.

 HTML: Hypertext Markup Language, used for creating web pages.

 J2EE: Java 2 Enterprise Edition, a programming platform for developing distributed Java
applications.

 HTTP: Hypertext Transfer Protocol, used for communication between web servers and clients.

 TCP/IP: Transmission Control Protocol/Internet Protocol, the communication protocol used on

the Internet.

1.4 References:
This document follows the IEEE Software Requirement Specification format.

1.5 Technologies to be Used:

 Frontend: HTML, JSP, JavaScript

 Backend: Java

 Database: Oracle 11g

1.6 Tools to be Used:

 Eclipse IDE for Java development

 Rational Rose or StarUML for UML modeling

1.7 Overview:

The SRS document is divided into two sections: Overall Description and Specific Requirements. The
Overall Description outlines the major components and connections of the system, while the Specific
Requirements detail the roles and functions of the actors.

2.0 Overall Description:

2.1 Product Perspective:

The system aims to provide a user-friendly interface for online ticket reservation while ensuring the
security of stored data. It prioritizes simplicity and efficiency to minimize the ticket booking duration.

2.2 Software Interface:

 Frontend: Passenger and system interfaces built using JSP and HTML, while the administrator
interface is built using Java.

 Web Server: Apache Tomcat Server

 Backend: Oracle 11g database

2.3 Hardware Interface:

The server is connected to client systems, providing access to the database.

2.4 System Functions:

 Secure registration of passenger information

 Generation of reports from the database

 Display of requested pages to users

 Database update after every successful transaction

2.5 User Characteristics:

Passengers are individuals seeking to book railway tickets and submit their information to the database.
2.6 Constraints:

 Passengers require a computer to access the system.

 Constant monitoring is necessary to prevent intrusion.

 Users must exercise caution when submitting information.

2.7 Assumptions and Dependencies:

 Applicants and administrators have basic computer knowledge.

 Applicants may need to scan and submit documents.

3. ER diagram

Entities and Attributes:

 1. Train Entity:

 Attributes: train_id (Primary Key), train_name, train_number, train_seat_number,

train_ticket, train_type, train_description

2. Ticket Entity:

 Attributes: ticket_id (Primary Key), ticket_customer_id (Foreign Key), ticket_type,

ticket_date, ticket_description

3. Booking Entity:

 Attributes: booking_id (Primary Key), booking_title, booking_type, booking_ticket

(Foreign Key), booking_date, booking_description

4. Customer Entity:

 Attributes: customer_id (Primary Key), customer_name, customer_mobile,

customer_email, customer_username, customer_password, customer_address

5. Payment Entity:

 Attributes: payment_id (Primary Key), payment_customer_id (Foreign Key),

payment_date, payment_amount, payment_description

6. Train Route Entity:

 Attributes: train_route_id (Primary Key), train_route_name, train_route_type,

train_route_description

Description of Railway Reservation System Database:

 The details of trains are stored in the Train table, along with their attributes.

 Each entity (Train Route, Booking, Payment, Ticket, Train) contains primary keys for unique
identification.

 The Booking and Payment entities are associated with the Train and Ticket entities using foreign
keys to maintain referential integrity.

 There are one-to-one and one-to-many relationships available between Payment, Customer,
Train Route, and Train, ensuring efficient data organization and retrieval.

 All entities (Train, Payment, Booking, Train Route) are normalized to reduce data redundancy
and ensure consistency.

 Normalization techniques such as breaking down data into smaller, more manageable tables,
and eliminating repeating groups have been applied to reduce duplicacy of records and maintain
data integrity.

4. Data flow diagram

5. Use Case Diagram
6. Activity Diagram
7. Sequence Diagram
8. Collaboration Diagram

9. Class Diagram