INTERNATIONAL UNIVERSITY OF BUSINESS

AGRICULTURE AND TECHNOLOGY

Project Report on
“Metro Rail Ticket Booking & Purchasing System”

This report is prepared for partial fulfillment of

CSC 470- Software Engineering Lab

Submitted To,
Md. Rashedul Islam
Assistant Professor & Coordinator,
Department of Computer Science & Engineering, IUBAT.

Submitted By:
Team: BitByte, Section: A
Name ID
Shahriar Hossain 20303014
Afrin Akhter Shakila 20303015
Antim Chandra Sarker 20303016
Sakibul Huda Rejon 20303025
Riana Azad 20303033

Date of Submission:15/05/2024

Page 1 of 67
 Abstract

The "Online Metro Rail Ticket Booking System" is a sophisticated software solution aimed
at revolutionizing the process of booking metro rail tickets. In response to the growing demand for
efficient and user-friendly ticketing platforms, this system offers a seamless experience for
commuters, providing easy access to metro information, streamlined ticket booking, and efficient
management of passes and feedback. Leveraging modern technologies such as HTML 5, CSS 3,
Tailwind CSS, Daisy UI, JavaScript, ReactJS, and NodeJS, coupled with MongoDB as the
database backend, the system promises robust performance, scalability, and security. By
incorporating features such as user-friendly registration, forgot password/reset password
functionality, comprehensive metro services information, booking for multiple passengers, secure
purchasing, and pass management, the system caters to the diverse needs of commuters while
promoting the use of public transportation. However, despite its advancements, the system may
face limitations such as limited coverage, connectivity dependency, and security concerns, which
necessitate continuous monitoring and improvement. Through careful design and implementation,
the "Online Metro Rail Ticket Booking System" stands poised to enhance the commuting
experience, contributing to the efficiency and sustainability of urban transportation networks.

Page 2 of 67
 Table of Contents
Chapter 1. Introduction
1.1 Objectives……………………………………………………………………………………5
1.2 System Benefits……………………………………………………………………………...5
1.3 Software Process Model…………………………………………………………………..…6
1.3.1 Reasons for Choosing Scrum …………………………………………………….………..7
Chapter 2. Requirement Engineering
2.1 User Requirements………………………………………………………………………..….9
2.2 System Requirement……………………………………………………………………..…..10
2.4 Non-Functional Requirements…………………………………………………...…………..20
2.5 Use Case Diagram……………………………………………………………………………21
Chapter 3. Analysis Modeling
3.1 Activity Diagram……………………………………………………………………………..31
3.2 Swimlane Diagram……………………………………………………………….…………..32
3.3 CRC ……………………………………………………………………………………….…38
3.4 Class Diagram……………………………………………………………………….……….39
Chapter 4. Project Management
4.1 Risk Identification……………………………………………………………………………40
4.2 Risk Analysis…………………………………………………………………………………41
4.3 Risk Planning………………………………………………………………………………...42
Chapter 5. Function Point Estimation
5.1 Function Point Estimation……………………………………………………………………46
5.2 Project Schedule Chart…………………………………………………………………….…50
Chapter 6. Project Estimation
6.1 Personnel Cost…………………………………………………………………………..……51
6.2 Hardware Cost……………………………..…………………………………………………51
6.3 Software Cost………………………………….……………………………………………..52
6.4 Other Cost:……………………………………………...……………………………………53
Chapter 7. Designing.
7.1 Data Flow Design…………………………………………………………………………….53
7.2 Database Design……………………………………………………………………………...54
7.2 ERD……………………………………………………………………………………...…...54
Chapter 8 Testing
8.1 Produced Test Cases (For all requirements)………………………………..…………………54
Chapter 9. Conclusion
9.1 Limitation of the Project……………………………………………………………………..62
9.2 References……………………………………………………………………………………63

Page 3 of 67
 List of Figures

1.1 Process Model Diagram……………………………………………………………………….8

2.1 Registration…………………………………………………………………………….…….10
2.2: Forget Password………………………………………………………………………….….11
2.3: Reset Password………………………………………………………………………………12
2.4: New Password…………………………………………………………………………….…12
2.5: Initiate Ticket Booking…………………………………………………………………..…..13
2.6: Metro Schedule…………………………………………………………………………...…14
2.7: Maximum Person……………………………………………………………………..……..15
2.8: Booking ticket……………………………………………………………………………….16
2.9 Recharge card………………………………………………………………………….……..17
2.12: Lost file……………………………………………………………………………………19
2.13: Responsive System………………………………………………………………….……..20
3.1 CRC Diagrams………………………………………….……………….…………….……..38
5.9: Gantt Chart……………………………………………………………………………….....50
3.2 Class Diagram…………………………………………………………………………….….39
2.10 Contact Us…………………………………………………………………………………..40
7.1 Data Flow Diagram…………………………………………………………………………..41
7.2 Database Design………………………….…………………………………………………..42
7.3 ERD…………………………………………………………………………………………..43
7.4 Interface Designs……………………………………………………………………………..44

Page 4 of 67
 List of Tables

Table 4.1: Risk Identification……………………………………………………….……………43

Table 4.2: Risk Analysis………………………………………………………………………….44

4.3 RMMM (Risk mitigation management and monitoring) plan………………………….……45

4.4: Risk Management Table……………………………………………………………………..45
Table 5.1 Functionality, Input, Output……………………………………………………………46
Table 5.2 Identify Complexity (TF)………………………………………………………………47
Table 5.3 Identify Complexity (DF)………………………………………….…………………..47
Table 5.4 UFP (TF)……………………………………………………………………………….48
Table 5.5 UFP (DF)………………………………………………………………………………49
Table 5.6 TDI………………………………………………………………………………….…49
Table 5.7 Final Calculation(Part 1)……………………………………………………………….49
Table 5.8 Final Calculation(Part 2)……………………………………………………………….49
Table 6.1 Personnel Cost………………………………………………………...……………….50
Table 6.2 Hardware Cost………………………………………………………...……………….50
6.4 Other Cost…………………………………………………………………...……………….51
Table 6.5 Accounts Table…………………………………………………………………………52

Page 5 of 67
 1. Introduction

We propose the “Metro-Rail Ticket Booking and Purchasing System”, a digital platform to
facilitate the purchase of metro rail tickets, making the process efficient, convenient, and user-
friendly forpassengers. This online system provides convenience for the passengers. It overcomes
the disadvantage of the traditional queuing system. Therefore, this system enhances the speed and
standardization of processing tickets for passengers. The objectives and system benefits are
explained in the following paragraphs.

1.4 Objectives

Our project aims to revolutionize metro rail ticket booking by providing a user-friendly online
platform that streamlines the booking process and enhances accessibility for commuters. The main
objectives are:

• Streamline the process of booking metro rail tickets for users.

• Provide a user-friendly platform for accessing metro information and purchasing tickets.
• Ensure easy management of metro services and user accounts for administrators.
• Enhance accessibility to metro rail services for commuters through an online booking
system.
• Improve the overall efficiency and effectiveness of metro rail operations through
digitalization.

1.5 System Benefits

The implementation of our project brings forth numerous benefits, including convenience, real-
time information access, enhanced management capabilities, and significant cost savings,
contributing to an overall improvement in metro rail services. Few other benefits are:

Page 6 of 67
 • Convenience: Users can easily access metro information and book tickets from anywhere,
anytime, using their preferred devices.
• Timesaving: Eliminates the need for users to physically visit ticket counters, saving time
and effort.
• Real-time Information: Provides up-to-date information on metro schedules, fares, and
routes, enhancing user experience and reducing uncertainty.
• Enhanced Management: Administrators can efficiently manage metro services, update
information, and respond to user queries or complaints through the system.
• Cost-effectiveness: Reduces operational costs associated with manual ticketing processes
and enhances revenue generation through online ticket sales.
• Accessibility: Increases accessibility to metro rail services for individuals with mobility
challenges or limited access to physical ticketing outlets.
• Data-driven Insights: Generates valuable data on user preferences, travel patterns, and
service utilization, enabling data-driven decision-making for future improvements and
expansions.
• Environmental Impact: Contributes to environmental sustainability by reducing paper
usage and promoting the use of public transportation over individual vehicle usage.

1.3 Software Process Model - SCRUM

Considering the dynamic nature of the project, the Scrum process model from agile
methodology is a well-suited choice due to its focus on iterative development and continuous
feedback.
Scrum is an iterative and incremental Agile software development methodology that
emphasizes collaboration, flexibility, and rapid delivery of value. Scrum projects are organized
into short cycles called sprints, typically lasting 2-4 weeks. At the beginning of each sprint, the
product backlog is prioritized, and a set of user stories is selected for development in that sprint.
The development team works collaboratively to complete the user stories within the sprint
timeframe. At the end of each sprint, the team conducts a sprint review to showcase the completed
work to stakeholders and gather feedback. A sprint retrospective is also held to identify areas for
improvement in the following sprint.

Page 7 of 67
 Fig 1.1: Scrum Process Model

1.3.1 Reasons for Choosing Scrum

Adopting the Scrum model will facilitate efficient project management, enhance team
communication, and ultimately lead to the successful delivery of our project. Here are some
key points explaining why the Scrum model is suitable for our project:

i. Iterative Development: Scrum emphasizes iterative development cycles, allowing us to

break down the project into smaller, manageable increments or sprints. This approach
enables us to deliver usable product increments at the end of each sprint, providing
early value to stakeholders.
ii. Flexibility and Adaptability: Scrum offers flexibility to adapt to changing requirements
or priorities. Through regular sprint planning and review meetings, we can re-prioritize
tasks, adjust project scope, and incorporate feedback from stakeholders, ensuring that
the project remains aligned with evolving needs.
iii. Enhanced Collaboration: Scrum promotes collaboration and transparency among team
members. Daily stand-up meetings, sprint planning sessions, and sprint reviews foster
open communication, facilitate knowledge sharing, and promote a shared
understanding of project goals and progress.
iv. Continuous Improvement: The Scrum model encourages continuous improvement
through retrospective meetings held at the end of each sprint. By reflecting on what

Page 8 of 67
 went well, what could be improved, and how to implement those improvements, we
can optimize our development process and deliver higher-quality results over time.
v. Faster Time-to-Market: By delivering working product increments at the end of each
sprint, Scrum enables us to achieve faster time-to-market. This incremental delivery
approach allows us to address critical user needs early on, validate assumptions, and
adapt our product roadmap based on real-world feedback.
vi. Overall, the Scrum model provides a structured yet flexible framework that promotes
collaboration, adaptability, and continuous improvement, making it an ideal choice for
our project to develop an online metro rail ticket booking system.

Page 9 of 67
 2. Requirement Engineering

2.1 User Requirements

User requirements refer to the needs, expectations, and specifications of end-users
regarding a product, system, or service. These requirements outline what functionalities, features,
and characteristics the users expect from the product or service to fulfill their objectives or solve
their problems effectively. User requirements are typically gathered through interviews, surveys,
observations, or workshops, and they serve as the foundation for the design and development
process, ensuring that the final product meets the users' needs and enhances their overall
experience. User requirements for the Metrorail Ticket purchasing and management system
encompass the specific needs and expectations of the end-users interacting with the software.
These are:

i. Users will have a user-friendly registration process where users can input their, NID
(National ID) number, email, password and submit their data to create an account.
ii. Users should be able to avail Forgot password/reset password functionality.
iii. Users should be able to easily select boarding and destination stations, as well as the date
of travel, to initiate the ticket booking process.
iv. Users should have access to comprehensive information about metro services including
fare details, schedules, and routes for informed decision-making.
v. Users should be able to make bookings for multiple passengers in a single transaction,
especially for group travel of up to a maximum of four persons.
vi. Users should have a seamless interface to select and purchase tickets securely.
vii. Users should be able to manage the balance of the MRT Pass and Rapid Pass.
viii. Users should be able to submit any issues, complaints, or feedback they encounter while
using the system for prompt resolution and improvement.
ix. In case of MRT or Rapid pass loss, the user will be able to submit a complaint and according
to the loss reason, there will be a fine system to retrieve the pass.
x. To retrieve an expired MRT or Rapid pass, users will need to submit a complaint to activate
the card again.

Page 10 of 67
 xi. Users must experience a responsive system that will be accessible across various devices
such as smartphones, tablets, and desktops.

2.2 System Requirement

System requirements refer to the detailed specifications and characteristics necessary for
the design, development, implementation, and operation of a software system or application. These
requirements serve as the basis for planning, designing, and evaluating the system's architecture
and functionalities, ensuring that it meets the needs and expectations of stakeholders while
adhering to technical standards and constraints. System Requirements along with the User
Requirements are given below:

UR#1 Users will have a user-friendly registration process where users can input their mobile
number, NID (National ID) number, and date of birth, verify their mobile number, and
submit their data to create an account.
1.1 While purchasing tickets user will be directed to the registration/log-in page. Or they can go
to the registration page from the register option in the navbar.

Fig 2.1: Registration

Page 11 of 67
1.2 The users will have to provide their NID, Email, and password in the form.

1.3 Finally submitting the form will successfully register the user into the system.

1.4 In case anyone is registered before they can visit the login page through Have an account?
Please Log in Option.

UR#2 Users should be able to avail Forgot password/reset password functionality.

2.1 To purchase tickets user must be logged in. Or they can go to the log-in page from the log-in
option in the navbar.
2.2 The user will have to provide their mobile number and password to successful log in.

Fig 2.2: Forget Password

Page 12 of 67
2.3 If the users forget their password they should reset their password by clicking Forgot
Password?

2.4 An email will be sent into users email address.

2.5 Click on the link from the email.

2.6 Finally the user can enter a new password.

Fig2.3: Reset Password

2.7. The user needs to give a new password to reset the password.

2.9. Click the Save button.

Fig2.4: New Password

Page 13 of 67
UR#3 Users should be able to easily select boarding and destination stations, as well as the
date of travel, to initiate the ticket booking process.
3.1 The user can select the boarding station from where he/she will board giving input on From.

3.2 The user can select the Destination station where he/she will get down giving input in To.

Fig2.5: Initiate Ticket Booking

3.3. The user will select the date of the journey.

3.4. Give input of the Quantity of the ticket.

3.5 Click Purchase Ticket button.

Page 14 of 67
UR#4 Users should have access to comprehensive information about the metro. services
including schedules for informed decision-making.

Fig 2.6: Metro Schedule

4.1 The User Clicks on the Metro Information from the navbar.

4.2 The user can see the Board Station.

43. The user can see the Destination Station.

4.4 The user can see the schedule.

Page 15 of 67
UR#5. Users should be able to make bookings for multiple passengers in a single transaction,
especially for group travel of up to a maximum of four persons

5.1. The user is on the home page to initiate ticket booking.

Fig2.7: Maximum Person

5.2 The user has given input of from, to, and date of the journey.

5.3 The user will select from 1 to a maximum 4 number of tickets at a single purchase.

Page 16 of 67
UR#6. Users should have a seamless interface to select and purchase tickets securely.
6.1 After giving all the information user will take into an interface named Booking where ticket
purchase confirmation will be shown precisely.

Fig 2.8: Booking ticket

6.2 The User will observe the booking information very carefully .

6.3 Click on the confirm button.

6.4 To see the ticket user will click on the download ticket button.

UR#7. Users should be able to manage the balance of the MRT Pass and Rapid Pass.
7.1 At the Home page User will see the Recharge card button.

7.2 The user will click on the button

7.3 A logged user will be taken into the Recharge interface.

Page 17 of 67
 Fig 2.9 Recharge card

7.4 The user will give his/her name, phone number, and recharge amount.

7.5 Click the recharge button.

7.6. After successful recharging user will see a new balance in the current balance box.

Page 18 of 67
UR# 8. Users should be able to submit any issues, complaints, or feedback they encounter
while using the system for prompt resolution and improvement.

Fig 2.10 Contact Us

8.1 The User will fill up his name with his First and Last name and an Email address.
8.2 The user can see the Get in Touch with Us having the metro office information contact number
and email.
8.3 The user will provide any issues, complaints, or feedback in the Message option in.
8.4 The user will click the Send button.

Page 19 of 67
UR#9 In case of MRT or Rapid pass loss, the user will be able to submit a complaint and
according to the loss reason, there will be a fine system to retrieve the pass with a minimum
300 BDT fine.

Fig 2.12: Lost file

9.1 The user will go to the Lost & file interface to retrieve his/her lost card and submit a complaint.

9.2 The user will select a reason. Here two reasons are given. The user must select one.

9.3 The user will submit a brief complaint and the loss reason to justify his/her retrieval claim for
the lost card taking 300 tk as a fine into the Message box.

9.4 The user will click Submit Case Button,

Page 20 of 67
UR# 10. Users must experience a responsive system that will be accessible across various
devices such as smartphones, tablets, and desktops.
11.1. Users asked for a responsive system for their devices.

11.2 The user asked for a smartphone view.

Fig 2.13: Responsive System

11.3 The user asked for a desktop view.

11.4. A user asked for a tablet view.

2.4 Non-Functional Requirements

Non-functional requirements for the online metro rail ticket booking system may include:

• Performance: The system should be responsive and able to handle multiple concurrent user
requests without significant delays, ensuring quick ticket bookings and information
retrieval.
• Reliability: The system should be highly reliable, with minimal downtime and robust error
handling to prevent service disruptions. It should accurately process transactions and
always maintain data integrity.

Page 21 of 67
• Scalability: The system should be able to scale seamlessly to accommodate increasing user
traffic and data volume, allowing for future growth without compromising performance or
user experience.
• Security: The system should implement strong security measures to protect user data,
including encryption of sensitive information, secure authentication mechanisms, and
prevention of unauthorized access or data breaches
• Usability: The user interface should be intuitive and user-friendly, catering to users of
varying technical abilities. It should provide clear navigation, informative feedback, and
accessible features to enhance the overall user experience.
• Accessibility: The system should be accessible to users with disabilities, complying with
accessibility standards such as WCAG (Web Content Accessibility Guidelines) to ensure
equal access to all users.
• Availability: The system should be available 24/7, with minimal scheduled maintenance
and downtime. It should have backup and disaster recovery mechanisms in place to ensure
continuous operation in case of system failures or outages.
• Compliance: The system should comply with relevant laws, regulations, and industry
standards, including data protection regulations (e.g., GDPR), payment card industry
standards (PCI DSS), and accessibility guidelines (e.g., WCAG).
• Performance Load Testing: The system should undergo performance load testing to ensure
it can handle peak loads without degradation in performance. This includes stress testing,
volume testing, and endurance testing to assess system behavior under various conditions.
• Documentation: Comprehensive documentation should be provided for system
administrators, developers, and end-users, including user manuals, technical specifications,
API documentation, and system architecture diagrams. This ensures clarity and facilitates
system understanding, maintenance, and troubleshooting.

Page 22 of 67
2.5 Use Case Diagram

Manage Booking(Admin):

Page 23 of 67
Ticket Booking:

Ticket purchase

Page 24 of 67
Recharge

Manage Schedule (Admin)

Page 25 of 67
Generate Report

Enter Feedback

Page 26 of 67
 3. Analysis Modeling

3.1 Activity Diagram

3.1.1 UR#1 Users will have a user-friendly registration process where users can input their, NID
(National ID) number, email, and password and submit their data to create an account.

3.1.2 UR#2 Users should be able to avail Forgot password/reset password functionality.

Page 27 of 67
3.1.3 UR#3 Users should be able to easily select boarding and destination stations, as well as the
date of travel, to initiate the ticket booking process.

Page 28 of 67
3.1.4 UR#4 Users should have access to comprehensive information about metro services
including fare details, schedules for informed decision-making.

Page 29 of 67
3.1.5 UR#5. Users should be able to make bookings for multiple passengers in a single transaction,
especially for group travel of up to a maximum of four persons.

3.1.6 UR#6. Users should have a seamless interface to select and purchase tickets securely.

Page 30 of 67
3.1.7 UR#7.Users should be able to manage the balance of the MRT Pass and Rapid Pass.

Page 31 of 67
3.1.8 UR# 8. Users should be able to submit any issues, complaints, or feedback they encounter

while using the system for prompt resolution and improvement

3.1.9 UR#9. In case of MRT or Rapid pass loss, the user will be able to submit a complaint and
according to the loss reason, there will be a fine system to retrieve the pass with a minimum 300
BDT fine.

Page 32 of 67
3.2 Swimlane Diagram

3.2.1 UR#1 Users will have a user-friendly registration process where users can input their mobile
number, NID (National ID) number, and date of birth, verify their mobile number, and submit their
data to create an account.

3.2.2 UR#2 Users should be able to avail Forgot password/reset password functionality.

Page 33 of 67
3.2.3 UR#3 Users should be able to easily select boarding and destination stations, as well as the
date of travel, to initiate the ticket booking process.

3.1.4 UR#4 Users should have access to comprehensive information about metro services
including fare details, and schedules for informed decision-making.

Page 34 of 67
3.2.5 UR#5. Users should be able to make bookings for multiple passengers in a single transaction,
especially for group travel of up to a maximum of four persons.

3.2.6 UR#6. Users should have a seamless interface to select and purchase tickets securely.

Page 35 of 67
3.2.7 UR#7 Users should be able to manage the balance of the MRT Pass and Rapid Pass.

3.2.8 UR# 8. Users should be able to submit any issues, complaints, or feedback they encounter
while using the system for prompt resolution and improvement.

Page 36 of 67
3.1.9 UR#9. In case of MRT or Rapid pass loss, the user will be able to submit a complaint and
according to the loss reason, there will be a fine system to retrieve the pass with a minimum 300
BDT fine.

Page 37 of 67
3.3 CRC

In the context of software systems, CRC (Cyclic Redundancy Check) serves as a crucial
error detection mechanism utilized to maintain data integrity. It involves appending a fixed-size
binary number, referred to as a polynomial, to the data within software processes. Subsequently,
this polynomial is employed to compute a checksum, which is then compared against a received
or stored value to detect any potential alterations or corruptions in the data. CRC is extensively
integrated into software applications, protocols, and file systems to ensure reliable data
transmission, storage, and processing, thereby enhancing the overall robustness and reliability of
software systems.

Fig 3.1 CRC Diagrams

Page 38 of 67
3.4 Class Diagram

A class diagram is a visual representation within software engineering that illustrates the
structure and relationships of classes and their attributes and methods within a system or
application.

Fig 3.2 Class Diagram

Page 39 of 67
 4. Project Management

Risk is an inherent aspect of any project or endeavor, representing the uncertainty and
potential for adverse events that may impact its objectives. Effective risk management involves
identifying, assessing, prioritizing, and mitigating risks to minimize their impact on project
outcomes and ensure its success. By proactively addressing risks, organizations can anticipate
challenges, capitalize on opportunities, and make informed decisions to achieve their goals. Stages
of Risk:
● Risk Identification
● Risk Analysis Risk
● Planning Risk
● Monitoring

4.1 Risk Identification

Risk Identification is the process of determining risks that could potentially prevent the
program, enterprise, or investment from achieving its objectives. For the "Metro Rail Ticketing &
Purchasing System", risks could include technical challenges, such as difficulties in integrating
with existing systems, or operational risks, such as the unavailability of key team members.

Risk Type Description

Technical Risks Group mates use different hardware and software and while collaborating
on the system, it may raise portability and incompatibility issues.

Security vulnerabilities leading to data breaches or unauthorized access

Operational Risks Unavailability of team members due to sickness, different concerns,

accidents, etc.

Requirements Requirements may not be fulfilled due to time constraints.

Page 40 of 67
 Unforeseen Requirements: New functionalities or changes needed during
development

Maintenance The version of used tools and technologies may change and need
continuous updates, failure to which may cause system malfunction.

Estimation May take longer time than estimated.

Testing Insufficient Testing: Incomplete or inadequate testing leads to bugs and

security vulnerabilities

Table 4.1: Risk Identification

4.2 Risk Analysis

Risk Analysis involves understanding the nature of each identified risk and the potential
impact on project outcomes. For example, if there's a risk that the project may face resource
shortages, the analysis would involve determining how this could affect the project timeline, costs,
and quality.

Risk Type Possible Risk Probability Impact

Group mates using different hardware and

software High Serious

Security vulnerabilities leading to data breaches

Technical Risks or unauthorized access Medium Catastrophic

Operational Unavailability of team members due to

Risks sickness, accidents, etc. Medium Serious

Requirements may not be fulfilled due to time

constraints High Serious

Unforeseen Requirements: New functionalities

Requirements or changes needed Medium Marginal

Page 41 of 67
 Version of tools and technologies may change,
Maintenance requiring continuous updates Medium Tolerable

Estimation May take longer time than estimated Medium Marginal

Insufficient Testing: Incomplete or inadequate

Testing testing High Serious

Table 4.2: Risk Analysis

4.3 Risk Planning

Risk Planning involves developing options and actions to enhance opportunities and reduce
threats to project objectives. It includes identifying potential risk mitigation strategies, preventive
measures, and contingency plans. For instance, a risk plan for the "Metro Rail Ticket Booking and
Purchasing System" might include strategies like additional training for team members to handle
technical challenges, or hiring temporary resources to handle potential resource shortages. There
are some strategies to plan for risk management. They are:

• Regular Review: Schedule regular reviews of the risk register to assess the current status
of identified risks.
• Key Performance Indicators (KPIs): Define KPIs to track project progress and identify any
deviations that may indicate emerging risks.
• Risk Metrics: Establish quantifiable metrics for each risk, such as probability and impact
ratings, to track changes over time.
• Stakeholder Communication: Maintain open communication channels with stakeholders to
gather feedback and insights on potential risks.
• Risk Reporting: Generate regular risk reports summarizing the status of identified risks,
mitigation measures, and any new risks identified.
• Alert Systems: Implement alert systems or triggers to notify project teams when risks reach
certain thresholds or require immediate attention.
• Risk Workshops: Conduct periodic risk workshops to brainstorm new risks, assess existing
ones, and update mitigation strategies accordingly.

Page 42 of 67
 • Risk Reviews: Perform post-implementation reviews to analyze the effectiveness of risk
mitigation measures and identify any lessons learned for future projects.

Risk Type Risk Description Strategy

Group mates use

different
hardware/software
Technical leading to Standardize hardware/software requirements for team
Risks incompatibility members and implement compatibility testing.

Security vulnerabilities
leading to data breaches Regular security audits, penetration testing, and adherence
or unauthorized access to secure coding practices.

Unavailability of team
members due to
Operational sickness or other Cross-training team members and maintaining
Risks reasons documentation for knowledge transfer.

Requirements may not

be fulfilled due to time Implement Agile methodologies like Scrum to allow for
constraints flexibility in responding to changing requirements.

Changes in versions of
tools and technologies
causing system Implement version control and regular updates to keep the
Maintenance malfunction system aligned with latest tools and technologies.

Project may take longer Use historical data and expert judgment for more accurate
Estimation than estimated estimation, and regularly monitor project progress.

Insufficient testing
leading to bugs and Implement comprehensive testing protocols, including unit
Testing security vulnerabilities tests, integration tests, and security testing.
4.3 RMMM (Risk mitigation management and monitoring) plan

Page 43 of 67
The Risk Mitigation, Management, and Monitoring (RMMM) plan outlines strategies to identify,
address, and track risks throughout the project lifecycle.

Requirements may not be fulfilled due to time constraints. Unforeseen

Risk Requirements: New functionalities or changes needed during development
Description
Probability Moderate (25%-50%)
Impact Serious
Mitigation Prioritize requirements and develop a clear understanding of project scope.
Implement agile methodologies to adapt to changing requirements.
Monitoring Regularly review and update project requirements. Track changes and assess
their impact on project timeline.
Status Managed

Risk The version of used tools and technologies may change and need continuous
Description updates, failure to which may cause system malfunction.
Probability Low (0-25%)
Impact Tolerable
Mitigation Regularly update software and technologies to the latest versions. Implement
version control systems to manage changes effectively.
Monitoring Monitor software updates and technological advancements in relevant fields.
Status Managed

Table 4.4: Risk Management Table

Page 44 of 67
 5. Project Planning and Scheduling

5.1 Function Point Estimation

Functionality, Input, Output

Table 5.1 Functionality, Input, Output

Table 5.2 Identify Complexity (TF)

Page 45 of 67
Table 5.3 Identify Complexity (DF)

Table 5.4 UFP (TF)

Page 46 of 67
Table 5.5 UFP (DF)

Page 47 of 67
 Table 5.6 TDI

Table 5.7 Final Calculation (Part 1)

Page 48 of 67
 Table 5.8 Final Calculation(Part 2)

5.2 Project Schedule Chart

Fig 5.9: Gantt Chart

Page 49 of 67
 6. Project Estimation

6.1 Personnel Cost

This refers to the expenses associated with the human resources involved in the project,
including their salaries, wages, and benefits. Personnel costs typically include payments to project
managers, developers, designers, and other team members involved in the development and
management of the project.

Role Number Hourly Rate(bdt) Hours per Month Months Total(bdt)

Senior Developer 2 50 130 4 52,000

Junior Developers 1 40 130 4 20,800

UI/UX Designer 1 40 70 2 5,600

Project Manager 1 60 50 4 12,000

Total 90,400

Table 6.1 Personnel Cost

6.2 Hardware Cost

This refers to the expenses associated with the human resources involved in the project, including
their salaries, wages, and benefits.

Item Number Cost per Unit(bdt) Total(bdt)

Developer Laptops 5 1200 6000

Testing Devices 5 400 2000

Server Infrastructure 1 2500 2500

Total 10500

Table 6.2 Hardware Cost

Page 50 of 67
6.3 Software Cost

Software cost refers to the expenses associated with acquiring or developing the software
components required for the project. This includes costs related to purchasing licenses for
commercial software, as well as expenses associated with developing custom software solutions.
Software costs are crucial for obtaining the necessary tools and platforms to build and run the
project.

Item Cost (bdt)

MongoDB Atlas 0

Express.js 0

React.js 0

Node.js 0

Development Tools Licenses 0

Total 0

Table 6.3 Software Cost

6.4 Other Cost

Other costs encompass miscellaneous expenses that are not directly attributable to personnel,
hardware, or software. These may include expenses such as utilities, office supplies, travel costs,
training expenses, and any other miscellaneous costs incurred during the course of the project.
Other costs are important for covering various operational and administrative expenses that may
arise during project execution.

Page 51 of 67
 Item Cost (bdt)

Utilities 500

Miscellaneous Expenses 2500

Total 3,000

Table 6.4 Other Cost

6.5 Accounts Table

Account Amount (bdt)

Personnel 90,400

Hardware 10,500

Software 0

Other 3,000

Total 103900

Contingency (10%) 12,468

Grand Total 1,16,368

Table 6.5 Accounts Table

Page 52 of 67
 7. Designing

7.1 Data Flow Design

Level 0:

Level 1:

Fig 7.1 DFD

Page 53 of 67
7.2 Database Design

Fig 7.2: Database Design

7.3 ERD

Fig 7.3 ERD

Page 54 of 67
7.4 Interface Design

Home Page

Register Page

Page 55 of 67
Login Page

Metro Schedule Page

Page 56 of 67
Recharge Page

Booking Page

Page 57 of 67
Feedback Page

Admin Lost Page

Page 58 of 67
 8. Testing

8.1 Produced Test Cases (For all requirements)

Test Case ID: 1

Test Designed by: Riana Azad
Test Priority: High
Test Designed Date: 12-05-2024
Module Name: User Registration
Test Executed by: Riana Azad
Test Title: User Registration Test
Test Executed Date: 13-05-2024
Description: User can register successfully in the system.
Pre-condition: Valid details of user and user is not registered from before.
Dependencies: None

Steps Test Steps Test Data Expected Actual Result Status Note
Result
1 Navigate to the NID: 75689655, Successful Successful Pass
registration Email: Registration Registration
page. [email protected] and user will and user will be
2 Enter valid test Password: be directed directed to last
data. 123456 to last page. page.
3 Click on the
Register button

Test Case ID: 2

Test Designed by: Riana Azad
Test Priority: High Test Designed Date: 12-05-2024
Module Name: Forgot password/reset password Test Executed by: Riana Azad
Test Executed Date: 13-05-2024
Test Title: User can reset password by clicking forgot
Password.
Description: User can reset password by clicking forgot Password.
Pre-condition: User is not registered from before and a new password

Page 59 of 67
Dependencies: None

Steps Test Steps Test Data Expected Actual Result Status Note
Result
1 Navigate to the Email: Password is Password is Pass
login page. [email protected] successfully successfully
2 Click on "Forgot Password: reset, and reset, and user
Password?" link 123456 user can log can log in with
and provide test in with the the new
data. new password.
3 Click on the password.
Confirm button

Test Case ID: 3

Test Designed by: Riana Azad
Test Priority: High Test Designed Date: 12-05-2024
Module Name: Purchase Ticket Test Executed by: Riana Azad
Test Executed Date: 13-05-2024
Test Title: User can purchase ticket.
Description: User can purchase ticket by providing station details for multiple passengers.
Pre-condition: User is logged in.
Dependencies: None

Steps Test Steps Test Data Expected Actual Result Statu Note
Result s
1 Select boarding and Boarding User User successfully Pass
destination station, Station: successfully books tickets for
travel date, number Uttara books multiple
of passengers(upto Destination tickets for passengers in a
4). Station: multiple single
2 Click on purchase. Agargaon passengers transaction.

Page 60 of 67
3 User will view Date of in a single
details and click Travel: transaction.
confirm. 20/05/2024
4 User will see his No of
booking and Passengers:
download option. 3
5 Clicking on
download option
will download the
ticket.

Test Case ID: 4

Test Designed by: Riana Azad
Test Priority: High Test Designed Date: 12-05-2024
Module Name: View Metro Schedule Test Executed by: Riana Azad
Test Executed Date: 13-05-2024
Test Title: User can access comprehensive
metro services information.
Description: User can access comprehensive metro services information to view schedule.
Pre-condition: User is logged in.
Dependencies: None

Steps Test Steps Test Data Expected Actual Result Status Note
Result
1 Navigate to the No data needed User will see User will get Pass
metro all the all the
information schedules schedules
section. along with along with
2 View fare fares. fares.
details,
schedules, and
routes.

Page 61 of 67
Test Case ID: 5
Test Designed by: Riana Azad
Test Priority: High Test Designed Date: 12-05-2024
Module Name: Recharge Account Test Executed by: Riana Azad
Test Executed Date: 13-05-2024
Test Title: User can recharge balance.
Description: User can recharge balance by any amount.
Pre-condition: User is logged in.
Dependencies: None

Steps Test Steps Test Data Expected Actual Result Status Note
Result
1 Navigate to the Recharge The account The account Pass
recharge option. amount: 500 balance will balance is
2 Select the increase by increased by
amount to be bdt 500. bdt 500.
recharged.

Test Case ID: 6

Test Designed by: Riana Azad
Test Priority: High Test Designed Date: 12-05-2024
Module Name: Lost Card/Complaint Submission. Test Executed by: Riana Azad
Test Executed Date: 13-05-2024
Test Title: User can submit complaint, issues, lost
Card incidence.
Description: User can submit complaint, issues, lost Card incidence.
Pre-condition: User is logged in.
Dependencies: None

Steps Test Steps Test Data Expected Actual Result Status Note
Result
1 Navigate to the Select Wallet The issue The issue is Pass
lost and fine theft option and will be submitted and
option. submit. submitted stored in the
2 Provide details. and stored in Database.

Page 62 of 67
3 Select reason the Admin
from options Database. received the
4 Click Submit Admin will details.
Button. receive the
details.

Test Case ID: 7

Test Designed by: Riana Azad
Test Priority: High Test Designed Date: 12-05-2024
Module Name: Lost Card/Complaint Manage. Test Executed by: Riana Azad
Test Executed Date: 13-05-2024
Test Title: Admin can deduct balance due to lost
Card or deny the request.
Description: Admin can deduct balance due to lost card or deny the request.
Pre-condition: Admin is logged in and there is a lost card issue.
Dependencies: None

Steps Test Steps Test Data Expected Actual Result Status Note
Result
1 Navigate to the Admin email: The deducted The amount Pass
lost and fine admin@admin. amount will be is deducted
option. com updated to a from the
2 View the reason Admin specific user user's
for the loss and Password: balance. The balance. The
other details. 123456 denied denied
3 Deduct Balance response request didn’t
if there is credit. won’t have have any
4 Deny if there is any effect till update till the
no credit. the user user
recharges. recharges.

Page 63 of 67
Test Case ID: 8
Test Designed by: Riana Azad
Test Priority: High Test Designed Date: 12-05-2024
Module Name: Generate Report. Test Executed by: Riana Azad
Test Executed Date: 13-05-2024
Test Title: Admin can generate a report of ticket
Bookings.
Description: Admin can generate a report of ticket bookings with all details.
Pre-condition: Admin is logged in.
Dependencies: None

Steps Test Steps Test Data Expected Actual Result Status Note
Result
1 Navigate to the Click on A report of all A report of all Pass
bookings page. generate report. ticket ticket
2 Admin will see purchases of purchases of
the details of all all passengers all
bookings. will be passengers is
3 Click on displayed. displayed.
generate report.

Page 64 of 67
 9. Conclusion

In conclusion, the "Online Metro Rail Ticket Booking System" represents a significant
advancement in modernizing public transportation services. The seamless integration of user-
friendly interfaces, efficient backend management, and secure database storage offers commuters
a convenient and hassle-free experience when booking metro rail tickets. By addressing key user
requirements such as easy registration, comprehensive metro information access, and secure
payment processing, the project has successfully met its primary objectives.

Moreover, the system's ability to handle multiple functionalities, including pass management,
complaint submission, and lost card reporting, demonstrates its versatility in catering to diverse
user needs. The emphasis on responsiveness and accessibility ensures that users can interact with
the system seamlessly across various devices, enhancing their overall experience.

The implementation of rigorous risk management strategies, thorough testing protocols, and
adherence to industry best practices has contributed to the reliability, security, and robustness of
the system. By mitigating potential risks and ensuring high-quality standards throughout the
development process, the project team has delivered a reliable and efficient solution to the
stakeholders.

Looking ahead, continual updates, enhancements, and user feedback integration will be essential
to maintaining the system's relevance and effectiveness in meeting evolving user demands and
technological advancements. Additionally, ongoing support and maintenance efforts will be crucial
for sustaining optimal system performance and ensuring long-term viability.

Overall, the "Online Metro Rail Ticket Booking System" stands as a testament to the power of
innovative technology in revolutionizing public transportation services, offering commuters a
modern, efficient, and user-centric solution for their travel needs.

Page 65 of 67
9.1 Limitation of the Project

While the System holds promise in streamlining ticket-related processes and enhancing user
experience, it's essential to acknowledge certain limitations that may impact its effectiveness and
usability:

• Payment options: The system may have limited payment options, potentially excluding
users who prefer alternative payment methods or currencies.
• Language barriers: The system may only support a single language, limiting accessibility
for users who speak different languages.
• Platform compatibility: The system may only be compatible with specific web browsers or
devices, potentially excluding users who use alternative platforms.
• Service disruptions: Technical issues or system maintenance activities may lead to
temporary service disruptions, impacting user experience and causing inconvenience.
• Data accuracy: The accuracy of metro information, schedules, and fares may depend on
timely updates from metro authorities, leading to potential discrepancies or outdated
information.
• User support: Limited user support channels or resources may hinder users' ability to
resolve issues or seek assistance when encountering problems with the system.
• Regulatory compliance: The system's compliance with regulatory requirements, such as
data protection laws or accessibility standards, may vary depending on jurisdictional
regulations, potentially leading to legal risks or penalties.
• Scalability challenges: As user demand grows, the system may face scalability challenges
in handling increased traffic, data volumes, or concurrent user sessions, leading to
performance issues or downtime.
• Dependency on third-party services: The system's functionality may rely on third-party
services or APIs, making it vulnerable to disruptions or changes in those services'
availability or functionality.
• User adoption: The success of the system relies on user adoption and acceptance, which
may vary depending on factors such as user preferences, familiarity with online booking
systems, or perceived benefits compared to traditional ticket purchasing methods.

Page 66 of 67
 By acknowledging these limitations upfront and proactively addressing them through proper
planning, risk mitigation strategies, and continuous improvement efforts, stakeholders can better
position the Ticket Management System for success and maximize its benefits for users and
organizations alike.

9.2 References

1. Gupta, R., & Kumar, A. (2019). Online ticket reservation system for metro using QR code.
International Journal of Advanced Research in Computer Science, 10(2), 139-144.
2. K. Goyal, N. Gupta, A. Khare, "Design and Implementation of Online Railway Reservation
System," International Journal of Computer Science and Mobile Computing, Vol. 3, Issue
5, May 2014.
3. A. Singh, S. Kumar, "Design and Development of Railway Reservation System,"
International Journal of Innovative Research in Computer and Communication
Engineering, Vol. 2, Issue 4, April 2014.
4. S. M. A. Halim, S. Ahmed, "Design and Development of an Online Bus Ticket Booking
System," International Journal of Engineering and Innovative Technology, Vol. 3, Issue 11,
May 2014.
5. R. S. Anand, S. Shukla, "Design and Development of Online Movie Ticket Booking
System," International Journal of Innovative Research in Computer and Communication
Engineering, Vol. 3, Issue 4, April 2015.
6. A. Mishra, P. Tiwari, "Design and Implementation of Online Hotel Room Booking
System," International Journal of Engineering Science and Computing, Vol. 7, Issue 1,
January 2017.

Page 67 of 67