Sofware

Ministry of Communications and Information Technology National Information Centre General Department of Information Technology Information Systems Department Policies and Standards Section

Software Procurement Standards
Commission on software standards

July 2010

First version

NIC/SD/SPS V1.0 :2010
1

Table of Contents
Page

Acronym List Section A – Introduction to RecommendedPractice Forward Introduction Summary of Model Description Graphical Representation of Process Model Section B – Detailed Description of Phases and Steps Initiation Phase Planning Phase Contracting Phase Implementation Phase Acceptance Phase Follow-on Phase Process Improvement Phase Section C – Recommendations and Further Reading Model Implementation, Tailoring and Enhancement References Section D– Appendices, Templates and Toolboxes Appendix A – Initiation Phase Check-lists Appendix B – Planning Phase Check-lists Appendix C – Contracting Phase Check-lists Appendix D – Implementation Phase Check-lists Appendix E – Acceptance Phase Check-lists Appendix F – Follow-on Phase Check-lists Appendix G – Process Improvement Phase Check-lists Template 1 – Solution Analysis Worksheet Template 2 –Project Proposal Template 3 – Project Charter Template 4 – Acquisition Plan Template 5 – Sample Contract Template 6 – Product Dossier Template 7 – Evaluation Record Toolbox 1 – Information Gathering and Communication Tools Toolbox 2 – Solution Comparison Methods Toolbox 3 – Requirements Definition Toolbox 4 – Evaluation Criteria Lists Toolbox 5 – Product Evaluation Methods Toolbox 6 – Methods ofCollection in User Surveys Toolbox 7 – CMMI-ACQ Implementation Questions

3 5 6 8 10 12 15 19 24 26 28 29 32 33 38 42 48 56 57 61 66 68 72 77 81 84 85 86 88 88 88 90 92 94 96
3

National Information Center- General Department of Information Technology - Information Systems Department - Policies and Standards Section

Acronym List

IEEE 1062, IEEE 610

Acquisition: The process of obtaininga system or software product. Acquirer: A person or organisation that acquires or procures a system or software product (which may be part of a system) from a supplier. Contract: A binding agreement between two parties, especially enforceable by law or similar internal agreement wholly within an organisation, for supply of service or for the supply, development, production, operation, ormaintenance of a software product. COTS (Commercial Off The Shelf) Software: A software product that is driven by market-need and commercially available and whose fitness have been demonstrated by a broad spectrum of commercial user. Criticality: The degree of impact that a requirement, module, fault, error, failure, or other item has on the development or operation of a system. Fully developed(custom-built) Software: Software that is produced on a one-of-a-kind or low volume basis that is usually unique to a specific application. MOTS (Modified Off The Shelf) Software: Software product that is already developed or available, usable either “as is” or with modifications, and provided by the supplier, acquirer or third party. Product: A complete set of computer programs, procedures and associateddocumentation and data pertaining to the operation of a computer system. The term is applicable to COTS, MOTS and custom-built software. Request for Proposal (RFP): A document used by the acquirer as a means to announce intention to potential bidders to acquire system of software product (which may be part of a system). Software acquisition process: The period of time that begins with the decisionto acquire a software product and ends when the product is no longer available for use. Statement of Work: A document used by the acquirer as a means to identify, describe, and specify the tasks to be performed under the contract. Supplier: A person or organisation that enters into a contract with the acquirer for the supply of a software product (which may be part of a system) under the terms...