Copy No.

:
Effective Date : 1 September 2005
SYSTEM DEVELOPMENT
Revision No. :0
LIFE CYCLE (SDLC)
PROCEDURE Revision Date : 1 September 2005
Page : 1 of 3

REV.NO REVISION NOTES

1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Prepared By Reviewed By Approved By

 Copy No. :
Effective date : 1 September 2005
HIGH-LEVEL PROJECT Revision No. :0
DEFINITION Revision Date : 1 September 2005
(TEMPLATE)
Page : 2 of 3

PROJECT ID / DESCRIPTION

Primary User /Dept

Other Users
Project Manager Name
Project Manager Phone/Extension
Project Manager E-mail
Prepared by / Date

1. Objectioves
a. What we need tp achieve by developing and/or implementing such project?
b. What the project is intended to accomplish and why it is being undertaken
(e.g. to resolve problems or to satisfy statutory requirement)
c. The following questionnaires can help to define the objectives:
• What is the general intent of the product?
• What organizations or departmental functions will the product
support?
• What are the major functional components of the product?
• Will the product produce any files or reports or provide data for
Government agencies, organizations and/or applications?
• Will the product use any files, reports or data generated from
Government agencies, organizations and/or applications?
• What Departmental mission(s) will the product support?
• What Departmental strategic goal(s) will the product support?
• Will the product be aligned with HRD’s plan, programs?

2. Goals – enumerate each of the stated objectives

a. Please also include schedule of deliverables (and dates)

3. Justification/Benefit – Why we need to achieve the stated objectives/goals?

Please include description of any deficiencies in the current manual and/or automated
process, the severity and impact of any problems, and the solutions and benefits that
will result from developing and/or implementing the project.

4. Scope – brief but concise description of the environment fostering the development
and/or implementation
a. Development/testing environment
b. Operating environment
• What user processes, organizations, and functions that will be
affected by the product?
 Copy No. :
Effective date : 1 September 2005
HIGH-LEVEL PROJECT Revision No. :0
DEFINITION Revision Date : 1 September 2005
(TEMPLATE)
Page : 3 of 3

• Identify the anticipated changes to current manual and/or automated

processes
Note: the scope may need to be downsized to remain feasible within the
constraints of resources, budget, time and risks negotiated with the primary
intended user.

c. The following questionnaires can help to define the scopes:

• What are the locations of the employees who will use the product?
• What tasks will be performed using the product?
• What will be the operating schedule for the product?
• How many and what types of reports will be needed?
• How and when will the report be distributed? Who receives the
reports?
• What query capabilities are needed?
• Are major changes in requirements anticipated in the next few years?
• Are major changes in level of use anticipated in the next few years?
• What is the estimated life expectancy of the product?
• What are the security requirements for the product?
• What are the standards, guidelines, policies with which the product
must comply?
• Will the product be mission-critical to IT Division or to user?
• Will the product contain vital records?
• What are the disaster recovery requirements for the product?
• Will the product require telecommunications?

5. Technologies Employed and/or Application Architecture

a. Major technologies (network, operating system, telecommunication, etc)
b. Anticipated application architecture (database, programming languages, etc)

6. Security – How security is being implemented in the system?

a. Development environment: source code, database integrity checking, etc.
b. Operating environment: menu applicatiom, network access/storage, etc.

7. Current Status
a. Current project status, phase, and SDLC approach
b. Schedule of deliverable completion review

8. Next Steps
a. Discuss how to complete the project remaining goals
b. Highlight of near-term efforts
c. Requested/required actions from other departments