Advanced Search
Search Results
106 total results found
Negotiations and Contracting [Mandatory]
Contracting process involves the following: Negotiations - Negotiations with the selected vendor covering the scope of work and financial proposal. Contract drafting: The contract should be drafted by the institution's legal team and technical input from ...
Test planning [Mandatory]
Test planning [Mandatory] The objective of test planning is to define the scope, approach, resources and schedule of testing activities. It includes: Defining test scope and objectives Defining the required resources including testing team, infrastructure...
Test design [Mandatory]
This step involves defining the test scenarios required to test the software requirements and the test cases required to test each scenario. Test cases should include: The reference to the requirement being tested Description of the function or feature ...
Test execution[Mandatory]
In this step testing is executed based on the test plan and test cases. Ensure the testing teams are aware of their responsibilities prior to testing. Ideally the testing team should be in one location to enable easier collaboration. Key activities include: ...
Test closure [Mandatory]
This is the final step in the testing process. The testing phase is closed when the following is achieved: All the tests have been completed and there are justifications for any tests that cannot be completed All critical defects have been resolved. If an...
Factors influencing the decision to upgrade or replace software
Software may need to be upgraded when it starts impacting efficiency, productivity, scalability, security, user experience or compatibility with modern technology. Some of the factors that may result in the need to upgrade software include: No longer meetin...
Measures to implement when upgrading software
The following should be considered when upgrading software to minimize the risks involved in the process such as data loss or security risk. Impact analysis [Mandatory] - Conduct an analysis to fully understand the impact of decommissioning the software. Th...
Planning and scoping [Recommended]
The scope of the project should be realistic and clearly defined Scope management procedures should be put in place to ensure that requests for scope changes are analysed for impact on budget, timelines and resources requirements before they are approved fo...
Vendor management [Recommended]
Evaluation criteria for vendors during the procurement process should factor in their prior experience and qualifications and strength of their team. In addition to evaluation of desktop proposals, wherever possible vendors should demonstrate their existing ...
Governance, roles and responsibilities [Recommended]
The governance and decision-making process for the project should be clearly defined including roles for the project sponsor, steering committee, project manager, internal project team and external vendors if applicable Ensure adequacy and availability of t...
Adopt agile software delivery approach [Recommended]
Agile software development is the recommended approach for Government institutions. The iterative nature of the approach helps to manage complexity, ensure timely feedback from stakeholders, achieve incremental delivery of software where feasible and enable co...
Adoption / change management plan [Mandatory]
New software projects often lead to new ways of working for users and key stakeholders. Change management is therefore important to ensure a high level of engagement of staff and other project stakeholders leading to greater adoption and success of new softwar...
Project plan and schedules [Mandatory]
Project plans and schedules are usually created before the project starts and are continuously updated during the software development process. A project plan defines the project’s scope, schedule, deliverables, milestones and tasks and may take different form...
Progress reports [Mandatory]
A project status or progress report is a document that describes the progress of a project within a specific period and compares it against the project plan. Project managers use status reports to keep stakeholders informed of progress and monitor costs, risks...
Change control documents [Mandatory]
A software change request document should be filled out when a change needs to be made to a software system. It should detail the person and department requesting the change, nature of the change requested, why it is needed and how it will affect other parts o...
Software support issue logs and reports [Mandatory]
During the life of the software users may raise support requests based on issues encountered while using the software. A support issue log is used to track such requests and includes details of the requester, date raised, details of the issue, analysis of the...
Software requirements document [Mandatory]
A software requirements document provides information about the required system functionality based on the needs of the institutions. Requirements are statements of what a system should do. They include functional and nonfunctional requirements and detail the ...
Design documentation [Mandatory]
Software architecture design documents, sometimes also called technical specifications, include the main architectural decisions made by the solution architect. Unlike software requirement documents that describe what needs to be built, the architecture design...
API documentation [Mandatory]
API documentation contains instructions about how to effectively use and integrate with an API. It’s a concise reference manual containing all the information required to work with the API, with details about the functions, classes, return types, arguments and...
Test documentation [Mandatory]
Test documentation describes the process, objectives, and results of software testing. It can also include information on the environment, setup, and configuration required to perform testing. Test documentation is used to communicate the details of a test pla...