| Data Warehouse Glossary |
|
If you do not see a particular word or phrase that you would like to know the definition of, please let us know by email and indicate the term you would like to be added to the Glossary. |
|
| |
| |
A
B
C
D
E
F
G
H
I
J
K
L
M
N O
P
Q
R
S
T
U
V
W
X
Y
Z |
|
| |
| Cache |
| |
A cache is a type of dynamic and high speed memory that is used to supplement the function of the central processing unit and the physical disk storage. The cache acts as a buffer when the CPU tries to access data from the disk so the data traveling from the CPU and physical disks can have synchronized speed. Disk reading and writing process is generally slower than CPU function. |
| |
| Cardinality |
| |
The number of data occurrences allowed on either side of a data relation. In the common data architecture, cardinality is documented with data integrity, not with the data structure. |
| |
| CASE |
| |
Computer Aided Software Engineering. |
| |
| CASE Management |
| |
The management of information between multiple CASE "encyclopedias," whether the same or different CASE tools. |
| |
| CASE Tools |
| |
A set of integrated Computer-Aided Systems Engineering (CASE) and application development tools that assist in software development; for example, analyzing business requirements, designing applications, generating application code, etc. |
| |
| Catalog |
| |
A component of a data dictionary that contains a directory of its DBMS objects as well as attributes of each object. |
| |
| Category |
| |
A structure for organizing, typing, and representing a dimension of a multidimensional cube. |
| |
| Central Repository |
| |
Location of a collection of documentation, customizations, modifications, or enhancements designed to alleviate the recreation of successfully completed work. |
| |
| Central Warehouse |
| |
A database created from operational extracts that adheres to a single, consistent, enterprise data model to ensure consistency of decision-support data across the corporation. A style of computing where all the information systems are located and managed from a single physical location. |
| |
| Centralized Data Warehouse |
| |
A data warehouse implementation in which a single warehouse serves the need of several business units simultaneously with a single data model which spans the needs of the multiple business divisions. |
| |
| Change |
| |
A deviation from a currently established baseline. |
| |
| Change Data Capture |
| |
The process of capturing changes made to a production data source. Change data capture is typically performed by reading the source DBMS log. It consolidates units of work, ensures data is synchronized with the original source, and reduces data volume in a data warehousing environment. |
| |
| Change Management |
| |
1. The complete set of processes employed on a project to ensure that changes are implemented in a visible, controlled and orderly fashion.
2. The activity, or set of activities, undertaken to govern systematically the effects of organizational change. |
| |
| Change Request |
| |
1. A request for a change to the required behavior of a system, usually from a user as a result of reviewing current behavior.
2. The mechanism by which a change is requested, investigated, resolved and approved; |
| |
| Classic Data Warehouse Development |
| |
The process of building an enterprise business model, creating a system data model, defining and designing a data warehouse architecture, constructing the physical database, and lastly populating the warehouses database. |
| |
| Client/Server |
| |
A type of technical architecture that links many personal computers or workstations (clients) to one or more large processors (servers). Clients generally manage the user interface, possibly with some local data. Servers usually manage multiple-access databases, including ensuring data integrity and other invariants. |
| |
| Client/Server Processing |
| |
A form of cooperative processing in which the end-user interaction is through a programmable workstation (desktop) that must execute some part of the application logic over and above display formatting and terminal emulation. |
| |
| Cluster |
| |
A means of storing data together from multiple tables, when the data in those tables contains common information accessed concurrently. |
| |
| Coarse Granularity |
| |
|
| |
| Collection |
| |
A set of data that resulted from a DBMS query. |
| |
| Collection Time |
| |
The time data were actually collected about the event. |
| |
| Column |
| |
A means of implementing an item of data within a table. It can be in character, date, or number format, and be optional or mandatory. |
| |
| Combined Data |
| |
A concatenation of individual facts. |
| |
| Common Data Architecture |
| |
A formal, comprehensive data architecture that provides a common context within which an integrated data resource is developed so that it adequately supports the business information demand. |
| |
| Common Data Model |
| |
A comprehensive model that represents the universe of data available to an organization that has been identified and defined within the common data architecture. It represents the objects and events in the real world that are of interest to the organization, is subject-oriented, and includes all perspectives of the real world. |
| |
| Common Data Modeling |
| |
The process of developing a model of the integrated data resource within a common data architecture. The process facilitates the integration of existing data and increases the awareness and understanding of those data. It is a process to plan the distribution of data based on business needs and the physical operating environment. |
| |
| Common Data Modeling Method |
| |
A method that combines forward data modeling, reverse data modeling, and vertical data modeling. The method provides an easy way to move between unnormalized business transactions and a denormalized database and between the real world and detailed data resource design within the common data architecture. Common Data Modeling is one of the core considerations when setting up a business data warehouse. Any serious company wanting to have a data warehouse will have to be first serious about data models. Building a data model takes time and it is not unusual for companies to spend two to five years just doing it. |
| |
| Common Data Structure |
| |
The structure of data within the common data architecture that provides a full understanding of all the disparate data structures and multiple perspectives of the real world represented by those data structures. |
| |
| Common Metadata |
| |
Metadata developed within the common data architecture to provide all the detail necessary to thoroughly understand the data resource and how it can be improved to meet the business information demand.
In simple but technical term, metadata is a data that describes another data. It can be any item describing an individual datum or a collection of multiple content items.
Metadata is very useful in facilitating the use, management and understanding of data in a large data warehouse. Depending on the type of data and the context where the data is being used, metadata required to effectively manage a database or large data warehouse varies. |
| |
| Communications Integrity |
| |
An operational quality that ensures transmitted data has been accurately received at its destination. |
| |
| Comprehensive Data Definition |
| |
A formal data definition that provides a complete, meaningful, easily read, readily understood definition explaining the content and meaning of data. |
| |
| Computer Network |
| |
An interconnected group of computers. |
| |
| Computer-Aided Systems Engineering (CASE) |
| |
The combination of graphical, dictionary, generator, project management, and other software tools to assist computer development staff engineer and maintain high-quality systems, within the framework of a structured method. |
| |
| Conceptual Schema |
| |
A schema that represents a common structure of data that is the common denominator between the internal schema and external schema. In any data warehouse implementation there are many different considerations which should in place before the final physical setting up. This is to avoid in problems related to quality of data and consistencies in data processes. |
| |
| Conformed Dimension |
| |
A dimension that has exactly the same meaning and content when being referred from different fact tables. |
| |
| Connectivity |
| |
The ability of a device to connect to another. This includes not only the physical issues associated with the buses, connector topologies and other such matters, but also the support of the protocols required to pass data successfully over the physical connection.
Computer networks are the main connectivity mechanism for passing data in an electronic environment. A network is composed of several computers connected by a wired or wireless medium so data and other resources can pass through for sharing. |
| |
| Consistent Data Quality |
| |
The state of a data resource where the quality of existing data is thoroughly understood and the desired quality of the data resource is known. It is a state where disparate data quality is known, and the existing data quality is being adjusted to the level desired to meet the current and future business information demand. |
| |
| Consumer |
| |
An individual, group or application that accesses data/information in a data warehouse. |
| |
| Consumer Profile |
| |
Identification of an individual, group or application and a profile of the data they request and use: the kinds of warehouse data, physical relational tables needed, and the required location and frequency of the data (when, where, and in what form it is to be delivered). |
| |
| Cooperative Processing |
| |
A style of computer application processing in which the presentation, business logic, and data management are split among two or more software services that operate on one or more computers. In cooperative processing, individual software programs (services) perform specific functions that are invoked by means of parameterized messages exchanged between them. |
| |
| Copy Management |
| |
The analysis of the business benefit realized by the cost of expenditure on some resource, tool, or application development. |
| |
| Critical Success Factor (CSF) |
| |
A business event, dependency, product, or other factor that, if not attained, would seriously impair the likelihood of achieving a business objective. |
| |
| Critical Success Factors |
| |
Key areas of activity in which favorable results are necessary for a company to reach its goal. |
| |
| Crosstab |
| |
A process or function that combines and/or summarizes data from one or more sources into a concise format for analysis or reporting. |
| |
| Currency Date |
| |
The date the data is considered effective. It is also known as the "as of" date or temporal currency. |
| |
| Custom Code |
| |
Coding added to a packaged application or module generated by a CASE tool to implement functionality that the application or generator has not provided. |
| |
|
|
|
|