Professional Documents
Culture Documents
SDP Template Sem2 1415
SDP Template Sem2 1415
SDP Template Sem2 1415
SOFTWARE
DEVELOPMENT
PLAN
(SDP)
SYSTEM NAME
To be
SOFTWARE DEVELOPMENT
PLAN (SDP)
DOCUMENT APPROVAL
Nam
e
Dat
e
Authenticated by:
Project
Manager
Approved
by:
Client
Software
Archiving Place :
Copies Available :
FSKK
P
TABLE OF CONTENTS
DOCUMENT APPROVAL
ii
TABLE OF CONTENTS
iii
LIST OF FIGURES
LIST OF TABLES
vi
1.
2.
INTRODUCTION
1.1
PROJECT IDENTIFICATION
1.2
PROJECT OVERVIEW
1.3
PROJECT DELIVERABLES
1.4
REFERENCE MATERIALS
2.1.1
2.1.2
2.1.3
2.1.4
Project Resources
2.2
PROCESS MODEL
2.2.1
3.
2.3
RISK MANAGEMENT
2.4
2.5
FORMAL REVIEWS
2.6
2.7
SOFTWARE ENGINEERING
3.1
SOFTWARE ITEMS
3.1.1
Software Items
3.1.2
Hardware Items
3.2
3.2.1
3.2.2
Design Standards
3.2.3
Coding Standards
3.2.4
Testing Approach
3.3
3.3.1
Evaluation Procedures
3.3.2
Evaluation Tools
3.3.3
4.
CONFIGURATION IDENTIFICATION
4.1.1
4.1.2
Identification Methods
4.2
5.
CONFIGURATION CONTROL
4.2.1
4.2.2
Review Procedures
4.3
4.4
CONFIGURATION AUDITS
NOTES
10
LIST OF FIGURES
Figure 2.1: Project Organization Structure.....................................................................2
LIST OF TABLES
Table 2.1: Internal management Organizational Structure............................................2
1.
INTRODUCTION
This section should describe the project and the software product being to be
built.
2.
In this section, describe the organizational structure (e.g., chain of command or management
reporting structure), and responsibilities of individuals on the project.
each
of
the
3.
SOFTWARE ENGINEERING
4.
Project leader has great responsibility in the project. They are responsible to
detect the accurate identification of all the items that involve in the project,
their status and also they need to control and monitor the progress of those
ii.
items.
Business Analyst normally deals with the technology in solving any problems
that arise during the development of the project. They also responsible to
document all the project activities and quarantining that the final product
iii.
contains all the solution that they discussed with the client.
Software Developer responsible in diagnosis, fix any problem in the system,
develop and execute subsystem test plans, procedures and processes. Software
Developer able to determine the priorities in the project development based on
iv.
information. So, all the members must ensure that the objective of the configuration
identification is aligning with the project that being develop.
Changes evaluation
Project manager will have to review the changes requested by the client and
make evaluation about the advantages and disadvantages of the changes. All
the risks or benefit will be list out before make a decision.
iii.
Changes approval/rejection
Based on the evaluation of the changes of CIs requested by the client, project
manager will decide if the changes are approved or not.
iv.
Changes implementation
If the changes of the CIs are approved, implementation process will proceed.
All the changes that occur will be documented to keep track the version
number. So if any problem arises regarding the project, programmer will refer
to the document based on version number.
5.
NOTES