Database Model
A Database Model is an information model of (the relationships within) a data base.
- AKA: Data Base Schema.
- Context:
- It can be of a Data Model Type, such as a Relational Data Model or an Object-Oriented Data Model.
- It can range from being a Physical Database Schema/Physical Data Model to being Logical Data Model to being a Conceptual Data Model.
- It can be a Data Record Schema.
- It can be based on a Data Model Pattern.
- It can be produced by: Database Modeling, Data Model Normalization Task.
- …
- Example(s):
- Counter-Example(s):
- an Enterprise Model.
- a UML Model.
- See: Data Structure, Entity Relationship Model, Data Dictionary, Data Entity, Data Attribute, Data Structure.
References
2013
- (Wikipedia, 2013) ⇒ http://en.wikipedia.org/wiki/Data_model Retrieved:2013-12-1.
- In software engineering, the term data model is used in two related senses. In the sense covered by this article, it is a description of the objects represented by a computer system together with their properties and relationships; these are typically "real world" objects such as products, suppliers, customers, and orders. In the second sense, covered by the article database model, it means a collection of concepts and rules used in defining data models: for example the relational model uses relations and tuples, while the network model uses records, sets, and fields.
[[File: make-or-buy decision. The figure is an example of the interaction between process and data models.[1]]]
Data models are often used as an aid to communication between the business people defining the requirements for a computer system and the technical people defining the design in response to those requirements. They are used to show the data needed and created by business processes.
According to Hoberman (2009), "A data model is a wayfinding tool for both business and IT professionals, which uses a set of symbols and text to precisely explain a subset of real information to improve communication within the organization and thereby lead to a more flexible and stable application environment."[2]
A data model explicitly determines the structure of data. Data models are specified in a data modeling notation, which is often graphical in form.[3]
A data model can be sometimes referred to as a data structure, especially in the context of programming languages. Data models are often complemented by function models, especially in the context of enterprise models.
- In software engineering, the term data model is used in two related senses. In the sense covered by this article, it is a description of the objects represented by a computer system together with their properties and relationships; these are typically "real world" objects such as products, suppliers, customers, and orders. In the second sense, covered by the article database model, it means a collection of concepts and rules used in defining data models: for example the relational model uses relations and tuples, while the network model uses records, sets, and fields.
- ↑ Paul R. Smith & Richard Sarfaty (1993). Creating a strategic plan for configuration management using Computer Aided Software Engineering (CASE) tools. Paper For 1993 National DOE/Contractors and Facilities CAD/CAE User's Group.
- ↑ "Data Modeling Made Simple 2nd Edition", Steve Hoberman, Technics Publications, LLC 2009
- ↑ Michael R. McCaleb (1999). "A Conceptual Data Model of Datum Systems". National Institute of Standards and Technology. August 1999.
1999
- (McCaleb, 1999) ⇒ Michael R. McCaleb (1999). "A Conceptual Data Model of Datum Systems". National Institute of Standards and Technology. August 1999.
1976
- (Chen, 1976) ⇒ Peter Pin-Shan Chen. (1976). “The Entity-relationship Model—toward a Unified View of Data.” In: ACM Transactions on Database Systems (TODS) Journal, 1(1). doi:10.1145/320434.320440
- QUOTE: … The entity-relationship model can be used as a basis for unification of different views of data: the network model, the relational model, and the entity set model. …