First you have to start with
o
Objective of the project and what are client expectations expectations
o
Your involvement and responsibility of your job and limitations of job, Project architecture and team structure.
Client Introduction:
Main objective of this project is we are providing a system with all the information regarding ransactions of entire ban!s all over the country. "e will get the daily transaction data from all branches at the end of the day. "e have to validate the transactions and implementt the business logic based on the implemen
transactions type or transaction code. "e have
to load all historical data into #"$ and once finished historical data. "e have to load #elta %oads. &lso explain about'
o
Target T arget Staging Area. Area.
o
Mappings.
o
Source to staging mappings.
o
Staging to warehousing.
(ach transaction contains ransa ransaction ction code. )ased on the transaction code we can identify whether that transaction belongs to withdraw withdraw,, deposit, loan, payment* based on that code cod e bu busin sines esss log logic ic wil willl be cha change nge.. "e validate validate and cal calcu culat late e the measure measure and loa load d to database.
+n +nformatica mapping, we first loo!up all the transaction codes with code master table to identify the transaction type to implement the correct logic and filter the unnecessary transactions. )ecause in )&- there are lot of transactions will be there but we have to consider only reuired transactions for the project. he transaction code exists in the code master table are only transactions we have to consider and other transactions load into one table called "rap table and invalid records/ transaction code missing, null, spaces0 to (rror table. For each dimension table we are creating surrogate !ey and load into #"$ tables.
SCD2 Mapping:
"e are implementing 12#3 mapping for customer dimension to !eep history of the customers. "e are using 12#3 #ate method.
Architecture of Project:
12#3 Mapping' "e are implementing 12#3 mapping for customer dimension to !eep history of the customers. "e are using 12#3 #ate method.
Architecture of Project:
o
4556 in onsite,)usiness &nalyst, project manager.
o
7ather the useful information for the #11 and indentifying the subject areas, identify the schema objects and all.
Design:
o
(% %ead, )& and #ata &rchitect
o
856 onsite ./ 1chema design in (rwin and implement in database and preparing the technical design document for (%.
o
356 offshore' $%# 9 :P
$igh %evel #esign #ocument, )ased on the echnical specs. #evelopers has to create the $%#, it will have the +nformatica flow chart. "hat are the transformations reuired for that mapping. $%# will cover only ;<6 of reuirement. :P'
Development: (% eam and offshore )& 4556 offshore )ased on the $%#. : have to create the mappings. &fter that code review and code standard review will be done by another team member. )ased on the review comments we have to update the mapping. :nit testing based on the :P. "e have to fill the :P and enter the expected values and name it as := /:nit est =esults0. 3 times code review and 3 times unit testing will be conducted in this phase. Migrating to testing repository. +ntegration test plan has to prepare by the senior people. esting eam, )usiness &nalyst and 2lient. 856 offshore based on the integration test plan testing the application and gives the bugs list to the developer. #evelopers will fix the bugs in the development repository and again migrated to
testing repository. &gain testing starts till the bugs free code. 356 Onsite
UAT > :ser &ccept esting. 2lient will do the :&. his is last phase of the (%
project.
Production' <56 offshore <56 onsite "or! will be distributed between offshore and onsite based on the run time of the %oading. Mapping bugs needs to fix by #evelopment team. #evelopment team will support for warranty period based on agreement days. +n (% projects hree =epositories. For each repository access permissions and location will be different. #evelopment' (4 esting' (3 Production' (? +n (% projects hree =epositories. For each repository access permissions and location will be different. #evelopment' (4 esting' (3 Production' (? #imensions' Mapping explanation'
o
&nalysis
o
=euirement 7athering
o
#esign
o
#evelopment
o
esting
Production &nalysis and =euirement 7athering' Output'
&nalysis #oc, 1ubject &rea
Output'
echnical #esign #oc@s, $%#,:P
$%#'
:nit est Plan. "rite the test cases based on the reuirement.
Output'
)ugs free code, :=, +ntegration est Plan
Testing:
Output'
+=, :&, #eployment #oc and :ser 7uide
ote' (4, (3, (? are =epository names. othing else.
(mployee 2ustomer &gent ransaction #ate
http://informaticakareem.blogspot.in/2012/08/informatica-project.html
https://www.scribd.com/doc/48634480/informatica-project
