Project on Airline Reservation System

Agenda
Introduction Project Overview System Analysis Software Requirement OO Approach Design Approach Requirements Listing Next Steps Q&A

Introduction
ARS is part of Passenger Service System (application support direct contact with passenger)  Inventory Management maintain flight details  Manual Vs Technical System  Model View Controller Design


2/5/2012

Manual Vs Technical System

 

Manual: Time consuming & lazy, more error prone Technical System:  Faster System  Accuracy  Reliability  Informative  Reservations and cancellations from any where to any place

2/5/2012

Model - View - Controller

  

Model: Application Object View: screen presentation Controller: Control the user interface update as per the user input

2/5/2012

Project Overview


Objective is to Design and develop an Airline Reservation System  Implement ARS as standalone system  Database design as data storage  Extensible system for future enhancement & maintenance  Object oriented approach

2/5/2012

System Analysis


Block Diagram
User Interface (Customer)
Request Response

ARS

Reports

Data Storage & Access

Process Customer Request

Database

Booking Processing

2/5/2012

Software Requirement
Language: C++ (Visual Studio)  Store Information: File or Database (Oracle/ IIS)  User Interface: MFC  Platform: Windows  Design diagram: Rational Rose


2/5/2012

OO Approach: Fundamentals
Procedural Vs Object Oriented Approach  Why use OO Approach  OO Overview  Object Oriented Principle


2/5/2012

Procedural Approach
APPLICATION
Module 1 Module 2 .. Module N

Program 1

Program 2

Program N

Function 1

Function 2

Function N

Developing an application using the procedural approach would involve  Identification of modules  Programs inside each module Every program would contain several functions and data  The data would be the information necessary for the program and its functions
9

2/5/2012

OO Approach


An Object oriented approach views systems and programs as a collection of interacting OBJECTS.
OBJECT

An object is a thing in a computer system that is capable of responding to messages. An object has to be created from a class so that it can be used

OBJECT

OBJECT

OBJECT

Do this Do this Do this



OBJECT

OBJECT

The procedural approach views systems and programs as a collection of interacting FUNCTIONS

In the procedural approach, a program responds to messages when its functions are invoked. By simply including the file, the functions can be invoked and invocation requires nothing else

2/5/2012

10

Procedural vs. Object-Oriented Programming



The unit in procedural programming is function, and unit function, in object-oriented programming is class objectProcedural programming concentrates on creating functions, while object-oriented programming starts from objectisolating the classes, and then look for the methods inside them. Procedural programming separates the data of the program from the operations that manipulate the data, while object-oriented programming focus on both of objectthem

figure1: procedural
2/5/2012

figure2: object-oriented object11

Why choose the Object Oriented approach?



The OO approach  Deals with classes as the building blocks  Allows Real World Modeling  The idea of OOP is to try to approach programming in a more natural way by grouping all the code that belongs to a particular objectsuch as an account or a customer together

Project * * ProjMgr 1 1 *

ProjLead *

Raise the level of abstraction  Applications can be implemented in the same terms in which they are described by users Easier to find nouns and construct a system centered around the nouns than actions in isolation

Employee

Manager 1 *

Salesperson

Easier to visualize an encapsulated representation of data and responsibilities of entities present in the domain The modern methodologies recommend the object-oriented approach even for applications developed in C or Cobol
12

2/5/2012

Overview of Object Orientation

Object orientation is a technique for system modeling, Object oriented analysis and design, or OOAD, attempts to describe a system as it exists in real life. The system is modeled as a number of related objects that interact. Any system needs objects to do work. It asks its objects to do its work, just as you might ask objects in an online store to deliver goods to you and charge the cost to your credit card. All objects have attributes (characteristics), this is sometimes referred to as state. They also have operations (or methods), this is sometimes referred to as behavior.
2/5/2012 13

About Object

2/5/2012

14

About Class

2/5/2012

15

2/5/2012

16

Object-oriented Principle Encapsulation



Encapsulation is the mechanism that binds together the code and the data it manipulates, and keeps both safe from outside interference and misuse. Public variables and methods Private variables and methods Public variables is not recommended
A Class

2/5/2012

17

Object-oriented Principle Inheritance



Inheritance is the process by which one object acquires the properties of another object. By use of inheritance, an object need only define all of its characteristics that make it unique within its class, it can inherit its general attributes from its parent. Account Checking Mortgage Loan
18

2/5/2012

Design Overview


Use Case overview  System Functionality

2/5/2012

19

Use Case Overview

a view of a system that emphasizes the behavior as it appears to outside users.  A use case model partitions system functionality into transactions (use cases) that are meaningful to users (actors).


2/5/2012

20

Use Case Modeling: Core Elements

Construct Description
use case A sequence of actions, including variants, that a system (or other entity) can perform, interacting with actors of the system. A coherent set of roles that users of use cases play when interacting with these use cases. Represents the boundary between the physical system and the actors who interact with the physical system.

Syntax

UseCaseName

actor

ActorName

system boundary

2/5/2012

21

Use Case example

T el ep h o n e C a ta lo g C he c k s ta tu s

P la ce orde r

S al es p e r so n

F ill o r d e r s C u s to m er E sta b l is h c re d i t S h ip p in g C le r k

S u p e r vi so r

2/5/2012

22

Use case diagram for ARS (Customer view)



Customer Use Case Diagram

2/5/2012

23

System Functionality


User Functionality  Administrator Functionality

2/5/2012

24

User Functionality


Enquiry  Reservation  Report  Edit  Cancellation  Concession

2/5/2012

25

Administrator Functionality
Add/Delete/Modify customer information  Add/Delete/Modify flight information  List all passenger/flight details  Cancellations of Reservation


2/5/2012

26

Requirements Listing
         

Enquiry Reservation Cancellation Report Concession Fare detail & payment List of all passenger List of all flights List of passenger(date wise) List of passenger(flight wise)
27

2/5/2012

Next Steps
Modules Identification  Data type identification  Interface definition  Class identification  Identify design pattern  Interaction between object and database  Table structure  User Interface

2/5/2012 28

Q&A

Thank You!
2/5/2012 29