This IV&V Handbook provides the minimum acceptable standards and procedures of the overall IV&V concept and management approach required to conduct an effective IV&V Engagement.
Figure 2.8 shows that an IV&V Engagement typically consists of three (3) phases, and an IV&V Provider may perform IV&V-related activities for all 3 phases. The phases are;
(a) Pre-Engagement Phase (offering input to contractual terms),
(b) Engagement Phase (performing IV&V oversight services),
(c) Post-Engagement Phase (maintenance IV&V) phases.
Table 2.3 below further explains the various IV&V Engagement phases and typical IV&V activities undertaken in each phase.
| IV&V Phase | Description of IV&V activities |
| Pre-Engagement | (a) Preparations for starting and defining the IV&V Engagement: - Stakeholder Requirements and Definition, - ICT Acquisition. (b) Appoint an IV&V Provider. |
| Engagement |
IV&V Provider engaged for the reviews and testing during the process of:
Note: Typically, in the Malaysian public sector, items (a) and (b) in this IV&V Engagement phase will be managed as an ICT Project and usually conforms to the traditional, widely-used structured software development process, e.g., waterfall model.
The process proceeds through the series of steps starting with the requirements definition, and ending with the ICT’s installation and handover to operations. There is usually a review at the end of each step to determine its status and readiness to proceed to subsequent steps. In the pure form of this practice, the different steps do not overlap. Further description of the ICT Project or Lifecycle Classifications are described in:
|
| Post-Engagement |
Work(s) performed after the IV&V Engagement is over, and may be covered by a separate contract:
|
It should be noted that in the structured software development process, the Development Team’s responsibilities for unit, module, integration, and system testing still remains, whilst the IV&V Provider will only augment the testing.
While a structured software development process is illustrated herein, similar support and services should be provided for ICT projects following rational unified process, iterative-type, spiral, agile-type, prototype, or other methodologies.
2.4.1 ICT Project
ICT projects are initiated to meet The Agency’s needs to:
(a) build, enhance or modify the ICT system to be released to users,
(b) maintain production ICT system for business continuity.
These projects are carried out by Development Team that produce deliverables that may consist of a combination of new, enhanced or modified artefacts such as:
• management and technical documents and specifications,
• system/Software,
• test cases,
• guides and manuals,
• etc.
For the purpose of V&V of the software development deliverables, in conformance with the MoF’s procurement guidelines, The Agency will engage IV&V Providers to assess and ascertain the quality of the said deliverables independently from the Development Team.
So as to ensure an objective and successful ICT project, one that is incorporating IV&V, the four (4) main stakeholders (The Agency, IV&V Provider, Development Team, and MyTCoE) shall communicate, agree on, and manage their contractual terms effectively and efficiently.
This IV&V Handbook therefore dictates that the ICT project or lifecycle classification be defined as per Table 2.4 below.
ICT project, depending on the size, complexity, criticality etc., may require more than one classification, possibly executed sequentially, concurrently, or in a hybrid fashion.
When establishing contractual terms, The Agency will need to outline the lifecycle for the IV&V Provider. The Agency shall ensure strong synchronization between the Development Team and the IV&V Provider in the performance of their activities, because:
(a) IV&V is dependent on the progress the Development Team,
(b) synchronization is important to plan out all development situations, including co-sourced, in-sourced, or outsourced Development Team,
(c) Development Team establishing its schedule of milestones, deliverables, and resourcing (human and non-human), which will influence the IV&V scoping.