- Business executives don’t understand the value of Conceptual and Logical Data Models and how they define their data assets.
- Data, like mercury, is difficult to manage and contain.
- IT needs to justify the time and cost of developing and maintaining Data Models.
- Data as an asset is only perceived from a physical point of view, and the metadata that provides context and definition is often ignored.
Our Advice
Critical Insight
- Data Models tell the story of the organization and its data in pictures to be used by a business as a tool to evolve the business capabilities and processes.
- Data Architecture and Data Modeling have different purposes and should be represented as two distinct processes within the software development lifecycle (SDLC).
- The Conceptual Model provides a quick win for both business and IT because it can convey abstract business concepts and thereby compartmentalize the problem space.
Impact and Result
- A Conceptual Model can be used to define the semantics and relationships for your analytical layer.
- It provides a visual representation of your data in the semantics of business.
- It acts as the anchor point for all data lineages.
- It can be used by business users and IT for data warehouse and analytical planning.
- It provides the taxonomies for data access profiles.
- It acts as the basis for your Enterprise Logical and Message Models.