SOFTWARE PROJECT MANAGEMENT PLAN

Rationale

Today, the advancement of technology has enabled educators to teach their

lessons in many different ways. Using our technology’s advancement, introducing the

Philippine history to students through educational games would be a new scene and at the

same time, an engagement for them.

A. Software Project Overview

a. Project Summary

i. Purpose, Scope and Objectives

Purpose

Regarding in our study we make a trivia game to provide an extra help in

developing and improving the ability of the student in learning Philippine History and

minimize the time consumed. To give an informative tool to them, they can easily learn
and adopt a new word and amplify their knowledge about Philippine History. With the

use of this trivia game, lesson makes faster and easier.

Scope

A trivia game is a unique way to help the students learn Philippine History in an

entertaining way.

Objectives

The aim of this project is to have an educational tool that will help the students

1. Help the teacher explain the lessons to the students.

2. Determine the history topics taught to students in grade 6.

3. Identify the specific topic where the students are having difficulty about Philippine history.

4. Design and develop an educational game that teaches the students about the Philippine
history

ii. Project Assumptions and Constraints

The advocates of this document are expecting to complete the project in this

semester. Business strategy will change during this project cost of materials; will increase

during the project development stage. Reliable information and resources are available

during the project development stage.

One of the constraints that the proponents will meet is the deadline of the project

it should be on time. Constraints include the following:

  The project must be user-friendly.

 The product must be reliable.

 The deadline must be met.

 The product must be effective to the students.

iii. Project Deliverables

 Software Project Management Plan

 Software Requirements Specification

 Software Design Document

 Software Requirements Specification

 Finished Project

 Architectural Design

 System User Interface

 System Decomposition

 Chapters 1, 2, 3, 4 and 5

 Hard Bound

iv. Schedule and Budget Summary

Budget Summary:

2 ream Short Bond Paper (8.5 in x 11 in) P 2,000

Internet Connection Subscription P2,000

Printing P1,000

Transportation P1000
 TOTAL: P6,000

Due Dates:

 Software Project Management Plan Dec. 2, 2014

 Software Requirements Specification Dec. 10, 2014

 Software Design Document Jan. 6, 2015

 Architectural Design Jan. 6, 2015

 System User Interface Jan. 6, 2015

 System Decomposition Jan. 6, 2015

 Finished Project Feb. 28, 2015

 Chapters 1 March 19, 2015

 Chapters 2 March 19, 2015

 Chapters 3 March 19, 2015

 Chapters 4 March 19, 2015

 Chapters 5 March 19, 2015

 Hard Bound March. 21, 2015

B. References

1. Pressman, Roger. (2010). Software Engineering 7th Edition, NY: McGRAW

HILL Companies

2. www.w3schools.com
 3. The IEEE Document Standards published in IEEE Standards Collection. 2nd

edition.

C. Operational Definition of Terms

Term Description

Audio-Visual lesson language Design to aid in learning or teaching by making

use of both hearing and sight.

Audio Dictionary Electronic resource that list the words of

language that provide an audio to dictate the

proper pronunciation of the words.

Server Hosts the database server.

Database Stores all users’ information.

Software Project Management The deliverable which consists of the project

Plan plan.

Software Requirements The deliverable which consist of the project’s

Specifications requirements specifications, features, and other

qualities of the project.

Software Design Description The deliverable which provides the project’s

planned design, planned software paradigm to be

used, architectural design, and interface design

and its explanation.

Waterfall Model The software paradigm used by the proponents.

Data Modeling Show the system’s table and its specific column

names.

Object-oriented Modeling Show the system’s use cases.

Scenario-based Modeling Shows the software’s activity diagram that

emphasize the various activities done by the user

and to show how the system responds during

processes.

Flow-oriented Modeling Uses Data Flow Diagrams to represents how data

objects are transformed as they move through the

system.

Class-based Modeling Used to show objects, operations, relationships

and collaborations of each class.

Class-responsibility- Used as part of the representation in Class-based

collaboration card Modeling.

 Behavioral Modeling Used to make a list of the different states of a

system and indicates how the system makes a

transition from one state to another. The

Proponents used sequence diagrams to show how

the system behaves in different scenarios.

Sequence Diagram Used by the proponents to represent Behavioral

modeling.

Component-level Design Used to show the specific components of Online

lesson language.

User Interface Design Shown through the graphical user interface

design of the online lesson language. The goal of

the GUI is to make the user’s interaction as

simple and as efficient as possible.

Software Paradigm The Proponent’s planned analysis model to use.

D. Project Organization

a. External Interfaces

Mandarin language teachers

Students

Faculty

b. Internal Interfaces
 The development team consisting of Panis, Hannah Junar Vee P.

Philippine History Interactive Trivia Game

Panis, Hannah Junar Vee P.

Programmer
Analyst
Budget Officer
Presenter
Secretary

c. Roles and Responsibilities

The team leader is the one who manages and assigns specific tasks to its

team members.

He plans the proper sequence of activities the team must follow in order to

maximize the small amount of time given to complete the project. The team

leader also monitors the team’s project progress to ensure the project’s

completion before the deadline.

The programmer is the one who makes the software. He is responsible for

the software’s structures and functions through coding. He solely focuses in

coding the software and applies algorithms to be used in the software’s certain

functions.

The software analyst is the person who studies the software application

domain and prepares the software requirements and specification (SRS)

 document. The software analyst identifies the possible problems that may hinder

the progress of the project in the development stages and formulates the solutions

to those problems to ensure the smooth run of the project’s progress.

The presenter is the one who gives a detailed presentation about the

project’s overall content. He thoroughly tackles the complete information about

the project and explains its content to the audience.

The secretary is the person responsible for the project’s documentation.

He lists all the important information related to the project and gives a complete,

formal, and detailed documentation of the project’s progress and contents.

The budget officer is the one who manages the resources to be used in the

project. He efficiently and effectively assigns the resources for each activity to

make sure that the limited resources of the project are enough for the project’s

completion and no resources would be wasted in the project’s course.

Major Activities Team Member Role

Software System Proposal Team Leader and Programmer: Panis, Hannah

Junar Vee P.

Analyst and Presenter: Panis, Hannah Junar Vee

P.

Secretary and Budget Officer: Panis, Hannah

Junar Vee P.
 Software Project Management Team Leader and Programmer: Panis, Hannah

Plan Junar Vee P.

Analyst and Presenter: Panis, Hannah Junar Vee

P.

Secretary and Budget Officer: Panis, Hannah

Junar Vee P.

Software Requirement Team Leader and Programmer: Panis, Hannah

Specification Junar Vee P.

Analyst and Presenter: Panis, Hannah Junar Vee

P.

Secretary and Budget Officer: Panis, Hannah

Junar Vee P.

Software Design Document Team Leader and Programmer: Panis, Hannah

Junar Vee P.

Analyst and Presenter: Panis, Hannah Junar Vee

P.

Secretary and Budget Officer: Panis, Hannah

Junar Vee P.

E. Managerial Process Plans

a. Startup Plan

i. Estimation Plan
 As the previously stated, the total development time is estimated to be a

semester and the total cost will be P6, 000.

ii. Staffing Plan

The entire project is needed for the entire semester, in managerial capacity

the preliminary requirements will be made with the system analyst. And the

half of the semester it would be the system development with the help of the

programmer and tester.

iii. Resource Acquisition Plan

All necessary hardware, software and case tools for the project are already

available. After making the system, the product will be delivered to the user

through internet.

iv. Project Staff Training Plan

No additional staff training is needed for this project.

b. Work Plan

i. Work Activities

Task

 Software Project Management Plan. The document, once

developed, will be altered throughout the life of the software’s

development.

 Software Requirements Specification. The document must be

completed and agreed upon by all parties by the end of December.

  Software Design Description. The final version of the document

must be agreed by the two developers.

 Chapter 1-2. Contains the project overview and the capabilities.

 Compilation of project for final submission. A period of time will

be allocated towards the end of the projects development to

compile all documents and code together into the deliverable

package.

ii. Schedule Allocation

Any reliable information and resources related to the study will be use and

spent in determining the project. Through conducting interview, gathering

information and observation.

iii. Budget Allocation

The project will utilize the resources in the form of printing materials and

laptop/desktop and it will all be spent in making the project deliverables.

c. Control Plan

i. Requirements Control Plan

Any major changes that affect the milestone have to be approved by the

team leader and the documented and will be determine whether they are

following the specification document and the project management plan.

ii. Schedule Control Plan

 If the work schedules gets behind, the team 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 and met the due date of the project.

iii. Budget Control Plan

The budget officer will be the responsible for ensuring that the project is

completed on time and if the budget is properly allocated.

iv. Quality Control Plan

The software quality assurance plan will be developed following

recommended departmental standards.

v. Reporting Plan

Any major problem faced by the team member will immediately be

reported and recorded by the secretary.

vi. Metrics Collection Plan

Metrics collection will be made a comparison between what is build and

what had built, so we anticipate the error happening and then extra cost

estimation.

vii. Risk Management Plan

The user is assumed to be a first timer with this kind of software.

Therefore the product has to be made as user-friendly as possible so that it will be

useful for them.

 The product should meet the specified objectives for the system.

viii. Closeout Plan

All details about the research, project objectives, analysis on reports and

the milestone achieved should be mentioned as part of the final documentation at

the end of the semester as final requirements for the Software Engineering course.

F. Technical Process

a. Process Model

There is various software development approaches defined and designed

which are in use during development process of software, these approaches are

also referred as “Software Life-cycle Models”, such approach/process used in

software Life-cycle id “The waterfall Model” because this method seems to fit

and is one of the effective model to use.

b. Methods, Tools and Techniques

The project is a web development which uses JavaScript, PHP, HTML,

jQuery and Notepad++.

c. Infrastructure Plan

Before the start of the project, the proponents assigned tasks and gathered

data relevant to the project. The proponents will then develop the project using

Notepad++.

d. Product Acceptance Plan

The instructor will test the system/application for acceptance.

G. Supporting Process Plans

a. Configuration Management Plan

The project deliverables are to be considered as website. The

configuration item as well as its file would be used after the document like SRS,

SDD and followed by the version number. The preliminary version of the entire

documents would be submitted to the adviser for checking.

b. Validation and Verification Plan

A Verification and Validation Plan as apart of the Software Quality

Assurance and Verification and Validation Plan will be developed following

recommended departmental standard.

c. Documentation Plan

Documentation will be produced as specified in the IEEE Standards. All

the documents will be discussed and reviewed with the adviser before the final

documentation are issued and distributed to the members of the committee on the

due dates mentioned.

d. Quality Assurance Plan

A Software Quality Assurance Plan will be developed following

recommend departmental standards.

e. Review and Audits

The programmer and Team leader will test the code, and Analyst and

Secretary will conduct integration testing. Extensive product testing will then be

performed by the team.

f. Problem Resolution Plan

Any major problems faced by the team members will immediately be

reported by the instructor and adviser.

g. Subcontractor Management Plan

N/A

h. Process Improvement Plan

All activities will be conducted in accordance with the business units plans

and the company itself to make the project proposed successful.