0% found this document useful (0 votes)
76 views4 pages

TICs

The document outlines phases for a master data management project including: 1) Manage - Define the project and plan/manage it. 2) Analyze - Determine business needs, requirements, scope, and readiness. 3) Architect - Develop the solution architecture and finalize the MDM architecture. 4) Design - Develop data models, integration, processes, and the presentation layer. 5) Build - Implement the physical database, processes, and build out the solution. 6) Test - Define a test strategy and execute system and user acceptance testing. 7) Deploy - Plan and conduct the deployment and roll out of the MDM system. 8) Operate - Define support procedures and maintain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
76 views4 pages

TICs

The document outlines phases for a master data management project including: 1) Manage - Define the project and plan/manage it. 2) Analyze - Determine business needs, requirements, scope, and readiness. 3) Architect - Develop the solution architecture and finalize the MDM architecture. 4) Design - Develop data models, integration, processes, and the presentation layer. 5) Build - Implement the physical database, processes, and build out the solution. 6) Test - Define a test strategy and execute system and user acceptance testing. 7) Deploy - Plan and conduct the deployment and roll out of the MDM system. 8) Operate - Define support procedures and maintain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as XLSX, PDF, TXT or read online on Scribd
You are on page 1/ 4

1 Manage

1.1 Define Project


1.2 Plan and Manage Project
1.3 Perform Project Close
2 Analyze
2.1 Define Business Drivers, Objectives and Goals
2.2 Define Business Requirements
2.3 Define Business Scope
2.4 Define Functional Requirements
2.5 Define Metadata Requirements
2.6 Determine Technical Readiness
2.7 Determine Regulatory Requirements
2.8 Perform Data Quality Audit
2.9 Perform MDM Analysis
3 Architect
3.1 Develop Solution Architecture
3.2 Design Development Architecture
3.3 Implement Technical Architecture
3.4 Finalize MDM Solution Architecture
4 Design
4.1 Develop Data Model(s)
4.2 Analyze Data Sources
4.3 Design Physical Database
4.4 Design Presentation Layer
4.5 Design Master Data Management
4.6 Design DT Integration with Invoking System
4.6.1 Design Source Connectivity
4.6.2 Design Target Connectivity
4.6.3 Design DT Invocation
4.7 Design DX Processes
4.7.1 Design Events Model
4.7.2 Design Individual Events and Properties
4.7.3 Design Event Hierarchy
4.7.4 Design Cross-Events/Hierarchy Interaction (Reconciliation)
4.7.5 Design DX Workflows
4.7.6 Design Individual Workflows
4.7.7 Design Chaining Workflow Processes
4.7.8 Design Workflow Input and Output
5 Build
5.01 Launch Build Phase
5.02 Implement Physical Database
5.03 Design and Build Data Quality Process
5.04 Design and Develop Data Integration Processes
5.05 Design and Develop B2B Data Transformation Processes
5.06 Design and Build Information Lifecycle Management Processes
5.07 Populate and Validate Database
5.08 Build Presentation Layer
5.09 Develop B2B Data Exchange Processes
5.10 Set Up MDM Development Environment
6 Test
6.1 Define Overall Test Strategy
6.2 Prepare for Testing Process
6.3 Execute System Test
6.4 Conduct User Acceptance Testing
6.5 Tune System Performance
6.6 MDM System Testing
7 Deploy
7.1 Plan Deployment
7.2 Deploy Solution
7.3 Roll Out MDM
8 Operate
8.1 Define Production Support Procedures
8.2 Operate Solution
8.3 Maintain and Upgrade Environment
The Manage phase encompasses the initial work to define the project and its potential
relationship with other projects in the context of an overall program, if applicable. The
Manage phase also defines tasks for ongoing project management and governance
throughout the entire lifecycle of the project.

The purpose of the Analyze Phase is to build a solid foundation for project scope through a
deliberate determination of the business drivers, requirements, and priorities that will form
the basis of the project design and development.

Once the business case for a data integration or business intelligence solution is accepted
and key stakeholders are identified, the process of detailing and prioritizing objectives and
requirements can begin - with the ultimate goal of defining project scope and, if appropriate,
a detailed roadmap for major project stages.

configuration recommendations is designed. The environments and strategies for the entire
development process are defined. The strategies include development standards, quality
assurance, change control processes and metadata strategy. It is critical that the architecture
decisions made during this phase are guided by an understanding of the business needs. As
Data Integration architectures become more real-time and mission critical, good architecture
decisions will ensure the success of the overall effort. This phase should culminate in the
implementation of the hardware and software that will allow the Design Phase and the Build

The Design phase lays the foundation for the upcoming Build phase. In the Design phase, all
data models are developed, source systems are analyzed and physical databases are
designed. The presentation layer is designed and a prototype constructed. Each task, if done
thoroughly, enables the data integration solution to perform properly and provides an
infrastructure that allows for growth and change.

Each task in the Design phase provides the functional architecture for the development
process. The design of target data store may include, data warehouses and data marts, star
schemas, web services, message queues or custom databases to drive specific applications
or effect a data migration.

The Build Phase uses the design work completed in the Architect Phase and the Design
Phase as inputs to physically create the data integration solution including data quality and
data transformation development efforts.

At this point, the project scope, plan, and business requirements defined in the Manage
Phase should be re-evaluated to ensure that the project can deliver the appropriate value at
an appropriate time.
data transformation development efforts.

At this point, the project scope, plan, and business requirements defined in the Manage
Phase should be re-evaluated to ensure that the project can deliver the appropriate value at
an appropriate time.

The Test phase includes the full design of testing plans and infrastructure as well as
comprehensive system-wide verification procedures. The System Test is conducted after all
elements of the system have been integrated into the test environment. It includes a
number of detailed technically-oriented verifications that are managed as processes by the
technical team with primarily technical criteria for acceptance. UAT is a detailed user-
oriented set of verifications with User Acceptance as the objective. It is typically managed by
end-users with participation from the technical team. A final step in the Test Phase activities
is related to tuning system performance.

to ensure that crucial steps are not missed in the production cut over.

Metadata, which is the cornerstone of any data integration solution, should play an integral
role in the documentation and training rollout to users. Not only is metadata critical to the
system operating smoothly by anticipating operational considerations such as
hardware/software upgrades, increased data volumes and network constraints before they
occur and planning for their resolution.

The project team enables ongoing suport by providing documentation and by conducting

You might also like