Proposal

Document Sample
Proposal Powered By Docstoc
					                 ZEBRAWARE




         Proposal
Dodo Airlines Scheduling System
      Bob Babilon, Joe Brock, Mark Woodraska
                    12/6/2008
Proposal Document                                                                                                                                  Version 1.1
Dodo Airlines Scheduling System                                                                                                                       12-6-08

Table of Contents
Table of Figures ............................................................................................................................................. 4
Letter of Proposal ......................................................................................................................................... 5
Scope ............................................................................................................................................................. 6
   Background of the System ........................................................................................................................ 6
       History of the Airline Industry ............................................................................................................... 6
       Existing System...................................................................................................................................... 7
       Market Research ................................................................................................................................... 8
Solution ....................................................................................................................................................... 10
   Why Choose Zebraware .......................................................................................................................... 10
   Technical ................................................................................................................................................. 10
   Financial .................................................................................................................................................. 11
   About Zebraware .................................................................................................................................... 11
   Organization Chart .................................................................................................................................. 11
   Zebraware Team ..................................................................................................................................... 12
       Bob Babilon ......................................................................................................................................... 12
       Joe Brock ............................................................................................................................................. 12
       Mark Woodraska................................................................................................................................. 12
Implementation Estimate ........................................................................................................................... 13
   Cost Analysis ........................................................................................................................................... 17
       Summary ............................................................................................................................................. 17
   Estimate Model ....................................................................................................................................... 18
Duration and Staffing .................................................................................................................................. 19
   Staffing .................................................................................................................................................... 19
   Duration .................................................................................................................................................. 19
Work Breakdown Structure ........................................................................................................................ 20
Activity Graph/Milestones .......................................................................................................................... 23
Critical Path Analysis ................................................................................................................................... 24
Project Schedule ......................................................................................................................................... 26
Project Team Organization ......................................................................................................................... 27


Zebraware, LLC.                                                                                                Phone: (605) 555-1234
Brookings, SD 57006                                                                                            Email: support@zebraware.com

                                                                        Page 2 of 40
Proposal Document                                                                                                                                Version 1.1
Dodo Airlines Scheduling System                                                                                                                     12-6-08

       Bob Babilon – Team Manager ............................................................................................................. 27
       Joe Brock – Lead Developer ................................................................................................................ 27
       Mark Woodraska – Lead Developer.................................................................................................... 27
Quality Assurance Plan ............................................................................................................................... 27
Documentation Plan ................................................................................................................................... 28
Data Management Plan .............................................................................................................................. 29
   Airline Scheduling System ....................................................................................................................... 29
   Data Backup System................................................................................................................................ 29
Resource Management Plan ....................................................................................................................... 30
Risk Management Plan ............................................................................................................................... 30
   List of Risks .............................................................................................................................................. 31
   Mitigation and Contingency Plan ............................................................................................................ 31
Test Plan ...................................................................................................................................................... 33
Security Plan................................................................................................................................................ 34
Server Selection Plan .................................................................................................................................. 35
   Main Server ............................................................................................................................................. 35
       HP ProLiant DL580 G5                  Dell PowerEdge 2950 III ............................................................................... 35
   Client Terminals ...................................................................................................................................... 36
       HP Compaq dc7800 Dell OptiPlex 755 ............................................................................................. 36
   Client Monitors ....................................................................................................................................... 36
       Dell 1708FP            ViewSonic VA703MB ................................................................................................... 36
   Workstation Printers ............................................................................................................................... 37
       HP CM6030f Ricoh Aficio MP C3000 ................................................................................................ 37
Project Deliverables .................................................................................................................................... 37
   Airline Scheduling System Software ....................................................................................................... 37
   System Proposal ...................................................................................................................................... 37
   Requirements Documentation ............................................................................................................... 38
   Design Documentation ........................................................................................................................... 38
Alternatives ................................................................................................................................................. 38
   Server Operating System ........................................................................................................................ 38


Zebraware, LLC.                                                                                              Phone: (605) 555-1234
Brookings, SD 57006                                                                                          Email: support@zebraware.com

                                                                       Page 3 of 40
Proposal Document                                                                                                                           Version 1.1
Dodo Airlines Scheduling System                                                                                                                12-6-08

   Client Operating System ......................................................................................................................... 38
Terms and Conditions ................................................................................................................................. 39
   Limited Warranty .................................................................................................................................... 39
   Limitations on Liability ............................................................................................................................ 39
   General Provisions .................................................................................................................................. 39




Table of Figures

Figure 1: Existing Dodo Airlines System ........................................................................................................ 8
Figure 2: Zebraware's Proposed System ..................................................................................................... 10
Figure 3: Zebraware Organization Chart..................................................................................................... 11
Figure 4: Web Server WBS .......................................................................................................................... 20
Figure 5: Database Server WBS................................................................................................................... 21
Figure 6: Client Application WBS ................................................................................................................ 22
Figure 7: Activity Graph .............................................................................................................................. 23
Figure 8: Critical Path .................................................................................................................................. 25
Figure 9: Project Schedule .......................................................................................................................... 26




Zebraware, LLC.                                                                                          Phone: (605) 555-1234
Brookings, SD 57006                                                                                      Email: support@zebraware.com

                                                                     Page 4 of 40
Proposal Document                                                                       Version 1.1
Dodo Airlines Scheduling System                                                            12-6-08

Letter of Proposal

Dear Dr. Shin,

Zebraware, LLC, would like to thank Dodo Airlines for accepting our preliminary project
proposal for implementing a complete airline scheduling system. As an established software
development company, our experience will be used to provide the best system possible. Our
company was established in 2004 to provide quality and affordable software packages to a
variety of business types. Our previous customers have been very satisfied with our web
applications, client applications, and server systems, and we hope to make Dodo Airlines our
next satisfied customer.

After informing the company of the proposal, our developers begin working on prototypes and
ideas to solve the problem. We examined existing airline scheduling systems and studied the
basic functionalities of such as system. In order to ensure your system is using the latest
technological advances, we will investigate all known systems and select the most advanced
system. From here we will modify the system and improve it.

Implementing this system will take approximately three months to complete. To ensure we are
able to implement the entire system in this time constraint, we will keep the web interface
minimal and utilize existing websites that provide eager flight customers to purchase flight
tickets. We will focus on the primary functions of this system: airline scheduling. Thus the client
application will be a sophisticated graphical user interface capable of managing Dodo's entire
airline system. Our cost will be based on salary including the man hours. You will find all the
details about the price and features in this proposal document and the requirements
document.



Sincerely,

Bob Babilon
President of Zebraware, LLC




Zebraware, LLC.                                                    Phone: (605) 555-1234
Brookings, SD 57006                                                Email: support@zebraware.com

                                           Page 5 of 40
Proposal Document                                                                        Version 1.1
Dodo Airlines Scheduling System                                                             12-6-08

Scope
Background of the System
In order to present a new solution for an airline scheduling system, the history of the airline
industry must first be studied and the past methods must be analyzed.

History of the Airline Industry
In 1978, the U.S. airline industry deregulation lowered barriers for new airlines. In this period,
new start-ups entered during downturns in the normal 8-10 year business cycle. At that time,
they find aircraft, are financed, contract hangar and maintenance services, train new
employees, and recruit laid off staff from other airlines.

As the business cycle returned to normalcy, major airlines dominated their routes through
aggressive pricing and additional capacity offerings, often swamping new startups. Only
America West Airlines (which has since merged with US Airways) remained a significant survivor
from this new entrant era, as dozens, even hundreds, have gone under.

In many ways, the biggest winner in the deregulated environment was the air passenger.
Indeed, the U.S. witnessed an explosive growth in demand for air travel, as many millions who
had never or rarely flown before became regular fliers, even joining frequent flyer loyalty
programs and receiving free flights and other benefits from their flying. New services and
higher frequencies meant that business fliers could fly to another city, do business, and return
the same day, for almost any point in the country. Air travel's advantages put intercity bus lines
under pressure, and most have withered away.

By the 1980s, almost half of the total flying in the world took place in the U.S., and today the
domestic industry operates over 10,000 daily departures nationwide.

Toward the end of the century, a new style of low cost airline emerged, offering a no-frills
product at a lower price. Southwest Airlines, JetBlue, AirTran Airways, Skybus Airlines and other
low-cost carriers began to represent a serious challenge to the so-called "legacy airlines", as did
their low-cost counterparts in Europe, Canada, and Asia. Their commercial viability represented
a serious competitive threat to the legacy carriers. However, of these, ATA and Skybus have
since ceased operations.

Thus the last 50 years of the airline industry have varied from reasonably profitable, to
devastatingly depressed. As the first major market to deregulate the industry in 1978, U.S.
airlines have experienced more turbulence than almost any other country or region. Today,
with the sole exception of American Airlines, every legacy carrier in the United States has

Zebraware, LLC.                                                    Phone: (605) 555-1234
Brookings, SD 57006                                                Email: support@zebraware.com

                                            Page 6 of 40
Proposal Document                                                                        Version 1.1
Dodo Airlines Scheduling System                                                             12-6-08

operated under Chapter 11 bankruptcy provisions or has gone out of business.
(From http://en.wikipedia.org/wiki/Airline )

Existing System
Dodo airlines are currently using a “Big Board” scheduling system where each flight is assigned
into a time slot on the big board. This is both time consuming to create and hard to manage
because any changes to flight departures must be relayed to the customer by phone call, snail
mail, or over the airports local Public Announcement system to give travelers information on
any flight changes for that particular day’s flights. With an electronic system, the user will be
able to check their flight’s departure time 24 hours a day. All flight changes will be updated to
the website within five minutes of the decision being made.

Currently ticketing is handled by the airport’s terminal employees who will schedule flights for
the customer either at the terminal or they will take telephone ticketing calls. This is a waste of
paper, since all tickets are sent out via mail, with flight confirmations sent out a week before
the scheduled flight. With the Zebraware online ticketing system, the user will be able to see
how many seats and the open seat layout of the plane, with up to the minute accuracy.
Ticketing can be done by both of the old methods (walk-in and telephone) as well as online
ticketing.

Currently all planes undergo an after flight inspection to ensure that the plane is in proper
condition for its next flight. All of these inspections are hard copy paper reports which after
completion must be transported half a mile back to the airport’s regional manager who must
approve the inspection status before the plane is cleared for the next flight. This is very time
consuming. With this method it is hard to keep track of the maintenance history of the airplane
since all reports are filed after approval, and all repair reports are filed as well. With the
Zebraware Maintenance Tracker system all of inspection and repair reports will be submitted
electronically. This gives a lot more information to the regional manager, because if he sees
something suspicious in the inspection report he can bring up all previous inspection and repair
reports within seconds.




Zebraware, LLC.                                                    Phone: (605) 555-1234
Brookings, SD 57006                                                Email: support@zebraware.com

                                            Page 7 of 40
Proposal Document                                                                              Version 1.1
Dodo Airlines Scheduling System                                                                   12-6-08

The figure below illustrates how the current system for Dodo Airlines is being used.

 Submit for Review




                                                         Create Flight Schedule



                                  Reject
                                                                                      Inform Customers


         Analyze                                              Approve




                                  Figure 1: Existing Dodo Airlines System

Market Research
Airlines assign prices to their services in an attempt to maximize profitability. The pricing of
airline tickets has become increasingly complicated over the years and is now largely
determined by computerized yield management systems.

Because of the complications in scheduling flights and maintaining profitability, airlines have
many loopholes that can be used by the knowledgeable traveler. Many of these airfare secrets
are becoming more and more known to the general public, so airlines are forced to make
constant adjustments.

Most airlines use differentiated pricing, a form of price discrimination, in order to sell air
services at varying prices simultaneously to different segments. Factors influencing the price
Zebraware, LLC.                                                             Phone: (605) 555-1234
Brookings, SD 57006                                                         Email: support@zebraware.com

                                              Page 8 of 40
Proposal Document                                                                         Version 1.1
Dodo Airlines Scheduling System                                                              12-6-08

include the days remaining until departure, the booked load factor, the forecast of total
demand by price point, competitive pricing in force, and variations by day of week of departure
and by time of day. Carriers often accomplish this by dividing each cabin of the aircraft (first,
business and economy) into a number of travel classes for pricing purposes.

A complicating factor is that of origin-destination control ("O&D control"). Someone purchasing
a ticket from Melbourne to Sydney (as an example) for AU$200 is competing with someone else
who wants to fly Melbourne to Los Angeles through Sydney on the same flight, and who is
willing to pay AU$1400. Should the airline prefer the $1400 passenger, or the $200 passenger
plus a possible Sydney-Los Angeles passenger willing to pay $1300? Airlines have to make
hundreds of thousands of similar pricing decisions daily.

The advent of advanced computerized reservations systems in the late 1970s, most notably
Sabre, allowed airlines to easily perform cost-benefit analyses on different pricing structures,
leading to almost perfect price discrimination in some cases (that is, filling each seat on an
aircraft at the highest price that can be charged without driving the consumer elsewhere).

The intense nature of airfare pricing has led to the term "fare war" to describe efforts by
airlines to undercut other airlines on competitive routes. Through computers, new airfares can
be published quickly and efficiently to the airlines' sales channels. For this purpose the airlines
use the Airline Tariff Publishing Company (ATPCO), who distribute latest fares for more than
500 airlines to Computer Reservation Systems across the world.

The extent of these pricing phenomena is strongest in "legacy" carriers. In contrast, low fare
carriers usually offer preannounced and simplified price structure, and sometimes quote prices
for each leg of a trip separately.

Computers also allow airlines to predict, with some accuracy, how many passengers will
actually fly after making a reservation to fly. This allows airlines to overbook their flights
enough to fill the aircraft while accounting for "no-shows," but not enough (in most cases) to
force paying passengers off the aircraft for lack of seats. Since an average of ⅓ of all seats are
flown empty, stimulative pricing for low demand flights coupled with overbooking on high
demand flights can help reduce this figure.
(From http://en.wikipedia.org/wiki/Airline )




Zebraware, LLC.                                                     Phone: (605) 555-1234
Brookings, SD 57006                                                 Email: support@zebraware.com

                                            Page 9 of 40
Proposal Document                                                                        Version 1.1
Dodo Airlines Scheduling System                                                             12-6-08

Solution
The following figure depicts the system that will be implemented by Zebraware for Dodo
Airline’s new airline scheduling system.

                                    Servers




       Database
                                                                      Dodo Admin




                                                                                       Users

                                  Figure 2: Zebraware's Proposed System

Why Choose Zebraware
Zebraware’s solution to an inefficient method of maintaining and scheduling a complete airline
system is provide an up-to-date computerized system complete with a database server, a web
server with a full blown user interface for customers, and a complete client application for
internal use. Our system will be efficient, time-saving, and, most important, easy to use. With
our 10 years of experience providing complete software systems, our company has proven itself
for delivering reliable software in a reasonable timeframe with an affordable cost.

Technical
The Zebraware team is committed to using the latest proven technologies to ensure that our
customers receive high quality and visually pleasing applications. By staying ahead of the curve,
our company can put itself ahead of our competitors by complying with the latest web
standards and practices.



Zebraware, LLC.                                                       Phone: (605) 555-1234
Brookings, SD 57006                                                   Email: support@zebraware.com

                                             Page 10 of 40
Proposal Document                                                                         Version 1.1
Dodo Airlines Scheduling System                                                              12-6-08

Financial
One of the main concerns at Zebraware is to keep our costs low, which results in a lower total
cost for our customers. We are very diligent in our project planning phase so that our coding
and testing phases can be performed more efficiently. For more information about
Zebraware’s cost saving procedures, refer to the Resource Management Plan later in the
proposal.

About Zebraware
Zebraware has been designing software for a variety of companies since 2004. We stand by all
of our software products from inception to delivery. Our software engineers will meet with you
on a regular basis to assure you our word is fulfilled as you expect. We can guarantee that our
software is more stable and reliable than any other leading software development company in
the world. We dedicate our lives to our software. No exceptions.

Organization Chart

                                              Bob Babilon
                                            Company President




                        Bob Babilon              Joe Brock          Mark Woodraska
                      Project Manager         Project Manager       Project Manager



                                  Figure 3: Zebraware Organization Chart




Zebraware, LLC.                                                        Phone: (605) 555-1234
Brookings, SD 57006                                                    Email: support@zebraware.com

                                             Page 11 of 40
Proposal Document                                                                 Version 1.1
Dodo Airlines Scheduling System                                                      12-6-08

Zebraware Team
Zebraware is composed of several small teams, each of which works together to perform tasks
in an efficient manner. Our three team leaders work closely with each other and our company
president to ensure that all tasks stay on schedule.

Bob Babilon
   Two years corporate experience
   Four years self interest
   Programming languages: C#, .NET Framework, C++, HTML, PHP, XSLT, XML, Python, Java

Joe Brock
    Four years at Zebraware
    Specialized in user applications
    Programming languages: C#, .NET Framework, C++, and XML

Mark Woodraska
   Four years at Zebraware.
   Specialized in Windows applications using .NET Framework
   Programming languages: C#, .NET Framework, SQL, C++, Java, and XML




Zebraware, LLC.                                               Phone: (605) 555-1234
Brookings, SD 57006                                           Email: support@zebraware.com

                                        Page 12 of 40
Proposal Document                                                        Version 1.1
Dodo Airlines Scheduling System                                             12-6-08

Implementation Estimate
Activity/Function                                   Approximate     Time estimate
                                                    Lines of Code     (in hours)
1 Server
1.1 Web Server
1.1.1 Login Page                                        200                2
1.1.1.1 Login Script                                     20               0.5
1.1.2 Logout Page                                        50               0.5
1.1.2.1 Logout Script                                    10               0.5
1.1.3 Home Page                                         400                3
1.1.3.1 Home Script                                      60                1
1.1.4 401 Page                                           40               0.5
1.1.5 Search flight schedule page                       300                2
1.1.5.1 Search script                                    70                1
1.1.6 Search results page                               250                2
1.1.6.1 Search results script                            50               0.5
1.1.7 Purchase Ticket page                              400                3
1.1.7.1 Send confirm email script                        30               0.5
1.1.7.2 Send info DB script                              40                1
1.1.7.3 Gather info script                               40                1
1.1.8 Registration page                                 350               2.5
1.1.8.1 Send info DB script                              50                1
1.1.8.2 Gather info script                               50                1
1.1.8.3 Send confirm email script                        30               0.5
1.1.9 Profile page                                      300                3
1.1.9.1 View profile                                    150                2
1.1.9.2 Update profile page                             300                2
1.1.9.2.1 Update profile script                          60               0.5
1.1.10 View flight info page                            300                3
1.1.10.1 Flight info script                              60                1
1.1.11 View flight paths page                           300                2
1.1.11.1 Flight paths script                             50                1
1.2 Database
1.2.1 Add procedures
1.2.1.1 Aircraft                                         50                1
1.2.1.2 Customers                                        50                1
1.2.1.3 Pilots                                           50                1
1.2.1.4 Flight logs                                      50                1
1.2.1.5 Maintenance logs                                 50                1

Zebraware, LLC.                                       Phone: (605) 555-1234
Brookings, SD 57006                                   Email: support@zebraware.com

                                    Page 13 of 40
Proposal Document                                                            Version 1.1
Dodo Airlines Scheduling System                                                 12-6-08

Activity/Function                                       Approximate     Time estimate
                                                        Lines of Code     (in hours)
1.2.1.6 Flight Schedules                                     100              1.5
1.2.1.7 Maintenance schedules                                 50               1
1.2.2 Get procedures
1.2.2.1 Aircraft                                             20               0.5
1.2.2.2 Customers                                            20               0.5
1.2.2.3 Pilots                                               20               0.5
1.2.2.4 Flight logs                                          20               0.5
1.2.2.5 Maintenance logs                                     20               0.5
1.2.2.6 Flight schedules                                     20               0.5
1.2.2.7 Maintenance schedules                                20               0.5
1.2.3 Update procedures
1.2.3.1 Aircraft                                             40                1
1.2.3.2 Customers                                            40                1
1.2.3.3 Pilots                                               40                1
1.2.3.4 Flight logs                                          40                1
1.2.3.5 Maintenance logs                                     40                1
1.2.3.6 Flight schedules                                     60                1
1.2.3.7 Maintenance schedules                                40                1
1.2.4 Remove Procedures
1.2.4.1 Aircraft                                             50               0.5
1.2.4.2 Customers                                            50               0.5
1.2.4.3 Pilots                                               50               0.5
1.2.4.4 Flight logs                                          50               0.5
1.2.4.5 Maintenance logs                                     50               0.5
1.2.4.6 Flight schedules                                     60                1
1.2.4.7 Maintenance schedules                                50               0.5
1.2.5 Search flight procedures
1.2.5.1 One way static start/end                             40                1
1.2.5.2 Round trip static start/end                          40                1
1.2.5.3 One way flexible start/end                           40                1
1.2.5.4 Round trip flexible start/end                        40                1
1.2.6 Search maintenance procedures
1.2.6.1 Based on aircraft                                    40                1
1.2.6.2 Based on date/time                                   40                1
1.2.6.3 Based on aircraft and/or date/time                   40                1
1.2.7 Search customers procedures
1.2.7.1 Based on customer info                               50                1

Zebraware, LLC.                                           Phone: (605) 555-1234
Brookings, SD 57006                                       Email: support@zebraware.com

                                        Page 14 of 40
Proposal Document                                                         Version 1.1
Dodo Airlines Scheduling System                                              12-6-08

Activity/Function                                    Approximate     Time estimate
                                                     Lines of Code     (in hours)
2 Client App
2.1 Ticketing
2.1.1 Sell tickets                                        20                1
2.1.1.1 Select customer                                   30                1
2.1.1.2 Select flight                                     30                1
2.1.1.3 Sell ticket                                       40               1.5
2.1.1.4 Update database                                   20               0.5
2.1.2 Verify ticket                                       20               0.5
2.1.2.1 Select ticket                                     30                1
2.1.2.2 Verify flight on schedule                         40               1.5
2.1.2.3 Verify customer correct                           40               1.5
2.1.3 Refund tickets                                      20               0.5
2.1.3.1 Select customer                                   30                1
2.1.3.2 Select flight                                     30                1
2.1.3.3 Select ticket                                     30                1
2.1.3.4 Update database                                   40               1.5
2.1.4 Confirm flight                                      20               0.5
2.1.4.1 Select flight                                     30                1
2.1.4.2 Check status                                      40                1
2.2 Administrative
2.2.1 Employee inventory                                  30                1
2.2.1.1 Add new pilot                                     60                2
2.2.1.2 Remove pilot                                      20               0.5
2.2.1.3 Update pilot profile                              40                1
2.2.2 Manual flight scheduling                            30                1
2.2.2.1 Schedule flight                                   60               1.5
2.2.2.1.1 Check conflicts                                 50               1.5
2.2.2.1.2 Upload to database                              50                1
2.2.2.2 Reschedule (update) flight                        40                1
2.2.2.2.1 Check conflicts                                 50               1.5
2.2.2.2.2 Upload to database                              50                1
2.2.2.3 Cancel flight                                     30                1
2.2.2.4 Delay flight                                      40                1
2.2.3 Auto flight scheduling                              30               0.5
2.2.3.1 Collect schedules                                 30               0.5
2.2.3.2 Analyze schedules                                 80               2.5
2.2.3.3 Check conflicts                                   50                1

Zebraware, LLC.                                        Phone: (605) 555-1234
Brookings, SD 57006                                    Email: support@zebraware.com

                                     Page 15 of 40
Proposal Document                                                          Version 1.1
Dodo Airlines Scheduling System                                               12-6-08

Activity/Function                                     Approximate     Time estimate
                                                      Lines of Code     (in hours)
2.2.3.4 Upload to database                                  50               1
2.2.4 Aircraft inventory                                    30               1
2.2.4.1 Add new aircraft                                    40               1
2.2.4.2 Remove aircraft                                     20              0.5
2.2.4.3 Update aircraft                                     40               1
2.2.5 Manual maintenance scheduling                         40               1
2.2.5.1 Schedule maintenance                                50               1
2.2.5.1.1 Check conflicts                                   60              1.5
2.2.5.1.2 Upload to database                                50               1
2.2.5.2 Reschedule (update) maintenance                     40               1
2.2.5.2.1 Check conflicts                                   40               1
2.2.5.2.2 Upload to database                                50               1
2.2.5.3 Cancel maintenance                                  30              0.5
2.2.6 Customer info management                              80               2
2.2.6.1 Add new customer                                    60               2
2.2.6.2 Remove customer                                     20              0.5
2.2.6.3 Update customer profile                             60              1.5
2.2.7 Auto maintenance scheduling                           40               1
2.2.7.1 Collect schedules                                   60              1.5
2.2.7.2 Analyze schedules                                   80              2.5
2.2.7.3 Check conflicts                                     40               1
2.2.7.4 Upload to database                                  50               1
2.3 Browse/search
2.3.1 View employee (pilot)                               100              1.5
2.3.2 View aircraft                                       100              1.5
2.3.3 View flight log                                      60               1
2.3.4 View maintenance log                                 60               1
2.3.5 View customer info                                   80               2
2.3.6 Search flight schedule                               70               2
2.3.7 Search maintenance schedule                          70               2
2.3.8 Search customer                                      70               2
Totals                                                    8400           130-170




Zebraware, LLC.                                         Phone: (605) 555-1234
Brookings, SD 57006                                     Email: support@zebraware.com

                                      Page 16 of 40
Proposal Document                                                                      Version 1.1
Dodo Airlines Scheduling System                                                           12-6-08

Cost Analysis
As shown in the table above, our initial estimate for code length is approximately 8400 lines of
code. However, most of the web server code will be written in web languages that general
require more lines of code to complete simple tasks such as creating web pages. The code
length estimates are based on previous experiences of the staff at Zebraware.

Web languages will take less time to produce more lines of code than a traditional
programming language such as C#. Totaling up all functions of the system, we estimate that
the coding will take approximately 130-170 hours to complete. This range also includes time
for unit testing, which is detailed later in the proposal.

For the cost of the coding process, Zebraware charges a flat rate of $45 per coding hour. This is
based on the current market average. At this rate, we estimate that the cost for coding will be
approximately $7,000. Note that this cost only covers the actual coding process. We can
estimate that the testing phases will take at least 150 hours. Adding in the cost for the
documentation, design, and planning stages, our final estimate for the complete system is
approximately $74,000, not including the cost of the computer hardware. The model for this
figure is explained in our Estimate Model on the following page.

Summary
   8400 lines of code
        o Web languages require more code
        o Estimates based on past experience
   130-170 hours of coding
        o $45 per hour
        o $7,000 for coding, not including testing, documentation, etc.
   150 hours of testing
   Total cost of the system: $74,000
        o Refer to estimate model for details




Zebraware, LLC.                                                  Phone: (605) 555-1234
Brookings, SD 57006                                              Email: support@zebraware.com

                                          Page 17 of 40
Proposal Document                                                                        Version 1.1
Dodo Airlines Scheduling System                                                             12-6-08

Estimate Model
The model we have used to determine the final system price was determined by using the
proven COCOMO model. The function we used to compute the cost is as follows:

where is the number of lines of code, and are modifiers determined through past
experiences, and is the product of several cost drivers listed below.

       Cost Driver                                         Tolerance        Multiplier
       Required software reliability                       Very High          1.40
       Size of the database                                 Nominal           1.00
       Execution time constraints                           Nominal           1.00
       Capabilities of the programmers                       High             0.86
       Use of modern programming practices                   High             0.91
       Use of software development tools                     High             0.91
       Total                                                                  0.99


                                  COCOMO Parameters for     and

                                           Basic                   Intermediate
             MODE                     a             b              a          b
             Organic                 2.4           1.05           3.2        1.05
             Semidetached            3.0           1.12           3.0        1.12
             Embedded                3.6           1.20           2.8        1.20


In our experiences, a system of this type will require modifiers of       and           . This
comes from the above table, with the system being semidetached and intermediate. Since our
estimate number of lines of source code is 8400, the final cost can be computed as follows:




This cost includes all design, development, and testing costs associated with the airline
scheduling system for Dodo Airlines. This price does not include the computer hardware
needed to run the system.




Zebraware, LLC.                                                    Phone: (605) 555-1234
Brookings, SD 57006                                                Email: support@zebraware.com

                                           Page 18 of 40
Proposal Document                                                                      Version 1.1
Dodo Airlines Scheduling System                                                           12-6-08

Duration and Staffing
Over the next several months, as indicated in our activity graph, the new airline scheduling
system for Dodo Airlines will be developed by a team of software development leaders
consisting of Bob Babilon, Joe Brock, and Mark Woodraska, three very skilled and professional
software developers.

Staffing
      Bob Babilon – Zebraware President
           o Oversee entire development process
           o Organize team meetings
           o Track status reports
           o Implement web application
      Joe Brock – Software Developer
           o Manage documentation
           o Implement client application
      Mark Woodraska – Software Developer
           o Create GUI design
           o Implement client application
           o Implement database

Duration
The complete development cycle of this software system will occur over a seven month period
beginning immediately and ending in early May. The first phase will end on October 23 and the
deliverables for this phase will include the Proposal and Requirements Documentation. The
next phase will be focused on production the Design Documentation. The test plans will be
produced in the next phase of design, and then the code will be written and the test plan will
be executed. Finally, the entire complete system will be installed on site and the project will be
finished. The final delivery date is scheduled tentatively for the end of April 2009.

      Phase 1: October 23, 2009
          o Proposal, Requirements Documentation
      Phase 2: November 14, 2008
          o Design Documentation
      Phase 3: March 2009
          o Acceptance test plan
      Phase 4: April 2009
          o Delivery and installation

Zebraware, LLC.                                                   Phone: (605) 555-1234
Brookings, SD 57006                                               Email: support@zebraware.com

                                          Page 19 of 40
Proposal Document                                                                                             Version 1.1
Dodo Airlines Scheduling System                                                                                  12-6-08

Work Breakdown Structure
                                                        1
                                                      Server



                                                     1.1
                                                  Web server




                                                                        1.1.8
           1.1.1                                                                                    1.1.10
                                                                  Registration page
         Login page                 1.1.5                                                   View flight info page
                        Search flight schedule page

                                                                       1.1.8.1                    1.1.10.1
           1.1.1.1                                               Send info DB script          Flight info script
         Login script            1.1.5.1
                               Search script

                                                                       1.1.8.2                      1.1.11
                                                                   Gather info script      View flight paths page
           1.1.2
        Logout page               1.1.6
                           Search results page                                                    1.1.11.1
                                                                       1.1.8.3               Flight paths script
                                                               Send confirm email script
          1.1.2.1                 1.1.6.1
        Logout script          results script

                                                                        1.1.9
                                  1.1.7                              Profile page
           1.1.3           Purchase ticket page
         Home page
                                                                       1.1.9.1
                                                                     View profile
                                 1.1.7.1
          1.1.3.1        Send confirm email script
        Home script
                                                                      1.1.9.2
                                                                 Update profile page
                                  1.1.7.2
            1.1.4           Send info DB script
          404 page
                                                                     1.1.9.2.1
                                                                 Update profile script
                                 1.1.7.3
                             Gather info script


                                           Figure 4: Web Server WBS




Zebraware, LLC.                                                                     Phone: (605) 555-1234
Brookings, SD 57006                                                                 Email: support@zebraware.com

                                                  Page 20 of 40
Proposal Document                                                                                                      Version 1.1
Dodo Airlines Scheduling System                                                                                           12-6-08

                                                 1
                                               Server


                                                 1.2
                                              Database




                                                                   1.2.3               1.2.4                      1.2.5
        1.2.1                   1.2.2                                                                         Search flights
                                                                  Update             Remove
   Add procedures          Get procedures                                                                      procedures
                                                                procedures          procedures


                               1.2.2.1                            1.2.3.1             1.2.4.1
       1.2.1.1                                                                                                  1.2.5.1
                               aircraft                           aircraft            aircraft
       aircraft                                                                                          One way static start/end


                               1.2.2.2                            1.2.3.2            1.2.4.2                      1.2.5.2
       1.2.1.2                customers                                             customers
                                                                 customers                               Round trip static start/end
      customers

                               1.2.2.3                                                1.2.4.3                    1.2.5.3
       1.2.1.3                                                    1.2.3.3
                                pilots                                                 pilots            One way flexible start/end
        pilots                                                     pilots



        1.2.1.4                 1.2.2.4                                                                            1.2.5.4
                                                                   1.2.3.4            1.2.4.4
      Flight logs             Flight logs                                                                Round trip flexible start/end
                                                                 Flight logs        Flight logs


                                1.2.2.5
        1.2.1.5                                                   1.2.3.5             1.2.4.5
                           Maintenance logs
   Maintenance logs                                          Maintenance logs    Maintenance logs


                                1.2.2.6
        1.2.1.6            Flight schedules                        1.2.3.6             1.2.4.6
   Flight schedules                                           Flight schedules    Flight schedules


                                  1.2.2.7
          1.2.1.7                                               1.2.3.7                 1.2.4.7
                           Maintenance schedules
   Maintenance schedules                                 Maintenance schedules   Maintenance schedules




                                               Figure 5: Database Server WBS




Zebraware, LLC.                                                                          Phone: (605) 555-1234
Brookings, SD 57006                                                                      Email: support@zebraware.com

                                                           Page 21 of 40
                                                                                                                                                                                                                                                             2.3
                                                                                                                                                                           2                                                                            Browse/search
                                                                                                                                                                       Client app




                Zebraware, LLC.
                                                                                                                                                                                                                                                           2.3.1
                                                                                                                                                                                                                                                    View employee (pilots)
                                                                                                                                                                                                                                                                                  Proposal Document




                                                                                                                                                                        2.2




                Brookings, SD 57006
                                                                                                                                                                    administrative
                                                                                                       2.1                                                                                                                                                2.3.2
                                                                                                    ticketing                                                                                                                                          View aircraft

                                                                                                                                                                                                                                      2.2.7
                                                                                                                                         2.2.1                 2.2.2                                              2.2.3
                                                                                                                    2.1.2                                                                                                       Auto maintenance          2.3.3
                                                                                                                                       Employee            Manual flight                    2.2.5              Auto flight
                                                                                                                                                                                                                                                                                  Dodo Airlines Scheduling System




                                                                                      2.1.1                      Verify ticket                                                                                                     scheduling         View flight log
                                                                                                                                       inventory            scheduling               Manual maintenance        scheduling
                                                                                    Sell tickets                                                                                         scheduling
                                                                                                                                                             2.2.2.1                                                                 2.2.7.1
                                                                                                                   2.1.2.1             2.2.1.1                                                                                                             2.3.4
                                                                                                                                                          Schedule flight                                        2.2.3.1        Collect schedules
                                                                                      2.1.1.1                    Select ticket       Add new pilot                                                                                                  View maintenance log
                                                                                                                                                                                            2.2.5.1         Collect schedules
                                                                                  Select customer                                                                                    Schedule maintenance
                                                                                                                                                                                                                                     2.2.7.2
                                                                                                                   2.1.2.2                                  2.2.2.1.1                                                                                     2.3.5
                                                                                                                                                                                                                                Analyze schedule
                                                                                      2.1.1.2                   Verify flight on        2.2.1.2           Check conflicts                                        2.2.3.2                            View customer info
                                                                                                                  schedule                                                                2.2.5.1.1
                                                                                    Select flight                                     Remove pilot                                                          Analyze schedule
                                                                                                                                                                                        Check conflicts
                                                                                                                                                            2.2.2.1.2                                                               2.2.7.3
                                                                                                                     2.1.2.3                                                                                                                                2.3.6
                                                                                      2.1.1.3                                                             Upload to DB                                                           Check conflicts
                                                                                                                Verify customer                                                                                                                     Search flight schedule
                                                                                     Sell ticket                                        2.2.1.3                                            2.2.5.1.2            2.2.3.3
                                                                                                                     correct
                                                                                                                                   Update pilot profile                                  Upload to DB        Check conflicts




Page 22 of 40
                                                                                                                                                             2.2.2.2                                                                 2.2.7.4
                                                                                      2.1.1.4                                                                                                                                                                  2.3.7
                                                                                                                                                           Reschedule                                                             Upload to DB
                                                                                  Update database                                                                                         2.2.5.2                                                   Search maintenance schedule
                                                                                                                    2.1.4                                 (update) flight                                        2.2.3.4
                                                                                                                                          2.2.4                                      Reschedule (update)      Upload to DB
                                                                                                                 Confirm flight
                                                                                                                                    Aircraft inventory                                  maintenance




                                               Figure 6: Client Application WBS
                                                                                                                                                            2.2.2.2.1                                                                2.2.6               2.3.8
                                                                                       2.1.3                                                              Check conflicts                                                        Customer info
                                                                                                                   2.1.4.1                                                                                                                          Search customer
                                                                                   Refund tickets                                                                                         2.2.5.2.1
                                                                                                                 Select flight          2.2.4.1                                                                                  management
                                                                                                                                                                                        Check conflicts
                                                                                                                                    Add new aircraft        2.2.2.2.2
                                                                                      2.1.3.1                                                             Upload to DB                                                               2.2.6.1
                                                                                                                   2.1.4.2
                                                                                  Select customer                                                                                          2.2.5.2.2                            Add new customer
                                                                                                                 Check status
                                                                                                                                       2.2.4.2                                           Upload to DB
                                                                                                                                    Remove aircraft          2.2.2.3
                                                                                      2.1.3.2                                                              Cancel flight                                                            2.2.6.2
                                                                                    Select flight                                                                                          2.2.5.3                              Remove customer
                                                                                                                                        2.2.4.3                                            Cancel
                                                                                                                                     Update aircraft        2.2.2.4                      maintenance
                                                                                      2.1.3.3                                                                                                                                       2.2.6.3
                                                                                                                                                           Delay flight




                Phone: (605) 555-1234
                                                                                    Select ticket                                                                                                                               Update customer
                                                                                                                                                                                                                                    profile



                                                                                      2.1.3.4




                Email: support@zebraware.com
                                                                                  Update database
                                                                                                                                                                                                                                                                                     12-6-08
                                                                                                                                                                                                                                                                                  Version 1.1
                                                                                                         3                                                                                                                                      2




                                                                                                                                             1
                                                                                                                                                                                                           1
                                                                                                                                                                          Start
                                                                                             Configure server hardware                                                                                                              Configure client hardware




                                                                                                                                                                                                                                                2




                                                                                                1
                                                                                                            1
                                                                                                                                            6                                                        13




                                                                                                                                                                          5
                                                                                                                                      Implement DB                                          Write DB comm. code                                  5




                                                                                                                                  1




                Zebraware, LLC.
                                                                                   7                             8                                                                                                                          Design GUI




                                                                                                                                                         1
                                                                          Configure web server          Configure database




                                                                                                                                                                                                     2




                                                                                                                                            2
                                                                                                                                                                     4
                                                                                                                                                                                                                                                                                               Proposal Document




                                                                                                                                                                                                                                                2




                Brookings, SD 57006
                                                                                   1
                                                                                                                                                             Write ER diagram
                                                                                                                                                                                                    17



                                                                                                                                                                                                                            2
                                                                                   11                                                       10                                                  Add DB code
                                                                                                                                         Verify DB                                                                                              9
                                                                               Design web                                                                                                                                                 Implement GUI
                                                                           interface template




                                                                                                                                                                                                     1
                                                                                                                                                                                                                                                2




                                                                                                                                            1




                                                                                   1
                                                                                                                                                                                                    22                                           12
                                                                                                                                                                                                                                                                                               Dodo Airlines Scheduling System




                                                                                  15                                                         14                                               Update DB code                             Verify GUI design




                                                                                                                                                                      2
                                                                              Login page                                              Write DB scripts
                                                                                                                                                                                                                                                2




                                                                                   1
                                                                                                                                                                                                     1




                                                                                                                                            2
                                                                                  20                                                                                                                                                           18
                                                                              Logout page                                                                                                            26                               Write GUI control code
                                                                                                                                                                                                                                                                   Activity Graph/Milestones




                                                                                                                                            19
                                                                                                                                                                                               Delete DB code




                                                                                                                2
                                                                                                                                      Test DB scripts




                                                                                   2
                                                                                                                                                                                                                                                2




                                                                                 24
                                                                                                                                                                                                     1




                                                                                                                                            0
                                                                              Home page                                                                                                                                                           36
                                                                                                                                                                                                                                    Write flight scheduling code




                                                                                   2
                                                                                                                                                                                                     29
                                                                                                                                             23                                                 Get DB code
                                                                                                                 30
                                                                                                                                                                                                                                                2




                                                                                   27                                                 Finish database




                                                                                                    1
                                                                              Profile page                Registration page




Page 23 of 40
                                                                                                                                                                                                     1




                                                                                                                                                                                                                                               39




                                                                                                    3
                                                                                                                                                                                                                                        Write maintenance




                                               Figure 7: Activity Graph
                                                                                                                                                                                                                                         scheduling code
                                                                                                                                                                                                                            2




                                                                                                                                                                                                    32
                                                                                  33                                                                                                          Custom DB code
                                                                          Search flights page
                                                                                                                                                                                                                                                3




                                                                                                                                                                                                     1




                                                                                   2
                                                                                                                                                                                                                                                 42
                                                                                    37                                                                                                                                                  Write ticketing code
                                                                                                                                                                                                       35
                                                                           Flight results page                                                                                         Test client/server communication
                                                                                                                                                         0
                                                                                                                                                                                                                                                4




                                                                                   3
                                                                                                                                                                                                                                                44
                                                                                                                                                                                                                                        View Inventory code
                                                                                                                                                                                                                                4




                                                                                                                                                                                                                45
                                                                                  40
                                                                                                                                                                                                         Admin tools code
                                                                          Purchase ticket page
                                                                                                                                                                                                 4




                                                                                   1
                                                                                                                                                                                              46




                Phone: (605) 555-1234
                                                                                  43                                                                                                  Browse/search code
                                                                               404 page
                                                                                                                                                                                  0




                                                                                                                              0

                                                                                                                                                             Finish




                Email: support@zebraware.com
                                                                                                                                                                                                                                                                                                  12-6-08
                                                                                                                                                                                                                                                                                               Version 1.1
Proposal Document                                                                    Version 1.1
Dodo Airlines Scheduling System                                                         12-6-08

Critical Path Analysis
Figure 8 shows the steps along the critical path based on the activity graph in Figure 7. Adding
up the days needed between each step, we get a total of 39 days. The first six steps along the
critical path involve getting the database set up and configured. This is necessary because we
need a functioning database before code can be written to interact with it. The following seven
steps along the critical path involve writing code for communicating with the database, as well
as adding, removing, and updating information in the database. In addition, the
communication between the database and the client must be tested.

The final steps along the critical path include the implementation of the internal client
application. We can see that the database must be configured and operating properly before
the client app code is written because the main functions of the client app will involve
communicating with the database.




Zebraware, LLC.                                                 Phone: (605) 555-1234
Brookings, SD 57006                                             Email: support@zebraware.com

                                         Page 24 of 40
Proposal Document                                                                                            Version 1.1
Dodo Airlines Scheduling System                                                                                 12-6-08

                Start


                  5

                  4                                 13
          Write ER diagram                 Write DB comm. code
                                                                                                36
                  1                                  2                            Write flight scheduling code


                  6                                17                                          2
            Implement DB                       Add DB code
                                                                                             39
                                                     1                                Write maintenance
                  2                                                                    scheduling code

                                                   22
                                             Update DB code
                 10                                                                            3
              Verify DB
                                  2                  1
                                                                                               42
                  1
                                                                                      Write ticketing code
                                                    26
                                                                             2
                  14                          Delete DB code
           Write DB scripts
                                                     1                                         4
                  2
                                                    29
                 19                            Get DB code                                   44
           Test DB scripts
                                                                                     View Inventory code
                                                     1
                  0
                                                   32
                  23                         Custom DB code
                                                                                               4
           Finish database
                                                     1

                                                      35                                      45
                                      Test client/server communication                 Admin tools code



                                                                                               4


                                                                                             46
                                                                                     Browse/search code

                                                                         0

                                                   Finish


                                           Figure 8: Critical Path




Zebraware, LLC.                                                                  Phone: (605) 555-1234
Brookings, SD 57006                                                              Email: support@zebraware.com

                                               Page 25 of 40
Proposal Document                                                     Version 1.1
Dodo Airlines Scheduling System                                          12-6-08


Project Schedule




      Figure 9: Project Schedule


Zebraware, LLC.                                    Phone: (605) 555-1234
Brookings, SD 57006                                Email: support@zebraware.com

                                   Page 26 of 40
Proposal Document                                                                     Version 1.1
Dodo Airlines Scheduling System                                                          12-6-08

Project Team Organization
Bob Babilon – Team Manager
Bob Babilon was chosen as the team manager as he is also the company president. This
important project needs a proven leader to oversee its completion. His responsibilities will
include:

       Organize team meetings
       Assign tasks to each team
       Develop web interface

Joe Brock – Lead Developer
Joe Brock was chosen as a lead developer due to past programming and leadership
experiences. His main responsibilities will include:

       Manage team of ten developers
       Develop client application
       Organize all documents handed to Dodo Airlines
       Design and document the airline scheduling system for Dodo Airlines

Mark Woodraska – Lead Developer
Mark Woodraska was also chosen as a lead developer due to his strong programming skills and
leadership abilities that he has shown at Zebraware. Mark’s main responsibilities will include:

       Develop database
       Design GUI for client application
       Develop client application


Quality Assurance Plan
This plan will describe Zebraware’s plans to keep the quality of our software to its maximum.
The main focus will be ensuring that all code is developed with the highest quality possible. To
do this, several ideas must be kept in mind while our developers write code. The following list
details several characteristics of quality software:

       Efficiency – Software should perform its function in a reasonable amount of time.
            o For the airline employees, their client application should retrieve data and
                process requests in less than 3 seconds.



Zebraware, LLC.                                                  Phone: (605) 555-1234
Brookings, SD 57006                                              Email: support@zebraware.com

                                            Page 27 of 40
Proposal Document                                                                      Version 1.1
Dodo Airlines Scheduling System                                                           12-6-08

          o For the customers of the airline, the web server should respond to client
              requests in less than 5 seconds.
      Code reusability – Whenever possible, code segments and class definitions should be
       reused throughout the system. This ensures that objects within the code contain
       compatible definitions throughout all aspects of the software.
      Documentation – Code documentation is essential for quality assurance. Our
       company’s documentation standards will be used to allow any member of our
       development team to be able to quickly understand what a particular segment of code
       does. The documentation will not be so complex as to distract from the function of the
       code, but it will be complete and concise.

In addition to ensuring that all of the above characteristics are implemented into all software
written by Zebraware, we will also hire a third party software company to review portions of
our code for further assurance of the quality of our software.


Documentation Plan
Zebraware is committed to providing quality software that can be maintained for years to
come. Documentation is the key for maintainability. Code documentation allows other
software developers to be able to understand any portion of code so it can be worked on at a
later date.

      Main documentation plans will be the deliverables
          o Proposal
          o Requirements Documentation
          o Design Documentation
          o Acceptance Test Plan
          o System Test Plan
      Each document will be reviewed
          o Between lead developers at Zebraware and executives of Dodo Airlines
          o After every major revision of the system.
          o Upon delivery
      Hard copy and soft copy in PDF form will be provided
      Revisions must be approved by the lead librarian, Joe Brock.
          o If accepted, the revision will be added to the appropriate documentation and
              notes will be placed in the revision history.



Zebraware, LLC.                                                   Phone: (605) 555-1234
Brookings, SD 57006                                               Email: support@zebraware.com

                                          Page 28 of 40
Proposal Document                                                                       Version 1.1
Dodo Airlines Scheduling System                                                            12-6-08

Data Management Plan
Data is the key to running a successful business. Keeping this data safe and organized is
essential. The following plan describes how all data for Dodo Airlines’ scheduling system will be
kept secure and organized.

Airline Scheduling System
      Source code and related data stored on Zebraware’s internal secure servers
          o Corporate firewall with 256-bit data encryption
          o Provides safety and protection
      Source code will be regularly backed up
          o All code will be synced with the server at the end of each day.
          o External HDDs will be used weekly for a full system backup.
                   These HDDs will be kept for 5 years after project completion
      Database on Dodo Airline’s server will store information
          o Customer information
          o Employee information
          o Aircraft information
          o Flight schedule information
          o Ticket information
      Only administrator accounts have full access to data
      Regular accounts have limited access

Data Backup System
      Main database server
          o Daily backup
                   Every night at midnight, the current day’s data will be backed up
                   Duplicate copy made on secondary server’s 500GB hard drives
                   Performed by an automatic scheduled task
          o Weekly backup
                   Performed every Sunday at 2:00 A.M.
                   All daily backups from that week transferred to data warehouse
                          Stored on backup server’s 750GB hard drives for 5 years
                   Performed by an automatic scheduled task
          o Monthly backup
                   Performed on the last business day of each month
                   Entire system backed up to 1TB tape drives
                   Sent to data storage facility, kept for 10 years
                   Performed by Database Administrator



Zebraware, LLC.                                                    Phone: (605) 555-1234
Brookings, SD 57006                                                Email: support@zebraware.com

                                           Page 29 of 40
Proposal Document                                                                      Version 1.1
Dodo Airlines Scheduling System                                                           12-6-08

Resource Management Plan
Each member of the Zebraware team is committed to performing tasks in an efficient manner
in order to provide the customer with the most cost-effective solution. To do this, we must
excel at managing what limited resources we have.

      Hardware Management
           o Workstations reside on a secure network
           o Central server to house all code and provide source control
           o Current data is backed up to a remote location nightly at midnight
      Financial Management
           o Schedules are checked daily to stay on track
           o Any predicted changes will be addressed immediately
           o Benefits are provided to employees who complete tasks on time
      Human Resource Management
           o Employee’s wages and benefits are kept competitive to reduce employee
              turnover
           o Activities are planned weekly to encourage employee interaction


Risk Management Plan
The following risks have been determined to be the top ten risks according to probability of
occurrence and the impact of the risk occurring. Risks that involve a higher impact are rated
higher than those that have a higher probability of occurring. In addition, a mitigation plan and
contingency plan is defined for each listed risk.

A risk’s probability of occurrence is rated as follows:

                                Rating               Probability
                           Extremely High     Above 80%
                           High               Between 60-80%
                           Medium             Between 30-60%
                           Low                Less than 30%


The impact of a risk occurring is rated as follows:

           Rating             Risk to Humans                       Cost
           Extremely          Human loss of life is likely         Over $600,000
           High

Zebraware, LLC.                                                    Phone: (605) 555-1234
Brookings, SD 57006                                                Email: support@zebraware.com

                                            Page 30 of 40
Proposal Document                                                                      Version 1.1
Dodo Airlines Scheduling System                                                           12-6-08

           High              Human loss of life is moderate      $200,000 - $600,000
           Medium            Small risk of human injury          $30,000 - $200,000
           Low               Very little risk of human injury    Less than $30,000

List of Risks
          Risk                                                           Probability    Impact
Risk 1    Critical software flaw causes system crash                     Low            Very High
Risk 2    Hardware failure in the main server system                     Low            High
Risk 3    Essential personnel decide to leave company                    Medium         Medium
Risk 4    Hardware failure in a client terminal system                   Medium         Low
Risk 5    Natural disaster occurs                                        Low            High
Risk 6    Network disruption prevents users from purchasing tickets      Low            Medium
Risk 7    Software development deadlines are not met                     Medium         Medium
Risk 8    Source code is lost                                            Low            High
Risk 9    Employee illness causes loss of time                           High           Low
Risk 10   Zebraware is purchased by another company                      Low            High


Mitigation and Contingency Plan
   1. Critical software flaw causes system crash.
      Mitigation Plan: In order to reduce the risk of a software flaw, extensive testing will be
      done as defined in the Unit Test Plan, Integration Test Plan, and System Test Plan
      documents.
      Contingency Plan: In case of a critical system error, the first course of action is to check
      the error logs to determine the cause of the crash, while also either restarting the
      system or activating the backup system. Next, the cause of the crash must be
      determined and the support documents must be consulted to determine what to do
      next.
   2. Hardware failure in the main server system.
      Mitigation Plan: Use high quality hardware with low risk of failure. Also, the main server
      should be completely backed up on a separate, redundant system so that in case of a
      failure it could be switched over to be the main server.
      Contingency Plan: In case of a hardware failure in the main server, the backup server
      should be activated as quickly as possible to ensure the minimal amount of system
      downtime. The main server should then be repaired as necessary and switched back on
      when it is repaired. The airline company is responsible for repairing the server
      hardware.


Zebraware, LLC.                                                  Phone: (605) 555-1234
Brookings, SD 57006                                              Email: support@zebraware.com

                                          Page 31 of 40
Proposal Document                                                                        Version 1.1
Dodo Airlines Scheduling System                                                             12-6-08

   3. Essential personnel decide to leave company.
      Mitigation Plan: In order to prevent members of our staff from leaving during critical
      stages of the software development cycle, we will:
           Provide fair compensation and benefits to our employees
           Reward quality work
           Inform them of the importance to complete the project

       Contingency Plan: If a staff member decides to leave the company for whatever reason,
       our company will:

            Find a suitable replacement as quickly as possible
            Ensure all critical tasks remain on track
   4. Hardware failure in a client terminal system.
      Mitigation Plan: All of the computer terminals used at the airport will be composed of
      the same hardware whenever possible to reduce the troubleshooting load of the IT
      staff. Spare terminals and parts will be kept on hand in case of failure.
      Contingency Plan: In the case of a hardware failure, that specific terminal will be fixed or
      replaced as necessary and another terminal will have to be used in its place until fixed.
      The airline company is responsible for fixing the hardware.
   5. Natural disaster occurs.
      Mitigation Plan: Equipment will be installed to reduce the risk of damage due to
      lightning storms and power surges. The structures containing the main servers will be
      constructed of quality materials to protect the equipment as best as possibly from
      floods, earthquakes, and tornados.
      Contingency Plan: If a natural disaster occurs and equipment is damaged, that
      equipment will have to be fixed or replaced and then the backups will have to be
      restored. The airline company is responsible for fixing the damaged equipment.
   6. Network disruption prevents users from purchasing tickets.
      Mitigation Plan: A reliable ISP must be chosen to ensure very minimal downtime for
      outside access to the system. Internally, the network must be continuously monitored
      for any interruptions to keep downtime to a minimum which will keep productivity up.
      Contingency Plan: If a network interruption occurs, it must first be determined if it is an
      internal or external interruption. If it is external, the ISP must be notified of the issue so
      that the access can be restored promptly. If the problem is internal, the network team
      is responsible for diagnosing and fixing the problem.




Zebraware, LLC.                                                    Phone: (605) 555-1234
Brookings, SD 57006                                                Email: support@zebraware.com

                                           Page 32 of 40
Proposal Document                                                                       Version 1.1
Dodo Airlines Scheduling System                                                            12-6-08

   7. Software development deadlines are not met.
       Mitigation Plan: Team managers will meet weekly with the project manager to stay up-
       to-date with planned schedules.
       Contingency Plan: If a team gets behind schedule, additional resources will be pulled
       from areas which are ahead of schedule.
   8. Source code is lost.
       Mitigation Plan: As stated above, all current source code is backed up nightly to a
       remote location. This ensures that any possibly data loss would be minimal. In addition,
       our primary server runs a source control program which ensures that all code is
       accounted for.
       Contingency Plan: If data loss were to occur, the data would be restored from the latest
       backup on the remote server.
   9. Employee illness causes loss of time.
       Mitigation Plan: All employees of Zebraware receive several sick days each year. This
       time is accounted for in all estimates.
       Contingency Plan: If an employee is only sick for a day or two, then their work can be
       put on hold for a short time, or it can be reassigned to another individual if necessary. If
       the illness is serious, schedules will be adjusted and resources will be allocated to
       ensure that the project is kept as close to the deadline as possible.
   10. Zebraware is purchased by another company.
       Mitigation Plan: Zebraware does not plan on being acquired anytime in the near future.
       Contingency Plan: If, for some reason, our company is purchased by another company,
       we will do our best to ensure the transition has minimal impact. However, most of the
       impact to our clients would be in the hands of the acquiring company.


Test Plan
This test plan will represent an overview of the procedure Zebraware will use to ensure that our
product is fully functional as specified in the requirements documentation. A more
comprehensive test plan will be delivered at a later date.

      Unit Testing
           o Each separate block of code is tested
           o Performed by the developer of that block of code
           o Use known inputs to test for expected outputs
           o Occurs after every unit is written
      Integration Testing

Zebraware, LLC.                                                   Phone: (605) 555-1234
Brookings, SD 57006                                               Email: support@zebraware.com

                                          Page 33 of 40
Proposal Document                                                                     Version 1.1
Dodo Airlines Scheduling System                                                          12-6-08

           o Common blocks of code are tested together
           o Performed by the developer who is assembling the units
           o Ensure that a group of functions performs an expected task
           o Occurs when a group of units are linked together
      System Testing
           o Hardware being used for the system at Dodo Airlines will be tested with the
             software to ensure it functions properly
           o Performed by Zebraware’s system test group
           o Install software on the chosen hardware
           o Occurs once software is complete and the hardware is chosen
      Acceptance Testing
           o Final phase of testing
           o A complete demonstration of the entire system is presented to Dodo Airlines
           o Each item in the Requirements Documentation is shown
           o Performed by Zebraware’s project managers
           o Occurs when the complete system is ready for delivery


Security Plan
Security is a major concern for any business, especially one that deals with a large amount of
private customer data, such as Dodo Airlines. As such, Zebraware will implement several
security features into the airline scheduling system. These features will protect customer
information and provide tiered access to the internal software system.

      Web application security
           o Users are required to register on the website
                    Unique user name and secure password
           o Users are logged off after 10 minutes of no activity
      Internal Client Application – Tiered access
           o Admin account
                    Full access to the database
                    Allowed to change/update information
                    View any logs created by the database
                    Should be limited to trusted network administrators
           o Ticketer account
                    Used by employees working at the ticket booths
                    Allows employees to sell tickets to customers

Zebraware, LLC.                                                  Phone: (605) 555-1234
Brookings, SD 57006                                              Email: support@zebraware.com

                                          Page 34 of 40
Proposal Document                                                                   Version 1.1
Dodo Airlines Scheduling System                                                        12-6-08

                      Look up flight schedules
                      Verify flight information

For the security of the internal network of Dodo Airlines, Zebraware will not be responsible.
We would recommend installing a strong firewall to prevent unwanted intruders, but that is the
responsibility of Dodo Airlines to implement and install, and Zebraware cannot be held
responsible for any such actions.


Server Selection Plan
The following server and client options are presented as the two options Zebraware
recommends for the hardware to run the airline scheduling system. Both options have been
configured with similar hardware, and the choice will be left up to Dodo Airlines.

Main Server
HP ProLiant DL580 G5                                 Dell PowerEdge 2950 III




Quad Core Intel Xeon E7440 processor                 Quad Core Intel Xeon X5460 processor
        (2.13Ghz, 12MB L3 Cache) x2                          (3.16Ghz, 2x6MB L3 Cache) x2
4GB PC2-5300 Ram                                     8GB 667Mhz Ram
No HDD standard                                      73GB 15K Rpm SCSI HDD x2
4U Rackmount                                         2U Rackmount
Total = $8,959.00                                    Total = $7,452.00




Zebraware, LLC.                                                  Phone: (605) 555-1234
Brookings, SD 57006                                              Email: support@zebraware.com

                                           Page 35 of 40
Proposal Document                                                               Version 1.1
Dodo Airlines Scheduling System                                                    12-6-08

Client Terminals
HP Compaq dc7800                               Dell OptiPlex 755




Intel Core 2 Duo E8300 processor                   Intel Core 2 Duo E8400 processor
        (2.83 GHz, 6MB L2 Cache)                       (3.0 GHz, 6MB L2 Cache)
2GB 800MHz DDR2 Ram                                2GB 800MHz DDR2 Ram
80GB 7200rpm SATA HDD                              80GB 7200rpm SATA HDD
Integrated Intel 3100 Graphics                     Integrated Intel 3100 Graphics
365W Efficient Power Supply
Total = $909.00                                    Total = $1,032.00

Client Monitors
Dell 1708FP                                   ViewSonic VA703MB




17” Viewable Size                             17” Viewable Size
1280 x 1024 Max Resolution                    1280 x 1024 Max Resolution
5 ms Response Time                            8 ms Response Time
Power Consumption: 75W                        Power Consumption: 35W
Total = $209.00                               Total = $169.99




Zebraware, LLC.                                             Phone: (605) 555-1234
Brookings, SD 57006                                         Email: support@zebraware.com

                                   Page 36 of 40
Proposal Document                                                                         Version 1.1
Dodo Airlines Scheduling System                                                              12-6-08

Workstation Printers
HP CM6030f                                             Ricoh Aficio MP C3000




Up to 30 PPM Black and Color                           Up to 30 PPM Black and Color
Up to 200,000 pages monthly                            First page out (black): 6.7 sec
First page out (black): 15.3 sec                       First page out (color): 9.7 sec
Memory: 512 MB                                         Memory: 1 GB
Total = $7,999.00                                      Total = $7,799.00


Project Deliverables
Airline Scheduling System Software
The main deliverable for the system being provided will be the software for the database and
the client application. Once the server hardware is chosen from the options above, our staff
will perform the initial install and setup of the database on the server. A recovery and
installation disk will also be provided in case of a server upgrade or other reason. For the client
system, a disk will be provided that will contain the software that needs to be installed on all
client terminals within Dodo Airlines. This installation will be the responsibility of Dodo Airlines,
but installation directions will be provided.

System Proposal
At the beginning of the development cycle, a formal proposal will be provided to Dodo Airlines
which will detail all planning of the airline scheduling system. As this is just an initial proposal,
most ideas presented are subject to change with approval by Dodo Airlines personnel. Also
included in this document is information about Zebraware, its employees, an overview of the
existing system at Dodo Airlines, and our proposed solution. A timeline and estimate model will
be presented, along with brief descriptions of our implementation plans and test plans.



Zebraware, LLC.                                                     Phone: (605) 555-1234
Brookings, SD 57006                                                 Email: support@zebraware.com

                                            Page 37 of 40
Proposal Document                                                                      Version 1.1
Dodo Airlines Scheduling System                                                           12-6-08

Requirements Documentation
The requirements documentation will outline all requirements established between Zebraware
and Dodo Airlines for the proposed airline scheduling system. All functional and non-functional
requirements will be fully documented and described. The functional requirements will be
directly derived from the Work Breakdown Structure presented in this document. The non-
functional requirement will detail aspects such as the performance and environment of the
system, documentation and testing requirements, and the maintainability of the system.

Design Documentation
The design documentation will take all requirements from the requirements documentation
and translate them into a usable form for a software developer. This documentation will
provide specific details of both the server side and client side applications for the airline
scheduling system. Data flow diagrams will be used to show how the system will perform
certain functions. The design documentation is essential to show how customer and airline
information will interact with the web server, database, and internal client application. This
document will be the main tool used by our software developers when implementing the
system for Dodo Airlines.


Alternatives
Server Operating System
      Plan: Windows Server 2003
      Alternative: Windows Server 2008

When developing this new airline scheduling system for Dodo Airlines, we plan on
implementing the main server with the Windows Server 2003 operating system. This particular
operating system has proven itself for several years, so we know its reliability is high. However,
we have a couple individuals researching the new Windows Server 2008 operating system, and
evaluating its possible reliability and performance advantages over the previous version. If that
team’s results prove to be conclusive, there is a possibility that we may develop the database
and server system for this new operating system. However, note that there will not be any
requirements change besides a few minor operating system related issues.

Client Operating System
      Plan: Windows XP
      Alternative: Windows Vista, Windows 7
           o Any operating system that implements the .NET 3.5 Framework


Zebraware, LLC.                                                   Phone: (605) 555-1234
Brookings, SD 57006                                               Email: support@zebraware.com

                                          Page 38 of 40
Proposal Document                                                                                                    Version 1.1
Dodo Airlines Scheduling System                                                                                         12-6-08

Along the same lines, we plan on implementing the internal client application on the Windows
XP platform for its proven track record in the corporate industry. However, the client app will
only be dependent on the .NET 3.5 Framework, so any operating system that can use this
framework will be suitable for use. This includes Windows Vista and the new Windows 7 that
will be released shortly.


Terms and Conditions
We grant you one license to install and use this software on a single computer at a time. If you do not agree to the following
terms of this license, please uninstall and remove all copies and return the product to the place that you purchased it from
within 30 days of your purchase for a full refund.

You may install and use the software on another computer, but the software may not be in use on more than one computer at
a time unless you purchase additional licenses. You may make back-up copies of the software for archival purposes. You may
permanently transfer your license to use the software to another party who will be bound by this agreement, provided you do
not retain any copies of the software.

The software is protected by the copyright laws of the U.S. and other countries, and we retain all intellectual property rights in
the software. You may not separately publish, sell, market, distribute, lend, lease, rent, or sublicense the software code.
However, this license is not to be construed as prohibiting or limiting any fair use sanctioned by copyright law, such as
permitted library and classroom usage or reverse engineering.


Limited Warranty
We warrant that the software will provide the features and functions generally described in the product specification on our
website when you purchased it and in the product documentation. Media on which the Software is furnished, if any, will be
free from defects in materials and workmanship.

 We have taken all reasonable steps to keep the software free of viruses, spyware, "back door" entrances, or any other harmful
code. We will not track or collect any information about you, your data, or your use of the software except as you specifically
authorize. The software will not download or install patches, upgrades, or any third party software without getting your
permission. We will not intentionally deprive you of your ability to use any features of the software or access to your data.

We do not warrant that the software or your ability to use it will be uninterrupted or error-free. To the extent permitted by
applicable law, we disclaim any implied warranty of merchantability or fitness for a particular purpose.


Limitations on Liability
Your exclusive remedy under the above limited warranty shall be, at our option, either a full refund of the purchase price or
correction of the defective software or media. To the fullest extent permitted by applicable law, we disclaim all liability for
indirect or consequential damages that arise under this license agreement. Nothing in this agreement limits our liability to you
in the event of death or personal injury resulting from gross negligence, fraud, or knowing misrepresentation on our part.


General Provisions
If any part of this agreement is found to be invalid or unenforceable, the remaining terms will stay in effect. This agreement
does not prejudice the statutory rights of any party dealing as a consumer.

If we have our corporate headquarters in the USA, this agreement will be governed by the laws, including Article 2 of the
Uniform Commercial Code, of the state in which we are headquartered. If that state has enacted the Uniform Computer

Zebraware, LLC.                                                                         Phone: (605) 555-1234
Brookings, SD 57006                                                                     Email: support@zebraware.com

                                                         Page 39 of 40
Proposal Document                                                                                                  Version 1.1
Dodo Airlines Scheduling System                                                                                       12-6-08
Information Transactions Act (UCITA) or substantially similar law, said statute shall not govern any aspect of this agreement and
instead the law as it existed prior to such enactment shall govern. If we do not have our corporate headquarters in the USA, this
agreement will be governed by the laws of England.

This agreement does not supersede any express warranties we made to you. Any modification to this agreement must be
agreed to in writing by both parties.




Zebraware, LLC.                                                                        Phone: (605) 555-1234
Brookings, SD 57006                                                                    Email: support@zebraware.com

                                                        Page 40 of 40

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:68
posted:8/12/2011
language:Slovenian
pages:40