Вы находитесь на странице: 1из 10

Implement an MDM with

Description of a first typical MDM project
A first typical MDM project
✓ Implementation of an MDM application for a specific
business domain such as Organization, RDM,…
✓ Setup of EBX5 Build chain and connection to directory.
✓ 3 main tables containing an average of 30 fields
✓ 10 secondary tables containing an average of 10 fields.
✓ 50 business rules (simple:30, medium:14, complex:6)
✓ 3 workflows of 10 steps with 2 specific ones each.
✓ 1 source system and 2 consumers to integrate.
✓ 3 groups of users with associated permissions, views and
✓ Basic user interface configuration with several customizations
(10 components, 3 forms, 3 services)

Topic focus planning

Phase 1 Phase 2 Phase 3

Infrastructure & Architecture

Data Models

Business Rules


User interfaces

Permissions & Access Rules


Data Sampling Data Recovery

add-ons implementation

Iterative phases
Phase are composed by short iterations. 2 teams
work in parallel. During design, previous iteration
is qualified and during development, the next
iteration is specified.

The functional team is composed by the project

leader and the business analyst.

The technical team is composed by the lead

developer and he developer.

Previous iteration Develop Qualify

Functional team
Current iteration Specify Design Develop Qualify Technical team
Next iteration Specify Design Editors validation
Actors involvement

20% 30% 40%

EBX5 Technical Product Project Tester

Expert Architect Owner Manager

50% 90%

Business Project Java Lead Key User

Analyst Leader Developer Developer

Resources Planning
EBX5 Expert
Technical Architect
Product Owner
Project Manager
Business Analyst
Project Leader
Java Developer
Lead Developer
Key user

✓ EBX 5 Expert is involved at the beginning for Infrastructure and Architecture and more punctually during the rest of
project to review all designs and realizations.
✓ The Technical Architect covers mainly the Infrastructure and Architectures workshops but also the connection with
other system at the end of the integration phase.
✓ The Product Owner Participate to the first workshop to give the main direction. He is also involved in UAT at each
phase to give a stamp on what has been done so far.
✓ The Key User is involved at each iteration for specifications and stay in support during the design to make compromise
with the technical team via the Business Analyst or the project manager. He is also part of UAT after each phase.


200 Man Days 100 Man Days

3 Phases 9 Iterations 3 months
External Internal

Technical Product Project Tester Key User
Architect Owner Manager

EBX5 Business Project Java Lead
Expert Analyst Leader Developer Developer

Orchestra Networks Experts mission
✓ Install and document first shared environment.
✓ Support other shared environments installation.
✓ Participate to technical Workshops.
✓ Review data models.
✓ Review designs of main features.
✓ Review implementation of main features.
✓ Control specific developments obsolescence and quality.
✓ Develop complex features.
✓ Be the technical referent at any level of the project

Main factors of success
✓ Get a first experience with a limited perimeter of Master
Data and few system to integrate
✓ Create an agnostic data model as close to reality as
✓ Be open to compromises between requirement and
features. EBX5 is a Product, not a development
✓ Involve an EBX5 expert from Orchestra Networks at key
steps, as described further.
✓ Do not be afraid by Java developments, they are often
simple and atomic component, confined in a rich API.

Main factors of delay
✓ The quality of existing data to integrate is overrated.
✓ Key users are involved too late and do not feel
concerned by MDM or do not understand it.
✓ Customization are developed, features are
implemented, high volumes of data are integrated,
without being careful of performances.
✓ Actors are not well identified or not enough involved.
✓ Derive of requirement specification.
✓ No involvement of Orchestra Networks EBX5 Experts to
ensure application of best practices.