outlines a series of use cases for a theoretical airline database system. The document details scenarios including new user registration, user authentication, city and airline determination, flight and ticket determination, booking information and price, manage users $($administrator side$),$ and add airline information $($provider side$).$

New User Registration:

Aim: To register a new user who does not exist in the Airline Database.

Primary Actor: User

Success: User is added into the Airline DB$,$ enabling access to the online booking service.

Failure: User encounters an authentication error and cannot use the application.

User Authentication:

Aim: To authenticate a user who holds a userid and password.

Primary Actor: User

Success: User is authenticated.

Failure: User is not authenticated.

City and Airline Determination:

Aim: To allow users to determine departure and arrival cities, dates, number of tickets, and select an airline company.

Primary Actor: Airline User

Success: Necessary details are determined.

Failure: The reservation process is halted due to validation or general errors.

Flight and Ticket Determination:

Aim: To enable users to choose from available flights and provide passenger information.

Primary Actor: Airline User

Success: User selects a flight and provides passenger info.

Failure: Information is not displayed due to an error.

Booking Information and Price:

Aim: To display booking details and total price to the user for confirmation.

Primary Actor: Airline User

Success: Booking is confirmed successfully.

Failure: Information display or form submission errors occur.

Manage Users $($Administrator Side$)$:

Aim: To allow administrators to manage user profiles, including adding, deleting, and updating.

Primary Actor: Airline Administrator

Success: User profiles are managed successfully.

Failure: Operations fail due to errors.

Add Airline Information $($Provider Side$)$:

Aim: For providers to add or delete informa$10$:$44$ PM

$$

$18$

Airline$-$Use$-$Cases$-$Modi...

Edit

$2.$ User Authentication

Characteristic Information:

$\backslash$table$[[$Goal in Context:,Authenticate user$],[$Scope:$,],[$Level:$,],[$Pre$-$Condition:,$\backslash$table$[[$User is registered and holds a userid and a$],[$password$]]],[$Success End Condition:,User is authenticated$],[$Failed End Condition:,User is not authenticated$],[$Primary Actor:,User$],[$Trieger Event:,User hits "Sign in$"$ in the Airline Main Screen$]]$

Main Success Scenario:

$\backslash$table$[[$Step$,$Actor,$],[1.,$User,$\backslash$table$[[$Fils in the userid field and password field with a valid Unique$],[$Identifier $($ex$.-$ Email Address$)$ and a valid Password$]]],[2.,$Eser,Hits the "Sign In$"$ button to submit the request.$],[3.,$System,$\backslash$table$[[$Checks submitted credentials against user database and grant access if$],[$they match with an existing record. If not they are asked to register.$]]],[4.,$System,$\backslash$table$[[-$ Displays the City and Airline Determination page that$],[$contains the following fields $($Departure City, Arrival$],[$City$,$ Deporting Date, Return Date, Airline company, and$],[$number of tickets required$)$ if the user is marked as a$],[$user in addition to options for viewing and updating the$],[$user$\text{'}$s profile.$],[-$ Displays the Administrator Page if the user is$],[$authenticated as Administrator$],[-$ Displays the Provider Main Page if the user is$],[$authenticated as Provider$]]],[5,$User,Hits the "Forsot" button to find his passuerd$],[6,$System,Display two fields the secret question and answer question$],[7,$User,Enter the ansuer of the serret aueation$]]$

$\backslash$table$[[$Step$,$Actor,$],[8,$User,Hits the "Sign up$"$ button to return back to the wer res$],[9,$User,Hits the "help" button$],[10,$System,Displas more information how to sign in$]]$

$3$ Citvand Sirline Determination

Select files

Add to Tags

Tools

Share

C $7$ DE

$1492$

YOLtion about airlines.

Primary Actor: Airline Provider

Success: Airline information is saved in the database.

Failure: Record could not be saved due to an error.

This document serves as an assignment and is designed to cover various aspects of database management and application design within the context of an airline reservation$$system$.$