Minoa's Reservation System

Signature Page

Change History

Preface

This Software Project Management Plan is intended to be followed to complete the Minoa's Reservation System. The Minoa Travel Agency needs the Reservation System to manage its three hotels: Minoa-A, Minoa-B, and Minoa-C. Please see the Project Description for more information of the content of this document.

This document is intended for the Project Manager and his superiors to provide the understanding and documentation of this project's organization and processes. This document also provides members of the Project Team the processes that they will follow to complete the project. In general, all individuals related to the project are considered part of the intended audience. This document should also provide information valuable to future Project Managers to improve Tech-9's development processes.

Table of Contents

List of Figures

List of Tables

Overview

Project Summary

Purpose, scope and objectives

The Minoa's Reservation Project aims at developing a system to store and retrieve information and conduct transactions related to prospective guests.

The Minoa's System will manage three hotels (Minoa-A, Minoa-B and Minoa-C) situated in the the Santorini island in Greece. The system will reside in those hotels and will interact with a database to store and get information.

The objectives of this project is to develop a reservation system that will

1. Generate the cost of a stay based on the time of the year and the type of reservation
2. Retain prospective guests' reservations and card information
3. Print three reports daily for management use

Assumptions and constraints

Assumptions:

1. The project team would be assumed to not to change from the inception of the project unless an unavoidable situations is to arise.
2. The project team members are expected to adhere to the project plan
3. The project plan is susceptible to changes.
4. The top management is expected to over see the progress of the project.
5. Java is assumed to be the main development language used for this project
6. There is a Trac server that would be running all the time.

Constraints:

1. All communication, processes, etc., need to abide by the applicable national and international laws and regulations of the United States and Greece.
2. The time zone difference between the client site and the development team is to be considered when deciding about meetings and schedules between the two parties.

Project deliverables

The deliverables of this project will be:

• Software Requirement Specification document
• Software Design Document
• Test Cases Document
• Result Test Cases Document
• Verification and Validation Document
• Quality Assurance Plan Document

Schedule and budget summary

Evolution of the plan

References

IEEE. IEEE std. 1058-1997 IEEE Standard for Software Project Management Plans. Retrieved June 12, 2008, from IEEE web site: http://standards.ieee.org/reading/ieee/std_public/description/se/1058-1998_desc.html

Definitions

Software

the computer programs in machine-readable code form and any subsequent error corrections or updates supplied to Sponsor by University.

V&V (Verification and Validation)

process of checking that a product, service, or system meets specifications and that it fulfils its intended purpose

CM (Configuration Management)

focuses on establishing and maintaining consistency of a product's performance

QA (Quality and Assurance)

set of planned and systematic actions necessary to provide appropriate confidence that a product or service will satisfy the requirements for quality.

KDSI (Kilo Delivered Source Instruction)

measure of a programmer's productivity or a project productivity

FSP (Full-Time Equivalent Software Personnel)

staffing unit. One unit is equivalent to one individual working with a standard, full-time, 40-hour work-week.

Project Organization

External Interfaces

The Project Manager is the point of contact for maintaining liaison with the client, conducting program reviews, coordinating and supporting meetings and approving primary deliverables. The project Manager attends all meetings and assurances the attendance of its managers

Internal Structure

The University is organized in a matrix structure. The Project Manager will establish and approve a schedule showing major activities needed to establish capability according to the requirements.

Roles and Responsibilities

Requirement Analysis Team

Staff is responsible for determining, specifying, reviewing and updating software functional, performance, interface and verification requirements.

Product Design Team

Staff is responsible for determining, specifying, reviewing and updating hardware-software architecture, program design and data base design.

Programming Team

Staff is responsible for detailed desiging, coding, unit testing and integrating individual computer program components.

Test Planning Team

Staff is responsible for specifying, reviewing and updating product test and acceptance test plans.

Verification and Validation Team

Team is responsible for verifying and validating the code

Project Office Functions Team

Team's reponsibilities include project level planning and control, contract and subcontract management, and customer interface

Configuration Management and Quality Assurance Team

Configuration Management's responsibilites include product integration, change control, status accounting, operation of program support library, development and monitoring of end item acceptance plan. Quality Assurance team's responsibilities include development and monitoring of project standards, and technical audits of software product and process

Manuals Team

Team is responsible for developing and updating user's manuals, operators' manuals, and maintenance manuals

Managerial process plan

Start-up plan

Estimation plan

Staffing plan

Based on the requirements of this organic project, its estimated size was 8 KDSI.

Resource acquisition plan

Project staff training plan

Work plan

Work activities

Schedule allocation

Resource allocation

Budget allocation

Control plan

Requirements control plan

Schedule control plan

Budget control plan

Quality control plan

Reporting plan

Metrics collection plan

Risk management plan

Closeout plan

Technical process plans

Process model

Methods, tools and techniques

Infrastructure plan

Product acceptance plan

Supporting process plans

Configuration management plan

Verification and validation plan

Documentation plan

Quality assurance plan

Reviews and audits

Problem resolution plan

Subcontractor management plan

Process Improvement plan

Additional plans

Annexes

Index