|
TERM |
DEFINITION |
|
Access Control |
Refers to mechanisms and policies that restrict access to computer
resources. |
|
Ad-Hoc reporting |
Unpredictable, unplanned access and manipulation of data . |
|
Archive Services |
Provides long-term off-line storage of data, which must be
retained for historic purposes. The services will allow
users to archive and retrieve data as needed to support the
business processes. Automated processes may also archive
data, which has not been accessed for a specified period of time. |
|
Atomic Database |
A database of change records that when applied in temporal order
will reconstruct, in a target database, an identical copy of a
source database at a point in time. |
|
Attribute |
Used in Logical Data Modeling, an Attribute is any detail that
serves to identify, describe, classify, quantify or provide the
state of an entity. For example, the entity, Employee, may have the following
attributes: Last Name, First Name, and Hire Date.
Attributes are the general equivalent of physical columns in a
table. |
| Audit Trail |
A record showing who has accessed a computer system and what
operations he or she has performed during a given period of
time. Data that is available to trace system activity
usually update activity. |
|
Best Practices Reports |
Canned routines based on predefined parameters. |
|
Change Tables |
Set of tables that mirror an OLTP in structure, with the possible
addition of auditing information. All OLTP tables will not
necessarily have associated change tables. |
|
Data Architecture |
A specific framework for
managing data to enable the institution to build and maintain
the strategic capabilities it needs to achieve its mission.
The framework consists of a set of principles, standards, and
models that describe how the data will be created, maintained,
and protected. The framework focuses on improving effectiveness
and reducing long-term costs and contains components that cover
the full data life cycle from creation to retirement. An example
is ETL tool. |
|
Database |
Any collection of data. |
|
Database Engine |
The software that holds the database and executes the requests
against that database. Oracle is an example of a Database Engine. |
|
DataMart |
A customized subset of data taken from the Data Warehouse. A
DataMart is typically set up by a specific individual or
department to support their particular needs. |
|
Data Model |
A graphical representation illustrating data-related business
requirements in the context of a given application. |
|
Data Replication |
Process of copying and maintaining schema objects in multiple
databases that make up a distributed database system.
Replication can improve the performance and protect the
availability of applications because alternate data access options
exist. |
|
DataStore |
See Operational Data
Store. |
|
Data Warehouse |
An enterprise-wide database. It is a read-only
collection of data from any number of sources. It is usually
refreshed from Operational
DataStores, but may also receive data from
OLTP's. It is also the likely source of data for a DSS. |
|
Decision Support System (DSS) |
A complete process for allowing users to access data which they
need to support their decision making process. This includes the
database(s) holding the data, the software application which
interfaces with the Database Engine, metadata, training, and
support. |
|
Degree |
Shows how many instances of an
entity can exist at one end of the relationship
for each entity instance at the other end. Crow's feet shows
a relationship degree of many and a single
point represents a relationship degree of one. |
|
Denormalization |
Roughly the opposite of Normalization. In a
denormalized database, some duplicated data storage is allowed.
The benefits are quicker retrieval of data and a database
structure that is easier for end-users to understand and is
thereby more conducive to adhoc queries. |
|
Domain |
A set of business validation rules, format constraints, and
allowable values that apply to a group of attributes. For example,
yes and no or days of the week. |
|
ETL |
It signifies Extraction, Transformation, and Load. The tool
extracts, transforms and loads data from data sources to data
targets in a central repository. The data sources can be a
database, file, or COBOL copybook or any combination of the
three. It will be primarily used to move data from an OLTP
to an ODS or an ODS
to DSS. |
|
Entity |
Used in Logical Data Modeling, an Entity is a thing of significance,
either real or conceptual, about which the business or system
being modeled needs to hold information. For example, if the
business needs to process sales orders, an Entity to represent
sales orders would be recorded. An Entity generally corresponds
to a physical table. Also see Attribute. |
|
Entity Relationship
Diagram (ERD) |
Entity relationship modeling involves identifying the things of importance in an organization
(entities), the properties of those things (attributes) and how they are related to one another
(relationships). The resulting information model is independent of any data storage or access method. |
|
Foreign Key |
In a table, one or more columns whose values must match the values
in the primary key of the referenced table.
The columns in the foreign key typically reference the primary
key of another table but may reference the same table. This
mechanism allows two tables to be joined together. |
|
Function Hierarchy Diagram |
Displays all of the functional requirements of an application and
their logical groupings. Shows the decomposition of functions
ranging from the highest level or root to the lowest level or leaf
required. |
|
Metadata |
This is "data describing the data." This data
provides information about a database, including descriptions of
the tables and columns, as well as descriptions of the data stored
within those tables and columns. |
|
Methodology |
Facilitates a repeatable structured approach to defining
requirements and developing business applications. A
methodology tells you what to do and when. An Example is
Develop a Data Movement process. |
|
MI Operations & Production Control |
Individuals filling this role are responsible for overseeing
the 24-hour operation of assigned systems. Direct the daily setup
of customer jobs for assigned systems. Negotiate schedules for
all systems in the area. |
|
Normalization |
A relational database design concept which eliminates
duplication of data storage in a database. This is a crucial
element of OLTP systems which can suffer severe performance
penalties if the database is not normalized. |
|
Not Nullable |
A mandatory attribute or column is marked as mandatory by
making it Not Nullable. Not Nullable indicates that a valid value
must be entered for each occurrence of the attribute or column.
Null values are not allowed. |
|
Null |
A Null indicates the absence of a value. This is the
equivalent of leaving a field empty. Columns marked as "Not
Nullable" or "Not Null" may not have Nulls.
A "blank" or a "space" is not the equivalent
as a null and are handled very differently than a null.
"Blanks" and "spaces" must be absolutely
avoided. |
|
On-Line Analytical Processing (OLAP) |
A Software technology that transforms data into multidimensional
views and that supports multidimensional data interaction, exploration,
and analysis. SAS is an example of OLAP. |
|
On-Line Transaction Process
(OLTP) |
An OLTP database is the database with Read and Write access.
This is where transactions are actually entered, modified, and/or
deleted. Due to performance considerations, read-only requests on
the database may be routed to an Operational Data
Store.
Typically, an OLTP is a "normalized" database. |
|
Operational DataStore (ODS) |
An ODS is a read-only database containing operational data in
support of a specific business need. It is updated on a frequent
basis (weekly, daily, hourly, or even more often) and may
be populated from one or more
OLTP and/or ODS databases. Depending upon its refresh
cycle and usage, the ODS may be normalized
or denormalized. |
|
Operational Reporting |
Standardized, stable, repeatable reports which are scheduled,
that access and manipulate data on parameters which are
predefined. |
|
Optionality |
The minimum number of an entity
instance that are possible at one end of the relationship
for each entity instance at the other end. For example, a dash
line indicates an optional relationship end that is read as
"maybe". A solid line indicates a mandatory relationship
end that is read as "must be". |
|
Oracle Replication |
Build data replication using Oracle generated snapshot tables
and snapshot logs. |
|
Primary Key |
While primarily referring to tables, Primary Keys can also
pertain to entities. A Primary Key is the mandatory column or
columns used to enforce the uniqueness of rows in a table. This is
normally the most frequent means by which rows are accessed.
Please note, however, that a column which is part of a Primary Key
may not contain null values! |
|
Process Model |
Visual illustration representing organizational units, which
consist of departments or groups within a business, responsible
for a specific business activity. It is strongly suggested that
the process model be used during analysis. |
|
Purge |
To systematically and permanently remove old and unneeded data.
The term purge is stronger than delete. It is often possible
to regain deleted objects by undeleting them, but purged objects
are gone forever. |
|
Relationship |
A named, significant association between two entities. Each end of the
relationship shows the degree of how the
entities are related and the optionality. |
|
Relational Database |
This terms refers to a database in which data is stored in
multiple tables. These tables then "relate" to one
another to make up the entire database. Queries can be run to
"join" these related tables together. |
|
Security |
Refers to techniques for ensuring that data stored in a computer
cannot be read or compromised. Protection provided to
prevent unauthorized or accidental access/manipulation of a
database. |
|
Snapshot Tables |
A point in time copy of table data originating from one or more
master tables. |
|
Strategy |
Is a synonym for plan, which
is defined as a scheme, program, or method worked out beforehand
for the accomplishment of an objective. The Strategy will
tell you how to do it, the guidelines and/or techniques
to use. An example is the naming
standards developed for the open systems environment. |
|
Table |
A tabular view of data used to hold one or more columns of
data. It is often the implementation of an entity. |
|
Trigger |
A stored procedure associated with a table that is automatically
executed on one or more specified events affecting the table. |
|
Unique Key |
1. Defines the attributes and relationships that uniquely identify
the entity. 2. A column or columns which contain unique values
for the rows of a table. A column in a Unique Key may contain
a null. Therefore, a Unique Key defined for an entity
may not make a suitable Primary Key for
a table. |
