A | B |
tangible | Perceptible by the senses especially the sense of touch. |
data type | A classification identifying one of various types of data, stating the possible values for that type, the operations that can be done on that type, and the way the values of that type are stored. |
business rules | A formalized statement of the usual, customary, or generalized course of action or behavior for a business. |
implementation-free | Not dependent on the physical model. |
Entity Relationship Diagram (ERD) | A drawing that is used to represent a data model. |
Physical Model | A design for an object (a car, a house, a database, etc.) which includes implementation details such as size, volume, weight, etc.) |
Mandatory | Required. Not optional. |
Nontangible / Intangible | Incapable of being perceived by the senses. |
Conceptual Model | A data model, usually represented by an entity-relationship diagram. |
Expenditure | That which is paid out. |
Data | A collection of facts from which conclusions may be drawn. |
Unique Identifier (UID) | Any combination of attributes and/or relationships that serves, in all cases, to uniquely identify an occurrence of an entity. |
Data Model | The product of the database design process which aims to identify and organize the required data. |
Entity Relationship Modeling | A drawing that is used to represent a data model. |
Instance | An occurrence or example. |
Attribute | Characteristic, something that describes, quantifies or specifies an entity. |
Optional | Not required. Not mandatory. |
Entity | A named thing or category of things that is significant to the business and about which data must be known. |
Null | A value that is unavailable, unassigned, unknown, or inapplicable; it is not a zero or space. |
Volatile | Highly changeable. |
Single-valued | an attribute can only have one value for each instance of the entity. |