Scribd
Upload
3 views

Software Enginnering Project File(to Submit)

The document outlines a Software Engineering Practical File for a Railway Reservation System, detailing the problem statement, software requirements specification (SRS), and various diagrams such as use case, class, activity, and sequence diagrams. The proposed system aims to modernize the outdated manual railway reservation process by providing real-time information, secure payment processing, and improved customer service. It includes functional and non-functional requirements, user classes, and design constraints to ensure a comprehensive and user-friendly application.

Uploaded by

tiwari.peeyush2006
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
3 views

Software Enginnering Project File(to Submit)

The document outlines a Software Engineering Practical File for a Railway Reservation System, detailing the problem statement, software requirements specification (SRS), and various diagrams such as use case, class, activity, and sequence diagrams. The proposed system aims to modernize the outdated manual railway reservation process by providing real-time information, secure payment processing, and improved customer service. It includes functional and non-functional requirements, user classes, and design constraints to ensure a comprehensive and user-friendly application.

Uploaded by

tiwari.peeyush2006
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

VIVEKANANDA INSTITUTE OF PROFESSIONAL STUDIES

VIVEKANANDA SCHOOL OF INFORMATION TECHNOLOGY

BACHELOR OF COMPUTER APPLICATION


Software Engineering Practical File
Paper Code: BCA 108P

SUBMITTED TO: SUBMITTED BY:


Ms. Chhaya Gupta Name: Peeyush Tiwari
Assistant Professor Enrolment No.: 09217702024
VSIT, VIPS BCA -2B
INDEX

S.NO. Name Of Practical SIGNATURE

1 Select and Write down the problem statement


for a real time system of relevance.
2 Analyze requirement for a system and develop
Software Requirement Specification Sheet
(SRS) for suggested system.

3 To create the function oriented diagram: Data


Flow Diagram (DFD)

4 To perform the user’s view analysis for the


suggested system: Use case diagram.

5 To draw the structural view diagram for the


system: Class diagram

6 To draw the behavioral view diagram : State-


chart diagram or Activity diagram

7 To perform the behavioral view diagram for the


suggested system : Sequence diagram

8 Draw the component diagram.

9 Draw the Deployment diagram.


RAILWAY RESERVATION SYSTEM
PROBLEM STATEMENT:-

The ABC Railway Corporation is currently using an outdated, manual railway reservation
system that is inefficient, time-consuming, and error prone. This system is causing
multiple issues, including delayed bookings, inaccurate train schedules, and poor
customer service. The Corporation has recognized the need for a new, modernized
railway reservation software system that can streamline operations, provide accurate
real-time information, and offer a seamless user experience.

The existing manual system has led to the following challenges:

Inefficient booking process: The current system requires customers to visit railway
stations or authorized ticket booking agents, which is time-consuming and
inconvenient.

Limited access to real-time information: Users are unable to access accurate train
schedules, seat availability, or waitlist status updates, leading to confusion and
dissatisfaction.

Inadequate search capabilities: Customers cannot search for trains based on


multiple criteria, such as destination, travel dates, and preferred class, resulting in a
tedious and frustrating booking experience.

Insecure payment processing: The existing system lacks a secure and reliable online
payment processing solution, posing potential risks for customers and the corporation.

No support for mobile devices: The current system is not optimized for mobile
devices,limiting the accessibility and convenience for users on the go.

Poor customer service: The lack of a centralized customer support system results in
delayed responses, inconsistent information, and overall dissatisfaction among
passengers.

The proposed railway reservation software system aims to address these challenges by
offering a comprehensive, user-friendly platform that integrates real-time train
schedules, advanced search functionality, secure payment processing, and an efficient
ticket booking process. Additionally, the software will feature mobile compatibility,
multi-language support, and accessibility features to cater to a diverse user base. The
system will also provide customer support through various channels, such as live chat,
phone, and email, to ensure timely and effective assistance. By implementing this new
railway reservation software system, the ABC Railway Corporation will significantly
enhance customer satisfaction, streamline operations, and improve overall efficiency.
Software Requirements Specification (SRS)

Project Title: Railway Reservation System


Prepared by: Peeyush Tiwari

1. Introduction
1.1 Purpose
The purpose of this document is to provide a detailed Software Requirements
Specification (SRS) for the Railway Reservation System. It is intended to define the
system’s functionality, constraints, and interface requirements for developers, testers,
and stakeholders.
1.2 Scope
This system will automate the railway ticket booking process. It will allow users to check
train availability, book tickets, cancel bookings, and view schedules. It will also provide
admin functionalities for managing trains, seats, and user records.
1.3 Definitions, Acronyms, and Abbreviations
• SRS: Software Requirements Specification
• UI: User Interface
• DB: Database
• PNR: Passenger Name Record
1.4 References
• IEEE Std 830-1998 Software Requirements Specification
• Indian Railways Reservation Portal (for benchmarking)
1.5 Overview
The rest of the document outlines system features, use cases, non-functional
requirements, and system constraints in detail.

2. Overall Description

2.1 Product Perspective


The Railway Reservation System will be a web-based application that interacts with a
central database. It is a self-contained system but can be integrated with existing
payment gateways and notification systems (email/SMS).
2.2 Product Functions
• User registration and login
• Train schedule viewing
• Ticket booking and cancellation
• Payment integration
• PNR status checking
• Admin panel for train and user management
2.3 User Classes and Characteristics
• Passenger: Can register, book/cancel tickets, check schedule, and PNR status.
• Admin: Can add/remove trains, manage users, and view system logs.
2.4 Operating Environment
• Platform: Web-based (HTML, CSS, JavaScript frontend; backend with Node.js /
PHP / Java)
• Database: MySQL / MongoDB
• OS: Cross-platform (Windows, Linux, macOS)
2.5 Design and Implementation Constraints
• The system must follow security standards to protect user data.
• Database should maintain ACID properties.
• Scalability should be considered for future expansion.
2.6 User Documentation
• User Manual
• Admin Guide
• Online Help / FAQs
2.7 Assumptions and Dependencies
• Users will have internet access.
• Payment processing depends on third-party gateway availability.

3. Specific Requirements

3.1 Functional Requirements


FR1: The system shall allow users to register and log in.
FR2: The system shall display available trains between two stations.
FR3: The system shall allow users to book a ticket and generate a PNR.
FR4: The system shall allow users to cancel a booking.
FR5: The system shall show PNR status and ticket details.
FR6: The system shall allow admins to add or remove trains.
FR7: The system shall send booking confirmations via email/SMS.
3.2 Non-Functional Requirements
• Performance: The system should respond within 2 seconds for 90% of queries.
• Reliability: 99.9% uptime is required.
• Usability: The interface must be intuitive for end users.
• Security: Passwords should be encrypted. Secure login (OAuth or CAPTCHA).
• Maintainability: Code should be modular and well-documented.
3.3 Interface Requirements
• User Interface: Web-based with responsive design
• Hardware Interface: Standard client-server architecture
• Software Interface: Database (MySQL/MongoDB), Payment Gateway APIs,
Email/SMS APIs
• Communication Interface: HTTP/HTTPS for communication
USECASE DIAGRAM:-
CLASS DIAGRAM:-
ACTIVITY DIAGRAM:-
SEQUENCE DIAGRAM:-

You might also like