P. 1
airline

airline

|Views: 18|Likes:
Published by kvbhavani
gsdgd
gsdgd

More info:

Published by: kvbhavani on Jan 26, 2013
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PPT, PDF, TXT or read online from Scribd
See more
See less

04/14/2014

pdf

text

original

Airline Reservation System

MSE Project Phase 1 Presentation
-- Kaavya Kuppa Committee Members: Dr.Daniel Andresen Dr.Torben Amtoft Dr. Mitchell L. Neilsen

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

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

.  Database design was also one of my major objective for choosing this project.NET. like C# and ASP.  Creating a web-based online application would give me more experience using these technologies.Project Overview continued  The main motivation for the project comes from my interest to learn new technologies.

Use Case Diagrams  Customer Use Case Diagram home page Login and Register Book Flights Customer or the End User Book Motel Book a Package Contact the company Booking Intructions .

Use Case Diagrams continued Lo in/Lo o g g ut  A /D le dd e te/M d o ify C stom In u er form tion a Administrator Use Case Diagram Ad e d /D lete/M dify o flig in rm ht fo ation Ad inistrato m r Ad e te od d/D le /M ify M tel in rm tion o fo a A /D te/M dify dd ele o P acka e Info a n g rm tio C cella n o an tio f R serv tio s e a n M dify d tails o o e f w bp ge e a E ail -m con ation firm s .

 User Functionality  Administrator Functionality .System Functionality  The functionality for the project is divided among the users and administrators of the Airline Reservation System.

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

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 .

also known as the COCOMO model .Cost Estimation Model  The Constructive Cost Model.  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. to give an estimate of number of man months it will take to develop a software product. .has been designed in 1981 by Barry Boehm.

The equations as they are modified for the organic projects are as follows: Effort = 3.Cost Estimation Model continued         The Airline Reservation System project has an average complexity and fair flexibility. Thus.38 where Effort = number of staff months (PM) EAF = effort adjustment factor Size = number of lines of code for completed product.2 * EAF * (Size) ^ 1.05 Time = 2. It is measures in KLOC (thousands of lines of code) Time = total number of months .5 * (Effort) ^ 0. this project is classified as an organic project under the COCOMO model.

2 * 0.0 ^ 1.5 * 4.44 months (development time) .56 staff months  Time = 2.45 * 3.56 ^ 0.Cost Estimation Model Continued  Effort = 3.05 = 4.38 = 4.

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 .

0  Software Quality Assurance Plan  Presentation 1 .0  Project Plan 1.Project Plan (Phase 1)  Vision Document 1.

0 Project Plan 2.Project Plan (Phase 2)          Action items identified during phase I Vision Document 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 ? .

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->