Вы находитесь на странице: 1из 10

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S

Annex A: Project Implementation Schedule


Month

Month

1
2
Month3 Month4 Month5 Month6
WEEKS
1 2 3 4 5 6 7 8 9 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2

Activity

0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
Project Planning
Prepare Kickoff

Presentation
Kick-off

Meeting
Formulate
BPS

Training Plan
Review
PIP
and

Training

Plan
Revise

and

Finalize

PIP

and

and

Training

Plan
Approve

and

Accept

PIP

and
Plan

Training

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S
Milestone:
Approved

PIP

and Training Plan


Needs
Assessment/Sys
tems
Investigation
Conduct
Needs
Assessment
and

Systems

investigation
Prepare User
Requirements/
Needs
Assessment

Report
Review Report

(PIP)
Revise

and

Finalize

Reports
Approve

and

Accept
Reports (PIP)

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S
Milestone:
Approved Needs
Assessment
Report
Hardware

and

Software
Upgrade,
Installation

and

Configuration
Gather Data
Run Capacity

Planning Tool
Prepare and
Submit
Hardware
Recommendat
ion

and

System
Architecture
Provide and
Configure
Recommended
Hardware
Infrastructure

and

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S
(PIP)
Formulate
Functional
Requirements
Specification
Review FRS

(PIP)
Revise

Finalize FRS
Approve and
Accept

and

FRS

(PIP)
Milestone:
Approved FRS

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S

Annex B: Change Request Form


Project Title:
HDS

Change Request #
Date:

Change Request Form

Customer:

Priority: [High, Medium or Low]

Requested By:

Affected System(s):

Description of Change Request:


[Describe the change being requested. Describe impacts to existing objectives and
deliverables as well as new objectives and deliverables.]
Justification / Reason for Change: [Provide a business case for the change being
requested.]
Effort estimates [in hours] to change:
Project Plans

Total Hours:

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S
Requirements

Total Hours:

Design

Total Hours:

Test

Total Hours:

Implementation

Total Hours:

Impacts:

Describe impacts on Scope, Requirements,


Describe risks associated with this change or overall impacts of change on project
risks.
Describe impacts of change on project schedule.
Include information about impacts on project budget with details of associated costs.
Describe any impacts to the project management plan or project organization.

Identify requirements, products/deliverables changes:


Total Hours:
[Describe

adjustments

to

project

requirements

and

deliverables]
Description of risks:

[Describe risks associated with making changes to system, project, and business]

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S
Recommendation:

[Discuss proposed action based on recommended change and impacts.]

Evaluated by:

Date:

Change Request Approval:


Reviewed

By:________________________

Project Date:

Manager

Approved By:________________________ Customer

Annex C: Bug Report Form

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S

HDS

Project Title:
Date:

Bug Report Form


Application:

Phase: [Test Phase - Unit, Functional,


Operational,

Reported By:

User

Acceptance;

Warranty

Period]
Affected Module(s):

Description of Issue/Bug:
Severity:

Status:

1 Urgent/ Very high priority

Assigned a point person has been

2 High priority

assigned

3 Medium priority

resolution of error/issue.

4 Low priority

In process being resolved by assigned

5 Very low priority

person

to

take

responsibility

for

By design not a programming issue


Pending nobody has been assigned to
Resolved error resolved

the

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S
Details:

[Describe details of the error or bug. Describe steps made before the error/bug occurred.
Insert
Screenshots.]
Resolution:

[Describe resolution made to solve the error/bug.]


Assigned To:
Date Resolved:

Annex D: Test Script Template


Test Case:
Test Phase:

Functional

Operational

Acceptance

System Test

System Test

Test

Unit Test
System/

P O LYT E C H N I C U N I V E R S I T Y O F T H E P H I L I P P I N E S
Application:
Test Objective:
Date(s) Executed:
Tested By:
Pre-condition:
Post-condition:

Defect/
I

Test

User

Condition Action

Input

Expected

Actual

Data

Results

Results

Pass/Fail Issue
No.