This action might not be possible to undo. Are you sure you want to continue?
Any project either banking or sales or insurance can use this explanation. First u have to start with 1) U have to first explain about objective of the project and what is client expectations 2) u have to start where ur involvement and responsibility of ur 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 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.
Aug 7 (21 hours ago)
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 u 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. 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..
. Gather the useful information for the DSS and indentifying the subject areas. developers has to create the HLD(high level design) it will have he Informatica flow chart. BA and Data Architect 80% onsite . Based on the review comments u have to updated the mapping. In some companies they won’t have HLD. Architecture Production◊ Testing ◊ Development ◊ Design◊ Requirement Gathering◊Analysis Analysis and Requirement Gathering: Output :Analysis Doc. 2 times code review and 2 times unit testing will be conducted in this phase. Subject Area 100% in onsite. After that code review and code standard review will be done by another team member.Responsibilities. Job Tracker. HLD will cover only 75% of requirement. UTR.Our projects are mainly onsite and offshore model projects.( Schema design in Erwin and implement in database and preparing the technical design document for ETL. Unit testing based on the UTP. U have to fill the UTP and Enter the expected values and name it as UTR (Unit Test Results).. Staging area simplify the process.) we simply give the dependencies between each mapping and run time.In this project we have one staging area in between source to target databases. write the test cases based on the requirement.( Control M. pick from Project architecture Post and tell according ur comfortable level. What are the transformation required for that mapping. identify the schema objects and all. we are responsible for only development and testing and scheduling we are using third party tools..... project manager. . 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 …. In some project they won’t use staging area’s. U have to create the mappings.. Development : output : Bugs free code... Integration Test Plan ETL Team and offshore BA 100% offshore Based on the HLD. Migrating to testing repository Integration test plan has to prepare by the senior people. HLD. UTP ETL Lead. Both positive and negative test cases. Business Analyst. 20% offshore: HLD & UTP Based on the Technical specs. Directly form technical specs they will create mappings. Based on that Information scheduling tool team will schedule the mappings. UTP Unit Test Plan. AutoSys. Tivoli or etc. Design: Output: Technical Design Doc’s.
. next deployment in production environment. 20% Onsite UAT User Accept Testing..... Mapping Bugs needs to fix by Development team... Client will do the UAT.. If you have any doubts and needs more explanation let me know. Developers will fix the bugs in the development repository and again migrated to testing repository.to be continued. UAT. Production: 50% offshore 50% onsite Work will be distributed between offshore and onsite based on the run time of the application. Again testing starts till the bugs free code. Business Analyst and Client.. If client satisfy with the product . Development team will support for warranty period of 90 days or based on agreement days. 80% offshore Based on the integration test plan testing the application and gives the bugs list to the developer. 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? waiting 4 detailed explanation? .. Pavan Aug 2 (5 days ago) Testing : Output: ITR.. this is last phase of the etl project. In ETL projects Three Repositorys. Development : E1 Testing : E2 Prduction : E3 forgot to mentioned above In Everyphase i given the Out come of the phase as OUTPUT after that Roles involved percentage of involvment. For each repository access permissions and location will be different.. Deployment Doc and User Guide Testing Team.
. i hope it will help in interviews. can u tell me fact & dimension tables names of ur project or any other project. @pavan.Informatica mappings impact. Distributor. etc.. because if clients are purchasing informatica software. they are trying to utilize the tool for another projects also. IP_X_IP Its is not mendatory that ur project had dimensions and fact tables. so that we can create our own facts & dimension names. Involveparty.. Customer.. again work will starts from Design schema till production. In interviews u people can tel that my project is not Datawarehousig project. dimensions are Account... ITS ME........ if required anything else.suppose in the middle of a project if the client needs to change some part of the design phase. simply using for some validations. converting from flat file to xml . we used to automate some process of the client..thanks again for ur pain In my project .. based on the impact analysis they will give the estimated hours to complete the task and billing amount separately. BA. my requirement is to validate the data and populate the target with valid and useful data to the clients. because now a days informatica is using for automations of any kind of process. we willl called as standard tables( Dimensions) and relationship tables( facts tables). . schema changes.. let me know. etc. chakravarthy Aug 6 (1 day ago) pavan. we won't call as dimensions and facts.. ETL Lead will analyze what is the impact on existing code. ACCT_X_CUST. Aug 6 (1 day ago) Excellent work.keep up thegood work...... its great to have many useful tips from u yaar..... PM . Once client approve on estimation... IP_X_ACCT.. Facts are relation between all those tables.