Integration Testing Approach

on Tuesday, 01 January 2013. Posted in Business Analysis, Blog

 

The following diagram summarises the 'V' integration testing approach, that I have used on my projects.

Each blue lozenge on the left represents a requirement or specification baseline.  The corresponding lozenge(s) on the right represent a test level which verifies or validates the implementation against the requirement or specification. 

The green boxes represent reviews at which the artefact is approved and baselined, i.e. becomes subject to formal change control.The diagonal dark blue arrows, making up the “V” show at a high level the flow of traceability.  Requirements traceability is a technique used to provide relationships between requirements, design and implementation of a system in order to manage the effect of change and ensure the success of the delivered systems.

 

 

int_testing

 

I have received multiple emails on Enterprise Software(ERP, CRM, EPM) cutover , in the next couple of blogs will write about go-live readiness, project plan, the importance of data cleansing and cutover dependencies with the business counterparts.

 

 

 

Comments (1)

  • Melinda from Texas

    Melinda from Texas

    22 January 2013 at 01:56 |
    I just transfered to the QA dept that tests integration for all of my companies enteprise software packages . lots of usefull information for me to get started could i use this diagram is it copyright will send you an email. Solid Info!

Copyright 2015 Appsconsultant.com. All rights reserved.