Project Plan: For Hotel Reservation System (HRS)
Project Plan: For Hotel Reservation System (HRS)
Project Plan: For Hotel Reservation System (HRS)
Version 1.0
Cem Oguzhan
CIS 895 – MSE Project
Kansas State University
1. Task Breakdown..........................................................................................................3
1.1. Inception Phase....................................................................................................3
1.2. Elaboration Phase................................................................................................3
1.3. Production Phase.................................................................................................3
2. Cost Estimate...............................................................................................................4
2.1. COCOMO............................................................................................................4
3. Architecture Elaboration Plan......................................................................................5
3.1. Revision of Vision Document.............................................................................6
3.2. Revision of Project Plan......................................................................................6
3.3. Architecture Design.............................................................................................6
3.4. Development of Prototype...................................................................................6
3.5. Test Plan..............................................................................................................6
3.6. Formal Technical Inspections..............................................................................6
3.7. Formal Requirements Specification....................................................................6
1. Task Breakdown
In the first presentation, the developer will demonstrate at least one executable prototype. The
executable prototype will display the feasibility of the project.
The inception phase will be completed once the committee members approve all required
documentation after the first presentation.
The elaboration phase will be completed once the committee members approve all required
documentation after the second presentation.
The production phase will be completed once the committee members approve all required
documentation and final version of the software product after the third and the last presentation.
The grant chart below shows a schedule for finishing the tasks in each phase.
2. Cost Estimate
2.1. COCOMO
The COnstructive COst MOdel (COCOMO) developed by Barry Boehm will be used to estimate
project effort and time. There are three modes, based on software domains, to estimate project
effort and time in COCOMO. These modes are organic, semidetached and embedded. Organic
mode projects are less complex developments and it has fair flexibility. Embedded mode projects
are usually similar to defense projects. Complexity, reliability and real-time issues are played
bigger role in embedded mode projects. Semidetached mode projects represent between organic
and embedded mode projects. The Hotel Reservation System is a web application, which will
have average complexity and fair flexibility. Therefore, the Hotel Reservation System is an
organic mode project. COCOMO cost estimation for organic mode projects follow this formula:
Effort = 3.2*EAF*(Size) ^1.05
Time = 2.5*(Effort) ^0.38
where:
Effort = number of staff months
EAF = Effort Adjustment Factor
Size = number of lines of code for completed product. It is measured in KLOC (thousands of
lines of code)
Time = total number of months
The Effort Adjustment Factor is the product of the 15 adjustment parameters. Each adjustment
parameter is defined as very low, low, nominal, high, or very high. The table 1 below shows all
the adjustment factors and their ranges.
The EAF value is calculated to 1.9. I looked at similar web application examples and based on the HRS
prototype, I estimated the size to be 2400 LOC.
I think that 15.2 staff months for Effort is kind of high for a student project. The reason for that COCOMO
is generally designed for large project, which has more than one developer. This is a school project and it
has only one developer. One developer means there is no team meetings, reviews and integration of the
parts of the product. Also, the application is not depended other application. Therefore, I think that 8-9 staff
months would be more realistic value for Effort. The new development time can be calculated as: