17% found this document useful (6 votes)
3K views28 pages

Product Backlog PassengerMgmt v1.0

This document outlines user stories, acceptance criteria, and instructions for an airline booking case study to be completed using Agile Scrum methodology by a team of 4-6 members. The case study involves developing UI pages for passenger registration and ticket booking, creating SQL database tables, and writing code to implement the features. Teams will submit artifacts including sprint backlog, burn down chart, UI, SQL, and code files in a zip folder along with team member details. Peer review is recommended where other teams can review the case study implementation.

Uploaded by

sanskriti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
17% found this document useful (6 votes)
3K views28 pages

Product Backlog PassengerMgmt v1.0

This document outlines user stories, acceptance criteria, and instructions for an airline booking case study to be completed using Agile Scrum methodology by a team of 4-6 members. The case study involves developing UI pages for passenger registration and ticket booking, creating SQL database tables, and writing code to implement the features. Teams will submit artifacts including sprint backlog, burn down chart, UI, SQL, and code files in a zip folder along with team member details. Peer review is recommended where other teams can review the case study implementation.

Uploaded by

sanskriti
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLS, PDF, TXT or read online on Scribd
You are on page 1/ 28

Feature

Passenger Registration – UI

Ticket Booking – UI

Booking List – UI

Passenger Registration – DB

Ticket Booking – DB

Master Data – DB

Booking List – DB

Passenger Registration – Programming

Ticket Booking – Programming

Booking List – Programming


Instructions:

Case study has few user stories to be implemented as static UI pages, few for creating SQL tables and writing queries and
either Java/Python/C#

User stories are disconnected when it comes to implementation. Hence there will be no direct layer between UI and datab
programming or UI and programming.

Please go through the webex recording shared in Agile Case Study course. It will explain how you can leverage online tools
execution

You may choose team members from your own college or other groups you are connected with

Ideally, recommended team size is 4-6 members. However you can adjust team size as per available members

Case study should not be implemented by single team member as the whole idea for Agile Scrum is to work as a team

Focus on daily standup updating sprint burn down chart on daliy basis

As case study artifacts, you need to submit Sprint Backlog, Burn down chart, UI files, SQL files and code files in .zip form
id of team members in separate file

Case study may be reviewed by faculties based on their availability. However we would recommend peer review where you
from your references and consider their review.

You can consider own assumptions for any of the user stories in case of any doubts

There is no standard format for submission as far as zip file includes below details:
Sprint backlog as simple xls file
Sprint burndown chart as image
UI files (HTML,CSS,JS files) where UI related user stories are implemented
SQL files where database related user stories are implemented
Code files (.java/.py/.cs) where coding related user stories are implemented
Team details - xls file referring CT/DT id and name of team members
Assumptions - txt file with any assumptions made for case study (not mandatory if there are no assumptions)

Product backlog tab in this xls has details of user stories

Next few tabs are reflecting sample UI screens


Story
SlNo Feature Description (Card)
number

Passenger As a Passenger, I want to be able to self register


1 US001
Registration – UI into the system with my details.
Ticket Booking – As a Passenger, I want to be able to login to the
2 US002
UI system and book ticket for a journey

As a Passenger, I want to be able to login to the


3 Booking List – UI US003
system and view the booked ticket history.

As a Developer
Passenger
4 US004 I want to create database table(s)
Registration – DB
So that I can store passenger information
As a Developer
Ticket Booking –
5 US005 I want to create database table(s)
DB
So that I can store Booking information

As a Developer
I want to create database table(s)
6 Master Data – DB US006
So that I can store master data information in
tables.

As a Developer
I want to retrieve all the booking detail
7 Booking List – DB US007
currently available including the passenger
information.

Passenger As a Developer, I want to be able to register


8 Registration – US008 Passenger into the system with my details from
Programming Console.
Ticket Booking – As a Developer, I want to be able to book ticket
9 US009
Programming for a journey for a Passenger from Console

Booking List – As a Developer, I want to be able to view the


10 US010
Programming booked ticket history.
Initial Size Business
Acceptance Criteria (Confirmation)
Estimate (SP) Priority

* Passenger can able to enter the following information in the screen;


 Passenger ID: A text value for Passenger ID with an auto populated
number which is not editable.
 Passenger Name: A text value for Passenger name(Maximum 50 characters)
 Email: A text field to capture the Email.
 Password: A text value for Password(Maximum 30 characters)
 Address: A text area to capture street, city details(Maximum 100
characters)
 Contact Number:Text field. Maximum 10 characters.
 Register: Submit button.
* After clicking the 'Register' button, a registration acknowledgment screen
need to be displayed with a success message. "Passenger Registration
successful." in green color.
* Also display the following attributes in the Acknowledgment screen;
Passenger Id (Randomly generated), Passenger Name and Email.
* The registration process is static only, no need to integrate with database.
* After login to the system using the userId and password, passenger can
book a ticket by entering the following information in the screen;
 PNRNO: A text value for PNR No with an auto populated number which is
not editable.
 Travel Date: A Date component to enter the journey date.
 Source: A text field to capture the Source airport.
 Destination : A text value for capture the Destination airport.
 Status: A drop down with following status New/Confirm/Hold
 Seat Preference: A drop down with following values Window, Middle,Aisle
 Meal Preference: A drop down with following values Veg, Non Veg
 Book Ticket: Submit button.
* After clicking the 'Book Ticket' button, a booking acknowledgment screen
need to be displayed with a success message. "Ticket Booked successfully." in
green color.
* Also display the following attributes in the Acknowledgment screen; PNR
No (Randomly generated), Travel Date, Source Airport and Destination
Airport.
* The Booking process is static only, no need to integrate with database.

* This screen shows rows with columns; PNR NO | Travel Date | Source |
Destination | Seat Preference | Meal Preference
* There should be a pagination option with Next> and <Prev links. The default
row size of the listing is 5.
* Display static data with 8 booking details for the passenger that need to be
span in two pages and navigate using the pagination links.

* The table should contain option for capturing the following information;
Passenger Name, Age, Email, Phone.
* Design the attribute with proper data type and primary key.
* Create the table script as an .sql file.
* Insert 5 passenger information to this table. Create the insert script for the
same. Also save it as an .sql file.
* The table should contain option for capturing the following information;
PNRNO, Travel Date, Source Airport, Destination Airport, Status, Seat
Preference, Meal Preference.
* Design the attribute with proper data type and primary key.
* Add a relationship with the Passenger table.
* Create the table script as an .sql file.
* Insert 10 booking details to this table. Create the insert script for the same.
Also save it as an .sql file.

* Create a table to setup the master data details for Booking Status and
insert the values.
* Create a table to setup the master data details for Seat Preference and
inser the master data to the same.
* Create a table to setup the master data details for Meal Preferences and
insert the values.
* Save the table schema and insert script in an .sql file.

* Write a SQL statement for retrieving the booking details and passenger
details together in a query.
* The query result should contain the following attributes;
PNR NO | Travel Date | Source | Destination | Seat Preference | Meal
Preference | Passenger Name | Email | Phone

* Developer needs to input the following information from the console using
programming to register Passenger:
 Passenger ID: A random 7 digit number for Passenger ID with a default
value
 Passenger Name: A string field for Passenger name(Maximum 50
characters)
 Email: A string field to capture the Email.
 Password: A string field for Password(Maximum 30 characters)
 Address: A string field to capture street, city details(Maximum 100
characters)
 Contact Number:Text field. Maximum 10 characters.
* Once all fields are taken as input, Passenger details need to be inserted in
array/list/appropriate collection. After successful registration, a registration
acknowledgment message need to be displayed on the console as "Passenger
Registration is successful".
* Developer needs to input the following information from the console using
programming to book ticket for a Passenger:
* Passenger ID: A 7 digit number for Passenger ID for whom booking is to be
done.
 PNRNO: A string field for PNR No with a default 7 digit number.
 Travel Date: A string field to enter the journey date in
format(dd/mm/yyyy).
 Source: A string field to capture the Source airport.
 Destination : A string field to capture the Destination airport.
 Status: A string field to select among following values New/Confirm/Hold
 Seat Preference: A string field to select among following values, Middle,Aisle
 Meal Preference: A string field to select among following values
* Once all fields are taken as input, Booking details need to be inserted in
array/list/appropriate collection. After successful booking, a booking
acknowledgment message need to be displayed on the console as "Ticket
Booked successfully, Happy Journey...”.

* Developer needs to input the following information from the console using
programming to view the booked ticket history for a Passenger:
* Passenger ID: A 7 digit number for Passenger ID for whom booking is to be
done.
* On submitting the passenger id, The console shows rows with columns
populated from inserted array/list/appropriate collections; PNR NO | Travel
Date | Source | Destination | Seat Preference | Meal Preference
Sprint
Comments
Number

Refer : ABC Screen1


Refer : ABC Screen2

Refer : ABC Screen3


ABC Screen1

Page 15
ABC Screen1

Page 16
ABC Screen1

Page 17
ABC Screen1

Page 18
ABC Screen2

Page 19
ABC Screen2

Page 20
ABC Screen2

Page 21
ABC Screen2

Page 22
ABC Screen2

Page 23
ABC Screen2

Page 24
ABC Screen3

Page 25
ABC Screen3

Page 26
ABC Screen3

Page 27
ABC Screen3

Page 28

You might also like