bankrupt airlines-ooad project

8/7/2019 Bankrupt Airlines-ooad Project

1/23

Use Case Specification:

Version


2/23

Version:

Date:

Confidential , 2000 ii

Revision HistoryDate Version Description Author


3/23

Version:

Date:

Confidential , 2000 iii

Table of Contents

1. Cancel a ticket 1

1.1 Brief Description 1

2. Flow of Events 4

2.1 Basic Flow 4

2.2 Alternative Flows 4

2.2.1 < First Alternative Flow > 1

2.2.2 < Second Alternative Flow > 1

3. PreConditions 4

3.1 < Precondition One >

3.2 < Precondition Two >

4. PostConditions 5

4.1 < Postcondition One >

4.2 < Postcondition Two>


4/23

Confidential , 2000 4


1. BOOK A TICKET

1.1 Brief description.

1.2 Ticket is issued to a passenger whenever requested.

2. Flow of Events

2.1 Basic Flow

1 Passenger selects book a ticket button.

2 System requests for passenger details

3 Passenger enters the details

4 Employee will check the availability

4.1 Message will be displayed ticket available

5.Passenger will click on OK button

6. Take back to home page.

2.2 Alternative Flows

3.1 If any errors, then clear that field and display that page again.

4.2 If not available check for another flight.

4.2.1 If he books a ticket go to 4.4.3 Click on exit.

2.3

3. PreConditions

3.1 Passenger is valid.

3.2 Ticket is available.


5/23


4. PostConditions

4.1 Passenger details should be update.

4.2 Flight details should be updated.


6/23



Version


7/23

Version:

Date:


Revision HistoryDate Version Description Author


8/23

Version:

Date:


Table of Contents

1. Cancel a ticket 1

1.1 Brief Description ii

2. Flow ofEvents 4

2.1 Basic Flow 42.2 Alternative Flows 4

2.2.1 < First Alternative Flow > 1

4. PreConditions 4

4.1 < Precondition One >4.2 < Precondition Two >

5. PostConditions 5

5.1 < Postcondition One >5.2 < Postcondition Two >


9/23

Version:

Date:



5. Cancel a ticket

5.1 Brief Description

Whenever passenger wants to cancel a ticket,he or she has to provide the details.

6. Flow of Events

6.1 Basic Flow

1. Passenger selects cancel a ticket button.

2. System requests for passenger details.

3. Passenger enters the details.

4. Employee will calculate no of days for the journey

4.1 Passenger will be given full refund if cancelled before 10 days.

4.2 Passenger will be given 50% refund if cancelled within 10 days.

5. Refund is displayed.

6. Take back to home page.

6.2 Alternative Flows

3.1 if any errors, then clear that field and display that page again.

7. PreConditions

7.1 Passenger is valid.

7.2 Ticket is cancelled.


10/23

Version:

Date:


8. PostConditions

8.1 Passenger details should be updated.

8.2 Flight details should be updated.


11/23

Version:

Date:

Confidential , 2000 iv

Vision

Version Revision History

Date Version Description Author

Add features SAKEC


12/23

Version:

Date:

Confidential , 2000 v

Table of Contents

1. Introduction

1.1 Purpose

1.2 Problem Statement

2. Stakeholder and User Descriptions

2.1 Passenger

2.2E

mployee

3. Product Features

3.1 VIEW FLIGHT DETAILS

3.2 BOOK A TICKET

3.3 ENTER PASSENGER DETAILS

3.4 CANCELLATION


13/23

Version:

Date:


Vision

9. Introduction

The purpose of this document is to collect, analyze and define high-level needsand features of the Bankrupt Airlines. It focuses on the capabilities needed bythe stakeholders, and the target users, and why these needs exist. The details ofhow the Bankrupt Airlines fulfils these needs are detailed in the use-case andsupplementary specifications.

9.1 Purpose

To provide web-based facilities and easy access to airlines services.

9.2 Problem Statement

Bankrupt Airlines offers numerous flights between many countries. Informationmaintained about flight no, departure time, departure city, arrival time, arrival city,and dates available. To reserve a seat on one of Bankrupts flight, customer hasto furnish name, address, CC No. Flight No, date boarding and destination citiesand class. Then the ticket is issued to the customer. Note that many customerscan book each flight and customer for many flights, but only a single ticket is tobe issued to a customer for particular flight. If a customer cancels a ticket before

10 days of date of journey, he or she will get full refund or 50 % refund

10. Stakeholder and User Descriptions

There are two users of the system.

10.1 Passenger

10.1.1

Representative Passenger

Description Passenger is the one who provides the details for booking a ticket.

Responsibility To book a ticket, To enter details


14/23

Version:

Date:


10.2 Employee

10.2.1

Representative Employee

Description Employee supervises the system

Responsibilitie

s

To calculate refund, to cancel a ticket

11. Product Features

11.1 VIEW FLIGHT DETAILS

Information about flight no, departure time, departure city, arrival

time, arrival city and dates available.


15/23

Version:

Date:


11.2 BOOK A TICKET

11.3 ENTER PASSENGER DETAILS

11.4 CANCELLATION


16/23

Version:

Date:



17/23


18/23

Version:

Date:



19/23

Version:

Date:



20/23

Version:

Date:



21/23

Version:

Date:



22/23

Version:

Date:



23/23

Version:

Date:


bankrupt airlines-ooad project

Documents