Create and Manage Enterprise Data Models

Keep track of your data with purpose-fit models.

Book This Workshop

Conceptual data models are often neglected:

  • Because of limitations of modeling tools, the conceptual model is a standalone artifact and is not part of the data modeling environment.
  • Data Architecture and Data Modeling are seen as one and the same process.
  • The SDLC is delivery focused and only uses the physical data model. Conceptual modeling is normally not a part of the SDLC.
  • The long-term perceived value of the conceptual model is low. The conceptual model only has value during the initial stages of a large program.

A conceptual data model is an important business artifact:

  • A conceptual data model is an important business artifact:
  • It represents business concepts and relationships to business.
  • It verifies IT understanding of business concepts as used by business processes.
  • It acts as a business taxonomy and eases communication both within the organization and to the outside world.
  • It defines the business from a data-centric perspective and assists in the definition of data domains.
  • The conceptual model plays a significant role in domain modeling to identify and create bounded contexts.

Book Your Workshop

Onsite Workshops offer an easy way to accelerate your project. If you are unable to do the project yourself, and a Guided Implementation isn’t enough, we offer low-cost onsite delivery of our Project Workshops. We take you through every phase of your project and ensure that you have a road map in place to complete your project successfully.

Book Now

Member Rating

Overall Impact

Average $ Saved

Average Days Saved

After each Info-Tech experience, we ask our members to quantify the real-time savings, monetary impact, and project improvements our research helped them achieve.

Read what our members are saying

Module 1: Establish the Data Architecture Practice

The Purpose

  • Understand the context and goals of data architecture in your organization.

Key Benefits Achieved

  • A foundation for your data architecture practice.

Activities: Outputs:
1.1 Review the business context.
  • Data Architecture vision and mission and governance.
1.2 Obtain business commitment and expectations for data architecture.
  • Revised SDLC to include data architecture.
1.3 Define data architecture as a discipline, its role, and the deliverables.
  • Staffing strategy.
1.4 Revisit your SDLC to embed data architecture.
  • Data Architecture engagement protocol.
1.5 Modeling tool acquisition if required.
  • Installed modeling tool.

Module 2: Business Architecture and Domain Modeling

The Purpose

  • Identify the concepts and domains that will inform your data models.

Key Benefits Achieved

  • Defined concepts for your data models.

Activities: Outputs:
2.1 Revisit business architecture output.
  • List of defined and documented entities for the selected.
2.2 Business domain selection.
  • Practice in the use of capability and business process models to identify key data concepts.
2.3 Identify business concepts.
  • Practice the domain modeling process of grouping and defining your bounded contexts.
2.4 Organize and group of business concepts.
2.5 Build the Business Data Glossary.

Module 3: Harvesting Reference Models

The Purpose

  • Harvest reference models for your data architecture.

Key Benefits Achieved

  • Reference models selected.

Activities: Outputs:
3.1 Reference model selection.
  • Established and practiced steps to extend the conceptual or logical model from the reference model while maintaining lineage.
3.2 Exploring and searching the reference model.
3.3 Harvesting strategies and maintaining linkage.
3.4 Extending the conceptual and logical models.

Module 4: Harvesting Existing Data Artifacts

The Purpose

  • Gather more information to create your data models.

Key Benefits Achieved

  • Remaining steps and materials to build your data models.

Activities: Outputs:
4.1 Use your data inventory to select source models.
  • List of different methods to reverse engineer existing models.
4.2 Match semantics.
  • Practiced steps to extend the logical model from existing models.
4.3 Maintain lineage between BDG and existing sources.
  • Report examples.
4.4 Select and harvest attributes.
4.5 Define modeling standards.

Module 5: Next Steps and Wrap-Up (offsite)

The Purpose

  • Wrap up the workshop and set your data models up for future success.

Key Benefits Achieved

  • Understanding of functions and processes that will use the data models.

Activities: Outputs:
5.1 Institutionalize data architecture practices, standards, and procedures.
  • Data governance policies, standards, and procedures for data architecture.
5.2 Exploit and extend the use of the Conceptual model in the organization.
  • List of business function and processes that will utilize the Conceptual model.
Visit our IT Cost Optimization Center
Over 100 analysts waiting to take your call right now: 1-519-432-3550 x2019