<BANKRUPT AIRLINES> Use Case Specification: <BOOK A TICKET >

Version <1.0>

Version:

<1.0>

Date: <25/08/2009>

Revision History
Date <24/08/2009> Version <1.0> Description <Add flow of events> <pooja> Author

Confidential

, 2000

ii

Version:

<1.0>

Date: <25/08/2009>

Table of Contents
1. Cancel a ticket 1.1 Brief Description 2. Flow of Events 2.1 Basic Flow 2.2 Alternative Flows 2.2.1 < First Alternative Flow > 2.2.2 < Second Alternative Flow > PreConditions 3.1 < Precondition One > 3.2 < Precondition Two > 4. PostConditions 4.1 < Postcondition One > 4.2 < Postcondition Two> 5 1 1 4 4 4 1 1 4

3.

Confidential

, 2000

iii

Use Case Specification: <BOOK A TICKET>

1.
1.1

BOOK A TICKET
Brief description. 1.2 Ticket is issued to a passenger whenever requested.

2.
2.1

Flow of Events
Basic Flow

1 2 3 4

Passenger selects book a ticket button. System requests for passenger details Passenger enters the details 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 3.1 4.2

Alternative Flows If any errors, then clear that field and display that page again. 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. 3.1 3.2

PreConditions Passenger is valid. Ticket is available.

Confidential

, 2000

4. 4.1 4 .2

PostConditions Passenger details should be update. Flight details should be updated.

Confidential

, 2000

<Bankrupt Airlines> Use Case Specification: <Cancel a ticket>

Version <1.0>

Confidential

, 2000

Version:

<1.0>

Date: <08/09/2009> <document identifier>

Revision History
Date <08/09/2009> Version <1.0> Description <Add flow of events> <roma> Author

Confidential

, 2000

ii

Version:

<1.0>

Date: <08/09/2009> <document identifier>

Table of Contents
1. Cancel a ticket 1.1 Brief Description 2. Flow of Events 2.1 Basic Flow 2.2 Alternative Flows 2.2.1 < First Alternative Flow > 4. PreConditions 4.1 < Precondition One > 4.2 < Precondition Two > 5. PostConditions 5.1 < Postcondition One > 5.2 < Postcondition Two > 1 ii 4 4 4 1 4

Confidential

, 2000

iii

Version:

<1.0>

Date: <11/08/09> <document identifier>

Use Case Specification: <Cancel a ticket>

5.
5.1 6. 6.1

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

Flow of Events 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 3.1

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

7. 7.1 7.2

PreConditions Passenger is valid. Ticket is cancelled.

Confidential

, 2000

ii

Version:

<1.0>

Date: <11/08/09> <document identifier>

8. 8.1 8.2

PostConditions Passenger details should be updated. Flight details should be updated.

Confidential

, 2000

iii

Version:

<1.0>

Date: <11/08/09> <document identifier>

<Bankrupt Airlines> Vision

Version <1.0>

Revision History
Date <11/08/09> Version <1.0> Add features Description SAKEC Author

Confidential

, 2000

iv

Version:

<1.0>

Date: <11/08/09> <document identifier>

Table of Contents
1. Introduction 1.1 Purpose

1.2 Problem Statement

2. Stakeholder and User Descriptions 2.1 Passenger 2.2 Employee

3.

Product Features 3.1 VIEW FLIGHT DETAILS 3.2 BOOK A TICKET 3.3 ENTER PASSENGER DETAILS 3.4 CANCELLATION

Confidential

, 2000

Version:

<1.0>

Date: <11/08/09> <document identifier>

Vision
9. Introduction
The purpose of this document is to collect, analyze and define high-level needs and features of the Bankrupt Airlines. It focuses on the capabilities needed by the stakeholders, and the target users, and why these needs exist. The details of how the Bankrupt Airlines fulfils these needs are detailed in the use-case and supplementary specifications. 9.1 9.2 Purpose To provide web-based facilities and easy access to airlines services. Problem Statement Bankrupt Airlines offers numerous flights between many countries. Information maintained about flight no, departure time, departure city, arrival time, arrival city, and dates available. To reserve a seat on one of Bankrupts flight, customer has to furnish name, address, CC No. Flight No, date boarding and destination cities and class. Then the ticket is issued to the customer. Note that many customers can book each flight and customer for many flights, but only a single ticket is to be 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.
10.1

Stakeholder and User Descriptions

There are two users of the system. Passenger

10.1.1 <passenger>

Representative Description Responsibility Confidential

Passenger Passenger is the one who provides the details for booking a ticket. To book a ticket, To enter details , 2000 6

Version:

<1.0>

Date: <11/08/09> <document identifier>

10.2

Employee
Representative Description Responsibilitie s Employee Employee supervises the system To calculate refund, to cancel a ticket

10.2.1 <employee>

11.
11.1

Product Features
VIEW FLIGHT DETAILS

Information about flight no, departure time, departure city, arrival time, arrival city and dates available.

Confidential

, 2000

Version:

<1.0>

Date: <11/08/09> <document identifier>

11.2 11.3 11.4

BOOK A TICKET ENTER PASSENGER DETAILS CANCELLATION

Confidential

, 2000

Version:

<1.0>

Date: <11/08/09> <document identifier>

Confidential

, 2000

Version:

<1.0>

Date: <11/08/09> <document identifier>

Confidential

, 2000

10

Version:

<1.0>

Date: <11/08/09> <document identifier>

Confidential

, 2000

11

Version:

<1.0>

Date: <11/08/09> <document identifier>

Confidential

, 2000

12

Version:

<1.0>

Date: <11/08/09> <document identifier>

Confidential

, 2000

13

Version:

<1.0>

Date: <11/08/09> <document identifier>

Confidential

, 2000

14

Version:

<1.0>

Date: <11/08/09> <document identifier>

Confidential

, 2000

15

Version:

<1.0>

Date: <11/08/09> <document identifier>

Confidential

, 2000

16