| 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 |
|
| |
| |
| B Tree |
| |
An indexing technique in which pointers to data are kept in a “Balanced Tree” structure such that all referenced data is equally accessible in an equal timeframe. It is also a tree data structure which keeps data sorted so that searching, inserting and deleting can be done in logarithmic amortized time. |
| |
| Backup and Recovery Strategy |
| |
A storage and recovery strategy that protects against business information loss resulting from hardware, software, or network faults.
|
| |
| Base Tables |
| |
The normalized data structures maintained in the target warehousing database. Also known as the detail data. |
| |
| Baseline |
| |
1. A starting point or condition against which future changes are measured. 2. A named set of object versions which fixes a configuration at a particular point in time. A baseline normally represents a milestone or key deliverable of a project. |
| |
| Bi-directional Extracts |
| |
The ability to extract, cleanse, and transfer data in two directions among different types of databases, including hierarchical, networked, and relational databases. |
| |
| Bit Mapped Indexes |
| |
Bit Map Indexing is a technique commonly used in relational databases where the application uses binary coding in representing data. Originally used only for Low Cardinality data, recent advances such as Sybase IQ have allowed this technique to be used for High Cardinality data as well. |
| |
| Braking Mechanism |
| |
A software mechanism that prevents users from querying the operational database once transaction loads reach a certain level. |
| |
| Budget |
| |
A plan for determining in advance the expenditure of time, money, etc. |
| |
| Bulk Data Transfer |
| |
A software-based mechanism designed to move large data files. It supports compression, blocking and buffering to optimize transfer times. |
| |
| Business |
| |
An enterprise, commercial entity, or firm in either the private or public sector, concerned with providing products or services to satisfy customer requirements. |
| |
| Business Activities |
| |
A component of information technology infrastructure that represent all business activities in an organization, whether they are automated or manual. They utilize the data resource and the plat-form resource to perform specific processes and tasks. |
| |
| Business Aim |
| |
A statement of business intent measured subjectively; for example, to move up market, or to develop a sustainable level of growth; usually strategic or tactical with a 3-5 year horizon. |
| |
| Business Architecture |
| |
One of the four layers of an information systems architecture. Business architecture describes the functions a business performs and the information it uses. |
| |
| Business Area |
| |
The set of business processes within the scope of a project. |
| |
| Business Constraint |
| |
Any external, management, or other factor that restricts a business or system development in terms of resource availability, dependencies, timescales, or some other factor. |
| |
| Business Data |
| |
Information about people, places, things, business rules, and events, which is used to operate the business. |
| |
| Business Drivers |
| |
The people, information, and tasks that support the fulfillment of a business objective. |
| |
| Business Experts |
| |
People that thoroughly understand the business and the data supporting the business. They know the specific business rules and processes unique to the organization or organizations within the scope of the common metadata. |
| |
| Business Function |
| |
Something an enterprise does, or needs to do, in order to achieve its objectives. |
| |
| Business Goal |
| |
A statement of business intent. |
| |
| Business Location |
| |
A uniquely identifiable geographic location, site, or place from which one or more business units may wholly or partly operate. |
| |
| Business Meta data |
| |
The information whereby users can understand and access the data warehouse. It focuses on what data is in the warehouse, how it was transformed, the source, and the timeliness of the data. |
| |
| Business Model |
| |
A view of the business at any given point in time. The view can be from a process, data, event or resource perspective, and can be the past, present or future state of the business. |
| |
| Business Object |
| |
A physical or logical object of significance to a business; for example, a sales order, department, assembly, item, balance, or invoice. A business object is analogous to a class in object-oriented terminology. |
| |
| Business Organization Type |
| |
A classification of a business organization into one of several functional categories. Each business organization type has a distinct set of business requirements. All the business organizations of a certain type will typically require similar applications and system capabilities. A given site may house one or more business organization types. Since business organizations may be related in a hierarchy, a high level business organization may be composed of several business organizations of different types. For the purposes of application architecture analysis and design, it is generally useful to decompose the hierarchy of business organizations until it is composed of atomic organization types. |
| |
| Business Priority |
| |
A statement of the level or urgency of important business needs. |
| |
| Business Process |
| |
The complete response that a business makes to an event. A business process entails the execution of a sequence of one or more process steps. It has a clearly defined deliverable or outcome. A Business Process is defined by the business event that triggers the process, the inputs and outputs, all the operational steps required to produce the output, the sequential relationship between the process steps, the business decisions that are part of the event response, and the flow of material and/or information between process steps. |
| |
| Business Process Reengineering (BPR) |
| |
The activity by which an enterprise reexamines its goals and how it achieves them, followed by a disciplined approach of business process redesign. A method that supports this activity. |
| |
| Business Rule |
| |
A rule under which an organization operates. A policy or decision that influences the process step. |
| |
| Business Schema |
| |
A schema that represents the structure of business transactions used by clients in the real world. It is considered to be unnormalized data. |
| |
| Business System |
| |
A combination of people and automated applications organized to meet a particular set of business objectives. |
| |
| Business Transaction |
| |
A unit of work acted upon by a data capture system to create, modify, or delete business data. Each transaction represents a single valued fact describing a single business event. |
| |
| Business Unit |
| |
Part of an organization treated for any purpose as a separate entity within the parent organization. Examples include a department or distribution center. |
| |
| Business-Driven Approach |
| |
The process of identifying the data needed to support business activities, acquiring or capturing those data, and maintaining them in the data resource. |
| |
| Business-Driven Data Distribution |
| |
The situation where the business need for data at a specific location drive the development of a data site and the distribution of data to the data site. It is independent of the existence of a telecommunications network |
| |
| Buy-In |
| |
The process whereby stakeholders, e.g. end-users as well as executives, come to see the goals of an organizational or change effort as their own; a key component in achieving change successfully. |
| |
| |
|
|
|
|