Logical data model

Logical data model

A logical data model also referred to as "LDM" in computer science is a representation of an organization's data, organized in terms of a particular data management technology. When ANSI first laid out the idea of a "logical schema" (in 1975 [1] ), the choices were "hierarchical" and "network". Relational had just been recognized as a data organization theory but no technology existed. Currently, the choices are "relational", "object-oriented", and "XML". Relational data is described in terms of tables and columns. Object-oriented data is described in terms of classes, attributes, and associations. XML is described in terms of "tags".

Logical data models, properly designed, should be based on the structures identified in the conceptual data model, since this describes the semantics of the business, which the logical model should also reflect. Even so, since the logical data model anticipates implementation on a finite-capacity computer, some will modify the structure to achieve certain efficiencies.

In certain organizations, there is a tendency to use the term 'Logical Data Model' to mean the 'Domain Model' or as an alternative to the domain model. While the two concepts are closely related, and having overlapping goals, domain model is more focused on capturing the concepts in problem domain than structure of the data which is associated with that domain.

What is a Logical Data Model

* Graphical representation of the business requirements
* Contains the things of importance in an organisation and how they relate to one another
* Contains business textual definitions and examples
* Validated and approved by a business representative
* Basis of physical database design

This is sometimes incorrectly called a "physical data model", which is not what the ANSI people had in mind. The physical design of a database involves deep use of particular database management technology. For example, a table/column design could be implemented on a collection of computers, located in different parts of the world. That is the domain of the physical model.

Difference of Logical & Physical Data Model

People often get confused with the fact that logical and physical data models are very different in their objectives, goals and content. Following are some key differences.

Why Build Logical Data Model

* Helps common understanding of business data elements and requirements
* Provides foundation for designing a database
* Facilitates avoidance of data redundancy and thus prevent data & business transaction inconsistency
* Facilitates data re-use and sharing
* Decreases development and maintenance time and cost
* Confirms a logical process model and helps impact analysis.

Logical Modeling Benefits

* Clarifies functional specifications and avoids assumption
* Confirms business requirements
* Facilitates business process improvement
* Focuses on requirements independent of technology
* Decreases system development time and cost
* Becomes a template for the enterprise
* Facilitates data re-use and sharing
* Faster ROI
* Gathers metadata
* Foster seamless communication between applications
* Focuses communication for data analysis and project team members
* Establishes a consistent naming scheme

References

# American National Standards Institute. 1975. “ANSI/X3/SPARC Study Group on Data Base Management Systems; Interim Report”. FDT(Bulletin of ACM SIGMOD) 7:2.


Wikimedia Foundation. 2010.

Игры ⚽ Нужно решить контрольную?

Look at other dictionaries:

  • Data model — Overview of data modeling context: A data model provides the details of information to be stored, and is of primary use when the final product is the generation of computer software code for an application or the preparation of a functional… …   Wikipedia

  • Physical data model — A physical data model (a.k.a. database design) is a representation of a data design which takes into account the facilities and constraints of a given database management system. In the lifecycle of a project it is typically derived from a… …   Wikipedia

  • Core Architecture Data Model — Example of a CADM Diagram for Overview and Summary Information (AV 1) of the DoDAF.[1] Core Architecture Data Model (CADM) in Enterprise Architecture is a logical data model of information used to describe and build architectures …   Wikipedia

  • Semantic data model — A semantic data model in software engineering is a data modeling technique to define the meaning of data within the context of its interrelationships with other data. A semantic data model is an abstraction which defines how the stored symbols… …   Wikipedia

  • Data architecture — in enterprise architecture is the design of data for use in defining the target state and the subsequent planning needed to achieve the target state. It is usually one of several architecture domains that form the pillars of an enterprise… …   Wikipedia

  • NGOSS Shared Information/Data Model — Shared Information/Data Model or SID is a unified reference data model providing a single number of terms of business objects included in basic business processes and also connections and relations between mentioned objects in telecommunications …   Wikipedia

  • Data modeling — The data modeling process. The figure illustrates the way data models are developed and used today. A conceptual data model is developed based on the data requirements for the application that is being developed, perhaps in the context of an… …   Wikipedia

  • Data warehouse — Overview In computing, a data warehouse (DW) is a database used for reporting and analysis. The data stored in the warehouse is uploaded from the operational systems. The data may pass through an operational data store for additional operations… …   Wikipedia

  • Model selection — is the task of selecting a statistical model from a set of candidate models, given data. In the simplest cases, a pre existing set of data is considered. However, the task can also involve the design of experiments such that the data collected is …   Wikipedia

  • Model–view–presenter — (MVP) is a derivative of the model–view–controller (MVC) software pattern, also used mostly for building user interfaces. In MVP the presenter assumes the functionality of the middle man (played by the controller in MVC). Additionally, the view… …   Wikipedia

Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”