Professional Documents
Culture Documents
Project Explanation:
I’m giving generic explanation of the project. Any project either banking or sales or
insurance can use this explanation.
Main objective of this project is we are providing a system with all the information
regarding Sales / Transactions (sales if sales domain / transactions if bank domain or
insurance domain) of entire organizations all over the country US / UK ( based on the
client location US/UK/…..). we will get the daily transaction data from all branches at the
end of the day. We have to validate the transactions and implement the business logic
based on the transactions type or transaction code. We have to load all historical data into
dwh and once finished historical data. We have to load Delta Loads. Delta load means
last 24 hrs transactions captured from the source system. In other words u can call it as
Change Data Capture (CDC). This Delta loads are scheduled daily basis. Pick some
points from What is Target Staging Area Post.. Source to Staging mappings, staging to
warehousing.. based on ur comfort level..
Each transaction contains Transaction code.. based on the transaction code u can identify
wheather that transaction belongs to sales, purchase / car insurance, health insurance, /
deposit , loan, payment ( u have to change the words based on the project..) etc., based on
that code business logic will be change.. we validate and calculate the measure and load
to database.
SCD2 Mapping:
We are implementing SCD2 mapping for customer dimension or account dimension to
keep history of the accounts or customers. We are using SCD2 Date method.before telling
this u should know it clearly abt this SCD2 method..careful abt it..
Responsibilities.. pick from Project architecture Post and tell according ur comfortable
level.. we are responsible for only development and testing and scheduling we are using
third party tools..( Control M, AutoSys, Job Tracker, Tivoli or etc..) we simply give the
dependencies between each mapping and run time. Based on that Information scheduling
tool team will schedule the mappings. We won’t schedule in Informatica .. that’s it
Finished…
Please Let me know if u required more explanation regarding any point reply ……
We have to start with ….Our projects are mainly onsite and offshore model projects.In
this project we have one staging area in between source to target databases. In some
project they won’t use staging area’s. Staging area simplify the process..
Architecture
Production◊ Testing ◊ Development ◊ Design◊ Requirement Gathering◊Analysis
Production:
50% offshore 50% onsite
Work will be distributed between offshore and onsite based on the run time of the
application. Mapping Bugs needs to fix by Development team. Development team will
support for warranty period of 90 days or based on agreement days..
In ETL projects Three Repositorys. For each repository access permissions and location
will be different.
Development : E1
Testing : E2
Prduction : E3
forgot to mentioned above
In Everyphase
If you have any doubts and needs more explanation let me know...
kamal
Aug 3 (4 days ago)
i'm impressed with the job u have done but 1 Q?
u have discussed abt the development and testing of a DWH?
suppose in the middle of a project if the client needs to change some part of the design
phase what kind of impact analysis is done on the source schema and the target schema?
Once client approve on estimation, again work will starts from Design schema till
production....
chakravarthy
Aug 6 (1 day ago)
pavan,
can u tell me fact & dimension tables names of ur project or any other project.
so that we can create our own facts & dimension names.
ITS ME..
Aug 6 (1 day ago)
Excellent work..
@pavan,
its great to have many useful tips from u yaar,keep up thegood work,thanks again for ur
pain
In my project ... we won't call as dimensions and facts.. we willl called as standard tables(
Dimensions) and relationship tables( facts tables)..
Its is not mendatory that ur project had dimensions and fact tables.. because now a days
informatica is using for automations of any kind of process.. simply using for some
validations, converting from flat file to xml .. etc.,, because if clients are purchasing
informatica software.. they are trying to utilize the tool for another projects also..
In interviews u people can tel that my project is not Datawarehousig project.. we used to
automate some process of the client.. my requirement is to validate the data and populate
the target with valid and useful data to the clients...