Focus: Validation is a key component of the Accenture V-Model Content: Validation occurs across stages.

s. Validation checks that the deliverables satisfy the requirements specified in earlier stage/s deliverables, and that the Business Case continues to be met. By doing so, it ensures that deliverables (work product) are within scope, contribute to the intended client benefits, and do not have undesired side effects. While techniques for validation vary based on the deliverable, validation is typically accomplished via simulations, inspections, or prototyping. For example, validation of the Technology Infrastructure may involve prototyping to ensure that targeted performance metrics are met; validation of test scripts may involve reviews to ensure that all documented requirements are thoroughly covered. One useful validation tool is the traceability matrix. Remind participants that we have discussed the traceability matrix at several points already in this course. The traceability matrix can be cross-referenced during tasks such as test plan writing to ensure that all requirements are addressed.

In summary, Validation is Doing the right thing: Effectiveness Validation - The activities performed on a deliverable to determine that it satisfies requirements. Frequently performed in conjunction with verification. In other words, VALIDATION ensures everything is in SCOPE and conforms to specific requirements. Therefore, here we emphasize that the TEST is as effective as the SCOPE. Validation really just asks the questions WHAT WORK MUST BE DONE TO SATISFY THE REQUIREMENTS? HAS ALL THE NECESSARY WORK BEEN DONE TO SATISFY THE REQUIREMENTS?

You may also know validation as SCOPE CHECK!

Focus: Verification is a key component of the Accenture V-Model Content: Verification occurs within each stage. Verification checks that a deliverable is correctly derived from the inputs of the corresponding stage, and is internally consistent. It also ensures that both the deliverable, and the process for creating that deliverable, conform to the standards in the projects quality plan. While verification techniques will vary depending on the deliverable, the most common technique is a deliverable inspection (and reviews). This technique uses a number of reviewers to check the deliverable for functional completeness, adherence to standards, and correct use of the technology infrastructure. (Additional Note not on slide) Repository validation is another effective technique for verification. Repository validation can be used when a design repository (e.g., BI Designer) is employed on a project and cross checks can be executed against the repository to ensure integrity of dependencies between variables.

In summary, Verification is Doing it the right way: Efficiency Verification - The activities performed on a deliverable to ensure that the deliverable is correctly derived from the inputs to the stage that creates it, is internally consistent, and conforms to standards. Frequently performed in conjunction with validation. The verification of a specification deliverable identifies errors in that deliverable before they are passed on to the next stage of development. Verification really just asks the question Has the work been done correctly?

You may also know Verification as Peer Reviews.

Validation - focuses on ensuring that the business case, requirements, and user expectations are met.

Verification - focuses on finding faults or errors.