This can be divided into two parts:
1.
Implementing Informatica Infrastructure.
2.
Implementing Infomratica Solution at functional
level.
a.
If it is a DWH solution-Please refer Dimensional
modeling tab to know how dimensional and fact tables are designed and
implemented using Informatica
b.
If it is a data integration the methodology will
e covered in this section.
The following methodology has been given by Informatica
Velocity, which id tailor made for data integration scenarios.
1.
Manage
2.
Analyze
3.
Architect
4.
Design
5.
Build
6.
Test
7.
Deploy
8.
Operate
1.
Manage Phase-
This phase lasts through the entire lifecycle of the project. Following
activities shall be a part of this
phase.
·
Project Estimation
·
Project Planning – Deciding the business scope
of the project. i.e. A high level solution of the problem that is being addressed
by the project.
·
Establishing the roles in the project i.e. What
kind of technical profile should the technical leads and project leads should
have. How many resources shallbe in the technical team? What should be the
number of years of experience team memebers should have and on which
technologies?
·
Build Business cases
·
Project Closure
2. Analyze Phase- Following are the activities
under this phase
·
Define Business Requirements
·
Define Business Scope- The proposed solution
should be frozen here through a business sign off. Road maps for incremental
delivery. Identification of source system. Data flow Diagrams.
·
Define Functional Requirement- Creation and
passing of the business requirement document.
·
Determine Technical readiness.
·
Perform Data Quality analysis of source data and
report the analysis to business.
3. Architecture Phase- This is the phase
where the actual action starts. It begins with the Solution architect analysis.
The Solution architect should perform the following activities :
·
Define Technical Requirement – What version of
Informatica is to be used? What is the License requirement? What is the backend
database used for metadata repository?
·
Develop Logical/Physical View of the architecture-
Through a box diagram, or Microsoft Visio diagram, show how the client and
server are related logically? What ports are opened and if they are outbound or
inbound?
·
Configuration Recommendation and Estimation of
the amount of data that will flow through informatica mappings.
·
The Solution Architect will develop a Technical
Design Document in this phase and will documents the findings in the TDD.
·
Define Development Architecture- The development
team will tell the number of folders they require in the informatica
environment .The naming conventions of the mappings/workflows. Define a
configuration management procedure for the code.
·
Implement technical architechture – Install informatica
client/server.
4. Design Phase
·
Develop facts and dimension tables- Presentation
layer
·
Create source to target data store matrix.
·
Design physical database design
·
Source and Target connectivity check.
·
Develop source and target relationships for
impact analysis.
5. Build Phase- Launch the build phase.
Develop reusable mappings, error handling strategies – i.e. error tables. Define
a defect tracking process, conduct peer reviews and unit tests.
6. Test Phase-Prepare test cases, conduct
system tests, integration tests and user acceptance test. Performance
improvement and tuning comes under this phase as well.
7.
Deployment
Phase – Prepare a punch list document. This document will have the links to
all the code that is uploaded to a storage location. The test or the prod
resource will use this document to download and deploy the code in this
environment. A runbook will have all the snapshots of the installation of the
code. It is a reference document for system administration.
8.
Operate
Phase – Develop and operations manual and monitor jobs. Maintain the
repository and do upgrades if required.
