One-day course: MDM best practices & procedures for modeling effective MDMWe are pleased to announce to our members this educational course regarding MDM best practices & procedures for modeling effective Master Data Management. This one-day course has been developed and is delivered by Pierre Bonnet, founder of the MAG Community. It is available in English and French languages.

Download the complete MDM Alliance Group Training materials to get a quick understanding of the MDM modeling procedures

Content of the one-day trainingDuring the day, attendees will discover the architecture and the modeling procedures used in the context of Master Data Management projects (MDM). The methodology framework is based on procedures describe in the MDM method guide of the MDM Alliance Group. This guide is published free of charge and is available in electronic format via this link.

This session is dedicated to IT specialists and business executives that are involved in information system projects who want to gain insight into the MDM method.

- Executives will have the key points needed to launch a first MDM project.- Project Directors will learn the key points for modeling so as to better identify proficiencies required to conduct MDM projects.- Project managers, engineers, enterprise architects, information architects, designers… will have the basis that allows for designing a MDM taking into account the procedures detailed in the MDM method guide.

Agenda for morningWhat is added value of Master Data Management?- Criteria for identifying ref/master data.- Architecture styles of MDM.- Why MDM is appearing now in the information systems strategy?- How to deploy MDM projects in a context of high use of software packages (ERP).

How to start a first MDM project?- The questions that must be asked.- The scope of the first project.- The iterative design life-cycle compared with a top-down life-cycle approach (Enterprise Architecture).

A first and quick insight into modeling procedures- Are there new procedures? What is the positioning of data administration as known for a long time?- What are criteria that the method must respect so as to be suitable for MDM projects? In particular, business life cycle and organizational life cycle of ref/master data must be separated.- Functions that must be excluded from the modeling and why?

Agenda for afternoonThe business modeling (core system)- Architecture of the Common Information Model structured with help from business objects (coarse grained objects).- Modeling of business objects and life cycles. Discovering of elementary business operations and extended business operations.- Reuse and upgrade ability of the Common Information Model- Usual modeling questions and MDM procedures: inheritance, object identifiers, enumeration, etc.- List of UML diagrams used.

The organizational modeling- Architecture based on use cases and processes for approving data, interconnection between systems, rights management, data traceability and audit, etc.- Modeling of elementary activities and extended activities.- Business transaction management.- List of UML diagrams used.

The logical modeling- Deriving business models in order to build the ref/master data logical model and business services, in a context that relies on both relational, oriented object, hierarchical (XML Schema) and triggers (facets, pre and post conditions) styles of data architecture.- Taking into account the logical-technical negotiation. Some key points of this negotiation are presented, for example, the difference between Complex type and Table concepts (table relies on referential integrity constraints), use of default CRUD procedures that are brought by the MDM tool, etc.- Setting up loosely coupled data architecture with help from the Category Class concept of Grady Booch.- Usual logical modeling questions: inheritance, object identifiers, enumeration, messages handling, etc.- Deriving organizational models in order to obtain the service logical model for organizational layer.- List of UML diagrams used.

Versions and variants management- Understanding the difference between version and variant.- Version management at the level of data models.- Version management at the level of data values.- Variant management so as to feed a unique data with several values depending on several contexts of execution.

Impacts regarding the organization- Organization of the MDM project. What are the respective roles of business users and IT specialists: process of validation, use of the enterprise topology so as to develop precise proficiencies required for a successful MDM project.- Organization after the MDM roll-out: responsibilities, deployment process, maintenance charter.

MDM strategic perspectives- What is the link between the enterprise governance and ref/master data repository?- How to use the MDM tool with the business rules management (BRMS) and with an orchestration engine / Business Process Management (BPM) ?