SlNo Feature Story number

1 Login and Registration (Flask) US001

2 Train Search and seat availibility US002

3 Ticket Booking US003

4 Booking History US004

5 Configure system settings US005

6 List Trains with available Seats US006

7 Retrieve Booking Details with passenger information US007

Description (Card)

As a user, I want to be able to login into the ticket system if already a

registered user, otherwise register for the same

As a user , I want to search for train and get information on seat

availibity
As a user I want to book tickets

As a user I want to see my booking history amd search for specific

bookings that I might have made

As an admin, I want to acess to system configuration settings

As a Admin, I want to provide users with a list of trains with available

seats

As a admin I want to retrieve detailed booking information

 Initial
Size Business
Acceptance Criteria (Confirmation)
Estimate Priority
(SP)

As a system user for Train ticket system, I want the customer/user to be able to
register in the system and admin to be predetermined.
Requirements:

Registration:
for the purpose of registration refer 1_PBL_UI -> US_UI_001 for UI And 4_PBL_SQL -
>US_SQL_001 for SQL
- Customer should be able to register themselves from the registration page, but the
admin should not be able to register himself as admin from the registration page.
- Admin will create the credentials for another admin from the backend itself

Login:
Refer 1_PBL_UI ->US_UI_002 for UI

- Customer and admin both should be able to login into the application from the same
login page.
- To login, the user will enter his username and password which will be queried from
the login table containing the login credentials and the role.

Validation and other caveats:

1) You will be storing the registered user in the database for the application.

2) The table for the user will store the required user information. You can create a
login table to store the login credentials and roles.

3) If the user logs out of the website they should be redirected back to the login page.

As a Customer I , after selecting a specific train and class, I want seamless transition to
ticket booking interface, allowing me to efficiently provide passenger details and
complete booking process.
Refer 1_PBL_UI ->US_UI_002 -> 2 for UI
4_PBL_SQL -> US_SQL_002 for database
Acceptance Criteria:
- After selecting a train from the search results and choosing the preferred class, the
system should navigate the user to the ticket booking page.
- The ticket booking page should retain information about the selected train and class.
- Relevant error messages should be displayed for incomplete or incorrect passenger
information.
- Users should receive immediate confirmation of their booking, with a usually
appealing summary of the ticket details.
- Relevant ticket details should be saved in the database with respective user
information and booking status.
- An option to return to the search results or explore other features should be
accessible from the confirmation page.
Refer 1_PBL_UI ->US_UI_002 -> 2 for UI
4_PBL_SQL -> US_SQL_003 for database

As a user, I want user-friendly interface to search and filter my booking history for
efficient retrieval of information.
Here the data will be pulled from the respective database tables.
The user will also get an option to cancel the ticket in this window.
Upon cancellation the status of ticket will be changed to cancelled from confirmed in
the respective database table

The refund will be processed in the below mentioned criteria :

-Within 48 hr of booking ticket -> 100% refund of ticket amount
-after 48 hr of booking and before 24 hr of departure of train 70%
-Otherwise 40% refund of the ticket amount
[Update data and reflecting the same on admin and user end]

Refer 1_PBL_UI ->US_UI_002 -> 3 for UI

4_PBL_SQL -> US_SQL_003 for database

Validate Admin Login refer 1_PBL_UI-> US_UI_003

Upon successful login the admin should be able to list the the train availablity for
users and check the train charts

As a admin I want to provide the the train and seat availability schedule for the users
to access
This page will take neccesary train details like train ID - Train name , train timings ,
starting and destination station , seats available in respective classes
Upon successful upload of this data the details should reflect for the user upon search
Refer 1_PBL_UI-> US_UI_003

Admin should be able to check train charts for specific trains with passenger
information such as name gender ID and the seats allocated to them etc
Refer 1_PBL_UI ->US_UI_003 for UI
4_PBL_SQL -> US_SQL_003 for database
Sprint
Number
 Story
SlNo Feature Description (Card)
number

1 Action RediUS_Web_0Page redirection

2 NavigationUS_Web_0Navigation for the application
3 Login and RUS_Web_0Login and Registration
4 Update andUS_Web_0Update and delete from user
5 ArchitecturUS_Web_0Architecture For the application
 Initial
Size Business
Acceptance Criteria (Confirmation)
Estimate Priority
(SP)

You will be working on the action phrase for the application. You will be developing JSP
pages, that you have already made during your PBL_UI. NOTE: You will be migrating the
HTML pages to JSP pages itself.

You will be redirecting from one web page to another. Right now no need to worry about
how the business logic will work. But one thing you need to remember you will not be
using just an anchor tag to redirect from one page to another. But should be in a specific
flow. You will be calling a servlet from JSP and then redirect to another page.
We will be working on the navigation. We will optimize our code to easily manage
our navigation bar. You will be developing the same with the help of JSP. You will
be writing the navigation bar, in a separate JSP and then you will be including the
same in all the JSP file where it is necessary.

HINT: You can make use of the JSP include function in the JSP to help you
optimize the Navigation bar.
Login:

You will be working the the login part for the application user. You will be taking 2 input
from the user, username/ user email or user id and the password for the application. You
need to follow the proper MVC architecture for developing the feature for the same. After
a successful registration you will be displaying appropriate message/alert and redirect it to
dashboard.

Validation:
1. All the field are required
2. If a field is not entered by the user you need to give the user an appropriate message for
the same.

Register:

You will be creating an register feature for the application user. You will find all the details
that you need for registering a user, from the PBL_SQL case study. You need to follow the
proper MVC architecture for developing the feature for the same. After a successful
registration you will be displaying appropriate message/alert and redirect it to dashboard.

Validation:
1. All the field are required
2. If a field is not entered by the user you need to give the user an appropriate message for
the same.
You will be having a profile page with 2 buttons on the same. One update and one delete
Update:

If I click on update button I should be able update my person information, You will once
again make sure that you are following proper MCV pattern for developing the code. If the
validation is done successfully you will be showing an alert message which states "Updated
Successfully".

Validation:

1. All the field are required

2. Validation need to be put up in every field.

Delete

If I click on delete button by record for the User should be deleted, but this is a hard delete
so you need to delete the reference from all the tables in the database. You will once again
make sure that you are following proper MCV pattern for developing the code. If the
validation is done successfully you will be showing an alert message which states "Deleted
Successfully". Once deleted, you will simply redirect to the login page.

Validation:

1. All the field are required

2. Validation need to be put up in every field.
You will be making MVC pattern architecture. This will make it easier, cleaner and better to manage the coding part in the upcoming sprint
Sprint
Number
coding part in the upcoming sprint for the application