I am giving generic explanation of the project. Any project either banking or sales or retail or e-commerce insurance can use this explanation.
First you have to start with
1) You have to first explain about objective of the project and what is client expectations
2) You have to start where ur involvement and responsibility
of your job and limitations of job.
Add some points from post Project Architecture reply like offshore and onsite model and team structure. etc.,
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 orinsurance domain) of entire organizations all over the
country US / UK ( based on theclient 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
Delta load means last 24 hrs transactions captured from the source system. In other words you 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 you can identify wheather that transaction belongs to sales, purchase / car
insurance, health insurance, /deposit , loan, payment ( u have to change the words basedon the project..) etc., based onthat code business logic will be change.. we validate and
calculate the measure and load to database.
One Mapping explanation : In Informatica mapping, we first lookup all the transaction
codes with code master table to identify the transaction type to implement the correct
logic and filter the unnecessary transactions.. because in an organization there are lot of
transactions will be there but you have to consider only required transactions for ur project..
the transaction code exists in the code master table are only transactions u have to
consider and other transactions load into one table called Wrap table and invalid records (
transaction code missing, null,spaces) to error table. For each dimension table we are creating surrogate key and load
into DWH tables.
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.
this you should know it clearly about this SCD2 method.careful about it.
Role and Responsibilities
Pick from Project architecture Post and tell according your 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 wont schedule in
Informatica .. thats it Finished
Please Let me know if u required more explanation regarding any point reply