<Project Name>

Project or Software Development Plan

Project Title

SEMESTER MAC 2019 – JUL 2019

GROUP: A4CS1104A/B/C/D

Name 1, student number 1

Name 2, student number 2
Name 3, student number 3
Name 4, student number 4
<Project Name> Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<document identifier>

Revision History
Date Version Description Author
<dd/mmm/yy> <x.x> <details> <name>

Confidential  CS1104/A/B/C/D 20xx Page 2 of 9

 <Project Name> Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<document identifier>

Table of Contents
1. Introduction 4
1.1 Purpose 4
1.2 Scope 4
1.3 References 4

2. Project Overview 5
2.1 Assumptions and constraints 5
2.2 Project deliverables 5

3. Project Organization 6
3.1 Organizational Structure 6
3.2 External Interfaces 6
3.3 Roles and Responsibilities 6

4. Management Process 7
4.1 Project Plan 7
4.2.2 Project Schedule 7
4.2.3 Project Resourcing 7
4.2.4 Budget 7

Confidential  CS1104/A/B/C/D 20xx Page 3 of 9

 <Project Name> Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<document identifier>

Project or Software Development Plan

1. Introduction
1.1 Purpose of SDP
[A short overview in which the students (team members) will justify:
 the significance of having a SDP to the clients, stakeholders and any external parties
involved.
 list the aspects that the students (team members) cover throughout the development
process
 For example; SDP is prepared to define the strategies in conducting the system
development project to avoid any delays and overbudget in completing the project.
The strategies may also include how the project will be implemented, observed and
controlled.]

1.2 Problem Statement

<A brief explanation on why this project is needed. Is the idea of completing this project comes from any
external clients’ request (e.g. to address corporate goals) or comes from the students (team members) own
problem? If the students (team members) would like to upgrade any existing system, they are strongly
recommended to include backgrounds of that existing system>

1.3 Project Objectives

<The project objectives must comply with S.M.A.R.T (Specific, Measurable, Agreed upon, Realistic, Time-
bound). If the project involves external clients, they must also agree on the objectives. Objective such as
“to develop (or design) a system that has an efficient user-friendly interface” should be avoided as it is
difficult to measure the efficiency of “user-friendly”>

1.4 Scope
<Project scope describes the project boundaries, what the project will and will not deliver. Project scope
must relate to the stated project objectives earlier. Example of activity that will not be included is provide
in-house training to the clients>
1.4.1 Included
1.4.2 Excluded

1.5 References
[This subsection should provide a list of all documents referenced elsewhere in the Project or Software
Development Plan. Each document should be identified by title, report number (if applicable), date, and
publishing organization/group of students. Specify the sources from which the references can be obtained.
This information may be provided by reference to an appendix or to another document.]

Basic Format for Books

Author, A. A. (Year of publication). Title of work: Capital letter also
for subtitle. Location: Publisher.

Confidential  CS1104/A/B/C/D 20xx Page 4 of 9

<Project Name> Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<document identifier>

Example:
Calfee, R. C., & Valencia, R. R. (1991). APA guide to preparing
manuscripts for journal publication. Washington, DC: American
Psychological Association.

Basic Format for Online Periodical

Author, A. A., & Author, B. B. (Date of publication). Title of
article. Title of Online Periodical, volume number(issue number if
available). Retrieved from 
http://www.someaddress.com/full/url/

Example:
Bernstein, M. (2002). 10 tips on writing the living Web. A List Apart:
For People Who Make Websites, 149. Retrieved from
http://www.alistapart.com/articles/writeliving

Basic Format for Human

Name, Position.
Date interview:

Confidential  CS1104/A/B/C/D 20xx Page 5 of 9

 <Project Name> Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<document identifier>

2. Project Overview
2.1 Assumptions and constraints
[A list of assumptions that this plan is based on, and any constraints (e.g. budget, staff, equipment, and
schedule) that apply to the project.]
<Assumptions are what are the things that the students (team members) assume to happen when this system
is developed. Typically, assumptions are associated with positive things, for example if the student requires
a portable scanner, there will be a vendor who can supply that equipment on time. However, if the vendor
is not able to supply the portable scanner on time, the project objectives, budget and schedule need to be
reassessed.

Constraints are real world conditions that the system must achieve that involve hardware, software, policy,
time etc. Constraints also define the project scopes. An example of a constraint is “the delivery order
system must accept inputs from a maximum of 5 remote sites at one time”. By examining the constraints,
students (team members) can identified whether the constraints must be met immediately after the system is
completed or the constraints are necessary at some future time >

2.2 Project deliverables

[Tabular list of the artifacts/end products to be created during the project, with target delivery dates.]

Confidential  CS1104/A/B/C/D 20xx Page 6 of 9

 <Project Name> Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<document identifier>

3. Project Organization
3.1 Organizational Structure
[Describe the organizational structure of the project team (Project Manager, Database Designer,
Programmer 1, Programmer 2, and supervisor among lecturer.]
3.2 External Interfaces
[Describe the project external groups if have. For each external group, identify the internal/external
contact names. If your group do not have link to any external group, just leave this blank for this section!]
3.3 Roles and Responsibilities
[Identify the project organizational units that will be responsible for each of the core workflows, workflow
details, and supporting processes.]

Confidential  CS1104/A/B/C/D 20xx Page 7 of 9

 <Project Name> Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<document identifier>

4. Management Process
4.1 Project Plan
4.1.1 Project Schedule
[Diagrams/tables showing target dates for completion of iterations and phases, release points, demos, and
other milestones.---please use Microsoft project for your milestone target
 Identify major milestones with their achievement criteria
 Define any important release points and demos]
4.1.2 Project Resourcing
4.1.2.1 Staffing Plan
[Identify here the numbers and type of staff required (including and special skills or experience), refer to
project team organizational structure.]
4.1.3 Budget
[Allocation of costs (software, salary. etc.)]

Confidential  CS1104/A/B/C/D 20xx Page 8 of 9

 <Project Name> Version: <1.0>
Software Development Plan Date: <dd/mmm/yy>
<document identifier>

5. Abbreviations and Definitions

<The students can write shorter version of any terms to maintain the simplicity of the documentation, or
even to reduce the size of paragraphs. This section will list all the shorter words along with their definitions
used within this SDP. Example:
HTML Hypertext Markup Language
SDLC Software Development Life Cycle>

Confidential  CS1104/A/B/C/D 20xx Page 9 of 9