Data Migration Test and Strategy Plan_Vdraft

8/13/2019 Data Migration Test and Strategy Plan_Vdraft

1/9

DATA MIGRATION

VALIDATION AND

TESTING

Origin/Author :

Approved by :

Date Approved :

Document Version: [1.0]


2/9

Contents

1 DOCUMENT MANAGEMENT........................................................................31.1 Contributors...........................................................................................................3

1.2 Version Control......................................................................................................3

2 VALDATON AND TE!TNG........................................................................"

2.1 Valiation S!o"e.....................................................................................................#

2.2 Valiation A""roa!$es..........................................................................................#2.2.1 Spot Checking...................................................................................................4

2.2.2 Record Count.....................................................................................................4

2.2.3 Report ...............................................................................................................5

2.2.4 Test Types.........................................................................................................5

3 DATA MG#ATON TE!T $DMT%...................................................................&

3.1 De%inition.................................................................................................................&

3.2 Roles an Res"onsibilities.....................................................................................&

3.3 Test Re'uire(ents ..............................................................................................)

3.# Test *arti!i"ants ....................................................................................................)

3.3 Test S!$eule .........................................................................................................+

3.# Assu("tions ...........................................................................................................+

" DATA MG#ATON TE!T! AND OUTCOME!.............................................'

#.1 Data Mi,ration Test S!enarios %ro( -usiness Re'uire(ents Do!u(ent ....... .+

#.2 Ot$er DMT S!enarios ...........................................................................................

#.3 O"en Issues.............................................................................................................

#.# Do!u(ent Si,n O%%.................................................................................................

_______________________________________________________________________________

Page 2 of 9


3/9

1 Document M(n()ement

When completing this document, please mark any section that is not required asN/A. A brief description of why the section is not required should also be included.

1.1 Contri*utors

Please provide details of all contributors to this document.

#o+e Unit N(me

Sponsor

Business Analyst (Owner) Capgemini

Application Analyst Capgemini

Deeloper Capgemini

Testers Capgemini !

1.2 Version Contro+

Please document all changes made to this document since initial distribution.

D(te Version Aut,or !ection Amen-ment

"#$ A++ niti(+ Document ersion 1.0

_______________________________________________________________________________

Page 3 of 9


4/9

2 V(+i-(tion (n- Testin)

2.1 Validation Scope

This validation will need to tae place to achieve the following!

%eri&ication o& the compliance to the requirements o& each o'ect as de&ined

in the C%$$ as well as in the &ile layouts proided 'y !he *+tract !eam#

eneral sanity checks such as row count, data consistency and

completeness ('etween the Source and Oracle instances)#

Spot checking - sampling o& data within the e+tracted &iles against the source

system#

Sign o&& the data &iles prior to their load into the D.! enironment#

2.2 Validation Approaches

"#$s will be responsible for %ata &alidation activities and will adopt thefollowing approach!

Checking each o& the supplied data e+tract &iles against 'oth the

corresponding C%$$ /unctional Design and the layouts proided 'y !he*+tract !eam# 0ser &ield mappings (&ields on the Oracle ""i screens) will 'eproided in the data e+tract &iles and !he *+tract !eam will proide layoutsto assist with this so that a column in the supplied data e+tract &ile can easily'e re&erenced 'ack to &ield in ""i

Spot checking a su'1set o& records in the data e+tract &iles against the data

held in ""i

2eporting o& any data anomalies which can then 'e addressed 'y the Data

*+tract !eam#

!he *+tract !eam will proide support to the S.*s in adance o& this actiityto help them understand how data alidation can 'e per&ormed and whichsupporting tools - techniques can 'e used# 3n addition, the Capgemini &unctionalteam will 'e on hand to answer any queries during the data alidation actiities'eing undertaken 'y #

2.2.1 !/ot C,ecin)

!his will inole checking &ields on the e+tract against the&ields on the &orm# !he purpose o& the spot checking is toproide con&idence that the e+tract process is e+tractingthe correct &ields# 3n some cases, the S.*s would 'ereasona'ly e+pected to know in which &orm the releantdata is iewa'le# 3n many cases, the detail o& which &ormshows the data has 'een included in the detail column,

2.2.2 #ecor- Count

_______________________________________________________________________________

Page 4 of 9


5/9

!his will inole checking the num'er o& records in thee+tract &ile against the detail o& where to &ind out thee+pected record count#

2.2.3 #e/ort

Standard or e+isting custom reports may need to 'e run in order to eri&y that thescope o& e+tract is correct# !he report &ield names may not match the &ield names inthe e+tract#

2.2." Test T/es

!he areas to 'e coered 'y Data %alidation and 2econciliation !esting include4

%eri&ying data e+tract &ile quality

%eri&ying data e+tract &ile completeness

3denti&ication o& any data gaps or issues with the supplied data e+tract &iles

2econciliation o& alues and record counts o& the data e+tract &iles

3 D(t( Mi)r(tion Test $DMT%

3.1 Deinition

!he purpose o& Data .igration !est(D.!) is to ensure that the solution 'y the proectmeets the &unctional and non1&unctional requirements speci&ied in the 'usinessrequirements# D.! may also identi&y issues that hae not 'een speci&ied in the B2Dsuch as those relating to usa'ility# D.! is the &inal step 'e&ore rolling out the

solution# D.! is typically carried out 'y end users in an enironment that closelymodels the real world# A well1managed D.! process will gie the 5roect Sponsor,proect team and end users con&idence that the solution 'eing deliered meets therequirements#

!his document outlines the plan &or D.! o& the proect deliera'les# !his documentis a high leel guide and will initially 'e deeloped during requirements gathering aspart o& the Business Analysis stage# Detailed test scripts-cases will 'e deeloped aspart o& the D.! 5lan and will 'e used to record the results o& user testing# !estingitsel& and the &ormal recording o& D.! results takes place during the Acceptancestage#

3.2 #o+es (n- #es/onsi*i+ities

#o+e #es/onsi*i+ities N(me

BusinessAnalyst

Assist 5roect Sponsor and-or 'usiness

representaties with the creation o& adetailed test plan and schedule

2eiew scripts-cases and scenarios &or

accuracy, completeness and sequencing#

Con&irm appropriate test data is de&ined

and made aaila'le &or testing

5roect

Sponsor

Agree &ormat and scope o& D.! plan

De&ine and agree acceptance criteria *nsure (with 5roect .anager) that

_______________________________________________________________________________

Page 5 of 9


6/9

detailed test scripts-cases, scenarios andinstructions are made aaila'le to testersprior to the start o& D.!

*nsure (with 5roect .anager) that the

test schedule is communicated and that

D.! takes place at the agreed time&rame

*nsure that 'usiness issues identi&ied

during D.! are logged in the !est 6og

Deeloperand ApplicationAnalyst

%alidation o& D.! enironment

!esters *+ecute test scripts-cases

2ecord test results

3.3 Test #euirements

D.! will take place 'eginning on 7insert date8 and end on 7insert date8 D.! will take place in 7insert location8# (Some testers may choose to per&orm

some testing &rom their regular work location where this is possi'le and isagreed in adance with the 5roect .anager and 5roect Sponsor

5articipants will receie training, guidance and instructions prior to the start o&

D.!

A &ully con&igured !*S! enironment including all o& the &unctionality and

adequate !*S! data will 'e proided &or D.!

!est scripts-cases and scenarios will 'e prepared prior to the start o& D.!

!echnical and 'usiness support will 'e proided &or test participant during

D.!

D.! participants will conduct the tests and record results in the !est6og-932A or other &ormat speci&ied

3ssues recorded in the 932A !est 6og (and-or other test documentation) will

tracked 'y the 5roect .anager and 5roect Sponsor

3." Test 4(rtici/(nts

!esting participants must include representaties &rom all areas who will use or 'eimpacted 'y the solution#

N(me Unit #e/resente- Testin) Are( o #es/onsi*i+it

*nsure the 'usiness requirements aremet 'y testing, the enironment andany re1work#

%alidate the test criteria and ensurethe test enironment allows testing o&the 'usiness requirements#

2e1work code where necessary toallow success&ul test results#

!est the 'usiness requirementsaccording to the tests de&ined in thistest document and record the resultso& tests

_______________________________________________________________________________

Page of 9


7/9

3.3 Test !c,e-u+e

Actiit #es/onsi*i+it T(r)etD(te

D(teCom/+ete-

Con&irm testers &or D.! 5roect Sponsor - BusinessAssurance Coordinator

Con&irm test scenarios, testdata and scripts-cases

5roect Sponsor - BusinessAssurance CoordinatorBusiness Analyst

*nsure D.! enironment iscon&igured &or testing i#e# new&unctionality and test data ismigrated to the !*S!enironment prior to the starto& D.!

5roect Sponsor - BusinessAssurance CoordinatorBusiness AnalystSystems Analyst - Designer!echnical Architect

Oersee testing 'y D.!participants

5roect Sponsor - BusinessAssurance Coordinator

3.4 Assumptions

!he D.! enironment will 'e aaila'le and &ully con&igured ahead o& the

D.!#

!he 'usiness team has reiewed and accepted &unctionality identi&ied in the

Business 2equirements Document (B2D) and System Design Document(SDS)#

Code walkthroughs-reiews hae 'een completed 'y the Deelopment !eamand signed o&& as part o& the 5eer 5roect Build 2eiew (55B2)

3ntegration testing, including where releant load and testing, has 'een

completed and signed o&& as part o& the 5eer 5roect 3ntegration 2eiew#

!esters will test the &unctionality documented in the approed B2D (taking

into account any changes in 'usiness requirement su'sequently agreed 'ythe 5roect !eam)

2esources identi&ied in this plan are aaila'le to conduct the D.! and

address issues as they are raised 'y the test team#

'usiness Analyst should record any additional assumptions here

!he 5roect .anager must noti&y the 5roect Sponsor i& any o& these assumptions arenot correct 'e&ore commencing the D.!#

" D(t( Mi)r(tion Tests (n- Outcomes

".1 D(t( Mi)r(tion Test !cen(rios rom 5usiness#euirements Document

0ser testing should 'e 'ased on the test scenarios and acceptance criteria identi&iedin the Business 2equirement Document# Any deiation &rom these scenarios should'e noted here#

_______________________________________________________________________________

Page ! of 9


8/9

5#D#e

!cen(rio 6 Acce/t(nce Criteri( Teste-5

D(teTeste-

Outcome$4A!! 6 7AL%

5#D#e

Notes on Test (n-6or Test Outcome

4.2 Other DMT Scenarios

Additional test scenarios used in testing 'ut not sourced &rom the Business2equirements Document should 'e identi&ied here# !he usti&ication &or including thescenario in the D.! must also 'e recorded#

#e Test !cen(rio (n- Acce/t(nce Criteri( Teste-5

D(teTeste-

Outcome$4A!! 6 7AL%

#e Notes on Test (n-6or Test Outcome

".3 O/en ssues

Any issues identi&ied during D.! must 'e added to the !est 6og# 5lease summariseor insert a copy o& any open issues &rom the 932A !est 6og# 3t may 'e agreed thatD.! can 'e signed o&& while some issues remain open please proide details o& theD.! impact o& each open issue#

5#D#e

8#ATestLo)#e

ssue !umm(r m/(ct on DMT !i)n O

(in to updated )*+A Test (og

"." Document !i)n OPlease add other signatories where required

4ro9ect M(n()er Name %ate "igned ,ff

_______________________________________________________________________________

Page " of 9


9/9

4ro9ect !/onsor Name %ate "igned ,ff

5usiness An(+st Name %ate "igned ,ff

Add other signatories here

_______________________________________________________________________________

Page 9 of 9

Documents

Data Migration Test and Strategy Plan_Vdraft