Sop for Software Development
STANDARD OPERATING PROCEDURE DEPARTMENT : IT & MIS
SOP NO.: KPC-SW-10-01 PAGE NO.: 1 OF 8 EFF. DATE:
TITLE: SOP FOR SOFTWARE DEVELOPMENT 1.0 OBJECTIVE
REVIEW DATE:
To describe the procedure for delivering technical solution through development of new software. 2.0 SCOPE This procedure is applicable to development of all new software application in the IT and MIS department. 3.0 RESPONSIBILITY 3.1 3.2 3.3 Programmers to develop software applications as per laid down procedure. Team Leader shall be responsible to carry out the activity as per procedure. Software Manager shall be responsible to ensure the total development, implementation and training of the procedure.
4.0
ACCOUNTABILITY 4.1 Head of Management Information Systems
5.0 PRECAUTIONS 5.1 Measure the actual cost, effort, and schedule for deploying each process and technology improvement. Measure the value of each process and technology improvement. Measure the progress toward achieving the organization's quantitative objectives for process and technology improvement. Analyze the progress toward achieving the organization's quantitative objectives for process and technology improvement and take corrective action as needed. PREPARED BY NAME DESIGNATION SIGN & DATE
FRM No.: KPC/SW-10-01
5.2 5.3
5.4
CHECKED BY
AUTHORISED BY
STANDARD OPERATING PROCEDURE DEPARTMENT : IT & MIS
SOP NO.: KPC-SW-10-01 PAGE NO.: 2 OF 8 EFF. DATE:
TITLE: SOP FOR SOFTWARE DEVELOPMENT 5.5 5.6
REVIEW DATE:
Store the measures in the organizational measurement repository. Consider the following issues: 5.6.1 Planning, designing, and conducting pilots 5.6.2 Cost/benefit analysis 5.6.3 Technology transition 5.6.4 Change management
5.7 5.8 5.9 5.10 5.11 5.12
Manage Configurations Identify and Involve Relevant Stakeholders Monitor and Control the Process Collect Improvement Information Review Status with Higher-Level Management Determine Causes of Defects 5.12.1 Select Defect Data for Analysis 5.12.2 Analyze Causes
5.13
SOP NO.: KPC-SW-10-01 PAGE NO.: 1 OF 8 EFF. DATE:
TITLE: SOP FOR SOFTWARE DEVELOPMENT 1.0 OBJECTIVE
REVIEW DATE:
To describe the procedure for delivering technical solution through development of new software. 2.0 SCOPE This procedure is applicable to development of all new software application in the IT and MIS department. 3.0 RESPONSIBILITY 3.1 3.2 3.3 Programmers to develop software applications as per laid down procedure. Team Leader shall be responsible to carry out the activity as per procedure. Software Manager shall be responsible to ensure the total development, implementation and training of the procedure.
4.0
ACCOUNTABILITY 4.1 Head of Management Information Systems
5.0 PRECAUTIONS 5.1 Measure the actual cost, effort, and schedule for deploying each process and technology improvement. Measure the value of each process and technology improvement. Measure the progress toward achieving the organization's quantitative objectives for process and technology improvement. Analyze the progress toward achieving the organization's quantitative objectives for process and technology improvement and take corrective action as needed. PREPARED BY NAME DESIGNATION SIGN & DATE
FRM No.: KPC/SW-10-01
5.2 5.3
5.4
CHECKED BY
AUTHORISED BY
STANDARD OPERATING PROCEDURE DEPARTMENT : IT & MIS
SOP NO.: KPC-SW-10-01 PAGE NO.: 2 OF 8 EFF. DATE:
TITLE: SOP FOR SOFTWARE DEVELOPMENT 5.5 5.6
REVIEW DATE:
Store the measures in the organizational measurement repository. Consider the following issues: 5.6.1 Planning, designing, and conducting pilots 5.6.2 Cost/benefit analysis 5.6.3 Technology transition 5.6.4 Change management
5.7 5.8 5.9 5.10 5.11 5.12
Manage Configurations Identify and Involve Relevant Stakeholders Monitor and Control the Process Collect Improvement Information Review Status with Higher-Level Management Determine Causes of Defects 5.12.1 Select Defect Data for Analysis 5.12.2 Analyze Causes
5.13
References: 7.1 7.2 CMMISM for Systems Engineering/Software Engineering, (CMMI-SE/SW, V1.02) IEEE standard for software project management plans (1058-1998) IEEE Standard for Software Verification and Validation (1012-2004) IEEE Standard for Developing a Software Project Life Cycle Process (1074-2006) IEEE recommended practice for software design descriptions (1016-1998) IEEE recommended practice for software requirements specifications (830-1998) “current Good Manufacturing Practices Guidelines” Simplicity Structured Maintainability 7.3 8.0 REVISION HISTORY Sr. No. 01 02 Revision Date Revision Status 00 Details of Revision Remarks First Issue 9.0 APPENDIX PREPARED BY NAME DESIGNATION SIGN & DATE FRM No.: KPC/SW-10-01 CHECKED BY AUTHORISED BY