preview

Sop for Software Development

Satisfactory Essays

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 …show more content…

6.3.1.3 Adhere to applicable standards and criteria. 6.3.1.4 Conduct peer reviews of the selected product components. 6.3.1.5 Perform unit testing of the product component as appropriate. 6.3.1.6 Revise the product component as necessary. 6.3.2 Establish Software Product Support Documentation 6.3.2.1 Review the requirements, the design, the product, and the test results to ensure that issues affecting the installation, operation, and maintenance documentation are identified and resolved. Use effective methods to develop the installation, operation, and maintenance documentation. Documentation CHECKED BY AUTHORISED BY 6.3.2.2 PREPARED BY NAME DESIGNATION SIGN & DATE FRM No.: KPC/SW-10-01 STANDARD OPERATING PROCEDURE DEPARTMENT : IT & MIS SOP NO.: KPC-SW-10-01 PAGE NO.: 5 OF 8 EFF. DATE: TITLE: SOP FOR SOFTWARE DEVELOPMENT REVIEW DATE: methods are documented, either directly or by reference, in the project's defined process. 6.3.2.3 Adhere to the applicable documentation standards. Examples of documentation standards include the following: Compatibility with designated word processors. Acceptable fonts. Numbering of pages, sections, and paragraphs. Consistency with designated style manual. Use of abbreviations. Security classification markings. Internationalization requirements. Develop preliminary versions of the installation, operation, and maintenance documentation early in the life cycle for

Get Access