SECTION $2$: SYSTEM REQUIREMENTS $(40$ MARKS$)$

In this section, your team shall propose User Stories for your proposed

assignment title$-$Flight Booking System that covers the following aspects.

$$ Apply sprints in scrum methodology as learned in the lecture. The elements

of each sprint cycle must include:

o Sprint goal $(6$ marks$)$

o Sprint backlog $(20$ marks$)$

o Estimated velocity $(6$ marks$)$

o Schedule $(6$ marks$)$

o Team members $(2$ marks$)$

Explanation of Flight Booking System flowchart:

The process begins with the user accessing the system. If the user is new, they must register. Otherwise, they can log in with existing credentials. For user registration, new users must provide personal information such as name, email address, phone number, and password. This data is validated to ensure it meets the required format and completeness. Once validated, the information is securely stored in the database, and the user will be notified of successful registration. For the user login$,$ returning users input their username and password. The system authenticates these credentials against the stored data. If valid, the user gains access to the main page; if not, an error message prompts re$-$entry or password recovery. Users enter travel details, including departure and destination cities, travel dates, and the number of passengers in search flights. The system queries the database to retrieve matching flights and display the results. Flight options are shown with relevant details such as airline, departure and arrival times, duration, and price. Users can filter and sort results based on price, airline, or duration preferences. Users select a preferred flight, which is then highlighted, and additional details are displayed for confirmation. Users provide passenger information for booking details, including names, contact details, and any special requirements. The data is validated and stored. Users can select a payment method such as credit card, debit card, or online banking for payment processing. The system interfaces with the payment gateway to process the transaction securely$.$ Upon successful payment, an e$-$ticket is generated. The system sends a confirmation email with the booking details and e$-$ticket attached. Users can also view this information in their accounts. Users can view current and past bookings, modify travel dates or passenger details, or cancel reservations if needed. The system applies relevant policies for changes or cancellations and updates the database accordingly. For additional assistance, users can contact support through a dedicated portal. Support staff can access booking details and help with modifications, cancellations, or other inquiries.