Chapter 2, Database Systems: Design, Implementation, and Management 12e

Terms in this set (70)

3 Vs
Three basic characteristics of Big Data databases: volume, velocity, and variety.
American National Standards Institute(ANSI)
A group that accepted the DBTG recommendations and augmented database standards in 1975 through its SPARC committee.
Attribute
A characteristic of an entity or object. An attribute has a name and data type.
Big Data
A movement to find new and better ways to manage large amounts of web-generated data and derive business insight from it, while simultaneously providing high performance and scalability at a reasonable cost.
Business Rule
A description of a policy, procedure, or principle within an organization. For example, a pilot cannot be on duty for more than 10 hours during a 24-hour period, or a professor may teach up to four classes during a semester.
Chen Notation
See entity relation (ER) model.
Class
A collection of similar objects with shared structure (attributes) and behavior (methods). A class encapsulates an object's data representation and a method's implementation. Classes are organized in a class hierarchy.
Class Diagram
A diagram used to represent data and their relationship in UML object notation.
Class Diagram Notation
The set of symbols used in the creation of class diagrams in UML object modeling.
Class Hierarchy
The organization of classes in a hierarchical tree in which each parent class is a superclass and each child class is a subclass. See also, inheritance.
Client Node
One of three types of nodes used in the Hadoop Distributed File System (HDFS). The client node acts as the interface between the user application and HDFS. See also Name Node and Data Node.
Conceptual Model
The output of the conceptual design process. The conceptual model provides a global view o an entire database and describes the main data objects, voiding details.
Conceptual Schema
A representation of the conceptual model, usually expressed graphically. See also Conceptual Model.
Connectivity
The type of relationship between intities. Classifications include 1:1, 1:M and M:N.
Constraint
A restriction placed on data, usually expressed in the form of rules. For example, "A student's GPA must be between 0.00 and 4.00." (Constraints are important because they help to ensure data integrity.)
Crow's Foot Notation
A representation of the entity relationship diagram that uses a three-pronged symbol to represent the "many" sides of the relationship.
Data Definition Language (DDL)
The language that allows a database administrator to define the database structure, schema, and subschema.
Data Manipulation Language (DML)
The set of commands that allows and end user to manipulate the data in the database, such as SELECT, INSERT, UPDATE, DELETE, COMMIT, and ROLLBACK.
Data Model
A representation, usually graphic, of a complex "real-world" data structure. Data models are used in the database design phase of the Database Life Cycle.
Data Modeling
The process of creating a specific data model for a determined problem domain.
Data Note
One of three types of noes used in the Hadoop Distributed File System (HDFS). The data node stores fixed-size data blocks (that could be replicated to other data nodes). See also, Client Node and Name Node.
Entity
A person, place, thing, concept, or event for which data can be stored. See also, attribute.
Entity Instance
A row in a relational table. Also known as Entity Occurrence.
Entity Occurrence
A row in a relational table. Also known as Entity Instance.
Entity Relationship (ER) Model (ERM)
A data model that describes relationships (1:1, 1:M, and M:N) among entities at the conceptual level with the help of ER diagrams. The model was developed by Peter Chen.
Entity Relationship Diagram (ERD)
A diagram that depicts an entity relationship model's entities, attributes, and relations.
Entity Set
A collection of like entities.
Eventual Consistency
A model for database consistence in which updates to the database will propagate through the system so that all data copies will be consistent eventually.
Extended Relational Data Model (ERDM)
A model that includes the object-oriented model's best features in an inherently simpler relational database structural environment. See also, Extended Entity Relationship Model (EERM).
Extensible Markup Language (XML)
A meta-language used to to represent and manipulate data elements. Unlike other markup languages, XML permits the manipulation of a document's data elements. XML facilitates the exchange of structured documents such as orders and invoices over the internet.
External Model
The application programmer's view of the data environment. Given its business focus, an external model works with data subset of the global database schema.
External Schema
The specific representation of an external view; the end user's view of the data environment.
Hadoop
A Java based, open source, high speed, fault-tolerant distributed storage and computational framework. Hadoop uses low-cost hardware to create clusters of thousands of computer nodes to store and process data.
Hadoop Distributed File System (HDFS)
A highly distributed, fault tolerant file storage system designed to manage large amounts of data at high speeds.
Hardware Indepence
A condition in which a model does not depend on the hardware used in the model's implementation. Therefore, changes in the hardware will have no effect on the database design at the conceptual level.
Hierarchical Model
An early database model whose basic concepts and characteristics formed the basis for subsequent database development. This model is based on an upside-down tree structure in which each record is called a segment. The top record is the root segment. Each segment has a 1:M relationship to the segment directly below it.
Inheritance
In the object-oriented data model, the ability of an object to inherit the data structure and methods of the classes above it in the class hierarchy. See also, Class Hierarchy.
Internal Model
In database modeling, a level of data abstraction that adapts the conceptual model to a specific DBMS model for implementation. The internal model is the representation of a database as "seen" by the DBMS. In other words, the internal model required a designer to match the conceptual model's characteristics constraints to those of the selected implementation model.
Internal Schema
A representation of an internal model using the database constructs supported by the chosen database.
Key-Value
A database model based on a structure composed of two data elements;: a key and a value, in which every key has a corresponding value or set of values. The key value data model is also called the associative or attribute-value data model.
Logical Design
A stage in the design phase that matches the conceptual design to the requirements of the selected DBMS and is therefore software dependent. Logical design is used to translate the conceptual design into the internal model for a selected database management system, such as DB2, SQL Server, Oracle, IMS, Informix, Access, or Ingress.
Logical Independence
A condition in which the internal model can be changed without affecting the conceptual model. (The internal model is hardware independent because it is unaffected by the computer on which the software is installed. Therefore, a change in storage devices or operating systems will not affect the internal model.)
MapReduce
An open-source application programming interface (API) that provides fast data analytics services; one of the main Big Data technologies that allows organizations to process massive data stores.
Many-To-Many Relationship
Association among two or more entities in which once occurrence of an entity is associated with many occurrences of a related entity and one occurrence of the related entity is associated with many occurrences of the first entity.
Method
In the object-oritented data model, a named set of instructions to perform an action. Methods represent real world actions, and are invoked through messages.
Name Node
One of three types of nodes used in the Hadoop Distributed File System (HDFS). The name node stores all the metadata abut the file system. See also client node and data node.
Network Model
An early data model that represented data as a collection of record types in 1:M relationships.
NoSQL
A new generation of database management systems that is not based on the traditional relational database model.
Object
An abstract representation of a real world entity that has a unique identity, embedded properties, and the ability to interact with other objects and itself.
Object Relational Database Management System (O/R DBMS)
A DBMS based on he extended relational model (ERDM). The ERDM, championed by many relational database researches, constitutes the relational model's response to the OODM. This model includes many of the object-oriented model's best features within an inherently simpler relational database structure.
Object-Oriented Data Model (OODM)
A data model whose basic modeling structure is an object.
Object-Oriented Database Management System (OODBMS)
Data management software used to manage data in an object-oriented database model.
One-To-Many Relationship
Associations among two or more entities that are used by data models. In a 1:M relationship, one entity instance is associated with many instances of the related entity.
One-To-One Relationship
Associations among two or more entities that are used by data models. In a 1:1 relationship, one entity instance is associated with only one instance of the related entity.
Physical Indepence
A condition in which the physical model can be changed without affecting the internal model.
Physical Model
A model in which physical characteristics such as location, path, and format are described for the data. The physical model is both hardware - and software dependent. See also Physical Design.
Relation
A logical construct perceived to be a two dimensional structure composed of intersecting rows (entities) and columns (attributes) that represents an entity set in the relational model.
Relational Database Management System (RDBMS)
A collection of programs that mananages a relational database. The RDBMS software translates a user's logical requests (queries) into commands that physically locate and retrieve the requested data.
Relational Diagram
A graphical representation of a relational database's entities., the attributes within those entities, and the relationships among the entities.
Relational Model
Developed by EF Codd of IBM in 19070, the relational model is based on mathematical set theory and represents data as independent relations. Each relation (table) is conceptually represented as a two dimensional structure of intersecting rows and columns. The relations are related to each other through the sharing of common entity characteristics (values in columns).
Relationship
An association between two entities ( tables).
Schema
A logical grouping of database objects, such as tables, indexes, views, and queries, that are related to each other. Usually a schema belongs to a single user or application.
Segment (SEGM)
In the hierarchical data model, the equivalent of a file system's record type.
Semantic Data Model
The first of a series of data models that more closely represented the real world, modeling both data and their relationship in a single structure known as an object. The SDM, published in 1981, was developed by M. Hammer and D. McLeod.
Software Independence
A property of any model or application that does not depend on the software used to implement it.
Sparse Data
A case in which the number of table attributes is very large by the number of actual data instances is low.
Subschema
The portion of the database that interacts with application programs.
Table
A logical construct perceived to be a two dimensional structure composed of intersecting rows (entities) and columns (attributes) that represents an entity set in the relational model.
Tuple
In the relational model, a table row.
Unified Modeling Language (UML)
A language based on object-oriented concepts that provide tools such as diagrams and symbols to graphically model a system.
YOU MIGHT ALSO LIKE...
;