Establishment of Requirements - Requirements Engineering and Management for Software Development Projects - page 83

5. Testing—testing of the new layer or the code changes of the COTS product are
tested to uncover defects lurking inside the code. Once all the defects are
rectified, the code would be passed on to the next stage.
6. Implementation—during this stage, the COTS product would be implemented.
Then if a new software layer is built, it would be implemented. Now the
implementation is tested to ensure that all functionalities are working as
designed without any defects, it would be commissioned for use in the

organization.

The above description is very brief and meant just to record an overview of an
elaborate process for COTS product implementation. Different organizations
would have different stages/phases with different nomenclature. For the purpose of
this topic and the topic, gaps analysis and SOW documents are relevant and would
be discussed in greater detail.

5.6.1 Gaps Analysis Document

This document records the gaps between the COTS product and the functional
practices of the client organization. Table 4.2 in Chap. 4 gives the suggested
format for capturing the gaps uncovered during the requirements analysis phase of
COTS product implementation projects. This is the first level document prepared
in the projects implementing a COTS product (such as ERP, SCM, CRM, or a data
warehousing product and so on). This document is the equivalent of URS in
software development projects. Based on this document, the SOW document
would be prepared.

5.6.2 SOW Document

SOW document in COTS product implementation projects may be viewed as the
equivalent of the SRS document in software development projects. It documents
the product specifications for the COTS product implementation projects.
SOW document would normally have four sections, namely, the title page, table
of contents page, SOW pages and the closing pages. A suggested template for
capturing the SOW is given in Table 5.3 .
Using this document, software design to build the additional layer or modify the
code is carried out.
The activities of quality control, obtaining approvals and configuration man-
agement are as described in Sects. 5.3 , 5.4 and 5.5 .