QA Plan of Data Conversion

1
QA Plan of Data Conversion
2
index

• QA Plan of Data Conversion
• The Value of a Comprehensive Data Conversion QA
  Plan
• Timing is Everything
• Iterate
• Engage
• Contact US

3
QA Plan of Data Conversion

• Client satisfaction is significant
• Parameter UAT(User Acceptance Testing) is great
• Even if it took a long period to complete
• Corrections and the supporting client services
  that are required at this phase of the project

4
QA Plan of Data Conversion

• Customer of altering their opinion
• Failing to give interim feedback,
• The programmer failing to comprehend what was
  required
• Unclear communication between business analyst
  and programmer
• Lack of enough time and cash for the UAT re-work
  cycle.
• Recognize issues early makes least expensive to
  correct.

5
The Value of a Comprehensive Data Conversion QA
Plan

• Data load revisions that so often surface during
  UAT
• Further, the excessive revision that follows can
  be kept away from if there is a quality assurance
  plan for the data conversion from the begin of
  the project.
• There will be a dedicated resource for software
  testing, but in the data conversion, we tend to
  concentrate our QA efforts on record checks and
  other metrics.
• This is the reason such a large number of data
  conversion issues dependably appear to surface
  during UAT this is frequently the first run
  through the customer is practicing a full scope
  of system processes using their own data.

6
Timing is Everything

• Much the same as your software QA design
• Data conversion QA plan ought to be built up
  during the planning stage
• Test cases and load validation reports
• Not to be restricted to SQL queries and reports.
• Incorporate the use of select system process with
  loaded client data as that is the point at which
  the genuine issues become easy to see and fix

7
Iterate

• Begin the conversion QA early and perform it
  regularly
• Break the conversion load work into parts or
  subsets
• Iterative testing and client feedback cycles.
• A conversion bug found while the code developing
• Inevitable time hit of the conversion clerk
  expecting to "recover their head into the code"

8
Engage

• Following the early and regularly guideline
• Bear in mind to draw in your client in a similar
  attitude.
• Work with their data in the new framework and
• Get used to giving regular feedback
• The more issues you will flush out early when
  they are the least costly to correct.

9
Contact US

• INDIA Head Office Plot No. 17, 2nd Floor, Cochin
  Special Economic Zone, Kakkanad - Kochi,
  Kerala - 682 037, India.Telephone [phone]
  1, 91-989-571-8589
• USA Representative Office1635 W Wise Rd., Suite
  10R, Schaumburg IL 60193,
  USA. Telephone [phone]
• Email info_at_offshoreindiadataentry.com
• Web site http//www.offshoreindiadataentry.com

10

• Thank You