Airline Reservation System

SOFTWARE PROJECT MANAGEMENT PLAN
for
ONLINE AIRLINE TICKET

RESERVATION SYSTEM
Preface
The document contains the Software Project Management Plan of ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The mission of the project is to develop a web-
based reservation system for an airport.
The goal of the Software Project Management Plan is to define the technical and
managerial processes necessary to develop software work products that satisfy the
ONLINE AIRLINE TICKET RESERVATION SYSTEM requirements. This system is
prepared according to IEEE standard 1058-1998 [1]. The Software Project Management
Plan is in content compliance with the IEEE standard 1058-1998 in which the contents
of this standard are rearranged and a mapping is provided. That is, the content
compliant Software Project Management Plan is mapped into various clauses and
subclauses of the IEEE standard 1058-1998.
In addition to the IEEE standards, functions of project are discussed in section 1.1.3.
I
Table of Contents
Preface...............................................................................................................................I
Table of Contents.............................................................................................................II
List of Tables..................................................................................................................IV
List of Figures..................................................................................................................V
1 OVERVIEW (Clause 1 of the SPMP)............................................................................1
1.1 Project Summary (Subclause 1.1 of the SPMP)......................................................1
1.1.1 Purpose, Scope and Objectives (Subclause 1.1.1 of the SPMP)......................1
1.1.2 Assumptions And Constraints (Subclause 1.1.2 of the SPMP)........................2
1.1.3 Functions Of Project.........................................................................................3
1.1.4 Project deliverables (Subclause 1.1.3 of the SPMP)........................................3
1.1.5 Schedule and Budget Summary (Subclause 1.1.4 of the SPMP).....................4
1.2 Evolution of Plan (Subclause 1.2 of the SPMP)......................................................4
2 REFERENCES (Clause 2 of the SPMP)........................................................................5
3 DEFINITIONS & ABBREVIATIONS (Clause 3 of SPMP).........................................6
4 PROJECT ORGANIZATION (Clause 4 of SPMP).......................................................8
4.1 External Interfaces (Subclause 4.1 of SPMP).........................................................8
4.2 Internal Structure.....................................................................................................8
4.3 Roles and Responsibilities.......................................................................................9
5 MANAGERIAL PROCESS PLANS (Clause 5 of the SPMP)....................................11
5.1 Project Start-up Plan..............................................................................................11
5.1.1 Estimation Plan...............................................................................................11
5.1.2 Staffing Plan...................................................................................................23
5.1.3 Resources Acquisition Plan............................................................................23
5.1.4 Project Staff Training Plan.............................................................................24
5.2 Work Plan (Subclause 5.2 of the SPMP)...............................................................24
5.2.1 Work activities (Subclause 5.2.1 of the SPMP).............................................24
5.2.2 Schedule Allocation (Subclause 5.2.2 of the SPMP).....................................60
5.2.3 Resource Allocation (Subclause 5.2.3 of the SPMP).....................................69
5.2.4 Budget Allocation (Subclause 5.2.4 of the SPMP)........................................85
5.3 Control Plan (Subclause 5.3 of the SPMP)............................................................86
5.3.1 Requirements Control Plan (Subclause 5.3.1 of the SPMP)..........................86
5.3.2 Schedule Control Plan (Subclause 5.3.2 of the SPMP)..................................88
5.3.3 Budget Control Plan (Subclause 5.3.3 of the SPMP).....................................89
5.3.4 Quality Control Plan (Subclause 5.3.4 of the SPMP).....................................89
5.3.5 Reporting Plan (Subclause 5.3.5 of the SPMP)..............................................89
5.3.6 Metrics Collection Plan..................................................................................90
5.4 Risk Management Plan (Subclause 5.4 of the SPMP)...........................................91
5.5 Project Closeout Plan (Subclause 5.5 of the SPMP).............................................93
6 Technical Process Plan (Clause 6 of the SPMP)..........................................................95
6.1 Process Model (Subclause 6.1 of the SPMP)........................................................95
6.2 Methods, Tools and Techniques ...........................................................................96
6.3 Infrastructure Plan ................................................................................................96
II
6.4 Product Acceptance Plan.......................................................................................97
7 Supporting Process Plans .............................................................................................98
7.1 Configuration Management Plan...........................................................................98
7.2 Verification and Validation Plan ..........................................................................98
7.3 Documentation Plan..............................................................................................99
7.4 Quality Assurance Plan ........................................................................................99
7.5 Review Plan ........................................................................................................100
7.6 Problem Resolution Plan.....................................................................................100
III
List of Tables
Table 1: Schedule of the Project........................................................................................4

Table 2: Update Plan of the SPMP....................................................................................4
Table 3: Roles and Responsibilities of OnAir Members.................................................10
Table 4: Complexity Factors Used in Function Point Calculation..................................11
Table 5:Factors Used in Complexity Calculation............................................................12
Table 6: Details of the Function Point Calculation.........................................................19
Table 7 :Influence Factors of Online Airline Reservation System..................................20
Table 8: Effort and Time Division..................................................................................21
Table 9: Effort Schedule..................................................................................................22
Table 10: Labor Schedule................................................................................................22
Table 11: Cost Schedule..................................................................................................23
Table 12:Software Resources..........................................................................................23
Table 13: Hardware Resources........................................................................................24
Table 14 :Staff Training Plan..........................................................................................24
Table 15: Schedule of the ONLINE AIRLINE TICKET RESERVATION SYSTEM. .69
Table 16:Budget allocation table.....................................................................................86
Table 17: Reporting Mechanisms of the Online Airline Ticket Reservation System.....90
Table 18: Initially identified risk factors.........................................................................92
Table 19: Details of software process..............................................................................96
Table 20: Details of Infrastructure Plan..........................................................................97
Table 21: Details of Verification and Validation Plan...................................................99
IV
List of Figures
Figure 1: External Interfaces of the ONLINE AIRLINE TICKET RESERVATION

SYSTEM...........................................................................................................................8
Figure 2: The Internal Structure of the Project Developing Organization........................9
V
1 OVERVIEW (Clause 1 of the SPMP)
1.1 Project Summary (Subclause 1.1 of the SPMP)
1.1.1 Purpose, Scope and Objectives (Subclause 1.1.1 of the SPMP)
The purpose of the project is to develop a web-based reservation system for an airline. The
name of the project is ONLINE AIRLINE TICKET RESERVATION SYSTEM and this is
also the name of the final product to be delivered.
The objectives of the ONLINE AIRLINE TICKET RESERVATION SYSTEM are:
The primary goal of this project is to help the passengers make flight reservation. The system
will be able to find all the flights fulfilling a passenger’s needs. It is also capable to search all
flights with a given origin and destination. The system displayed the arrival and departure
times, the price, and the flight number for each flight it finds. Then, the passenger will decide
the flight reservation based on the displayed information.
The secondary goal is to provide a means for the airline manager to manage the flights. The
airline manager will be able to schedule new flights, drop flights from the schedule and
change the fare for a flight. Manager will also have clearer and better view about the flight
schedule. The manager can decide to add flights if there are high demand of reservation at a
certain time (e.g.: festive season).
To reserve a flight seat, the web site helps passenger seek for flights according to the
passenger’s desire location, departure time and arrival time. After the flight confirmation is
done, ticketing staff will ask for passenger information to make the flight reservation.
• Add/Delete Airline Manager Information

• Add/ Delete Ticketing Staff Information
• Add/ Delete Flight Information
1
• Add/Delete Passenger Information
• Make Reservation
• View/Query/Cancel Reservation
• View/Query on Flight Information
• View/Query on Passenger Information
• View/Query on Airline Manager Information
• View/Query on Ticketing Staff Information
• Report on Flight, Passenger, Airline Manager and Ticketing Staff
Online Airline Ticket Reservation System project is aimed to make a website for the Airline
customers.
This document presents the detailed software requirements analysis for the Online Airline
Ticket Reservation System. The scope includes the functional, performance and operational
requirements of the Online Airline Ticket Reservation System.
The software requirements analysis is based on the Online Airline Ticket Reservation System
Initial Plan [9]
1.1.2 Assumptions And Constraints (Subclause 1.1.2 of the SPMP)
The assumptions of the project are;
• The staff of the project is consisting of four (4) people and each person will work twenty
(20) hours a week.
• The programming language Java, PHP, XHTML is decided for the project. However,
according to the customer’s demand it can be changed.
The constraints of the project are;
• The schedule of the project is predefined by the customer.

• Since it is possible to have users from all over the world, the ONLINE AIRLINE TICKET
RESERVATION SYSTEM will be web-based, platform independent.
2
• Since the project is being developed as part of the graduate course Software eng, there
will be no real payment to OnAir by CTIS.
• The software development processes and any kind of documentation will be in
compliance with the IEEE Standards [1, 2, 3, 4].
1.1.3 Functions Of Project
According to initial meetings done with customers the users of the ONLINE AIRLINE
TICKET RESERVATION SYSTEM consists of system groups. These are users and
administrator (this will be referred as root from now on).
* The functions of root;
• define users on the ONLINE AIRLINE TICKET RESERVATION SYSTEM
- assign each user a unique user-id
- assign each user a password
* The functions of administrator;
• use the user control function
* The functions of customer;
• use the reservation function
1.1.4 Project deliverables (Subclause 1.1.3 of the SPMP)
• Initial Plan: The document will be prepared and submitted to

[email protected] e-mail address until October 17th, 2006.
• SRS: The document will be prepared and submitted to [email protected] e-
mail address until November 17th, 2006.
• SPMP: The document will be prepared and submitted to [email protected]
address until November 30th, 2006
• SDD: The document will be prepared and submitted to [email protected]
e-mail address until December 20th, 2006.
• Delivery of Product: The product will be delivered on May 20th, 2002.
• User Manual: The document will be prepared on June 9th, 2002.
3
• Demonstration of Product: The demonstration of the product will be done on May
30th, 2002.
• Delivery of Final Product: The final product will include the software, the
software source codes and the user manuals. The delivery will be on June 9th, 2002.
1.1.5 Schedule and Budget Summary (Subclause 1.1.4 of the SPMP)
Due Date Document / Activity Name

17 October 2006 Initial Plan
17 November 2006 SRS
30 November 2006 SPMP
20 December 2006 SDD
Table 1: Schedule of the Project
As explained in subclause 1.1.2, no real budget is associated with ONLINE AIRLINE

TICKET RESERVATION SYSTEM. For hardware and software needs existing resources of
OnAir will be used.
1.2 Evolution of Plan (Subclause 1.2 of the SPMP)
This is the initial version of the Software Project Management Plan.
Due Date Document Status
17 October 2006 Initial Plan Created

17 November 2006 SRS Created
30 November 2006 SPMP Created
Table 2: Update Plan of the SPMP
4
2 REFERENCES (Clause 2 of the SPMP)
[1] IEEE Std 1058-1998, IEEE Standard for Software Management Plans
[2] IEEE Std 830-1998. IEEE Recommended Practice for Software Requirements
Specifications
[3] IEEE Std 1016-1998, IEEE Recommended Practice for Software design Descriptions
[4] IEEE Std 1063-1987, IEEE Standard for Software User Documentation
[5] Sommerville, Ian, Software Engineering, Sixth Edition, Pearson Education, 2001.
[6] Pressman, Roger S., Software Engineering “A practitioner’s Approach”, Fifth Edition,
McGraw-Hill, 2000.
[7] Laudon Kenneth C. and Laudon Jane P., Management Information Systems “New
Approaches to Organization & Technology”, Fifth Edition, Prentice Hall, 1998.
[8] IRWIN, Stephan R., Software Engineering, First Edition, Aksen Associates, 1990.
[9] ONLINE AIRLINE TICKET RESERVATION SYSTEM Initial Plan, version 1.1, 17
October 2006.
[10] ONLINE AIRLINE TICKET RESERVATION SYSTEM Software Requirements
Specification, version 1.0, 17 November 2006
5
3 DEFINITIONS & ABBREVIATIONS (Clause 3 of SPMP)
CTIS: Computer Technology and Information System
IEEE: Institute of Electrics & Electronics Engineering
OnAir: will be referred to software development team
PC: Personal Computer
SRS: Software Requirements Specification
Acquirer: specifies requirements for and accepts delivery of a new or modified software
product and its documentation. In this project acquirers refer to Duygu Albayrak.
Admin: the administrator is a person who has privileges to control server as well as
responsibilities to manage the running system.
Member: the user who is signed up before.
Project Deliverable: A work product to be delivered to the acquirer. Quantities, delivery
dates, and delivery locations are specifying in a project agreement. [1]
User: refers to people who will see the routes.
User id: A set of characters that identifies the user.
The Acquiring Organization: is the organization that will receive the final product.
The Quality Control Manager: is responsible from controlling the product whether it satisfies
the customer’s demand and provide consultancy in this area. In this project quality control
manager refers to Beyhan Akporay.
Work Product: Any tangible item produced during the process of developing or modifying
software.
Sign-up: refers to recording user information to the system at first time to have a chance to
use the system
6
Software Project: is the set of work activities both technical and managerial required to
satisfy the terms and conditions of a project agreement
Contract: A legally binding document agreed upon by the customer and the supplier. This
includes the technical and organizational requirements, and schedule for a product. A contract
may also contain informal but useful information such as the commitment or expectations of
the parties involved. [1]
Customer: The person or persons who pay for the product and usually (but not necessarily)
decide the requirements. In the context of this recommended practice the customer and the
supplier may be members of same organization. [1]
User: refers to people who will utilize from the Online Airline Ticket Reservation System.
User Interface: The interface that the users will see while using Online Airline Ticket
Reservation System.
Project Deliverable: A work product to be delivered to the acquirer. Quantities, delivery
dates, and delivery locations are specifying in a project agreement. [1]
SPMP: Software project management plan. The controlling document for managing the
software project.
WBS #: Work Break Down Structure number.
7
4 PROJECT ORGANIZATION (Clause 4 of SPMP)
4.1 External Interfaces (Subclause 4.1 of SPMP)

Figure 1 indicates the external interfaces of the ONLINE AIRLINE TICKET
RESERVATION SYSTEM.
Bilkent University
The Acquiring
OnAir
Project Developing
CTIS
Quality Control Manager
Figure 1: External Interfaces of the ONLINE AIRLINE TICKET RESERVATION SYSTEM
List of Responsible People to Contact:
Bilkent University (The Acquiring Organization): CTIS Department
The Quality Control Manager: CTIS Instructor (Beyhan Akporay)
4.2 Internal Structure
The project responsibilities and authority line are separated among OnAir. Thus, the project is
a matrix organization. The internal structure of the project is given in Figure 2.
Board of Directors
Project Management Customer Relations Training

Department Department Department
Requirements Design Coding Testing Documentation

Analysis Team Team Team Team Team
8
Figure 2: The Internal Structure of the Project Developing Organization
You should have a project manager responsible from your project. This organization may be
used by other projects. But, this your project, and it must be your organization.
How are these organizational unit interact with each other?
4.3 Roles and Responsibilities
External Entities:
Acquiring Organization: It is the person who defines the requirements for the project both
approves and accepts the product deliverables and the final product.
Quality Control Manager: It is the person who carries out the quality assurance of the project.
Therefore, manager is responsible from the preparation of review reports for the project
documentation.
Internal Entities:
Name E-mail address Roles

Gürhan Yankı [email protected] Group member
Head of coding team
Configuration Manager
Programmer
Merve Bayraktar [email protected] Group member
Requirements engineer
Head of training team
Test engineer
Özge Koray [email protected] Project manager
Head of design team
Customer relations representative
Programmer
Tuğçe Pakarar [email protected] Group member
9
Customer relations representative
Head of documentation team
Member of documentation team
Test engineer
Table 3: Roles and Responsibilities of OnAir Members
Board of Directors: is responsible from setting corporate strategy, overall direction, mission
and vision.
Training Department: is responsible from planning and giving / outsourcing the necessary
training for the company personnel at all levels.
Customer Relations Department: is responsible from managing the high-end relations with
the customers.
Project Management Department:
Requirements Analysis Team: is responsible for collecting and documenting the system
requirements as a whole.
Design Team: is responsible from planning how the required system functionality is to be
provided.
Coding Team: is responsible from realizing the products designed.
Testing Team: is responsible from verifying that the developed system represents the
requirements in a complete and correct manner.
Documentation Team: is responsible from preparing the system documentations intended for
different audiences.
10
5 MANAGERIAL PROCESS PLANS (Clause 5 of the SPMP)
5.1 Project Start-up Plan
5.1.1 Estimation Plan
In this part of the Initial Plan, the cost and schedule for conducting the project as well as
methods, tools and techniques used to estimate project cost, schedule and resource
requirements are specified.
Since it is a convenient method to use in the early phases of project development, the size of
the Online Airline Reservation System is estimated according to the function-point (FP)
method [8]. In counting function points, external inputs, external outputs, external enquiries,
internal files and external interfaces of the software are identified. Each instance for each
separate class is multiplied with the associated weight factor. The overall sum is calculated to
find the function points. Weights for simple, average and complex inputs, outputs, enquires,
files and external interfaces, which are used in calculations, are depicted below:
Simple Average Complex

External input 3 4 6
External output 4 5 7
External enquiry 3 4 6
Internal file 7 10 15
External interface 5 7 10
Table 4: Complexity Factors Used in Function Point Calculation
In order to systematically find complexity levels, references to file accesses, record type
accesses and data elements are counted and complexity scores are determined accordingly.
The table below depicts the factors used for complexity calculation. For example, an external
input that reference four files and nine data types (3 + 2) is considered ‘complex’. (2 - 3
simple -denoted by the letter ‘S’, 4 average -denoted by the letter ‘A’, 5- 6 complex -denoted
by the letter ‘C’)
11
Function Determinants
files # record types # data elements
1 2 3 1 2 3 1 2 3
Input 0-1 2 3+ 1-4 5-15 16+
Output 0-1 2-3 4+ 1-5 6-19 20+
Int. File 1 2-5 6+ 1-19 20-50 51+
Interface 1 2-5 6+ 1-19 20-50 51+
Enquiry Use the greater of the input and output components
Table 5:Factors Used in Complexity Calculation
Files Rec. Data Elements Comp. Score

Types
EXTERNAL INPUTS
Define new user User - Userid S 3
authentication file Password
User information Name of the
file employee
Name of the
customer
Delete an existing user User - Userid S 3
authentication file
User information
file
Update an existing user User - Userid S 3
authentication file
User information
file
Define new seat Seat - Seatid S 3
authentication file Properties of the seat
User information
file
Delete an existing seat Seat - Seatid S 3
authentication file
User information
file
Update an existing seat Seat - Seatid S 3
authentication file
User information
file
Define new class Class - Classid S 3
authentication file Properties of the class
User information
file
12
Delete an existing class Class - Classid S 3
authentication file
User information
file
Update an existing class Class - Classid S 3
authentication file
User information
file
Authenticate user during User - Userid S 3
login authentication file Password
Define new plane Plane - Planeid S 3
authentication file Properties of the
User information plane
file
Delete an existing plane Plane - Planeid S 3
authentication file
User information
file
Update an existing plane Plane - Planeid S 3
authentication file
User information
file
Define new flight Flight - Flightid S 3
User information flight
file
Delete an existing flight Flight - Flightid S 3
authentication file
User information
file
Update an existing flight Flight - Flightid S 3
authentication file
User information
file
Define new gates Gates - Gatesid S 3
User information gates
file
Delete an existing gates Gates - Gatesid S 3
authentication file
User information
file
Update an existing gates Gates - Gatesid S 3
authentication file
User information
file
Define new airport Airport - Airportid S 3
User information airport
13
file
Delete an existing airport Airport - Airportid S 3
authentication file
User information
file
Update an existing airport Airport - Airportid S 3
authentication file
User information
file
Define new city City - Cityid S 3
authentication file Properties of the city
User information
file
Delete an existing city City - Cityid S 3
authentication file
User information
file
Update an existing city City - Cityid S 3
authentication file
User information
file
Define new country Country - Countryid S 3
User information country
file
Delete an existing Country - Countryid S 3
country authentication file
User information
file
Update an existing Country - Countryid S 3
country authentication file
User information
file
Define new bank Bank - Bankid S 3
authentication file Properties of the bank
User information
file
Delete an existing bank Bank - Bankid S 3
authentication file
User information
file
Update an existing bank Bank - Bankid S 3
authentication file
User information
file
Define new ticket Ticket - Ticketid S 3
User information ticket
file
14
Delete an existing ticket Ticket - Ticketid S 3
authentication file
User information
file
Update an existing ticket Ticket - Ticketid S 3
authentication file
User information
file
Define new reservation Reservation - Reservationid S 3
User information reservation
file
Delete an existing Reservation - Reservationid S 3
reservation authentication file
User information
file
Update an existing Reservation - Reservationid S 3
reservation authentication file
User information
file
Define new service Service - Serviceid S 3
User information service
file
Delete an existing service Service - Serviceid S 3
authentication file
User information
file
Update an existing service Service - Serviceid S 3
authentication file
User information
file
EXTERNAL OUTPUTS
Login successful message None - Message text S 4
Login failed message None - Message text S 4
Successful user addition None - Message text S 4

message
Failed user deletion None - Message text S 4
message
Successful seat addition None - Message text S 4
message
Failed seat deletion None - Message text S 4
message
Successful class addition None - Message text S 4
message
Failed class deletion None - Message text S 4
message
15
Successful plane addition None - Message text S 4
message
Failed plane deletion None - Message text S 4
message
Successful flight addition None - Message text S 4
message
Failed flight deletion None - Message text S 4
message
Successful gate addition None - Message text S 4
message
Failed gate deletion None - Message text S 4
message
Successful airport addition None - Message text S 4
message
Failed airport addition None - Message text S 4
message
Successful city addition None - Message text S 4
message
Failed city addition None - Message text S 4
message
Successful country None - Message text S 4
addition message
Failed country addition None - Message text S 4
message
Successful bank addition None - Message text S 4
message
Failed bank addition None - Message text S 4
message
Successful ticket addition None - Message text S 4
message
Failed ticket addition None - Message text S 4
message
Successful reservation None - Message text S 4
addition message
Failed reservation addition None - Message text S 4
message
Successful service None - Message text S 4
addition message
Failed service addition None - Message text S 4
message
Successful user deletion None - Message text S 4
message
Failed user deletion None - Message text S 4
message
Successful seat deletion None - Message text S 4
message
Failed seat deletion None - Message text S 4
message
16
Successful class deletion None - Message text S 4
message
Failed class deletion None - Message text S 4
message
Successful plane deletion None - Message text S 4
message
Failed plane deletion None - Message text S 4
message
Successful flight deletion None - Message text S 4
message
Failed flight deletion None - Message text S 4
message
Successful gate deletion None - Message text S 4
message
Failed gate deletion None - Message text S 4
message
Successful airport deletion None - Message text S 4
message
Failed airport deletion None - Message text S 4
message
Successful city deletion None - Message text S 4
message
Failed city deletion None - Message text S 4
message
Successful country None - Message text S 4
deletion message
Failed country deletion None - Message text S 4
message
Successful bank deletion None - Message text S 4
message
Failed bank deletion None - Message text S 4
message
Successful ticket deletion None - Message text S 4
message
Failed ticket deletion None - Message text S 4
message
Successful reservation None - Message text S 4
deletion message
Failed reservation deletion None - Message text S 4
message
Successful service None - Message text S 4
deletion message
Failed service deletion None - Message text S 4
message
INTERNAL FILES
User authentication file - None Userid S 7
Password
17
User information file - None Userid S 7
Seat authentication file - None Seatid S 7
Seat information file - None Seatid S 7
Class authentication file - None Classid S 7
Class information file - None Classid S 7
Flight authentication file - None Flightid S 7
Flight information file - None Flightid S 7
Gate authentication file - None Gateid S 7
Gate information file - None Gateid S 7
Airport authentication file - None Airportid S 7
Airport information file - None Airportid S 7
City authentication file - None Cityid S 7
City information file - None Cityid S 7
Country authentication - None Countryid S 7

file
Country information file - None Countryid S 7
Bank authentication file - None Bankid S 7
Bank information file - None Bankid S 7
Ticket authentication file - None Ticketid S 7
Ticket information file - None Ticketid S 7
Reservation authentication - None Reservationid S 7

file
Reservation information - None Reservationid S 7
file
Service authentication file - None Serviceid S 7
Service information file - None Serviceid S 7
EXTERNAL ENQUIRIES
18
None - - - - -
EXTERNAL INTERFACES
None - - - - -
TOTAL UNADJUSTED FUNCTION POINTS 470
Table 6: Details of the Function Point Calculation
Influence Factors Degree of Comment

Influence-DI
Data Communication 5 Distributed environment
Distributed Functions 1 Client-server architecture
Performance Objective 5 Online response time is critical
Heavily Used Configuration 5 Maximum system load is average
Transaction Rate 3 Transaction rate is average
On-line Data Entry 5 All of the transactions are online
End-User efficiency 5 Ease of use is critical
On-line Update 0 No special requirements
Complex Processing 4 Only security issues
Reusability 0 No special requirements
Installation Ease 0 No special requirements
Operational Ease 3 Short start-up time for client
19
Multiple Site 5 Must operate platform independently
Facilitate Change 0 No special requirements
Sum of Degree of Influence = 41
Table 7 :Influence Factors of Online Airline Reservation System
Size Estimation:
Total Degree of Influence (TDI) = Sum of Degree of Influence (DI) = 41

Value Adjustment Factor (VAF) = 0.65 + (0.01 * TDI) = 0.65 + (0.01 * 41) = 1.06
Function Point (FP) = VAF * Unadjusted Function Point (UFP) = 1.06 * 470 = 498.2
FP Conversion Factors (Conversion Factor for Line of Code) = 20 (The approximate value for
the object-oriented languages) [8].
LOC = Function Point * FP Conversion Factors = 498.2 * 20 = 9964
Size = 9.964 KLOC
Effort Estimation: Since the COCOMO model is a widely used technique, which can be used
for small, medium and large-scale projects and since it can be incorporated into different
application domains, the COCOMO model is used [8]. The Online Airline Reservation
System is fairly small project. The selected mode of difficulty for COCOMO is organic.
Therefore, the appropriate constraints for COCOMO model are a = 2.4 and b = 1.05.
Effort = a * Size b ⇒ 2.4 * 9.964 1.05 = 37.894 ≅ 37.8 person months.

Schedule Estimation:
The total time for the Online Airline Reservation System needed is
Total Time = a * Effort b ⇒ 2.5 * 37.8 0.38 = 9.9 months.
The COCOMO model assumes 19 working days/month and 8 working hours/day. That is 152
working hours/month. On the other hand, for OnAir there are 80 working days/month and an
average of 4 working hours/day. That is 320 working hours/month.
According to the COCOMO model the required effort for the project is 11.5 person months.
However for OnAir, this represents 9.9 * (152/320) = 4.7 person months.
20
Since, there are 3 months available to complete the project, an average of 4.7/3 = 1.5 ≅ 2
people is needed.
COCOMO divides effort and time as follows [8];
17% Requirements Analysis

25% Design
25% Coding and Unit Testing
33% Integration and Testing
If it is adapted to Airline Reservation System the following table occurs;
Phase Month-1 Month-2 Month-3 TOTAL

Requirements
75% 25% 0% 100%
Analysis
Design 25% 50% 25% 100%
Coding & Unit
0% 50% 50% 100%
Testing
Integration &
0% 25% 75% 100%
Testing
Table 8: Effort and Time Division
According to this the effort schedule can be shown as following;
Effort Month-1 Month-2 Month-3

Phase
(staff * months) (staff * months) (staff * months) (staff * months)
Requirements
0.17 * 4.7 = 0.8 0.8 * 0.75 = 0.6 0.8 * 0.25 = 0.2 0.8 * 0 = 0
Analysis (17%)
1.18 * 0.50 = 1.18 * 0 25 =
Design (25%) 0.25 * 4.7 = 1.18 1.18 * 0 25 = 0.29
0.58 0.29
Coding & Unit 1.18 * 0.50 = 1.18 * 0 25 =
0.25 * 4.7 = 1.18 1.18 * 0 25 = 0.29
Testing (25%) 0.58 0.29
Integration & 1.55 * 0.25 = 1.55 * 0.75 =
0.33 * 4.7 = 1.55 1.55* 0 = 0
Testing (33%) 0.38 1.16
TOTAL EFFORT 4.71 1.17 1.77 1.77
21
(staff * months)
Table 9: Effort Schedule

Assumption: The labor category for all employees of the OnAir is the same.
According to the effort schedule the labor schedule can be shown as following;
Labor
% Effort Month-1 Month-2 Month-3
Category
Normal 100% 1.17 1.77 1.77
Table 10: Labor Schedule
Assumptions:
• Since the labor category for all the members of OnAir is the same, their payment rates
are the same and $5000/month.
• The payment rate for each member of CTIS is $10/hour.
• Each member of CTIS works 4 hours/week (4hours/week * 4 weeks/month * 4 people
= 64 staff*hours/month)
• As details are given in sub clause 5.1.3, no cost will be paid for transportation,
training, and hardware and software requirements.
• The cost of the electricity consumed by OnAir is assumed to be $30/month according
to the historical data.
According to the labor schedule and the assumptions above cost schedule can be shown as
following;
Month-1 Month-2 Month-3 TOTAL

1.17 * 5000 = 1.77 * 5000 = 1.77 * 5000 =
Cost of the staff ($) 23550
5850 8850 8850
Cost of the
subcontracted 64 * 10 = 640 64 * 10 = 640 64 * 10 = 640 1920
processes ($)
Cost of the
electricity 30 30 30 90
consumed ($)
22
TOTAL COST ($) 6520 9520 9520 25560
Table 11: Cost Schedule
Since, the requirements can change the re-estimation of size, effort, cost and the schedules
will be done after the SRS document is produced by the same methods used.
5.1.2 Staffing Plan
OnAir has four members; all of them will work in every phase of the project. The Staffing
plan is defined by project phase in Appendix A.
5.1.3 Resources Acquisition Plan
• Since both project members and acquirers are studying now in Bilkent University,
there will be no transportation cost for meetings.
• Group members need training. Some of training will be provided from library.
Therefore, there is no need payment for training.
• For any kind of hardware and software needs the existing resources of OnAir will be
used.
Software Java2 Standard Edition v.1.3.1_02 from Sun Microsystems

Apache Web Server v.1.3.23
Microsoft Internet Explorer v.5.5
Netscape Navigator v.4.79
Microsoft Word 2003
Microsoft Project 2003
Table 12:Software Resources
HARDWARE NAME QUANTITY VERSION # SOURCE

LAPTOP LAPTOP 3 Pentium Processor Self Acquisition
23
PC PC 1 Pentium Processor Self Acquisition
Table 13: Hardware Resources
5.1.4 Project Staff Training Plan
Subject Start End Trainer Method

Standards 11. 10. 2006 17. 10. 2006 Merve Bayraktar Self Study
Java 05. 01. 2007 27. 02. 2007 Gürhan Yankı Self Study
Flash Mx 10. 01. 2007 1. 03. 2007 Tuğçe Pakakar Self Study
HTML 01. 03. 2007 10. 03. 2007 Özge Koray Self Study
Testing 01. 04. 2007 20. 05. 2007 Gürhan Yankı Self Study
Table 14 :Staff Training Plan
5.2 Work Plan (Subclause 5.2 of the SPMP)
5.2.1 Work activities (Subclause 5.2.1 of the SPMP)
The ONLINE AIRLINE TICKET RESERVATION SYSTEM work breakdown structures:
Name Stating the problem statement

WBS # 1
Estimated duration 6 days
Predecessor activity -
Successor activity 3
Description Clarifing the problem statement of the ONLINE AIRLINE
TICKET RESERVATION SYSTEM and at the end to bring
out a report about it
Name Training for IEEE Std. 1058-1998

WBS # 2
Estimated duration 1 day
Description Giving training to Özge Koray & Gürhan YANKI by lectures
and discussions to make a background about IEEE Std. 1058-
1998 [1].
Name Preparation of the Initial Plan
24
WBS # 3
Predecessor activity 1, 2
Description Describing the overall picture of the ONLINE AIRLINE
TICKET RESERVATION SYSTEM and at the end to bring
out a report about it.

WBS # 4
1998 [2].
Name Preparation of the SRS

WBS # 5
Description Presenting the detailed software requirements analysis for the
ONLINE AIRLINE TICKET RESERVATION SYSTEM and
at the end to bring out a report about it.
Name Review meeting for the changes of software requirements

with the customer
WBS # 6
Predecessor activity 5
Description Reviewing the software requirements of the ONLINE
AIRLINE TICKET RESERVATION SYSTEM to determine
that if there is anything that the customer wants to add.

WBS # 7
1998 [1].
Name Preparation of the SPMP

WBS # 8
25
Successor activity -
Description Symbolizing all of the SPMP processes that lies below this
work activity.
Name Preparation of managerial process plans

WBS # 8.1
Successor activity 15, 18
Description Symbolizing all of the managerial process plans that lies
below this work activity.
Name Work plan

WBS # 8.1.1
Description Specifing the work activities, schedule, resources and budget
details for the ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Control plan

WBS # 8.1.2
Description Specifing the reporting mechanisms and control procedures
necessary to measure report and control the ONLINE
AIRLINE TICKET RESERVATION SYSTEM requirements,
schedule, budget and recourses, the quality of work processes
and work products.
Name Risk management plan

WBS # 8.1.3
Description Specifing the risk management plan of ONLINE AIRLINE
TICKET RESERVATION SYSTEM for identifying and
analyzing ONLINE AIRLINE TICKET RESERVATION
SYSTEM risk factors.
Name Project closeout plan

WBS # 8.1.4
Description Containing the plans necessary to ensure orderly closeout of
the ONLINE AIRLINE TICKET RESERVATION SYSTEM.
26
Name Control of the project schedule
WBS # 8.2
Estimated duration 0.5 day
Description Comparing actual progress to planned progress and to
implement corrective action when actual progress does not
conform to planned progress.
Name Control of the budget requirements

WBS # 8.3
Description Comparing the planned cost to budgeted cost and implement
corrective action when actual cost does not conform to
budgeted cost.
Name Review of the project risk factors

WBS # 8.4
Description Specifying ,analyzing and identifying the ONLINE AIRLINE
TICKET RESERVATION SYSTEM risk factors
Name Review meeting for the content of the SPMP with the
customer
WBS # 8.5
Description Reviewing the SPMP’s content to determine that if there is
anything that the customer wants to add.
Name Preparation of technical process plans

WBS # 8.6
Description Specifing the development process model, technical methods,
tools and techniques.
Name Preparation of supporting process plans

WBS # 8.7
27
Description Containing plans for supporting processes that span the
duration of ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Control of the quality of the SPMP

WBS # 8.8
Description Comparing the actual quality level to the planned quality level
and implement corrective action when actual quality level
does not conform to planned quality level.
Name Writing of the SPMP documentation

WBS # 8.9
Description Documenting the activities that have been done for SPMP of
Name Review meeting for SPMP documentation

WBS # 8.10
Description Reviewing the SPMP documentation of the ONLINE
AIRLINE TICKET RESERVATION SYSTEM by Özge
Koray to determine quality of the SPMP documentation using
IEEE std. 1058-1998 [1].
Name Update of the SPMP documantation

WBS # 8.11
Description Updating the SPMP documentation to do the necessary
changes about the SPMP that is determined either at the
Review meeting for the content of the SPMP with the
customer or Review meeting for SPMP documentation with
Özge Koray.

WBS # 9
28
1998 [3].

with the customer
WBS # 10
Name Preparation of the SDD

WBS # 11
Description Symbolizing all of the SDD processes that lies below this
work activity.
Name Design of the ONLINE AIRLINE TICKET RESERVATION

SYSTEM
WBS # 11.1
Description Symbolizing all of the design processes that lies below this
work activity.
Name Design of the communication protocol between client &

server software
WBS # 11.1.1
Description Establishing a design for the communication protocol between
the client software and server software to construct the
communication protocol.
Name Design of the user and room information files

WBS # 11.1.2
Description Establishing a design for the user and room information files
to state how many fields they have, how these fields are used
and when these fields are needed.
29
Name Design of the server software
WBS # 11.1.3
Description Symbolizing all of the design processes for server software
that lies below this work activity.
Name Design of the common functions of all users

WBS # 11.1.3.1
Description Symbolizing the design process for all users that lies below
this work activity.
Name Design of the user authentication function for server software

WBS # 11.1.3.1.1
Description Establishing a design for the user authentication function of
server software. All users should use this function to enter the
ONLINE AIRLINE TICKET RESERVATION SYSTEM.
Therefore, security issue is a part of the user authentication
function. This function is also used to define the user
information to the system. The user information file is used.
Name Design of the functions for root

WBS # 11.1.3.2
Description Symbolizing all of the design processes for root that lies
Name Design of the user addition function for server software

WBS # 11.1.3.2.1
Description Establishing a design for the user addition function of server
software. Only the root can use this function if she/he chooses
the user addition function, after the user authentication, to add
a user to the ONLINE AIRLINE TICKET RESERVATION
SYSTEM. The user information file is used.
Name Design of the user deletion function for server software

WBS # 11.1.3.2.2
30
Description Establishing a design for the user deletion function of server
the user deletion function after the user authentication to
delete an existing user from the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The user information file is used.
Name Design of the user update function for server software

WBS # 11.1.3.2.3
Description Establishing a design for the user update function of server
the user update function after the user authentication to
change information (except the User_id) of an existing user of
Name Design of the seat addition function for server software

WBS # 11.1.3.3.1
Description Establishing a design for the seat addition function of server
the seat addition function, after the seat authentication, to add
a seat to the ONLINE AIRLINE TICKET RESERVATION
SYSTEM. The seat information file is used.
Name Design of the seat deletion function for server software

WBS # 11.1.3.3.2
Description Establishing a design for the seat deletion function of server
the seat deletion function after the seat authentication to delete
an existing seat from the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The seat information file is used.
Name Design of the seat update function for server software

WBS # 11.1.3.3.3
Description Establishing a design for the seat update function of server
31
the seat update function after the seat authentication to change
information (except the Seat_id) of an existing seat of the
Name Design of the class addition function for server software

WBS # 11.1.3.4.1
Description Establishing a design for the class addition function of server
the class addition function, after the class authentication, to
add a class to the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The class information file is
used.
Name Design of the class deletion function for server software

WBS # 11.1.3.4.2
Description Establishing a design for the class deletion function of server
the class deletion function after the class authentication to
delete an existing class from the ONLINE AIRLINE TICKET
used.
Name Design of the class update function for server software

WBS # 11.1.3.4.3
Description Establishing a design for the class update function of server
the class update function after the class authentication to
change information (except the Class_id) of an existing class
of the ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Design of the plane addition function for server software

WBS # 11.1.3.5.1
Description Establishing a design for the plane addition function of server
the plane addition function, after the plane authentication, to
add a plane to the ONLINE AIRLINE TICKET
32
RESERVATION SYSTEM. The plane information file is
used.
Name Design of the plane deletion function for server software

WBS # 11.1.3.5.2
Description Establishing a design for the plane deletion function of server
the plane deletion function after the plane authentication to
delete an existing plane from the ONLINE AIRLINE TICKET
used.
Name Design of the plane update function for server software

WBS # 11.1.3.5.3
Description Establishing a design for the plane update function of server
the plane update function after the plane authentication to
change information (except the Plane_id) of an existing plane
SYSTEM.
Name Design of the flight addition function for server software

WBS # 11.1.3.6.1
Description Establishing a design for the flight addition function of server
the flight addition function, after the flight authentication, to
add a flight to the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The flight information file is
used.
Name Design of the flight deletion function for server software

WBS # 11.1.3.6.2
Description Establishing a design for the flight deletion function of server
the flight deletion function after the flight authentication to
delete an existing flight from the ONLINE AIRLINE TICKET
33
used.
Name Design of the flight update function for server software

WBS # 11.1.3.6.3
Description Establishing a design for the flight update function of server
the flight update function after the flight authentication to
change information (except the Flight_id) of an existing flight
SYSTEM.
Name Design of the gates addition function for server software

WBS # 11.1.3.7.1
Description Establishing a design for the gates addition function of server
the gates addition function, after the gates authentication, to
add a gates to the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The gates information file is
used.
Name Design of the gates deletion function for server software

WBS # 11.1.3.7.2
Description Establishing a design for the gates deletion function of server
the gates deletion function after the gates authentication to
delete an existing gates from the ONLINE AIRLINE TICKET
used.
Name Design of the gates update function for server software

WBS # 11.1.3.7.3
Description Establishing a design for the gates update function of server
the gates update function after the gates authentication to
change information (except the Gates_id) of an existing gates
SYSTEM.
34
Name Design of the airport addition function for server software
WBS # 11.1.3.8.1
Description Establishing a design for the airport addition function of
server software. Only the root can use this function if she/he
chooses the airport addition function, after the airport
authentication, to add a airport to the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The airport information
file is used.
Name Design of the airport deletion function for server software

WBS # 11.1.3.8.2
Description Establishing a design for the airport deletion function of
chooses the airport deletion function after the airport
authentication to delete an existing airport from the ONLINE
AIRLINE TICKET RESERVATION SYSTEM. The airport
information file is used.
Name Design of the airport update function for server software

WBS # 11.1.3.8.3
Description Establishing a design for the airport update function of server
the airport update function after the airport authentication to
change information (except the Airport_id) of an existing
airport of the ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Design of the city addition function for server software

WBS # 11.1.3.9.1
Description Establishing a design for the city addition function of server
the city addition function, after the city authentication, to add
a city to the ONLINE AIRLINE TICKET RESERVATION
SYSTEM. The city information file is used.
Name Design of the city deletion function for server software
35
WBS # 11.1.3.9.2
Description Establishing a design for the city deletion function of server
the city deletion function after the city authentication to delete
an existing city from the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The city information file is used.
Name Design of the city update function for server software

WBS # 11.1.3.9.3
Description Establishing a design for the city update function of server
the city update function after the city authentication to change
information (except the City_id) of an existing city of the
Name Design of the country addition function for server software

WBS # 11.1.3.10.1
Description Establishing a design for the country addition function of
chooses the country addition function, after the country
authentication, to add a country to the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The country
Name Design of the country deletion function for server software

WBS # 11.1.3.10.2
Description Establishing a design for the country deletion function of
chooses the country deletion function after the country
authentication to delete an existing country from the ONLINE
AIRLINE TICKET RESERVATION SYSTEM. The country
Name Design of the country update function for server software

WBS # 11.1.3.10.3
36
Description Establishing a design for the country update function of server
the country update function after the country authentication to
change information (except the Country_id) of an existing
country of the ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Design of the bank addition function for server software

WBS # 11.1.3.11.1
Description Establishing a design for the bank addition function of server
the bank addition function, after the bank authentication, to
add a bank to the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The bank information file is
used.
Name Design of the bank deletion function for server software

WBS # 11.1.3.11.2
Description Establishing a design for the bank deletion function of server
the bank deletion function after the bank authentication to
delete an existing bank from the ONLINE AIRLINE TICKET
used.
Name Design of the bank update function for server software

WBS # 11.1.3.11.3
Description Establishing a design for the bank update function of server
the bank update function after the bank authentication to
change information (except the Bank_id) of an existing bank
SYSTEM.
Name Design of the ticket addition function for server software

WBS # 11.1.3.12.1
37
Description Establishing a design for the ticket addition function of server
the ticket addition function, after the ticket authentication, to
add a ticket to the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The ticket information file is
used.
Name Design of the ticket deletion function for server software

WBS # 11.1.3.12.2
Description Establishing a design for the ticket deletion function of server
the ticket deletion function after the ticket authentication to
delete an existing ticket from the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The ticket information
file is used.
Name Design of the ticket update function for server software

WBS # 11.1.3.12.3
Description Establishing a design for the ticket update function of server
the ticket update function after the ticket authentication to
change information (except the Ticket_id) of an existing ticket
SYSTEM.
Name Design of the reservation addition function for server software

WBS # 11.1.3.13.1
Description Establishing a design for the reservation addition function of
chooses the reservation addition function, after the reservation
authentication, to add a reservation to the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The reservation
Name Design of the reservation deletion function for server software

WBS # 11.1.3.13.2
Description Establishing a design for the reservation deletion function of
38
chooses the reservation deletion function after the reservation
authentication to delete an existing reservation from the
The reservation information file is used.
Name Design of the reservation update function for server software

WBS # 11.1.3.13.3
Description Establishing a design for the reservation update function of
chooses the reservation update function after the reservation
authentication to change information (except the
Reservation_id) of an existing reservation of the ONLINE
AIRLINE TICKET RESERVATION SYSTEM.
Name Design of the service addition function for server software

WBS # 11.1.3.14.1
Description Establishing a design for the service addition function of
chooses the service addition function, after the service
authentication, to add a service to the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The service information
file is used.
Name Design of the service deletion function for server software

WBS # 11.1.3.14.2
Description Establishing a design for the service deletion function of
chooses the service deletion function after the service
authentication to delete an existing service from the ONLINE
AIRLINE TICKET RESERVATION SYSTEM. The service
Name Design of the service update function for server software

WBS # 11.1.3.14.3
Description Establishing a design for the service update function of server
39
the service update function after the service authentication to
change information (except the Service_id) of an existing
service of the ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Design of the client software

WBS # 11.1.4
Description Symbolizing all of the design processes for client software

WBS # 11.1.4.1
Description Symbolizing the design process for all users that lies below
this work activity.
Name Design of the user authentication function for client software

WBS # 11.1.4.1.1
Description Establishing a design for the user authentication function of
client software. All users should use this function to enter the
Therefore, security issue is a part of the user authentication
function.

WBS # 11.1.4.2
Description Symbolizing all of the design processes for root that lies
Name Design of the user addition function for client software

WBS # 11.1.4.2.1
Description Establishing a design for the user addition function of client
the user addition function, after the user authentication, to add
a user to the ONLINE AIRLINE TICKET RESERVATION
40
SYSTEM. The user information file is used.
Name Design of the user deletion function for client software
WBS # 11.1.4.2.2
Description Establishing a design for the user deletion function of client
the user deletion function after the user authentication to
delete an existing user from the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The user information file is used.
Name Design of the user update function for client software

WBS # 11.1.4.2.3
Description Establishing a design for the user update function of client
the user update function after the user authentication to
change information (except the User_id) of an existing user of
Name Design of the seat addition function for client software

WBS # 11.1.4.3.1
Description Establishing a design for the seat addition function of client
the seat addition function, after the seat authentication, to add
a seat to the ONLINE AIRLINE TICKET RESERVATION
SYSTEM. The seat information file is used.
Name Design of the seat deletion function for client software

WBS # 11.1.4.3.2
Description Establishing a design for the seat deletion function of client
the seat deletion function after the seat authentication to delete
an existing seat from the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The seat information file is used.
Name Design of the seat update function for client software

WBS # 11.1.4.3.3
41
Description Establishing a design for the seat update function of client
the seat update function after the seat authentication to change
information (except the Seat_id) of an existing seat of the
Name Design of the class addition function for client software

WBS # 11.1.4.4.1
Description Establishing a design for the class addition function of client
the class addition function, after the class authentication, to
add a class to the ONLINE AIRLINE TICKET
used.
Name Design of the class deletion function for client software

WBS # 11.1.4.4.2
Description Establishing a design for the class deletion function of client
the class deletion function after the class authentication to
delete an existing class from the ONLINE AIRLINE TICKET
used.
Name Design of the class update function for client software

WBS # 11.1.4.4.3
Description Establishing a design for the class update function of client
the class update function after the class authentication to
change information (except the Class_id) of an existing class
SYSTEM.
Name Design of the plane addition function for client software

WBS # 11.1.4.5.1
Description Establishing a design for the plane addition function of client
42
the plane addition function, after the plane authentication, to
add a plane to the ONLINE AIRLINE TICKET
used.
Name Design of the plane deletion function for client software

WBS # 11.1.4.5.2
Description Establishing a design for the plane deletion function of client
the plane deletion function after the plane authentication to
delete an existing plane from the ONLINE AIRLINE TICKET
used.
Name Design of the plane update function for client software

WBS # 11.1.4.5.3
Description Establishing a design for the plane update function of client
the plane update function after the plane authentication to
change information (except the Plane_id) of an existing plane
SYSTEM.
Name Design of the flight addition function for client software

WBS # 11.1.4.6.1
Description Establishing a design for the flight addition function of client
the flight addition function, after the flight authentication, to
add a flight to the ONLINE AIRLINE TICKET
used.
Name Design of the flight deletion function for client software

WBS # 11.1.4.6.2
Description Establishing a design for the flight deletion function of client
43
the flight deletion function after the flight authentication to
delete an existing flight from the ONLINE AIRLINE TICKET
used.
Name Design of the flight update function for client software

WBS # 11.1.4.6.3
Description Establishing a design for the flight update function of client
the flight update function after the flight authentication to
change information (except the Flight_id) of an existing flight
SYSTEM.
Name Design of the gates addition function for client software

WBS # 11.1.4.7.1
Description Establishing a design for the gates addition function of client
the gates addition function, after the gates authentication, to
add a gates to the ONLINE AIRLINE TICKET
used.
Name Design of the gates deletion function for client software

WBS # 11.1.4.7.2
Description Establishing a design for the gates deletion function of client
the gates deletion function after the gates authentication to
delete an existing gates from the ONLINE AIRLINE TICKET
used.
Name Design of the gates update function for client software

WBS # 11.1.4.7.3
Description Establishing a design for the gates update function of client
the gates update function after the gates authentication to
44
change information (except the Gates_id) of an existing gates
SYSTEM.
Name Design of the airport addition function for client software

WBS # 11.1.4.8.1
Description Establishing a design for the airport addition function of client
the airport addition function, after the airport authentication,
to add a airport to the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The airport information file is
used.
Name Design of the airport deletion function for client software

WBS # 11.1.4.8.2
Description Establishing a design for the airport deletion function of client
the airport deletion function after the airport authentication to
delete an existing airport from the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The airport information
file is used.
Name Design of the airport update function for client software

WBS # 11.1.4.8.3
Description Establishing a design for the airport update function of client
the airport update function after the airport authentication to
change information (except the Airport_id) of an existing
airport of the ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Design of the city addition function for client software

WBS # 11.1.4.9.1
Description Establishing a design for the city addition function of client
the city addition function, after the city authentication, to add
a city to the ONLINE AIRLINE TICKET RESERVATION
45
SYSTEM. The city information file is used.
Name Design of the city deletion function for client software
WBS # 11.1.4.9.2
Description Establishing a design for the city deletion function of client
the city deletion function after the city authentication to delete
an existing city from the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The city information file is used.
Name Design of the city update function for client software

WBS # 11.1.4.9.3
Description Establishing a design for the city update function of client
the city update function after the city authentication to change
information (except the City_id) of an existing city of the
Name Design of the country addition function for client software

WBS # 11.1.4.10.1
Description Establishing a design for the country addition function of
client software. Only the root can use this function if she/he
chooses the country addition function, after the country
authentication, to add a country to the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The country
Name Design of the country deletion function for client software

WBS # 11.1.4.10.2
Description Establishing a design for the country deletion function of
chooses the country deletion function after the country
authentication to delete an existing country from the ONLINE
AIRLINE TICKET RESERVATION SYSTEM. The country
Name Design of the country update function for client software

WBS # 11.1.4.10.3
46
Description Establishing a design for the country update function of client
the country update function after the country authentication to
change information (except the Country_id) of an existing
country of the ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Design of the bank addition function for client software

WBS # 11.1.4.11.1
Description Establishing a design for the bank addition function of client
the bank addition function, after the bank authentication, to
add a bank to the ONLINE AIRLINE TICKET
used.
Name Design of the bank deletion function for client software

WBS # 11.1.4.11.2
Description Establishing a design for the bank deletion function of client
the bank deletion function after the bank authentication to
delete an existing bank from the ONLINE AIRLINE TICKET
used.
Name Design of the bank update function for client software

WBS # 11.1.4.11.3
Description Establishing a design for the bank update function of client
the bank update function after the bank authentication to
change information (except the Bank_id) of an existing bank
SYSTEM.
Name Design of the ticket addition function for client software

WBS # 11.1.4.12.1
47
Description Establishing a design for the ticket addition function of client
the ticket addition function, after the ticket authentication, to
add a ticket to the ONLINE AIRLINE TICKET
RESERVATION SYSTEM. The ticket information file is
used.
Name Design of the ticket deletion function for client software

WBS # 11.1.4.12.2
Description Establishing a design for the ticket deletion function of client
the ticket deletion function after the ticket authentication to
delete an existing ticket from the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The ticket information
file is used.
Name Design of the ticket update function for client software

WBS # 11.1.4.12.3
Description Establishing a design for the ticket update function of client
the ticket update function after the ticket authentication to
change information (except the Ticket_id) of an existing ticket
SYSTEM.
Name Design of the reservation addition function for client software

WBS # 11.1.4.13.1
Description Establishing a design for the reservation addition function of
chooses the reservation addition function, after the reservation
authentication, to add a reservation to the ONLINE AIRLINE
TICKET RESERVATION SYSTEM. The reservation
Name Design of the reservation deletion function for client software

WBS # 11.1.4.13.2
48
Description Establishing a design for the reservation deletion function of
chooses the reservation deletion function after the reservation
authentication to delete an existing reservation from the
The reservation information file is used.
Name Design of the reservation update function for client software

WBS # 11.1.4.13.3
Description Establishing a design for the reservation update function of
chooses the reservation update function after the reservation
authentication to change information (except the
Reservation_id) of an existing reservation of the ONLINE
AIRLINE TICKET RESERVATION SYSTEM.
Name Design of the service addition function for client software

WBS # 11.1.4.14.1
Description Establishing a design for the service addition function of
chooses the service addition function, after the service
authentication, to add a service to the ONLINE AIRLINE
file is used.
Name Design of the service deletion function for client software

WBS # 11.1.4.14.2
Description Establishing a design for the service deletion function of client
the service deletion function after the service authentication to
delete an existing service from the ONLINE AIRLINE
file is used.
Name Design of the service update function for client software

WBS # 11.1.4.14.3
49
Description Establishing a design for the service update function of client
the service update function after the service authentication to
change information (except the Service_id) of an existing
service of the ONLINE AIRLINE TICKET RESERVATION
SYSTEM.
Name Design of the functions for instructor, students & customers

WBS # 11.1.4.15
Description Symbolizing the design process for instructor, students &
customers that lies below this work activity.

WBS # 11.1.5

WBS # 11.1.6
budgeted cost.

WBS # 11.1.7
Name Review meeting for the content of the SDD with the customer
WBS # 11.2
Description Reviewing the SDD’s content to determine that if there is
anything that the customer wants to add.
50
Name Control of the quality of the SDD
WBS # 11.3
Name Writing of the SDD documentation

WBS # 11.4
Description Documenting the activities that have been done for SDD of
Name Review meeting for SDD documentation

WBS # 11.5
Estimated duration 0.25 days
Description Reviewing the SDD documentation of the ONLINE AIRLINE
TICKET RESERVATION SYSTEM by Duygu Albayrak to
determine quality of the SDD documentation using IEEE std.
1016-1998 [3].
Name Training for Java programming language and networking

WBS # 12
Description Giving training to Özge Koray & Merve Bayraktar about the
Java programming language with the special emphasis on the
applets and console applications by lectures.
Name Coding of the ONLINE AIRLINE TICKET RESERVATION

SYSTEM
WBS # 13
Description Symbolizing all of the coding process that lies below this
work activity.
Name Coding of the server software

WBS # 13.1
51
Description Symbolizing all of the coding process for server software that
lies below this work activity.
Name Coding of the common functions of all users

WBS # 13.1.1
Description Symbolizing the coding process for all users that lies below
this work activity.
Name Coding of the user authentication function for server software

WBS # 13.1.1.1
Description Writing a software module using the Java programming
language, according to the design specifications described as
the work product of the activity number 11.1.3.1.1. The
module shall evaluate the authentication information sent by
the client software and shall produce a reply to the client
software accordingly.
Name Coding of the functions for root

WBS # 13.1.2
Description Symbolizing the coding process for root that lies below this
work activity.
Name Coding of the necessary addition function for server software

WBS # 13.1.2.1
Name Coding of the necessary deletion function for server software

WBS # 13.1.2.2
52
Name Coding of the necessary update function for server software

WBS # 13.1.2.3
Name Coding of the functions for instructor, students & customers

WBS # 13.1.3
Description Symbolizing the coding process for instructor, students &
Name Coding of the client software

WBS # 13.2
Description Symbolizing all of the coding processes for client software

WBS # 13.2.1
Description Symbolizing the coding process for all users that lies below
this work activity.
Name Coding of the user authentication function for client software

WBS # 13.2.1.1
53
module shall send the authentication information entered by
the user to the server software and shall produce a reply to the
user according to the reply from the server software.

WBS # 13.2.2
Description Symbolizing all of the coding processes for root that lies

WBS # 13.2.2.1

WBS # 13.2.2.2

WBS # 13.2.2.3
54

WBS # 13.2.3
Description Symbolizing the coding process for instructor, students &

WBS # 13.3
Name Control of the budget requirement

WBS # 13.4
budgeted cost.

WBS # 13.5
Name Control of the quality of the code generated

WBS # 13.6
Name Training for testing processes

WBS # 14
55
Description Giving training Merve Bayraktar & Gürhan YANKI by
lectures and discussions to make a background about testing
techniques.
Name Testing of the ONLINE AIRLINE TICKET RESERVATION

SYSTEM
WBS # 15
Description Symbolizing all of the testing processes that lies below this
work activity.
Name Testing of the common functions of all users

WBS # 15.1
Description Symbolizing the testing process for all users that lies below
this work activity.
Name Testing of the user authentication function

WBS # 15.1.1
Description Finding out the bugs in this function and to test whether the
links of this function are working correctly with other
functions.
Name Testing of the functions for root

WBS # 15.2
Predecessor activity 74,89,107
Description Symbolizing all of the testing processes for root that lies
Name Testing of the necessary addition function

WBS # 15.2.1
functions.
56
Name Testing of the necessary deletion function
WBS # 15.2.2
functions.
Name Testing of the necessary update function

WBS # 15.2.3
functions.
Name Testing of the functions for instructor, students & customers

WBS # 15.3
Predecessor activity 84, 99, 107
Description Symbolizing the testing process for instructor, students &
Name Testing of the search function

WBS # 15.3.1
functions.

WBS # 15.4

WBS # 15.5
57
budgeted cost.

WBS # 15.6
Name Delivery of initial product

WBS # 16
Successor activity 125, 126, 129, 131
Description Submitting the initial product to the customer.
Name Review meeting for the initial product with the customer
WBS # 17
Description Reviewing the initial product of the ONLINE AIRLINE
TICKET RESERVATION SYSTEM to determine that if there
is anything that the customer wants to add.

WBS # 18

WBS # 19
budgeted cost.
58
WBS # 20
Name Control of the quality of the initial product

WBS # 21

WBS # 22
1987 [4].
Name Preparation of the User Manual

WBS # 23
Description Describing how the ONLINE AIRLINE TICKET
RESERVATION SYSTEM is working and at the end to bring
out a report about it.
Name Product Demonstration

WBS # 24
Description Showing the final product to the customer.
Name Delivery of the final product

WBS # 25
Description Submitting the final product to the customer.
59
5.2.2 Schedule Allocation (Subclause 5.2.2 of the SPMP)
The ONLINE AIRLINE TICKET RESERVATION SYSTEM schedule allocation is given in
Table 15. The gray backgrounded work activities (WBS #: 22, 23, 24 and 25) are the critical
path activities of the ONLINE AIRLINE TICKET RESERVATION SYSTEM schedule. The
GANTT chart for the schedule can be viewed in Appendix A.
The milestones of the ONLINE AIRLINE TICKET RESERVATION SYSTEM are the
activites with WBS #: 1, 3, 5, 8.10, 8.12, 11.4, 11.6, 16, 23, 24, 25 in Table 15.
The time–sequencing of the ONLINE AIRLINE TICKET RESERVATION SYSTEM is

given in Table 15 with the concurrent work activities given in the predecessor coloumn of
Table 15.
Duration
No WBS # Work Activity Start Date End Date
(d=day)
1 1 Stating the problem 6d October 2. October 8
statement 2006 2006
2 2 Training for IEEE Std. 1d October 9 October 9
1058-1998 2006 2006
3 3 Preparation of the Initial 10d October 10 October 20
Plan 2006 2006
4 4 Training for IEEE Std. 4d October 21 October 24
830-1998 2006 2006
5 5 Preparation of the SRS 17d October 25 November 10
2006 2006
6 6 Review meeting for the 1d November November 13
changes of software 13 2006 2006
requirements with the
customer
7 7 Training for IEEE Std. 3d November November 14
1058-1998 12 2006 2006
8 8 Preparation of the SPMP 25d November December 23
14 2006 2006
9 8.1 Preparation of 2d November November 15
managerial process plans 14 2006 2006
10 8.1.1 Work plan 2d November November 16
15 2006 2006
11 8.1.2 Control Plan 2d November November 17
16 2006 2006
12 8.1.3 Risk management plan 2d November November 18
17 2006 2006
13 8.1.4 Project closeout plan 2d November November 19
18 2006 2006
60
14 8.2 Control of the project 1d November November 20
schedule 20 2006 2006
15 8.3 Control of the budget 1d November November 21
requirements 21 2006 2006
16 8.4 Review of the project 1d November November 22
risk factors 22 2006 2006
17 8.5 Review meeting for the 1d November November 23
content of the SPMP with 23 2006 2006
the customer
18 8.6 Preparation of technical 2d November November 25
process plans 24 2006 2006
19 8.7 Preparation of supporting 3d November November 27
process plans 25 2006 2006
20 8.8 Control of the quality of 2d November November 29
the SPMP 28 2006 2006
21 8.9 Writing of the SPMP 1d November November 30
documentation 30 2006 2006
22 8.10 Review meeting for 1d December 4 December 4
SPMP documentation 2006 2006
23 8.11 Update of the SPMP 2d December 4 December 5
documentation 2006 2006
24 9 Training for IEEE Std. 2d December 5 December 6
1016-1998 2006 2006
25 10 Review meeting for the 1d December 6 December 6
changes of software 2006 2006
requirements with the
customer
26 11 Preparation of the SDD 25d December 1 December 25
2006 2006
27 11.1 Design of the ONLINE 17d December 1 December 16
AIRLINE TICKET 2006 2006
RESERVATION
SYSTEM
28 11.1.1 Design of the 2d December 2 December 3
communication protocol 2006 2006
between client & server
softwares
29 11.1.2 Design of the user and 1d December 3 December 3
information files 2006 2006
30 11.1.3 Design of the server 6d December 3 December 8
software 2006 2006
31 11.1.3.1 Design of the common 0.125d December 3 December 3
functions of all users 2006 2006
32 11.1.3.1.1 Design of the user 0.125d December 3 December 3
authentication function 2006 2006
for server software
33 11.1.3.2 Design of the functions 0.125d December 3 December 3
for root 2006 2006
61
addition function for 2006 2006
server software
deletion function for 2006 2006
server software
36 11.1.3.2.3 Design of the user update 0.125d December 3 December 3
function for server 2006 2006
software
37 11.1.3.3.1 Design of the seat 0.125d December 4 December 4
server software
server software
39 11.1.3.3.3 Design of the seat update 0.125d December 4 December 4
software
40 11.1.3.4.1 Design of the class 0.125d December 4 December 4
server software
server software
update function for 2006 2006
server software
43 11.1.3.5.1 Design of the plain 0.125d December 4 December 4
server software
server software
server software
46 11.1.3.6.1 Design of the flight 0.125d December 5 December 5
server software
server software
server software
49 11.1.3.7.1 Design of the gates 0.125d December 5 December 5
server software
server software
62
server software
52 11.1.3.8.1 Design of the airport 0.125d December 5 December 5
server software
server software
server software
55 11.1.3.9.1 Design of the city 0.125d December 6 December 6
server software
56 11.1.3.9.2 Design of the city 0.125d December 6 December 6
server software
57 11.1.3.9.3 Design of the city update 0.125d December 6 December 6
software
58 11.1.3.10. Design of the country 0.125d December 6 December 6
1 addition function for 2006 2006
server software
2 deletion function for 2006 2006
server software
3 update function for 2006 2006
server software
61 11.1.3.11. Design of the bank 0.125d December 7 December 7
server software
server software
server software
64 11.1.3.12. Design of the ticket 0.125d December 7 December 7
server software
server software
server software
67 11.1.3.13. Design of the reservation 0.125d December 7 December 7
63
server software
server software
server software
70 11.1.3.14. Design of the service 0.125d December 8 December 8
server software
server software
server software
73 11.1.4 Design of the client 8d December 8 December 15
software 2006 2006
74 11.1.4.1 Design of the common 0.125d December 8 December 8
for client software
76 11.1.4.2 Design of the functions 0.125d December 8 December 8
for root 2006 2006
client software
client software
79 11.1.4.2.3 Design of the user update 0.125d December 9 December 9
function for client 2006 2006
software
client software
client software
82 11.1.4.3.3 Design of the seat update 0.125d December 9 December 9
function for client 2006 2006
software
client software
client software
64
85 11.1.4.4.3 Design of the class 0.125d December December 10
update function for client 10 2006 2006
software
86 11.1.4.5.1 Design of the plain 0.125d December December 10
addition function for 10 2006 2006
client software
deletion function for 10 2006 2006
client software
software
89 11.1.4.6.1 Design of the flight 0.125d December December 10
client software
client software
software
92 11.1.4.7.1 Design of the gates 0.125d December December 10
client software
client software
software
95 11.1.4.8.1 Design of the airport 0.125d December December 11
client software
client software
software
98 11.1.4.9.1 Design of the city 0.125d December December 11
client software
99 11.1.4.9.2 Design of the city 0.125d December December 11
client software
100 11.1.4.9.3 Design of the city update 0.125d December December 11
function for client 11 2006 2006
software
101 11.1.4.10. Design of the country 0.125d December December 12
1 addition function for 12 2006 2006
65
client software
2 deletion function for 12 2006 2006
client software
3 update function for client 12 2006 2006
software
104 11.1.4.11. Design of the bank 0.125d December December 12
client software
client software
software
107 11.1.4.12. Design of the ticket 0.125d December December 12
client software
client software
software
110 11.1.4.13. Design of the reservation 0.125d December December 13
client software
client software
software
113 11.1.4.14. Design of the service 0.125d December December 13
client software
client software
software
116 11.1.4.15 Design of the functions 0.125d December December 13
for instructor, students & 13 2006 2006
customers
117 11.1.5 Control of the project 2d December December 15
schedule 14 2006 2006
118 11.1.6 Control of the budget 2d December December 16
requirements 15 2006 2006
66
119 11.1.7 Review of the project 1d December December 16
risk factors 16 2006 2006
120 11.2 Review meeting for the 1d December December 16
content of the SDD with 16 2006 2006
the customer
121 11.3 Control of the quality of 2d December December 17
the SDD 16 2006 2006
122 11.4 Writing of the SDD 4d December December 20
123 11.5 Review meeting for SDD 0.25d December December 25
124 12 Training for Java 31d December January 26
programming language 27 2006 2007
125 13 Coding of the ONLINE 16d January 26 February 12
RESERVATION
SYSTEM
126 13.1 Coding of the server 15d January 12 January 26
software 2007 2007
127 13.1.1 Coding of the common 1d January 12 January 12
128 13.1.1.1 Coding of the user 1d January 12 January 12
for server software
129 13.1.2 Coding of the functions 12d January 12 January 23
for root 2007 2007
130 13.1.2.1 Coding of the necessary 2d January 12 January 14
server software
server software
server software
133 13.1.3 "Coding of the functions 2d January 17 January 18
for instructor, students & 2007 2007
customers"
134 13.2 Coding of the client 6d January 30 February 05
software 2007 2007
135 13.2.1 Coding of the common 1d January 30 January 30
136 13.2.1.1 Coding of the user 1d January 30 January 30
for client software
137 13.2.2 Coding of the functions 12d February 01 February 12
for root 2007 2007
138 13.2.2.1 Coding of the necessary 2d February 01 February 02
67
client software
client software
update function for client 2007 2007
software
141 13.2.3 "Coding of the functions 2d February 04 February 05
customers"
142 13.3 Control of the project 1d February 05 February 05
schedule 2007 2007
143 13.4 Control of the budget 2d February 05 February 06
requirements 2007 2007
144 13.5 Review of the project 1d February 06 February 06
risk factors 2007 2007
145 13.6 Control of the quality of 1d February 07 February 07
the code generated 2007 2007
146 14 Training for testing 4d February 07 February 10
processes 2007 2007
147 15 Testing of the ONLINE 12d February 07 February 18
RESERVATION
SYSTEM
148 15.1 Testing of the common 1d February 07 February 10
149 15.1.1 Testing of the user 1d February 07 February 10
150 15.2 Testing of the functions 2d February 07 February 08
for root 2007 2007
151 15.2.1 Testing of the necessary 3d February 09 February 11
addition function 2007 2007
deletion function 2007 2007
update function 2007 2007
154 15.3 "Testing of the functions 2d February 14 February 15
customers"
155 15.3.1 Testing of the search 1d February 15 February 15
function 2007 2007
156 15.4 Control of the project 1d February 16 February 16
schedule 2007 2007
157 15.5 Control of the budget 1d February 17 February 17
158 15.6 Review of the project 1d February 18 February 18
159 16 Delivery of initial 1d February 19 February 19
product 2007 2007
68
160 17 Review meeting for the 1d February 20 February 20
initial product with the 2007 2007
customer
161 18 Control of the project 1d February 21 February 21
schedule 2007 2007
162 19 Control of the budget 1d February 22 February 22
163 20 Review of the project 1d February 23 February 23
164 21 Control of the quality of 1d February 24 February 24
the initial product 2007 2007
165 22 Training for IEEE Std. 2d February 25 February 26
1063-1987 2007 2007
166 23 Preparation of the User 19d February 24 March 13
Manual 2007 2007
167 24 Product Demonstration 1d March 13 March 13
2007 2007
168 25 Delivery of the final 1d March 14 March 14
product 2007 2007
Table 15: Schedule of the ONLINE AIRLINE TICKET RESERVATION SYSTEM
5.2.3 Resource Allocation (Subclause 5.2.3 of the SPMP)
The detailed itemization of the resources allocated to each individual work activity in the
work breakdown structure is given below.
The only resource that wroth planning, allocating and tracking for every work activity in the
work breakdown structure is the personnel. Since planning, allocating and tracking other
resources to the work activities shall result in high overhead for the project when compared
with the benefits of providing such an allocation, they shall simply be neglected.
Name Stating the problem statement

WBS # 1
Personnel responsible All of the OnAir members

WBS # 2
Personnel responsible Merve Bayraktar
Name Preparation of the Initial Plan

WBS # 3
69
WBS # 4
Name Preparation of the SRS
WBS # 5

with the customer
WBS # 6
Personnel responsible Özge Koray, Gürhan YANKI

WBS # 7
Name Preparation of the SPMP

WBS # 8
Name Update of the Initial Plan

WBS # 8.1
Name Preparation of managerial process plans

WBS # 8.2
Name Work plan

WBS # 8.2.1
Personnel responsible Gürhan YANKI
Name Control plan

WBS # 8.2.2
Personnel responsible Özge Koray
Name Risk management plan

WBS # 8.2.3
Name Project closeout plan

WBS # 8.2.4

WBS # 8.3
70
WBS # 8.4

WBS # 8.5
Name Review meeting for the content of the SPMP with the
customer
WBS # 8.6
Name Preparation of technical process plans

WBS # 8.7
Name Preparation of supporting process plans

WBS # 8.8
Personnel responsible Özge Koray & Merve Bayraktar
Name Control of the quality of the SPMP

WBS # 8.9
Personnel responsible All of the OnAir members & Assoc. Prof. Onur Demirörs
Name Writing of the SPMP documentation

WBS # 8.10
Name Review meeting for SPMP documentation

WBS # 8.11
Personnel responsible Duygu Albayrak members
Name Update of the SPMP documantation

WBS # 8.12

WBS # 9

with the customer
WBS # 10
Name Preparation of the SDD

WBS # 11
71
Name Design of the ONLINE AIRLINE TICKET RESERVATION

SYSTEM
WBS # 11.1
Name Design of the communication protocol between client &

server software
WBS # 11.1.1
Name Design of the user information files

WBS # 11.1.2
Personnel responsible Gürhan YANKI & Özge Koray
Name Design of the server software

WBS # 11.1.3
Personnel responsible Gürhan YANKI & Merve Bayraktar

WBS # 11.1.3.1
Name Design of the user authentication function for server software

WBS # 11.1.3.1.1

WBS # 11.1.3.2
Name Design of the user addition function for server software

WBS # 11.1.3.2.1
Personnel responsible Gürhan YANKI & Tuğçe Pakakar
Name Design of the user deletion function for server software

WBS # 11.1.3.2.2
Name Design of the user update function for server software

WBS # 11.1.3.2.3
Name Design of the seat addition function for server software

WBS # 11.1.3.3.1
72
Name Design of the seat deletion function for server software
WBS # 11.1.3.3.2
Name Design of the seat update function for server software

WBS # 11.1.3.3.3
Name Design of the class addition function for server software

WBS # 11.1.3.4.1
Name Design of the class deletion function for server software

WBS # 11.1.3.4.2
Name Design of the class update function for server software

WBS # 11.1.3.4.3
Name Design of the plane addition function for server software

WBS # 11.1.3.5.1
Name Design of the plane deletion function for server software

WBS # 11.1.3.5.2
Name Design of the plane update function for server software

WBS # 11.1.3.5.3
Name Design of the flight addition function for server software

WBS # 11.1.3.6.1
Name Design of the flight deletion function for server software

WBS # 11.1.3.6.2
Name Design of the flight update function for server software

WBS # 11.1.3.6.3
Name Design of the gates addition function for server software

WBS # 11.1.3.7.1
73
Name Design of the gates deletion function for server software
WBS # 11.1.3.7.2
Name Design of the gates update function for server software

WBS # 11.1.3.7.3
Name Design of the airport addition function for server software

WBS # 11.1.3.8.1
Name Design of the airport deletion function for server software

WBS # 11.1.3.8.2
Name Design of the airport update function for server software

WBS # 11.1.3.8.3
Name Design of the city addition function for server software

WBS # 11.1.3.9.1
Name Design of the city deletion function for server software

WBS # 11.1.3.9.2
Name Design of the city update function for server software

WBS # 11.1.3.9.3
Name Design of the country addition function for server software

WBS # 11.1.3.10.1
Name Design of the country deletion function for server software

WBS # 11.1.3.10.2
Name Design of the country update function for server software

WBS # 11.1.3.10.3
Name Design of the bank addition function for server software

WBS # 11.1.3.11.1
74
Name Design of the bank deletion function for server software
WBS # 11.1.3.11.2
Name Design of the bank update function for server software

WBS # 11.1.3.11.3
Name Design of the ticket addition function for server software

WBS # 11.1.3.12.1
Name Design of the ticket deletion function for server software

WBS # 11.1.3.12.2
Name Design of the ticket update function for server software

WBS # 11.1.3.12.3
Name Design of the reservation addition function for server software

WBS # 11.1.3.13.1
Name Design of the reservation deletion function for server software

WBS # 11.1.3.13.2
Name Design of the reservation update function for server software

WBS # 11.1.3.13.3
Name Design of the service addition function for server software

WBS # 11.1.3.14.1
Name Design of the service deletion function for server software

WBS # 11.1.3.14.2
Name Design of the service update function for server software

WBS # 11.1.3.14.3

WBS # 11.1.3.15
75
Name Design of the client software
WBS # 11.1.4
Personnel responsible Merve Bayraktar, Özge Koray

WBS # 11.1.4.1
Name Design of the user authentication function for client software

WBS # 11.1.4.1.1

WBS # 11.1.4.2
Name Design of the user addition function for client software

WBS # 11.1.4.2.1
Personnel responsible Merve Bayraktar & Tuğçe Pakakar
Name Design of the user deletion function for client software

WBS # 11.1.4.2.2
Personnel responsible Merve Bayraktar & Gürhan YANKI
Name Design of the user update function for client software

WBS # 11.1.4.2.3
Personnel responsible Merve Bayraktar & Özge Koray
Name Design of the seat addition function for client software

WBS # 11.1.4.3.1
Name Design of the seat deletion function for client software

WBS # 11.1.4.3.2
Name Design of the seat update function for client software

WBS # 11.1.4.3.3
Name Design of the class addition function for client software

WBS # 11.1.4.4.1
Name Design of the class deletion function for client software

WBS # 11.1.4.4.2
76
Name Design of the class update function for client software
WBS # 11.1.4.4.3
Name Design of the plane addition function for client software

WBS # 11.1.4.5.1
Name Design of the plane deletion function for client software

WBS # 11.1.4.5.2
Name Design of the plane update function for client software

WBS # 11.1.4.5.3
Name Design of the flight addition function for client software

WBS # 11.1.4.6.1
Name Design of the flight deletion function for client software

WBS # 11.1.4.6.2
Name Design of the flight update function for client software

WBS # 11.1.4.6.3
Name Design of the gates addition function for client software

WBS # 11.1.4.7.1
Name Design of the gates deletion function for client software

WBS # 11.1.4.7.2
Name Design of the gates update function for client software

WBS # 11.1.4.7.3
Name Design of the airport addition function for client software

WBS # 11.1.4.8.1
Name Design of the airport deletion function for client software

WBS # 11.1.4.8.2
77
Name Design of the airport update function for client software
WBS # 11.1.4.8.3
Name Design of the city addition function for client software

WBS # 11.1.4.9.1
Name Design of the city deletion function for client software

WBS # 11.1.4.9.2
Name Design of the city update function for client software

WBS # 11.1.4.9.3
Name Design of the country addition function for client software

WBS # 11.1.4.10.1
Name Design of the country deletion function for client software

WBS # 11.1.4.10.2
Name Design of the country update function for client software

WBS # 11.1.4.10.3
Name Design of the bank addition function for client software

WBS # 11.1.4.11.1
Name Design of the bank deletion function for client software

WBS # 11.1.4.11.2
Name Design of the bank update function for client software

WBS # 11.1.4.11.3
Name Design of the ticket addition function for client software

WBS # 11.1.4.12.1
Name Design of the ticket deletion function for client software

WBS # 11.1.4.12.2
78
Name Design of the ticket update function for client software
WBS # 11.1.4.12.3
Name Design of the reservation addition function for client software

WBS # 11.1.4.13.1
Name Design of the reservation deletion function for client software

WBS # 11.1.4.13.2
Name Design of the reservation update function for client software

WBS # 11.1.4.13.3
Name Design of the service addition function for client software

WBS # 11.1.4.14.1
Name Design of the service deletion function for client software

WBS # 11.1.4.14.2
Name Design of the service update function for client software

WBS # 11.1.4.14.3

WBS # 11.1.4.3
Name Design of the chat function for client software

WBS # 11.1.4.3.1

WBS # 11.1.5
Personnel responsible Özge Koray & Tuğçe Pakakar

WBS # 11.1.6

WBS # 11.1.7
79
Name Review meeting for the content of the SDD with the customer
WBS # 11.2
Name Control of the quality of the SDD

WBS # 11.3
Personnel responsible All of the OnAir members & Assoc. Prof. Onur Demirörs
Name Writing of the SDD documentation

WBS # 11.4
Name Review meeting for SDD documentation

WBS # 11.5
Name Update of the SDD documentation

WBS # 11.6
Name Training for Java programming language and networking

WBS # 12
Name Coding of the ONLINE AIRLINE TICKET RESERVATION

SYSTEM
WBS # 13
Name Coding of the server software

WBS # 13.1

WBS # 13.1.1
Name Coding of the user authentication function for server software

WBS # 13.1.1.1

WBS # 13.1.2
80
WBS # 13.1.2.1

WBS # 13.1.2.2

WBS # 13.1.2.3

WBS # 13.1.3
Name Coding of the chat function for server software

WBS # 13.1.3.1
Name Coding of the client software

WBS # 13.2

WBS # 13.2.1
Name Coding of the user authentication function for client software

WBS # 13.2.1.1

WBS # 13.2.2
Name Coding of the user addition function for client software

WBS # 13.2.2.1
Name Coding of the user deletion function for client software

WBS # 13.2.2.2
Name Coding of the user update function for client software

WBS # 13.2.2.3
Name Coding of the chat group addition function for client software
81
WBS # 13.2.2.4
Name Coding of the chat group deletion function for client software
WBS # 13.2.2.5
Name Coding of the chat group update function for client software
WBS # 13.2.2.6
Name Coding of the room addition function for client software

WBS # 13.2.2.7
Name Coding of the room deletion function for client software

WBS # 13.2.2.8
Name Coding of the room update function for client software

WBS # 13.2.2.9

WBS # 13.2.3
Name Coding of the chat function for client software

WBS # 13.2.3.1

WBS # 13.3
Name Control of the budget requirement

WBS # 13.4

WBS # 13.5
Name Control of the quality of the code generated

WBS # 13.6
Name Training for testing processes
82
WBS # 14
Name Testing of the ONLINE AIRLINE TICKET RESERVATION

SYSTEM
WBS # 15
Name Testing of the common functions of all users

WBS # 15.1
Name Testing of the user authentication function

WBS # 15.1.1
Name Testing of the functions for root

WBS # 15.2
Name Testing of the user addition function

WBS # 15.2.1
Name Testing of the user deletion function

WBS # 15.2.2
Name Testing of the user update function

WBS # 15.2.3
Name Testing of the chat group addition function

WBS # 15.2.4
Name Testing of the chat group deletion function

WBS # 15.2.5
Name Testing of the chat group update function

WBS # 15.2.6
Name Testing of the room addition function

WBS # 15.2.7
83
Name Testing of the room deletion function
WBS # 15.2.8
Name Testing of the room update function

WBS # 15.2.9
Name Testing of the functions for instructor, students & customers

WBS # 15.3
Name Testing of the chat function

WBS # 15.3.1

WBS # 15.4

WBS # 15.5

WBS # 15.6
Name Delivery of initial product

WBS # 16
Name Review meeting for the initial product with the customer
WBS # 17
Personnel responsible Özge Koray & Gürhan YANKI

WBS # 18

WBS # 19

WBS # 20
84
Name Control of the quality of the initial product
WBS # 21

WBS # 22
Name Preparation of the User Manual

WBS # 23
Name Product Demonstration

WBS # 24
Name Delivery of the final product

WBS # 25
5.2.4 Budget Allocation (Subclause 5.2.4 of the SPMP)

The detailed breakdown of the budget allocation provided for each of the major work activity
in the work breakdown structure is given below.
Since the only resource allocated to individual work activities is personnel as mentioned in
section 5.2.3, the allocated budget for every individual work activity shall be increased by
5%.
Since planning, allocating and tracking an individual budget to each one of the work activities
shall result in high overhead for the project when compared with the benefits of providing
such an allocation, budget allocation shall be done in only the detail necessary.
As calculated in section 5.1.1 Estimation Plan in order for the project to finish at time 6
people are needed and the payment given for each person is estimated to be 1500$. Since
OnAir can allocate 3 people for the ONLINE AIRLINE TICKET RESERVATION SYSTEM
the monthly payment to be given for each person shall be 3000$. Which makes 100$ per day.
Also payment for the Duygu Albayrak members is 10$ as indicated in section 5.1.1
Estimation Plan.
85
The calculations done in Table 16 depends on the above payment criterias.
Major Work Activity Name Total Cost ($)

Review meeting for the changes of software
(2*100)+ (200*0.05) = 210
requirements with the customer
Training for IEEE Std. 1058-1998 (3*100)+ (300*0.05) = 315
Preparation of the SPMP ((19.5*100)+ (1*10))+(1960*0.05) = 2048
Review meeting for the changes of software
(2*100)+ (200*0.05) = 210
requirements with the customer
Preparation of the SDD ((62*100)+ (1*10))+(6210*0.05) = 6520.5
Training for Java programming language and
(15*100)+(1500*0.05)=1575
networking
Coding of the ONLINE AIRLINE TICKET
(108*100)+(10800*0.05)=11340
RESERVATION SYSTEM
Training for testing processes (4*100)+(400*0.05)=420
Testing of the ONLINE AIRLINE TICKET
(10*100)+(1000*0.05)=1050
RESERVATION SYSTEM
Review meeting for the initial product with the
(2*100)+ (200*0.05) = 210
customer
Control of the project schedule & Control of
(2*100)+ (200*0.05) = 210
the budget requirements
Review of the project risk factors (1*100)+(100*0.05)=105
Control of the quality of the initial product (3*100)+ (300*0.05) = 315
Preparation of the User Manual (57*100)+(5700*0.05)=5985
TOTAL COST for the major work activities 30933.5
Table 16:Budget allocation table
5.3 Control Plan (Subclause 5.3 of the SPMP)
In all over the document duration is 1 day means the activity will be finished in that particular
day.
5.3.1 Requirements Control Plan (Subclause 5.3.1 of the SPMP)

The schedule for the activities related to the requirements change management process and
the names of the personnel, responsible from the requirements change management activities
specified are given below.
86
with the customer
WBS # 6

with the customer
WBS # 10
The requirements change management process shall be done in the way described below, in
order to treat all the change proposals in a consistent manner:
The customer shall specify the proposed requirements changes in a written way. The change
proposal supplied shall be analyzed by the OnAir to check the validity, consistency and
accuracy of the proposal. If needed, a more specific requirements change proposal shall be
requested.
The effect of every individual change on other requirements shall be assessed. The cost of
making the change in terms of schedule, labor and monetary cost shall be estimated. In the
estimation calculations, strictly the methods followed in the software project management
plan shall be followed.
Once this analysis is completed, the customer shall be informed from the results of the
analysis in a written manner by the OnAir Customer Relations Department.
87
5.3.2 Schedule Control Plan (Subclause 5.3.2 of the SPMP)
The goal of the schedule control process is to compare the actual progress to the planned
progress and to implement corrective action, when actual progress does not conform to
planned progress.
The schedule for the activities related to the schedule control plan and the names of the
personnel, responsible from the schedule control activities specified are given below.

WBS # 8.3

WBS # 11.1.5

WBS # 13.3

WBS # 15.4
88

WBS # 18
By taking into consideration the individual work activities that are delayed and the
dependencies between the project work activities, the project schedule shall be revised. The
new estimations shall be compared with the planned values. If the total deviation from the
planned project schedule is less or equal to 5%, than the personnel working hours shall be
adjusted in a way to eliminate the deviation. If the total deviation from the planned project
schedule is greater than 5%, than the Project Management Department of the OnAir shall
directly inform the board of directors in a written manner.
In schedule calculations, strictly the methods followed in the software project management
plan shall be followed during the schedule control process.
5.3.3 Budget Control Plan (Subclause 5.3.3 of the SPMP)
N/A
5.3.4 Quality Control Plan (Subclause 5.3.4 of the SPMP)

Please see 7.4
5.3.5 Reporting Plan (Subclause 5.3.5 of the SPMP)

The reporting mechanisms of the Online Airline Ticket Reservation System shall be done as
shown in the Table 17.
Reports Submitted Submission
by Submitted To Date
Duygu Duygu Albayrak e-mail 17 October
Initial Plan OnAir Albayrak account 2006
89
OnAir Duygu Albayrak e-mail
account
Customer
http://www.bilkent.edu.tr/
~team8
Duygu
SRS OnAir Albayrak http://www.bilkent.edu.tr/ 17 November
OnAir ~team8 2006
Customer
Duygu
SPMP OnAir Albayrak 30 November
OnAir http://www.bilkent.edu.tr/ 2006
Customer ~team8
Duygu
SDD OnAir Albayrak 20 December
OnAir 2006
Table 17: Reporting Mechanisms of the Online Airline Ticket Reservation System
The Online Airline Ticket Reservation System report format shall be as follows:
1. Any kind of documentation prepared for Online Airline Ticket Reservation System shall
be in content compliance with IEEE standards [7, 8, 9, 10].
be written in Times New Roman, 12 point with 1.5 line spacing except for title page, table
of contents, list of figures, list of tables and figures.
include the page numbers at the footer on the right hand side.
include the document name and version number at the footer on the left hand side.
5. Heading 1 of any kind of documentation prepared for Online Airline Ticket Reservation
System shall be uppercase and bold. Other headings shall be title case and bold.
5.3.6 Metrics Collection Plan
• In order to provide a basis for control activities regarding schedule and budget control
processes, each OnAir member shall specify the percentage of completion for each
individual work activity under his/her responsibility.
90
• The percentage calculation shall be based on the difference between total time required
to complete the work activity and the time elapsed for the completed portion of the work
activity.
• The percentage calculation shall be based on the subjective judgment of the OnAir
members according to their historical experience.
• The specifications mentioned in the first bullet shall be submitted to the project manager
at the end of each working day of the week via e-mail.
5.4 Risk Management Plan (Subclause 5.4 of the SPMP)
The risk factors that are initially identified, the strategies developed in order to manage the
risks specified and the category of the strategy proposed for every individual risk factor are
depicted in Table 18. The proposed strategies are grouped into three categories:
1. Avoidance Strategies: These are the strategies that shall reduce the probability that the risk
will arise.
2. Minimization Strategies: These are the strategies that shall reduce the impact of the risk
on the project.
3. Contingency Plans: These are the strategies that are in place to deal with the risk.
Risk Strategy Type Strategy

Changes to software Avoidance strategy There shall be scheduled meetings with
requirements the customer as scheduled in section 5.3.1
Underestimated Minimization strategy The schedule of the project shall be
development time revised as scheduled in section 5.3.2
Underestimated Contingency plan In case of deviation from the planned
development time schedule up to 5% occurs, the working
hours of the employees shall be adjusted
as specified in section 5.3.2
Underestimated project Contingency plan As specified in section 5.3.3, a budget
cost overflow of 5% shall be allowed
Staff illness Contingency plan The personnel allocation to the work
activities shall be done in such a manner
that there shall be more overlap of work
and people, where possible. Therefore, the
people’s understanding of each other’s
jobs shall improve.
Inexperienced coding Minimization strategy Before the coding stage of the project, the
team coding team members shall be intensively
trained on the Java programming
language with a special emphasis on
project related aspects, namely, applets
91
and console application development
Unfamiliar application Minimization strategy Before the design phase of the project, the
domain design team members shall be intensively
trained on computer networking.
Incorrect judgment Minimization strategy The project manager shall have at least 5
about the probability or years of experience both on the
seriousness of risk application domain and on the Java
factors programming language
Table 18: Initially identified risk factors
The schedule for the activities related to the risk management plan and the names of the
personnel, responsible from the risk management activities specified are given as below.

WBS # 8.5
Description Specifying, analyzing and identifying the ONLINE AIRLINE

WBS # 11.1.7

WBS # 13.5

WBS # 15.6
92

WBS # 20
The risk management process is comprised four parts:
1. Risk identification is concerned with discovering new risk factors to the project. Risk
identification shall be carried out using brainstorming approach among the OnAir
members.
2. During the risk analysis part, each of the identified risks shall be considered in turn and a
judgment shall be made about the probability and seriousness of the risk. The project
manager shall judge about the probability and seriousness of the risk. The probability of
the risk indicates the chance of occurance of the risk The seriousness of the risk indicates
the importance of the risk for the project. The probability of a risk factor shall be indicated
with a scale 0.1-1, 1 showing the most probable. The seriousness of a risk factor shall be
indicated with a scale 1-10, 10 showing the most serious. Each risk factor, for which the
(probability*seriousness) value is less than 0.25, shall be neglected.
3. During the risk planning part, an avoidance strategy, a minimization strategy or a
contingency plan shall be developed for each of the risk factors in consideration.
4. Risk monitoring shall involve, regular assessment of each of the identified risks in order
to decide whether or not that risk is becoming more or less probable and whether the
effect of the risk has changed.
5.5 Project Closeout Plan (Subclause 5.5 of the SPMP)
93
The ONLINE AIRLINE TICKET RESERVATION SYSTEM closeout plan shall include
three kinds of plan. First plan is the archiving project materials plan. Second plan is the staff
reassignment plan and third plan is the final report which shall include the lessons learned.
The archiving of the metarials of the ONLINE AIRLINE TICKET RESERVATION

SYSTEM shall be done by storing the documents in the personel computers of all members of
the OnAir. The archiving of the metarials of the ONLINE AIRLINE TICKET
RESERVATION SYSTEM shall be also stored in the account of Özge Koray.
Except the above mentined archiving methods, all the documentions of the ONLINE
AIRLINE TICKET RESERVATION SYSTEM shall be uploaded to
http://www.bilkent.edu.tr/~team8.html address.
The staff reassignment plan of the ONLINE AIRLINE TICKET RESERVATION SYSTEM
shall depend on the control activities if there exists inconsistency with the budget or schedule
plan, then the OnAir members shall be reassigned to the work activities in order to finalize the
project milestones.
94
6 Technical Process Plan (Clause 6 of the SPMP)
6.1 Process Model (Subclause 6.1 of the SPMP)
The software life cycle of the Online Airline Reservation System Project shall be the waterfall
model.
The detail of the software process is shown in Table 19.
Deliverable Successor
Predecessor
No Documentation Activity No
Activity Name Due Date Activity No
Name
Initial Plan
Documentation -
1
Initial Plan 17 October 2006 1
SRS 1
Documentation
2 17 November 2006
SRS 2
SPMP 2
Documentation
3
SPMP 30 November 2006 3
SDD 3
Documentation
4
SDD 20 December 2006 4
5
Demonstration of Product - 02 May 2007 5
5
Final Product
6
Delivery of Final Product 09 May 2006 6
95
Table 19: Details of software process
6.2 Methods, Tools and Techniques
The methods, tools, and techniques that shall be used for the Online Airline Reservation
System Project are explained below.
Software process model: Waterfall model

Software programming language: Java2
Software design methodology: Object-oriented analysis & design technique
Software documentation: MS Word 2003, MS Project 2003
Animations: Flash MX
To store and retrieve the user and customer information: Mysql
Standard for software requirements specification documentation: IEEE Std. 1830-1998 [2]
Standard for software project management plan documentation: IEEE Std. 1058-1998 [1]
Standard for software design description documentation: IEEE Std. 1016-1998 [3]
Standard for user manual development: IEEE Std. 1063-1997 [4]
6.3 Infrastructure Plan
There is no interface between the Online Reservation System and the hardware on which it
shall operate. So, the hardware configuration specified below shall not be taken either as a
hardware interface of the Online Airline Reservation System or as a minimum required
configuration. The hardware configuration specified below indicates resources, which are
already available to OnAir and which shall be allocated to the Online Airline Reservation
System Project.
During the development of the Online Reservation System, team members will use their own
computers to develop software. Ms Project 2003 shall be used as project management
software. Windows XP must be installed Flash Player for the operating systems.
The development environment for the Online Airline Reservation System is represented
below. The specified infrastructure is already available and shall be provided to each
individual, who is allocated to the Online Airline Reservation System project in the OnAir.
Hardware A microprocessor having 866 MHz clock speed

configuration 128 MB RAM
96
10 GB total hard disk space
8 MB graphics card memory
A network interface card supporting 100 Mbps connections
Operating system Microsoft Windows XP
Network connection 100 Mbps network connection
Software Java2 Standard Edition v.1.3.1_02 from Sun Microsystems
Apache Web Server v.1.3.23
Microsoft Internet Explorer v.5.5
Netscape Navigator v.4.79
Microsoft Word 2003
Microsoft Project 2003
Table 20: Details of Infrastructure Plan
6.4 Product Acceptance Plan
The acquirer acceptance of the delivered work products generated shall be as follows:
1. Any deliverable work product shall satisfy 100% of the requirements specified in the
software requirements specification, where each requirement specification shall be
weighted equally.
2. If it is proven that a work product delivered to the customer within its scheduled time
period satisfies more than 90% of the requirements, OnAir shall be given an additional
one week time to modify the work product.
3. If it is proven that a work product delivered to the customer within its scheduled time
period satisfies less than 90% of the requirements, OnAir shall pay $100 for each working
day passed to the delivery of the modified version, satisfying 100% of the requirements
specified in the software requirements specification.
97
7 Supporting Process Plans
7.1 Configuration Management Plan
All the project deliverables are to be considered as configuration items. The configuration
item as well as its file would be named as the document name followed by the version
number. For example, all the preliminary versions that are submitted to Beyhan Akporay for
review would be named with the abbreviation followed by 1.0, 2.0... After Beyhan Akporay
approves the first version, this baseline document will be version 1.1, 2.1…
Document files will be in MS Word 2003 format and project plan schedule files will be in MS
Project 2003 format.
7.2 Verification and Validation Plan
The details of the verification and validation plan shall be done by testing activities and they
are depicted in Table 21. Testing of the Online Airline Ticket Reservation System shall be
done by the OnAir testing team. However the programmer and the testing engineer shall not
be the same person.
The testing activities shall be composed of the verification of the correctness of the
requirements specified in the software requirement specification of the Online Airline Ticket
Reservation System [10] for the corresponding work activity in the coding phase of the
Online Airline Ticket Reservation System. No special method will be used by OnAir
members while doing testing activities since there is not enough time to do so.
WBS #: Work Activity Duration Start Date End Date

(d=day)
15 Testing of the Online Airline Ticket 15d Wed 5/2/07 Wed 5/16/07
Reservation System
15.1 Testing of the common functions of 1d Sat 5/5/07 Sat 5/5/07
all users
15.1.1 Testing of the user authentication 1d Sat 5/5/07 Sat 5/5/07
function
15.2 Testing of the functions for root 2d Mon Tue 5/15/07
5/14/07
98
15.2.1 Testing of the user addition function 2d Mon Tue 5/15/07
5/14/07
15.2.2 Testing of the user deletion function 2d Mon Tue 5/15/07
5/14/07
15.2.3 Testing of the user update function 2d Mon Tue 5/15/07
5/14/07
15.2.4 Testing of the chat group addition 2d Mon Tue 5/15/07
function 5/14/07
15.2.5 Testing of the chat group deletion 2d Mon Tue 5/15/07
function 5/14/07
15.2.6 Testing of the chat group update 2d Mon Tue 5/15/07
function 5/14/07
15.2.7 Testing of the room addition 2d Mon Tue 5/15/07
function 5/14/07
15.2.8 Testing of the room deletion 2d Mon Tue 5/15/07
function 5/14/07
15.2.9 Testing of the room update function 2d Mon Tue 5/15/07
5/14/07
15.3 Testing of the functions for 1d Wed Wed 5/16/07
instructor, students & customers" 5/16/07
15.3.1 Testing of the chat function 1d Wed Wed 5/16/07
5/16/07
Table 21: Details of Verification and Validation Plan
7.3 Documentation Plan
The IEEE standards would be followed for all documentation purposes. All the documents
would be discussed with Beyhan Akporay before their baseline versions are issued and
distributed. Moreover before submitting the major milestones, a meeting will be done with the
customer. All the documentation plans will be prepared by OnAir team members.
7.4 Quality Assurance Plan
Verification, validation, reviews and configuration management are the methods that using for
quality assurance.
Design team is responsible for both verification and validation. Work products are ensured
right and align with the requirements set in SRS after Internal reviews and review meeting
with OnAir.
99
The instructor holds review meetings to right requirements and OnAir reviews the work
products and corrected them according to associated standards [1, 2, 3, and 4]. At the end,
work product will be again provided by OnAir as good quality.
7.5 Review Plan

N/A
7.6 Problem Resolution Plan
Scheduled problems which would arise from the deviations of the actual planning will be
solved and updated by the project manager. The project manager will reassign the team
members to the work activities in order to resolve the scheduled problems.
Technical problems will be solved by the OnAir group members.
The member, who identified the problem in the OnAir group, will communicate to the other
group members.
100
101

Airline Reservation System

Uploaded by

Copyright:

Available Formats

Airline Reservation System

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Airline Reservation System

Uploaded by

Copyright:

Available Formats

What is the goal of the Software Project Management Plan?

What is the goal of the Software Project Management Plan?

What standards is this project following?

What standards is this project following?

SOFTWARE PROJECT MANAGEMENT PLAN

ONLINE AIRLINE TICKET

Table 1: Schedule of the Project........................................................................................4

Figure 1: External Interfaces of the ONLINE AIRLINE TICKET RESERVATION

1.1 Project Summary (Subclause 1.1 of the SPMP)

1.1.1 Purpose, Scope and Objectives (Subclause 1.1.1 of the SPMP)

The objectives of the ONLINE AIRLINE TICKET RESERVATION SYSTEM are:

• Add/Delete Airline Manager Information

requirements of the Online Airline Ticket Reservation System.

Initial Plan [9]

1.1.2 Assumptions And Constraints (Subclause 1.1.2 of the SPMP)

The assumptions of the project are;

The constraints of the project are;

• The schedule of the project is predefined by the customer.

1.1.3 Functions Of Project

1.1.4 Project deliverables (Subclause 1.1.3 of the SPMP)

• Initial Plan: The document will be prepared and submitted to

1.1.5 Schedule and Budget Summary (Subclause 1.1.4 of the SPMP)

Due Date Document / Activity Name

Table 1: Schedule of the Project

As explained in subclause 1.1.2, no real budget is associated with ONLINE AIRLINE

1.2 Evolution of Plan (Subclause 1.2 of the SPMP)

This is the initial version of the Software Project Management Plan.

Due Date Document Status

17 October 2006 Initial Plan Created

Table 2: Update Plan of the SPMP

CTIS: Computer Technology and Information System

IEEE: Institute of Electrics & Electronics Engineering

OnAir: will be referred to software development team

PC: Personal Computer

SRS: Software Requirements Specification

responsibilities to manage the running system.

Member: the user who is signed up before.

Project Deliverable: A work product to be delivered to the acquirer. Quantities, delivery

dates, and delivery locations are specifying in a project agreement. [1]

User: refers to people who will see the routes.

User id: A set of characters that identifies the user.

manager refers to Beyhan Akporay.

use the system

satisfy the terms and conditions of a project agreement

the parties involved. [1]

supplier may be members of same organization. [1]

Project Deliverable: A work product to be delivered to the acquirer. Quantities, delivery

dates, and delivery locations are specifying in a project agreement. [1]

4.1 External Interfaces (Subclause 4.1 of SPMP)

Figure 1: External Interfaces of the ONLINE AIRLINE TICKET RESERVATION SYSTEM

List of Responsible People to Contact:

Bilkent University (The Acquiring Organization): CTIS Department

The Quality Control Manager: CTIS Instructor (Beyhan Akporay)

4.2 Internal Structure

a matrix organization. The internal structure of the project is given in Figure 2.

Project Management Customer Relations Training

Requirements Design Coding Testing Documentation

4.3 Roles and Responsibilities

Name E-mail address Roles

Table 3: Roles and Responsibilities of OnAir Members