University of Buea

CSC 404
Software Engineering

Patriott Web Browser

Project Management
Version <1.0>
http://www.patriott.zzl.org

GROUP MEMBERS
Name Student ID
MADI WAMBA GILLES SC08A738
TCHAMDOU TCHATAT JULES AUDREY SC08A800
TONKEU NENDA FRANCE CYNTICHE SC08A810
NDANGANG YAMPA HAROLD SC08A757

Revision History
Date Version Description Author

1. Overview
1.1. Project Summary
1.1.1. Scope, Purpose and Objectives
1.1.2. Assumptions and Dependecies
1.1.3. Project Deliverables
1.1.4. Schedule and Budget Summary

[Type text]
2.0. References

3.0. Glossary

4. Project Organization
4.1. Roles and Responsibilities
4.2. Project Planning
4.1. Requirements Analysis
4.2. System Design
4.3. Object Design Phase
4.4. Implementation
4.5. Unit Testing
4.6. System Testing
4.7. Manual Integration
4.8. Project Presentation
4.3. Work Plan
4.3.1. Work Activities
4.3.2. Schedule Allocation
4.4. Resource Allocation
4.4.1. Budget Allocation
4.5.1. Schedule Control Plan
4.5.2. Budget Control Plan
4.5.3. Quality Control Plan
4.6. Risk Management Plan
4.7. Methods, Tools, and Techniques
5.0 Support Process Plans

5.1. Validation & Verification Plan

[Type text]
 1. Overview
Project Summary
Scope, Purpose and Objectives
Patriott is a simple desktop application that allows the user to browser the internet.

Nowadays Internet is primordial to everybody, to do researches, collaborative work,

entertainment...

In other to browser the internet, a specialized software is required, Patriott is one of them.

Assumptions and Dependecies

The project is expected to be completed within three months. This project will use resources
in the form of time and effort that will be spent developing the project deliverables.

The application is developed in C++ platform with the environment of Qt for the
interface.Without additional hardware\software systems, Patriott can be operated in simply
Configured PC. Moreover, the user has not to be trained with any kind of IT packages.
Computer friendly user can be friend of Patriott.

Project Deliverables
The list of project deliverables is:
● Project Management Plan
● Specification Document
● Design Document
● Implementation Document
● Software Quality Assurance(Testing/Debugging/validation)
● User guide

Schedule and Budget Summary

Budget Summary: “No budget required”.

[Type text]
A tentative schedule is as shown below in table 1.

Figure 1: Schedule

Item Due date

Specifications Document April 26, 2011

Design Document May 03, 2011

Implementation document May 24, 2011

Software Quality Assurance and Validation May 31, 2011

Software Project Management Plan (this June 02, 2009

document)

User Guide

References
The most usable references is web. The web sites related to c++/Qt.

E-books are listed below:

1. The art of building QT applications, Daniel Molkentin

Websites:

www.google.com

www.qtcentre.org

www.siteduzero.com

Glossary
none

Project Organization
Roles and Responsibilities
The project members are responsible for all documentation to be developed and for all work
to be done.

[Type text]
Project Planning
Project planning includes description of project tasks, activities and functions, dependencies,
resource requirements and a detailed schedule.

4.1. Requirements Analysis

The requirements analysis activity takes the problem statement and reviews it in terms of
consistency, completeness and feasibility. During this activity, a set of models for the
developpement of patriott is determined by discussing project members resulting in the
requirements model.

4.2. System Design

The purpose of the system design activity is to devise a system architecture that maps the
analysis model to the chosen target environment. The major part of the Patriott design phase
is the design of Patriott, that is, the decomposition of the system with respect to the chosen
target platform.

4.3. Object Design Phase

In this phase, new classes are added to the analysis object model if necessitated by the system
architecture. Attributes and methods for each object are fully typed.

4.4. Implementation

The focus of this activity is on coding the individual objects described in the implementation
document.

4.5. Unit Testing

During unit testing, test suites are designed and executed for objects or collections of objects.
Unit testing enables the individual objects to be tested independent from the status of the other
components of the programm.

4.6. System Testing

Structural Testing: We did no structural test.

Functional Testing: We tested the major functionalities (use cases) of Patriott.

Alpha-test (Client Acceptance Test): The system is tested to make sure it passes acceptance
criteria as defined in the specification document.

[Type text]
 4.7. Creation of project home page
During this activity, the project’s home page is created

4.7. Manual Integration

During this activity, the project deliverables are revised. As a result, a complete set of
documents consisting of the software project management plan, specification document,
design document, implementation document, testing/debugging/validation document, user
guide and source code is made available on the project home page.

4.8. Project Presentation

At the Project Presentation, a slide presentation and software demonstration will be given at
the university of buea. The software developed during the project will be demonstrated.

Work Plan

Work Activities

Refer to section 5.1.2 Gantt chart.

[Type text]
Grantt chart for the project activities.

[Type text]
 Schedule Allocation

Resource Allocation

This project will use resources in the form of time and effort that we shall spend developing
the project deliverables as mentioned in section 1.1.3.
Budget Allocation

None.

Control Plan
Schedule Control Plan

[Type text]
If the work scheduled in section 1.1.4 is gets behind, the developer is ready to spend extra
time on the project in between and after the schedules to make up for the lost time and deliver
the final project on time.

Budget Control Plan

None.

Quality Control Plan

Please refer to Testing/Debugging/Validating document.

Risk Management Plan

Risk # 1 “Deficiency in the knowledge and understanding of the problem and its solution”
indicates that the developer does not have the complete understanding of the problem. This
will affect the quality of the project in terms of requirements of the product and their
fulfillment, which is not desirable. Building a prototype for the project model and doing an
extensive literature search can overcome this. This will help us in delivering an efficient and
quality product.

[Type text]
 Technical Process
Methods, Tools, and Techniques
This project adapts the system for use on a Personal Computer. The developing environment
is a personal computer on windows 7, with C++ compiler, Qt 4.7, GDB for debugging.

Support Process Plans

Validation & Verification Plan

A Verification and Validation Plan as a part of the Software Quality Assurance and
Verification & Validation Plan will be developed following recommended departmental
standards. See section 1.1.4 for its delivery date.

[Type text]