CMMI - L 3 - Defined - PI, VAL, VER

Product Integration

This process area is more focussed towards Systems Engineering. It talks of how big hardware and software systems are integrated. (This does not refer to Integration testing.) In software scenario, this refers to how different data streams (input, output) are integrated. That is, how the business flow is maintained.

Verification

Verification, as the name suggests is to ensure that the work products (all work products like Requirements, Design, code, test plans) meet their required criteria. The activities involved here are preparation for verification, performing the verification activity and identifying corrective actions.

The goals in this process area are:

1. Prepare for Verification
2. Perform Peer reviews
3. Verify selected work products

All reviews, Unit testing, Integration testing and System testing come under part of verification. Specific significance is given to reviews, since finding and correcting defects through reviews, very early, is highly cost effective. Also, you cannot “test” a requirement document or a design document – you can “review” them !

Experience has proved that cost of rework increases by a factor of up to 100, as we find defects late. Earlier the defects are found, the better. That is where a formal review process (with standards, checklists) help.

Validation

Validation on the other hand, focuses on Acceptance testing. This is to demonstrate that a product fulfills its intended use. Actually the differentiating line between Verification and Validation is very thin.

The goals for Validation are:

1. Prepare for validation
2. Validate product


Next - CMMI - L3 - DEFINED - Risk Management