Final Project 2

COURSE TITLE: SOFTWARE ENGINEERING
COURSE CODE: CT-365

BCIT SOFTWARE ENGINEERING TEAM
NAME ROLL NO.
Inshaal Navid Malik CT-21077
Sheeban Ali CT-21095
Muhamad Hudaib Waseem CT-21086
Ahmed Siddiqui CT-21078
CUSTOMERS/ STAKEHOLDERS
NAME ROLL NO.
Ahmed Ubaidullah CT-21092
Muhammad Ali CT-21093
Hasnain Ali CT-21073
Farman CT-21065
Asadullah CT-21066
Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements
Specification
For
Railway Reservation System (RRS)
Version 1.0 approved
Prepared by BCIT Software Engineering Team
11 December 2023
Copyright © 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.
Software Requirements Specification for RRS Page iii
Table of Contents
Table of Contents..........................................................................................................................iii
Revision History............................................................................................................................iv
1. Introduction..............................................................................................................................1
1.1 Purpose..............................................................................................................................................1
1.2 Document Conventions.....................................................................................................................1
1.3 Intended Audience and Reading Suggestions...................................................................................1
1.4 Project Scope.....................................................................................................................................2
1.5 References.........................................................................................................................................3
2. Overall Description..................................................................................................................3
2.1 Product Perspective...........................................................................................................................4
2.2 Product Features................................................................................................................................4
2.3 User Classes and Characteristics.......................................................................................................4
2.4 Operating Environment.....................................................................................................................4
2.5 Design and Implementation Constraints...........................................................................................5
2.6 User Documentation..........................................................................................................................5
2.7 Assumptions and Dependencies........................................................................................................5
3. System Features........................................................................................................................5
3.1 User Registration and Authentication...............................................................................................5
3.2 Train Schedule...................................................................................................................................6
3.3 Ticket booking and Reservation........................................................................................................7
3.4 Payment.............................................................................................................................................7
3.5 Real Time Train Tracking.................................................................................................................8
3.6 View and Modify Booking................................................................................................................8
3.7 Notification........................................................................................................................................8
3.8 Feedback And Support......................................................................................................................9
3.9 User Management..............................................................................................................................9
3.10 Train Schedule Management...........................................................................................................10
3.11 Train Status Update.........................................................................................................................11
3.12 Ticket Validation.............................................................................................................................11
3.13 Train Status Update.........................................................................................................................11
3.14 View Train Schedule.......................................................................................................................12
3.15 Customer Support............................................................................................................................12
3.16 Train Information............................................................................................................................12
3.17 Registration and Login....................................................................................................................13
4. External Interface Requirements..........................................................................................13
4.1 User Interfaces.................................................................................................................................13
4.2 Hardware Interfaces.........................................................................................................................14
4.3 Software Interfaces..........................................................................................................................15
4.4 Communications Interfaces.............................................................................................................15
5. Other Nonfunctional Requirements.....................................................................................16
5.1 Performance Requirements.............................................................................................................16
5.2 Safety Requirements........................................................................................................................16
5.3 Security Requirements.....................................................................................................................16
5.4 Software Quality Attributes.............................................................................................................16
6. Other Requirements...............................................................................................................17
Appendix A: Glossary..................................................................................................................19
Appendix B: Analysis Models.....................................................................................................20
Appendix C: Issues List...............................................................................................................23
Software Requirements Specification for RRS Page iv
Revision History
Name Date Reason For Changes Version
Software Requirements Specification for RRS Page 1
1. Introduction
1.1 Purpose
The purpose of this Software Requirement Specification (SRS) is to define the functional and non-
functional requirements for the development of the project Railway Reservation System (RRS).
This system aims to streamline and enhance various aspects of railway operations, including but not
limited to scheduling, ticketing, passenger information, maintenance, and overall management. The
SRS serves as a guide for stakeholders, developers, and testers to understand the scope and
expectations for the successful implementation of the railway system.
1.2 Document Conventions

In this document a consistent font style is maintained with the descriptions being 12 font Times
New Roman. Headings are highlighted in bold and maintain an 18 font Times New Roman for
main headings and 14 font Times New Roman for sub headings. Additionally and links
provided in the document are highlighted in blue color. The document also uses some
abbreviations in the system feature section which is used to distinguish which feature is for which
user. They are also highlighted in bold and are as follows.
 FRP: Used to describe the System features which are intended for the use of the passenger.
 FRA: Used to describe the system features which are intended to be used by
the administration.
 FRC: Used to describe the system features which are to be used by the conductor or
train staff.
 FRG: Used to describe the system features for unauthenticated user.
1.3 Intended Audience and Reading Suggestions

This document is strategically crafted to cater to a diverse audience involved in the planning,
development, and operation of the Railway Management System. It serves as a comprehensive
guide and agreement among stakeholders. The following are the primary audience groups for this
document:
1.3.1 Stakeholders' Authorities: Top-level executives, decision-makers, and leaders overseeing

the implementation and management of the Railway Management System. This document
provides insights into strategic implications and alignment with organizational goals.
1.3.2 System Architects and Design Team: Architects, system designers, and engineers
responsible for conceptualizing and structuring the Railway Management System. This
document outlines the system's design principles, ensuring a clear understanding of the
architecture.
1.3.3 Developers and IT Professionals: Software developers, programmers, and IT specialists

responsible for building and maintaining the technical infrastructure of the Railway Management
System. This document details the technical specifications, software requirements, and
integration protocols.
1.3.4 Project Managers and Coordinators: Professionals overseeing the planning, execution,
and coordination of the Railway Management System project. This document provides critical
insights into project timelines, resource allocations, and key milestones.
1.3.5 Operations and Maintenance Team: Teams responsible for the day-to-day operations,
maintenance, and support of the Railway Management System. This document includes
operational guidelines, troubleshooting procedures, and system maintenance requirements.
1.3.6 Security and Compliance Teams: Security analysts, compliance officers, and risk
management professionals. This document highlights security protocols, compliance standards,
and risk mitigation strategies specific to the Railway Management System.
1.3.7 Quality Assurance and Testing Team: Testing and quality assurance professionals
tasked with ensuring the reliability and functionality of the Railway Management System. This
document outlines testing criteria, scenarios, and procedures for comprehensive quality testing.
1.4 Project Scope:

The Railway Management System is a comprehensive software solution designed to streamline and
enhance the efficiency of railway operations. It encompasses a wide range of features aimed at
optimizing various aspects of railway management. The product scope is outlined as follows:
1.4.1 Train Operations Management: Efficient scheduling and management of train

operations, including route planning, allocation of resources, and real-time tracking of train
movements.
1.4.2 Passenger Management: Facilitation of passenger reservations, ticketing, and boarding

processes. The system ensures a smooth and organized experience for passengers from booking
to disembarkation.
1.4.3 Cargo and Freight Management: Handling and monitoring of cargo and freight
logistics, from booking to delivery. The system optimizes cargo routes, tracks shipments, and
manages inventory.
1.4.4 Maintenance and Repairs: Tracking and scheduling maintenance activities for trains,
tracks, and related infrastructure. The system aids in proactive maintenance planning to minimize
downtime and ensure safety.
1.4.5 Employee and Crew Management: Management of railway staff, including scheduling,
training, and performance tracking. The system ensures proper allocation of crew members for
each train and monitors their certifications.
1.4.6 Financial Management: Tracking financial transactions related to ticket sales, cargo
bookings, and other revenue streams. The system provides comprehensive financial reports
for analysis and decision-making.
1.4.7 Reporting and Analytics: Generation of detailed reports and analytics on various aspects
of railway operations. This includes performance metrics, passenger demographics, and financial
summaries.
1.4.8 Security and Safety Features: Implementation of robust security measures to ensure the
safety of passengers, staff, and infrastructure. Integration with surveillance systems and
emergency response protocols.
1.4.9 Communication and Information Sharing: Facilitation of communication among

railway staff, passengers, and relevant stakeholders. Real-time updates on train status, delays, and
other important information.
1.4.10 Integration with External Systems: Compatibility with external systems, such as
transportation networks, emergency services, and maintenance suppliers, to ensure
seamless interoperability
1.5 References
1.5.1 For UI Style Guides:

 https://themeforest.net/item/book-your-train-online-booking-psd-template/11431825
 https://xdfile.com/online-train-ticket-booking-service-xd-website-template/
2. Overall Description
The Overall Description provides a high-level overview of the railway system, including its
perspective, features, user classes, operating environment, constraints, user documentation, and
underlying assumptions and dependencies.
2.1 Product Perspective
Before the implementation of the proposed system, let us first discuss the problems faced by the
existing manual system which are:
1. High probability of errors due to manual data entry and extensive paperwork.
2. The use of paper as a means of storage posed security risks, as data could be lost, stolen,
or destroyed in natural disasters.
3. The manual system was time-consuming and slow.
4. Additionally, the difficulty in managing data, such as adding, deleting, or editing

information, created many problems and increased the workload on railway
employees.
The proposed computerized system aims to address these challenges and bring about significant
benefits such as:
1. The transition to a computerized environment will reduce the use of paper,

minimizing paperwork which will in return lead to less workload on employees.
2. Automation of calculations within the system will enhance accuracy, reducing the
likelihood of errors that were prevalent in the manual system.
3. Moreover, the computerized system will enforce strict access controls, ensuring that
only authorized users have access to sensitive data, thereby enhancing data security.
Overall, the proposed system is designed to optimize operational efficiency, reduce manual errors,
and provide a secure and streamlined approach to railway management.
2.2 Product Features
The system provides an extensive set of features catering to different user classes. Passengers can
register, book tickets, receive real-time updates, and provide feedback. Administrators can manage
user accounts, train schedules, and receive real-time updates from conductors. Conductors can
validate tickets and report train status. Key features include user authentication, real-time tracking,
flexible booking options, and comprehensive user management capabilities for administrators.
2.3 User Classes and Characteristics

The system caters to three primary user classes:
1. Passengers can register an account book or reserve train tickets as well as track trains
and modify or cancel bookings as well as provide feedback.
2. Administrators can manage the system such as managing the user’s data, changing
train routes/fares/schedule etc.
3. Conductors can validate tickets and report train status.
Passengers are diverse, ranging from occasional travelers to frequent commuters, while
administrators and conductors possess roles crucial for the system's smooth operation, requiring
administrative privileges and the ability to interact with real-time train data.
2.4 Operating Environment
The railway system operates in a digital environment accessible through web browsers as well as
mobile devices. Passengers interact through a user-friendly web interface or mobile app,
administrators manage the system through a web-based portal, and conductors utilize handheld
devices which contain system interface for QR code scanner for ticket validation. The system can
run on any system which contains a Windows/ Linux/ Mac operating system, a Pentium processor
as well as 2 GB Ram and 10 GB Storage. In mobile devices it will run on android version 9 with 2
GB Ram and 8 GB Storage.
2.5 Design and Implementation Constraints
Design and implementation constraints include compatibility with various devices and browsers,
adherence to security protocols to safeguard user data, and the need for scalability to accommodate
potential growth in user interactions. Cross-platform compatibility, accessibility standards, and
secure communication are integral considerations during the system's development.
2.6 User Documentation
The system will provide an online documentation as well as an online tutorial when the user creates
an account on the system. This will help the user in getting to know about the system.
2.7 Assumptions and Dependencies
The successful operation of the railway system assumes reliable internet connectivity for users,
administrators, and conductors. Dependencies include the availability of third-party services for
online payments and the integration of QR code scanners for conductors. Additionally, the system
relies on accurate and timely train schedule data for real-time tracking and updates.
3. System Features
Designing a SRS for Railway Reservation System (RRS) would require a large range of features and
functionalities which are specifically made for the passenger, administration and conductor’s needs.
Following are some of the main system features that are necessary for the system.
3.1 User Registration and Authentication (FRP)
3.1.1 Description: Enables users to create an account by providing personal information

and authenticate themselves for accessing the system.
3.1.2 Stimulus/Response Sequences:
 Stimulus: User selects the registration option.
 Response: System prompts for required information and validates entries.

 Stimulus: User agrees to terms and conditions.
 Response: System validates and registers the user.
3.1.3 Functional Requirements:
1. The system shall prompt the user to provide Name, Email-id, Password, Contact
Number, Date of Birth, and CNIC Number during the registration process.
2. Account creation shall not proceed unless all required fields are filled.
3. The system shall validate the provided information before registering the user.
4. Users must agree to the terms and conditions to complete the registration.
5. Users must be 18 years or older to create an account.
6. The contact number provided must be an 11-digit numeric number.
3.2 Train Schedule (FRP)
3.2.1 Description: Allows users to check train schedules, including stations, arrival/departure
times, and real-time seat availability.
 Stimulus: User selects a specific train.
 Response: System displays detailed information about the train schedule, stations, and
seat availability.
 Stimulus: User checks real-time seat availability.
 Response: System updates and displays current seat availability.
1. Users shall have the ability to view detailed train schedules, including stations, arrival,
and departure times.
2. The system shall provide real-time updates on seat availability.
3. The system shall display the number of available seats and booked/reserved seats for
a selected train.
3.3 Ticket Booking and Reservation (FRP)
3.3.1 Description: Enables users to book or reserve seats by entering destination, departure date,
and time, including selecting a preferred train, seat, fare calculation, and initiating online
payment.
 Stimulus: User enters destination, date, and time.
 Response: System displays a list of trains with available seats.
 Stimulus: User selects preferred train and seats.
 Response: System calculates fare and initiates the online payment process.
1. Users shall enter destination, departure date, and time to search for available trains.
2. The system shall display a list of trains with available seats based on the entered criteria.
3. Users shall select a preferred train and seats.
4. The system shall calculate the fare for the selected booking.
5. The system shall initiate the online payment process.
3.4 Payment (FRP)
3.4.1 Description: Facilitates the payment process for booked or reserved tickets, offering
multiple payment options.
 Stimulus: User completes the booking process.
 Response: System generates a payment slip.
 Stimulus: User chooses a payment method.
 Response: System processes the payment and generates a digital e-ticket.
1. The system shall produce a payment slip after the booking process is completed.
2. Users shall have the option to pay using credit cards or any online banking app
(e.g., Sadapay, Payoneer, and Easypaisa).
3. After successful payment, the system shall generate a digital e-ticket containing a QR code.
3.5 Real-Time Train Tracking (FRP)
3.5.1 Description: Allows users to track the real-time location of the booked train, stations
passed, and provides updates on any delays.
 Stimulus: User selects the train tracking option.
 Response: System displays the current location of the train, stations passed, and any delays.
1. Users shall have the ability to track the real-time location of the booked train.
2. The system shall display the stations the train has passed through.
3. Users shall receive updates on any delays in the arrival of the train.
3.6 View and Modify Bookings (FRP)
3.6.1 Description: Provides users with the ability to view past bookings and modify
existing bookings, including changing departure times, seats, and canceling bookings.
 Stimulus: User selects the bookings option.
 Response: System displays past bookings.
 Stimulus: User selects a booking to modify.
 Response: System allows changes to departure time, seats, or cancellation.
1. Users shall have the ability to view their past bookings.
2. Users shall be able to modify bookings, including changing departure times and seats.
3. Users shall be able to cancel a booking and book a new ticket if desired.
3.7 Notifications (FRP)
3.7.1 Description: Users receive notifications for booking confirmation, delays, cancellations,
and other relevant alerts.

 Stimulus: Booking confirmation.
 Response: System sends a notification to the user.
 Stimulus: Notification of delays or cancellations.
 Response: System sends timely alerts to affected users.
1. Users shall receive notifications for booking confirmations.
2. Users shall be notified of delays or cancellations.
3. The system shall send relevant alerts to users based on their bookings.
3.8 Feedback and Support (FRP)
3.8.1 Description: Provides users with the ability to provide feedback on their experience
and access customer support features, such as live chat or a helpline.
 Stimulus: User selects the feedback option.
 Response: System prompts for feedback.
 Stimulus: User seeks customer support.
 Response: System provides access to live chat or helpline.
1. Users will be able to give feedback on their travel.
2. Helpline feature will help in providing customer support to the user.
3.9 User Management (FRA)
3.9.1 Description: Enables administrators to manage user accounts by creating new

accounts, updating user information, and deleting accounts. Administrators can assign
specific roles (conductor, passenger, admin) to users and define/modify associated
permissions.
 Stimulus: Administrator selects user management.
 Response: System provides options to create new accounts, update information, and
delete accounts.
 Stimulus: Administrator assigns roles and modifies permissions.
 Response: System updates user roles and permissions accordingly.
1. Administrators shall have the ability to create new user accounts for conductors,
passengers, and other system users.
2. Administrators shall be able to update user information and delete accounts as needed.
3. Administrators shall have the option to assign roles (conductor, passenger, admin) to users.
4. The system shall allow administrators to define and modify permissions associated with
each role.
3.10 Train Schedule Management (FRA)
3.10.1 Description: Enables administrators to manage train schedules, including adding new
routes, updating existing routes, deleting outdated routes, modifying departure/arrival timings,
assigning specific trains to routes, and scheduling crews.
 Stimulus: Administrator selects train schedule management.
 Response: System provides options to add new routes, update routes, and delete
outdated routes.
 Stimulus: Administrator modifies departure and arrival timings, assigns trains to routes,
and schedules crews.
 Response: System updates the train schedule based on the administrator's actions.
1. Administrators shall be able to add new train routes to the system.
2. The system shall allow administrators to update existing routes and delete outdated
or unused routes.
3. Administrators shall have the ability to modify trains' departure and arrival timings.
4. The system shall provide options for administrators to assign specific trains to
specific routes.
5. Administrators shall be able to assign and schedule crews for each train.
3.11 Train Status Updates (FRA)
3.11.1 Description: Allows administrators to provide real-time updates to passengers about

the current location of the train, stations passed, estimated arrival time, and any delays.
 Stimulus: Administrator initiates real-time status updates.
 Response: System broadcasts updates on the train's location, stations passed,

estimated arrival time, and any delays.
1. Administrators shall have the ability to provide real-time updates to passengers on

the current location of the train.
2. The system shall display information on stations passed, estimated arrival time, and
any delays.
3.12 Ticket Validation (FRC)
3.12.1 Description: Empowers conductors to scan the QR code of a customer and verify the
correct customer is sitting in the correct seats on the train.
 Stimulus: Conductor scans the customer's QR code.
 Response: System verifies the correct customer and their seat assignment.
1. Conductors shall have the ability to scan the QR code of customers.
2. The system shall verify that the correct customer is sitting in the correct seats on the train.
3.13 Train Status Updates (FRC)
3.13.1 Description: Allows conductors to inform the administration about the train's
status, including any delays, the current location, and estimated arrival times.
 Stimulus: Conductor provides status updates.

 Response: System records and displays the train's status, delays, location, and
estimated arrival times.
1. Conductors shall have the ability to inform the administration about the train's status.
2. The system shall record and display information on delays, the train's current location,
and estimated arrival times.
3.14 View Train Schedule (FRG)
3.14.1 Description: Allows guests to view basic information about train schedules without the
need to log in.
 Stimulus: Guest accesses the train schedule.
 Response: System displays basic information about train schedules.
1. Guests shall have the ability to view basic information about train schedules without logging
in.
3.15 Customer Support (FRG)
3.15.1 Description: Enables guests to communicate with customer support through live chat or
a helpline.
 Stimulus: Guest accesses customer support.
 Response: System provides options for live chat or helpline communication.
1. Guests shall have the ability to communicate with customer support through live chat or a
helpline.
3.16 Train Information (FRG)
3.16.1 Description: Provides guests with the ability to see information about trains,
including routes, departure and arrival times, seat availability, and ticket costs.
 Stimulus: Guest accesses train information.
 Response: System displays train details, routes, timings, seat availability, and ticket costs.
1. Guests shall have the ability to see information about trains, including routes, departure and
arrival times, seat availability, and ticket costs.
3.17 Register and Log In (FRG)
3.17.1 Description: Allows guests to register an account or log in to access additional features.
 Stimulus: Guest selects the register or log in option.
 Response: System provides options for account registration or logging in.
1. Guests shall have the option to register a new account by providing necessary information.
2. Guests shall have the option to log in using their credentials to access additional features.
3. The system shall provide a user-friendly interface for the registration and login processes.
4. External Interface Requirements

This section of the SRS describes the interface requirements of the Railway Reservation System
which describe in detail the user, hardware, software and communication interfaces.
4.1 User Interfaces
The user interfaces play a vital role in ensuring a seamless interaction between the system and its
users. They include interfaces for passengers, administrators, and conductors.
4.1.1 Passenger Interface
 Web Interface: Passengers will have access to the system through a web-based
interface, allowing them to register, log in, book tickets, and track trains. This interface
should be intuitive, with clear navigation and user-friendly design.
 Mobile App: A dedicated mobile app will provide an alternative interface for passengers,
offering similar functionalities as the web interface. It should be compatible with both
iOS and Android platforms.
4.1.2 Administrator Interface
 Web Portal: Administrators will manage the system through a web-based portal. This
portal should provide comprehensive functionalities for user management, train schedule
management, and real-time updates.
4.1.3 Conductor Interface
 Handheld Device Interface: Conductors will utilize handheld devices equipped with a
QR code scanner and an interface for reporting train status. This interface should be
straightforward, facilitating efficient ticket validation.
4.2 Hardware Interfaces
Hardware interfaces are crucial for ensuring compatibility with different devices and systems.
4.2.1 Mobile Devices (Passenger and Conductor)
 The system should be compatible with various mobile devices, including smartphones
and tablets, used by both passengers and conductors.
4.2.2 Web Browser (Passenger and Administrator)
 The user interfaces should be compatible with popular web browsers such as
Chrome, Firefox, Safari, and Edge.
4.2.3 QR Code Scanners (Conductor)
 Conductors' handheld devices should seamlessly integrate with QR code scanners

for efficient ticket validation.
4.2.4 Server and Database
 The system's software should run on servers with adequate capacity to handle concurrent
user requests, and the database server should have sufficient storage and processing
power.
4.3 Software Interfaces
Software interfaces are essential for the proper functioning of the system, including communication
between different software components.
4.3.1 Operating System Compatibility
 The system should be compatible with major operating systems, ensuring accessibility
for users on different platforms.
4.3.2 Web Server
 The web-based interfaces should be hosted on a reliable web server, ensuring

optimal performance and availability.
4.3.3 Database Management System (DBMS)
 The system should interact with a robust DBMS to manage and retrieve data efficiently
4.3.4 Payment Gateway Integration
 Integration with secure payment gateways is essential to facilitate online

transactions securely.
4.4 Communications Interfaces
Communication interfaces are critical for real-time updates, notifications, and data exchange.
4.4.1 APIs
 APIs should facilitate communication between different system components,

allowing seamless integration.
4.4.2 Notification Services
 The system should integrate with notification services to deliver timely updates and alerts
to users.
4.4.3 Secure Communication Protocols
 The use of secure communication protocols is essential to protect sensitive data

during interactions between users and the system.
5. Other Nonfunctional Requirements

The nonfunctional requirements of the railway reservation system places a significant emphasis on
performance, safety, security, and software quality attributes.
5.1 Performance Requirements
To ensure a responsive and efficient user experience, the system mandates a maximum response
time of 3 seconds for user requests. Concurrently, the system must be capable of handling a
minimum of 1,000 users simultaneously without notable performance degradation. Database queries
related to train schedules, seat availability, and user information should be optimized, ensuring data
retrieval within a swift 2-second timeframe.
5.2 Safety Requirements
User data protection is paramount, requiring encryption for personal and sensitive information
during storage and transmission. Additionally, the system must incorporate documented emergency
procedures to swiftly address and recover from critical errors or system failures.
5.3 Security Requirements
Security considerations are integral to the system's design. Robust user authentication, employing
strong encryption, and role-based authorization mechanisms are paramount. Measures such as
checksums or hashing should be in place to maintain data integrity during storage and transmission.
For financial transactions, secure and encrypted protocols must be employed. Comprehensive
logging and monitoring tools are to be implemented to track user activities and promptly respond to
security incidents.
5.4 Software Quality Attributes
Several key software quality attributes are outlined to ensure the system's reliability, scalability,
maintainability, usability, and portability. The system aims for an uptime of at least 99.9%,
minimizing disruptions. Scalability is a core consideration, accommodating growth in both user
numbers and database size without compromising performance. Code maintainability is facilitated
through thorough documentation and modular design. Usability is prioritized across user interfaces
for passengers, administrators, and conductors. Lastly, portability is emphasized, allowing the
system to run seamlessly on various platforms, web browsers, and mobile devices.
6. Other Requirements
Additional Requirements for Railway System are the requirements which help us in making our
system even more efficient, user friendly and powerful. They are as follows.
6.1 Data Management and Analytics
 Implement a robust data management platform to collect, store, and analyse operational
data efficiently.
 Develop advanced analytics tools to gain insights into system performance,
passenger behaviour, and resource utilization.
 Utilize data for predictive maintenance, demand forecasting, and decision-making processes.
 Ensure data privacy and security through appropriate data governance policies and
access controls.
6.2 Cybersecurity and Resilience
 Implement robust cybersecurity measures to protect the system against cyberattacks and
data breaches.
 Develop comprehensive incident response plans and recovery procedures to
minimize disruption in case of cyber incidents.
 Promote a culture of cybersecurity awareness among railway staff and stakeholders.
 Regularly assess and update cybersecurity measures to adapt to evolving threats
and vulnerabilities.
6.3 Smart Mobility and Integration
 Integrate the railway system with other transportation modes to provide seamless
multimodal travel options.
 Develop smart ticketing systems and mobile applications to enhance passenger
convenience and journey planning.
 Utilize real-time data and information sharing to improve traffic management and
passenger information.
 Promote sustainable and smart mobility solutions to reduce traffic congestion
and environmental impact.
6.4 Workforce Development and Training
 Invest in training programs and skills development for railway staff to adapt to
new technologies and operational changes.
 Develop programs to attract and retain qualified personnel in the railway industry.
 Promote diversity and inclusion in the workforce to create a more representative
and inclusive environment.
 Foster a culture of continuous learning and innovation within the railway organization.
6.5 Interoperability and Standardization

 Ensure compatibility with other railway systems and adhere to relevant
international standards
 Facilitate seamless passenger and freight transportation across different networks
 Collaborate with industry stakeholders to develop and implement common standards
for railway systems.
 Stay updated with evolving technological trends and adopt new standards to
maintain interoperability.
6.6 Regulatory and Legal Compliance:

 Comply with all applicable laws and regulations governing railway operations
 Implement procedures for ensuring data privacy and security in accordance with
relevant regulations
 Obtain necessary permits and licenses for operating the railway system.
 Maintain transparency and accountability in all operations and decision-making process.
Appendix A: Glossary
Term Definition
The software solution aimed at streamlining and enhancing various aspects

RRS
of railway operations.
FRP System features for passengers.
FRA System features for administration
FRC System features for conductors.
FRG System features for guests (Unauthenticated User)
Software that manages databases, ensuring efficient data storage and

DBMS
retrieval.
Interfaces facilitating communication between different system

APIs
components.
QR Code A Quick Response code used for ticket validation.
A dedicated application providing an alternative interface for passengers,

Mobile App
compatible with iOS and Android platforms.
A dedicated Website which will be used for the railway reservation

Web Portal
system.
UI Style Guides External Source providing style guides.
Use Case Diagram A diagram which will be used to describe what each user will do.
Class Diagram A diagram which will show the functions of our website and application.
ERD Entity Relationship diagram which will describe the tables in our database.
Sequence Diagram A diagram which is used to show the sequence of our application.
Appendix B: Analysis Models
Class Diagram:
Use Case Diagram:

Entity Relationship Diagram:

Sequence Diagram:
Appendix C: Issues List

1. Finalize the user authentication framework, considering factors like multi-
factor authentication.
2. Define the encryption standards and protocols for securing user data.
3. Address compatibility issues with different browsers and devices.
4. Establish a clear and swift recovery process for unexpected incidents.
5. Determine how feedback will be collected, analyzed, and acted upon.
6. Ensure that conductors can efficiently validate tickets using QR codes.

Final Project 2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Project 2

Uploaded by

Copyright:

Available Formats

COURSE TITLE: SOFTWARE ENGINEERING

COURSE CODE: CT-365

NAME ROLL NO.

Inshaal Navid Malik CT-21077

Sheeban Ali CT-21095

Muhamad Hudaib Waseem CT-21086

Ahmed Siddiqui CT-21078

NAME ROLL NO.

Ahmed Ubaidullah CT-21092

Muhammad Ali CT-21093

Hasnain Ali CT-21073

Railway Reservation System (RRS)

Version 1.0 approved

Prepared by BCIT Software Engineering Team

1.2 Document Conventions

1.3 Intended Audience and Reading Suggestions

1.3.1 Stakeholders' Authorities: Top-level executives, decision-makers, and leaders overseeing

1.3.3 Developers and IT Professionals: Software developers, programmers, and IT specialists

1.4 Project Scope:

1.4.1 Train Operations Management: Efficient scheduling and management of train

1.4.2 Passenger Management: Facilitation of passenger reservations, ticketing, and boarding

1.4.9 Communication and Information Sharing: Facilitation of communication among

1.5.1 For UI Style Guides:

2.1 Product Perspective

3. The manual system was time-consuming and slow.

4. Additionally, the difficulty in managing data, such as adding, deleting, or editing

1. The transition to a computerized environment will reduce the use of paper,

2.2 Product Features

2.3 User Classes and Characteristics

2.4 Operating Environment

2.5 Design and Implementation Constraints

2.6 User Documentation

2.7 Assumptions and Dependencies

3.1 User Registration and Authentication (FRP)

3.1.1 Description: Enables users to create an account by providing personal information

3.1.2 Stimulus/Response Sequences:

 Stimulus: User selects the registration option.

 Response: System prompts for required information and validates entries.

 Stimulus: User agrees to terms and conditions.

 Response: System validates and registers the user.

3.1.3 Functional Requirements:

5. Users must be 18 years or older to create an account.

6. The contact number provided must be an 11-digit numeric number.

3.2 Train Schedule (FRP)

3.2.2 Stimulus/Response Sequences:

 Stimulus: User selects a specific train.

 Stimulus: User checks real-time seat availability.

 Response: System updates and displays current seat availability.

3.2.3 Functional Requirements:

2. The system shall provide real-time updates on seat availability.

3.3 Ticket Booking and Reservation (FRP)

3.3.2 Stimulus/Response Sequences:

 Stimulus: User enters destination, date, and time.

 Response: System displays a list of trains with available seats.

 Stimulus: User selects preferred train and seats.

3.3.3 Functional Requirements:

3. Users shall select a preferred train and seats.

5. The system shall initiate the online payment process.

3.4 Payment (FRP)

3.4.2 Stimulus/Response Sequences:

 Stimulus: User completes the booking process.

 Response: System generates a payment slip.

 Stimulus: User chooses a payment method.

 Response: System processes the payment and generates a digital e-ticket.