There are three stages of data modeling, and three types of data model - 1. Conceptual, 2. Logical and 3. Physical - each of which plays a distinct role in the data modeling process. They help organization’s efforts in organizing, understanding, and making productive use of enterprise data resources.
The three types of data model are conceptual data models, logical data models and physical data models. Each type of data model conveys the same information, from different perspectives. In order to create well-rounded and comprehensive models, the different types of data model help address different stakeholders needs and levels of expertise.
Conceptual, logical, and physical data models address the use of data assets from different degrees of abstraction. The models increase in complexity - starting with conceptual, through to physical data models. The models are used in different stages of the development process to foster the alignment of business goals and requirements with how data resources are used.
Concepts and system requirements are refined at each step as they move from conceptual models to logical models and are solidified in physical models.
When done right, data modeling adds value to the modern enterprise. But to maximize that value, organizations need a solid understanding of the types of data model, and stages of data modeling. Different types of data models can be used to address the diverse audiences involved in the development of new database systems.
It is important to use the correct type of data model to engage the business stakeholders involved in different stages of system development. The wrong type of data model will not convey the desired information to the intended audience nor be as useful in outlining and defining system requirements.
The initiative for a new database or application often comes from stakeholders trying to address evolving business requirements. These teams or individuals are interested in resolving a problem or streamlining a process from a very high-level perspective. The details of how the requirements will be met are irrelevant and will be handled by the appropriate technical parties.
Conceptual data models are the right vehicle for describing the purpose and components of the new system. A well-constructed conceptual model provides decision-makers with the information they need to approve or reject the proposed system.
See Also: What Is Conceptual Data Modeling? (And When Should It Be Used?)
Logical data models are then constructed by data architects in consultation with business analysts who understand the goals outlined in a conceptual model. At this level of abstraction, it becomes important to have a good understanding of the entities that will be represented in the system.
The purpose of logical models is to fully define the attributes and relationships exhibited by the identified entities. Ideally, this should be done while maintaining flexibility as to the database platform used for implementation. During the development and refinement of a logical model, it may become apparent that a particular database solution should be used for its implementation.
See Also: What Is Logical Data Modeling? (And Why Is It Important?)
Physical data models turn the initial abstract concepts regarding the entities involved in the system into schemas that target a specific database platform. They are used by the teams responsible for implementing the ideas and creating viable systems to address business requirements.
Physical data models are necessarily the most technical type of model. Concepts that are easily communicated abstractly can be technically challenging to implement. Keeping this sensitive data safe is simply stated in a conceptual model, but not so easily laid out when considering its physical implementation.
IDERA’s ER/Studio suite of data modeling tools enables teams to collaborate in the creation of conceptual, logical, and physical entity-relationship data models. The tools allow models to be created at the required level of abstraction to communicate with a specific audience.
Business Architect provides teams with a tool for creating conceptual data models to facilitate designing processes aligned with business goals and requirements. Create models to map relationships between people, processes, and data. The conceptual models can then be exported to ER/Studio Data Architect for the creation of logical data models.
Data Architect lets teams build and manage entity-relationship (ER) data models to streamline and enhance the database development cycle. The tool can discover and document existing data assets across the computing environment so they can be appropriately addressed. Impact analysis can be performed to ensure that new policies or changes to data models, databases, or data fields don’t clash with business requirements and expectations.
Enterprise Team Edition is a data modeling tool that fosters the collaboration necessary to create effective data models across an organization. The tool can be used to build a foundation for a data governance program and can discover and document existing enterprise data assets. The collaborative features of this tool help with the creation of global business data glossaries and definitions, making communication more productive throughout all parts of an organization.
These excellent data modeling solutions can be evaluated with a free 14-day trial that does not require a credit card and provides access to the tools’ full slate of features.
ER/Studio Business Architect DatasheetEverything you need to know, all in one downloadable PDF. DOWNLOAD THE DATASHEET
ER/Studio Data Architect Datasheet Everything you need to know, all in one downloadable PDF. DOWNLOAD THE DATASHEET
ER/Studio Enterprise Team Edition Datasheet Everything you need to know, all in one downloadable PDF. DOWNLOAD THE DATASHEET
See all data modeling resources.
Powered by IDERA