Airline Reservation System

Agenda

 Project Overview
 Use Case Diagrams
 System Functionality
 Cost Estimation Model
 Gantt Chart
 Architecture Elaboration Plan
 Project Plan
 Questions
Project Overview

 The main objective of this project is to design

and develop an Airline Reservation System.
 This project is mainly intended for the
customers, who use the airline websites to
make reservations on flights.
 This system will be implemented in C#.NET
and SQL Server 2000 will act as the
database.
Project Overview continued

 The main motivation for the project comes

from my interest to learn new technologies,
like C# and ASP.NET.
 Creating a web-based online application
would give me more experience using these
technologies.
 Database design was also one of my major
objective for choosing this project.
Use Case Diagrams

 Customer Use Case

Diagram
Use Case Diagrams continued

 Administrator Use Case

Diagram
System Functionality

 The functionality for the project is divided

among the users and administrators of the
Airline Reservation System.

 User Functionality
 Administrator Functionality
User Functionality

 New Registration
 Edit personal details
 Login/Logout
 Book flights
 Book motels, packages along with the airline
ticket reservations
 Contact the airline company
 View the booking instructions online
Administrator Functionality

 Login/Logout
 Add/Delete/Modify customer information
 Add/Delete/Modify flight information
 Add/Delete/Modify package or motel
information
 Cancellation of Reservations
 E-mail Confirmation
 Modify details of web-page
Cost Estimation Model

 The Constructive Cost Model, also known as

the COCOMO model ,has been designed in
1981 by Barry Boehm, to give an estimate of
number of man months it will take to develop
a software product.
 The model also estimates the development
schedule for the project in months and gives
us a schedule distribution for all the major
phases of a project.
Cost Estimation Model continued

 The Airline Reservation System project has an average

complexity and fair flexibility. Thus, this project is classified as
an organic project under the COCOMO model.
 The equations as they are modified for the organic projects are
as follows:
 Effort = 3.2 * EAF * (Size) ^ 1.05
 Time = 2.5 * (Effort) ^ 0.38 where
 Effort = number of staff months (PM)
 EAF = effort adjustment factor
 Size = number of lines of code for completed product. It is
measures in KLOC (thousands of lines of code)
 Time = total number of months
Cost Estimation Model Continued

 Effort = 3.2 * 0.45 * 3.0 ^ 1.05 = 4.56 staff

months
 Time = 2.5 * 4.56 ^ 0.38 = 4.44 months
(development time)
Gantt Chart
Architecture Elaboration Plan

 Revision of the Vision document

 Revision of the Project Plan
 Architecture Design
 Developing Prototype
 Test Plan
 Formal Technical Inspections
 Formal Requirements Specification
 Phase 2 Presentation
Project Plan (Phase 1)

 Vision Document 1.0

 Project Plan 1.0
 Software Quality Assurance Plan
 Presentation 1
Project Plan (Phase 2)

 Action items identified during phase I

 Vision Document 2.0
 Project Plan 2.0
 Formal Requirement Specification
 Architecture Design
 Test Plan
 Formal Technical Inspection – submitted by two
individual MSE students
 Executable Architecture Prototype
 Phase 2 Presentation
Project Plan (Phase 3)

 Action items identified during phase II

 User Manual
 Component Design
 Source Code
 Assessment Evaluation
 Project Evaluation
 Test Results
 References
 Formal Technical Inspections - submitted by two individual MSE
students
 Final MSE presentation
Questions ?