DT cv020

Ministry/Agency Name
Complete file/properties to populate fields on this page and in the document headers. To see
instructions select Tools/Options Print tab, and make sure that Hidden Text is checked. elete red
instructions !hen filling in the template or select Tools/Options Print tab, and make sure that Hidden
Text is not checked.
Project Name
Project #:
Data Conversion Strategy
Prepared by: Author's Name
Prepared or: !Company Name"
Date Submitted: !Date"
Project Sponsor: Project Sponsor's Name
C#ient Acceptor: !i dierent than Sponsor"
Project Manager: !Project Manager$s Name"
Document Number: %&'()*(/Project Number /C+S
Security C#assiication: ,o-
+ersion: (./
,ast 0pdated: 1une &2 *(/&
Creation Date: !Date"
About this template: This template uses built in st"les to assist the author in preparing
the la"out of the document. #or assistance !ith st"les, please contact the Pro$ect %upport
Office.
ata Con&ersion %trateg" Pro$ect 'ame
3ab#e o Contents
3ab#e o Contents.............................................................................................................. *
/. 4ntroduction..................................................................................................................... 5
*. 6ac7ground..................................................................................................................... &
2.1. Purpose............................................................................................................................ 4
2.2. Scope and Application...................................................................................................... 4
5. Conversion 8e9uirements............................................................................................. '
&. Constraints and Assumptions....................................................................................... %
'. Conversion Approach.................................................................................................... :
%. 4mp#ementation Approach.............................................................................................. ;
6.1. Planning Approach........................................................................................................... 9
6.2. Deliverables...................................................................................................................... 9
:. Conversion 3eam <rgani=ation................................................................................... /(
7.1. Conversion Tea........................................................................................................... 1!
7.2. "oles and "esponsibilities............................................................................................. 1!
>. Conversion 8esource 8e9uirements.......................................................................... //
#.1. So$t%are ........................................................................................................................ 11
#.2. &ard%are 'nvironent .................................................................................................. 11
#.(. )et%or* + ,ile Transport.................................................................................................11
#.4. Sta$$ing........................................................................................................................... 11
#.-. .ther.............................................................................................................................. 12
;. Project Standards......................................................................................................... /5
9.1. Tool Standards............................................................................................................... 1(
9.2. Deliverable )aing Standards.......................................................................................1(
/(. Data C#ean)up Process............................................................................................... /&
1!.1. Data Clean/up.............................................................................................................. 14
1!.2. 0e1 Data Translations.................................................................................................. 14
//. 3esting Strategy.......................................................................................................... /'
/*. 6usiness System Processing.................................................................................... /%
12.1. Deliver1........................................................................................................................ 16
12.2. Data Acceptance.......................................................................................................... 16
/5. 4ssue 3rac7ing Process.............................................................................................. /:
1(.1. 2ssue 3anageent Procedure.....................................................................................17
1(.2. 2ssue "esolution........................................................................................................... 17
/&. +ersion Contro# Procedures...................................................................................... />
/'. Project Metrics............................................................................................................ /;
/%. Project Mi#estones...................................................................................................... *(
/:. Conversion 8is7s....................................................................................................... */
8evision ,og.................................................................................................................... **
Appendices...................................................................................................................... *5
Approva#........................................................................................................................... *&
(ast re&ised) *+,-.+/.+- Page * of *-
/&ar/!!!/apps/con&ersion/tmp/scratch01/*1*2231-/.doc
%ecurit" Classification) (o!
/. 4ntroduction
This docuent is used to deterine the strateg1 $or eeting the de$ined conversion
re4uireents. The Data Conversion Strateg1 is intended to provide a roadap $or per$oring the
conversion o$ data $ro the legac1 s1ste to the ne% .racle s1ste. The tas*s and resources
needed to $ul$ill this strateg1 are also discussed in this deliverable. The strateg1 in the deliverable
teplate is based upon the proven conversion ethods practiced b1 the .racle Advanced
Conversion Technologies 5ACT6 7roup.
The Data Conversion Strateg1 is used as $ollo%s8
The conversion tea uses this docuent to counicate to the client
the strateg1 $or success$ull1 converting their legac1 data to the ne% .racle
s1ste5s6.
The conversion tea uses this docuent as a roadap $or per$oring
the conversion. All ebers o$ the tea9 both consultants and client tea
ebers9 should understand and $ollo% the sae strateg1.
The pro:ect anager uses this docuent to understand ho% the
conversion tea plans to per$or the conversion9 and ho% the conversion e$$ort
a1 ipact the overall pro:ect.
There$ore9 the readers o$ the Data Conversion Strateg1 include the $ollo%ing8
the client pro:ect leader %ho should sign/o$$ the conversion re4uireents
and strateg1
each eber o$ the conversion tea
the pro:ect leader %ho needs to revie% and deterine %hat other groups
should be given the docuent
;se the $ollo%ing criteria to revie% this deliverable8
2s the strateg1 understood b1 those on the distribution list $or this
deliverable<
Are all assuptions9 constraints9 and ris*s %hich could ipact the
conversion process stated and understood<
(ast re&ised) *+,-.+/.+- Page 1 of *-
*. 6ac7ground
*./. Purpose
The purpose o$ this docuent is to provide 3inistr1+Agenc1 )ae %ith a strateg1 $or planning the
conversion pro:ect to ensure the highest 4ualit1 conversion. This deliverable docuent
suari=es the *e1 areas to $ocus on in organi=ing9 planning9 and e>ecuting the conversion
pro:ect tas*s and deliverables.
*.*. Scope and App#ication
The application o$ this Data Conversion Strateg1 provides direction $or all phases in con:unction
%ith the .racle Custo Developent 3ethod.
(ast re&ised) *+,-.+/.+- Page - of *-
5. Conversion 8e9uirements
2nsert te>t here.
&. Constraints and Assumptions
The $ollo%ing constraints and assuptions appl18
conversion pro:ect start date8
target production date8
(ast re&ised) *+,-.+/.+- Page / of *-
'. Conversion Approach
This section provides a graphical description o$ the conversion approach %hich %ill be used to
convert the ?S1ste to be Converted@ to the ne% application. An e>planation o$ this strateg1
$ollo%s.
2nsert diagra here.
2nsert diagra caption here.
/. Data Mapping
The data apping process provides detailed lists o$ the ?S1ste to be Converted@ data sets and
data eleents that %ill need to be oved into the .racle tables during the data conversion.
During this process9 soe decisions %ill need to be ade %ith regard to obtaining re4uired
in$oration needed b1 the target application %hich a1 not be present in the old s1ste. De$ault
settings9 user input9 and ne% data entries are an1 issues that ust be addressed during this
phase.
The output o$ this section is data apping spreadsheets that sho% %hat is needed $or the .racle
target application processing to eet business operational re4uireents and %here these data
eleents %ill coe $ro.
*. Do-n#oad Programs
These progras are used to e>tract the identi$ied conversion data eleents $ro the current
e>isting ?S1ste to be Converted@. Ahat tool is used to accoplish this tas* is usuall1
dependent on the abilities o$ the current s1ste to develop an ASC22 $lat $ile. 2t is iportant to
reeber ho% the $lat $ile %ill be structured 5the order o$ the records as the1 are pulled6 9 t1pe o$
delineation used9 nuber o$ records9 etc. This ust atch ho% the interi tables are set up.
The output $ro this is the ASC22 $lat $iles identi$ied in the ne>t section.
5. ASC44 ?#at ?i#e
3ost database or $ile s1stes output data in te>t $or. A coa or space deliited9 variable or
$i>ed $orat data $ile $ro the e>isting s1ste should be generated. 2$ 1ou cannot $ind a %a1 to
produce clean te>t data9 tr1 generating a report to dis*9 using a te>t editor to $orat 1our data.
&. 0p#oad Program
.nce data has been put into an ASC22 $lat $ile and ph1sicall1 oved onto the sae coputer that
has the .racle "DB3S9 the ne>t step is to load the data into a relational database environent.
Progras ust be %ritten and run to ove data9 validate data9 and perhaps insert standard
values into de$ault $ields. ;suall1 a single loader progra is %ritten $or each data table being
loaded.
'a. Description o 4nterace 3ab#e
The detailed technical description o$ an1 inter$ace table that the data is placed into $ro the ASC22
$lat $ile is described. A teporar1 table %hich iics the production table that the data %ill
eventuall1 be loaded into should be built. This allo%s 1ou to anipulate the data as needed
be$ore loading the legac1 data into the production tables.
'b. Creation o 4nterace 3ab#e
Be$ore loading the .racle application production tables9 the legac1 data should $irst be loaded
into teporar1 or inter$ace tables. The inter$ace tables provide a location $or 1ou to anipulate
and translate the data as needed be$ore validating the data and loading the application
production tables. These teporar1 inter$ace tables need to be built be$ore 1ou run the loader
script to populate these tables.
%. 3rans#ation Programs
These scripts are developed to translate data $ro the e>isting s1ste $orat into use$ul data $or
the .racle target application. An e>aple o$ this ight be ta*ing the date $orat that e>ists in the
legac1 s1ste and converting it into an .racle $orat. There a1 be several or no translation
progras9 depending on both the t1pe o$ data coing across and the $orat o$ that data.
:. 4nterace Programs
The inter$ace progra scripts are used to populate the production database. The purpose o$ the
inter$ace progras is not onl1 to ove the data to the target tables but also to validate the data
%hich %ould be validated b1 the $or in the target odule i$ the data %as converted anuall1.
>. App#ication Production 3ab#e
This is the $inal production data table %here the converted data resides. These tables are
identi$ied earl1 on %hen doing the initial data apping. These tables drive soe o$ the translation
progras that ust ultiatel1 ensure that 1!!C o$ the re4uired in$oration that the target
applications re4uire is present in the $inal data structures.
;. 3esting
This test plan has been integrated into the entire conversion process so that9 even during the pre/
conversion steps9 soe t1pe o$ validation reports are generated $ro the9?S1ste to be
Converted@ s1stes9 to be copared later %ith the converted data.
The approach to data validation
/(. @rite and Perorm Conversion ABecution P#an
The conversion e>ecution plan is the e>ecution docuent eant to be $ollo%ed %hen per$oring
the actual conversion. This docuent is speci$icall1 tailored $or the ?Copan1 Short )ae@
conversion.
The $ollo%ing steps %ithin the approach described above %ill be anaged using the autoated
conversion tool described belo%8
%. 4mp#ementation Approach
%./. P#anning Approach
A %ater$all developent ethod is being used on this pro:ect. The ethod covers the $ollo%ing
phases o$ the pro:ect li$e c1cle8
De$inition
Anal1sis
Design
Build
Transition
Production
%.*. De#iverab#es
This section lists the tas*s and deliverables %hich %ill be produced during this conversion pro:ect8
3as7 De#iverab#e
Docuent Data Conversion "e4uireents Data Conversion Strateg1
De$ine Data Conversion Strateg1 Data Conversion Strateg1
De$ine Data Conversion Aor*plan Data Conversion Aor*plan
Design Data Conversion 3odules Data Conversion 3odule Design
Code Conversion 3odules Conversion 3odules
Per$or Conversion 3odule Test Conversion 3odule Test "esults
Convert and Deri$1 Data Converted and Deri$ied Data
:. Conversion 3eam <rgani=ation
:./. Conversion 3eam
The organi=ation structure $or this conversion pro:ect is as $ollo%s8
:.*. 8o#es and 8esponsibi#ities

The conversion pro:ect roles %ill be sta$$ed b1 the indicated person8
<rac#e 3eam Member C#ient 3eam Member 8o#e
Conversion Pro:ect 3anager
Anal1st
3odule Designer
Prograer
Tester
Technical '>pert
(ast re&ised) *+,-.+/.+- Page ,+ of *-
>. Conversion 8esource 8e9uirements
The $ollo%ing so$t%are and hard%are re4uireents are considered a part o$ this conversion e$$ort8
>./. Sot-are
The application so$t%are considered as part o$ this pro:ect includes8
,egacy Anvironment CSourceD:
<rac#e Anvironment C3argetD:
>.*. Eard-are Anvironment

The hard%are and operating so$t%are to be used includes8
,egacy Anvironment:
<rac#e Anvironment:
>.5. Net-or7 / ?i#e 3ransport

>.&. Staing
The sta$$ involved %ith this pro:ect ust have the bac*ground 9 e>perience9 and training in the
$ollo%ing areas8
Belo% is a list s*ills %hich the current conversion pro:ect tea does not $ul$ill8
(ast re&ised) *+,-.+/.+- Page ,, of *-

>.'. <ther
(ast re&ised) *+,-.+/.+- Page ,* of *-
;. Project Standards
;./. 3oo# Standards
A list o$ tool standards speci$ic to the conversion pro:ect $ollo%s8
App#ication 3oo#s:
Conversion 3oo#s:
Source Contro#:
+ersion Contro#:
System Management 3oo#s:
;.*. De#iverab#e Naming Standards

The $ollo%ing table provides instructions on ho% to nae $iles9 progras9 and other pro:ect
deliverables.
Program 3ype ?ormat ABtension ABamp#e
;pload 3odule
Do%nload 3odule
2nter$ace Table Creation
3odule
Translation 3odule
2nter$ace+ Conversion
3odule
Aord Docuents
.ther Pro:ect
Deliverables
(ast re&ised) *+,-.+/.+- Page ,1 of *-
/(. Data C#ean)up Process
/(./. Data C#ean)up
Speci$ic areas 5entities6 %hich are candidates $or data clean/up include the $ollo%ing8
/(.*. Fey Data 3rans#ations

Strategic data %hich re4uires translation includes the $ollo%ing entities8
(ast re&ised) *+,-.+/.+- Page ,- of *-

//. 3esting Strategy
The agreed upon conversion pro:ect deliverables should be signed/o$$ b1 those client
representatives %ho are responsible $or the success o$ the conversion pro:ect. 2n addition three
levels o$ conversion testing have been identi$ied and described in the Data Conversion 3odule
Design deliverable docuent. The $ollo%ing criteria should be considered %hile per$oring data
integrit1 and conversion integration testing8
record counts
hash totals
balances
:ournal debits and credits 5balanced transactions6
/*. 6usiness System Processing
/*./. De#ivery
All conversions %ill be deeed to be delivered $ollo%ing success$ul business s1ste testing.
Conversion data acceptance criteria should include the $ollo%ing8
transactabilit1
abilit1 to reconcile $inancial in$oration
de$inition and acceptance o$ account level variances
/*.*. Data Acceptance
(ast re&ised) *+,-.+/.+- Page ,/ of *-
/5. 4ssue 3rac7ing Process
/5./. 4ssue Management Procedure
All conversion issues %ill be trac*ed and anaged as part o$ the overall pro:ect level
ipleentation process.
/5.*. 4ssue 8eso#ution
All conversion issues %ill be resolved using the overall pro:ect issue resolution process.
/&. +ersion Contro# Procedures
All versions o$ instance in$oration and conversion odules %ill be anaged under
version+source control. The version source control strateg1 being used b1 the overall pro:ect %ill
be $ollo%ed.
/'. Project Metrics
The $ollo%ing etrics are considered in deterining the cople>it1 $actors in the CD3 estiating
odel8
e>isting record volues b1 entit18
volues o$ data to be converted b1 entit18
throughput o$ the conversion inter$aces8
nuber o$ users8
nuber o$ concurrent users8
/%. Project Mi#estones
The Developent Tea and ?Copan1 Eong )ae@ %ill revie% and approve each pro:ect
ilestone b1 using the standard acceptance criteria $or each tas* deliverable produced.
2n addition to the previousl1 de$ined conversion pro:ect deliverables9 the $ollo%ing additional
pro:ect ilestone9 %hich are sub:ect to client acceptance have also been identi$ied8
Phase Current Conversion Mi#estone
Date
Actua# Conversion Mi#estone
Date
(ast re&ised) *+,-.+/.+- Page *+ of *-
/:. Conversion 8is7s
The $ollo%ing ris*s have been identi$ied as having an ipact on the overall success o$ the
conversion pro:ect8
(ast re&ised) *+,-.+/.+- Page *, of *-

8evision ,og
Date +ersion Change 8eerence Author 8evie-ed by
F1111//ddG !.1
(ast re&ised) *+,-.+/.+- Page ** of *-
Appendices
'nter content here.
(ast re&ised) *+,-.+/.+- Page *1 of *-
Approva#
This docuent has been approved as the o$$icial Data Conversion Strateg1 $or the Pro:ect )ae
pro:ect.
,ollo%ing approval o$ this docuent9 changes %ill be governed b1 the pro:ectHs change
anageent process9 including ipact anal1sis9 appropriate revie%s and approvals9 under the
general control o$ the 3aster Pro:ect Plan and according to Pro:ect Support .$$ice polic1.
Prepared by Signature Date
AuthorIs )ae
FTitleG
F.rgani=ationG
Accepted by Signature Date
FClient AcceptorHs )aeG
FTitleG
F.rgani=ationG
Approved by Signature Date
FClient ApproverHs )aeG
FTitleG
F.rgani=ationG
FClient ApproverHs )aeG
FTitleG
F.rgani=ationG
FPro:ect 3anagerHs )aeG
FTitleG
F.rgani=ationG
F237 ApproverHs )aeG
FTitleG
F.rgani=ationG
(ast re&ised) *+,-.+/.+- Page *- of *-

DT cv020

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

DT cv020

Diunggah oleh

Hak Cipta:

Format Tersedia

Ministry/Agency Name

:.*. 8o#es and 8esponsibi#ities

<rac#e Anvironment C3argetD:

>.*. Eard-are Anvironment

>.5. Net-or7 / ?i#e 3ransport

(ast re&ised) +,-.+/.+- Page ,, of -

System Management 3oo#s:

;.*. De#iverab#e Naming Standards

/(.*. Fey Data 3rans#ations

(ast re&ised) +,-.+/.+- Page ,- of -

(ast re&ised) +,-.+/.+- Page , of *-

Anda mungkin juga menyukai