Another term for disparate data because they support legacy systems.

An existing system repository of information and processes. Link Test A test to identify errors in linked modules of an application system. Link testing is an extension of module testing carried out on a number of levels of detail. Examples include, linked modules of a program, linked programs of a functional area or subsystem, and linked subsystems of the complete application system. The link test is usually a white box test.

Evaluational data that are summarized by removing one, or a few, data characteristic from the primary key of the data focus. Lightly summarized data have fine granularity.

A primary key whose uniqueness is limited to a subset of the data occurrences within the scope of the common data architecture.

Implementation process has ended and the solution is put into production.

(1) A network covering a relatively small geographic area (usually not larger than a floor or small building). Compared to WANs, LANs are usually characterized by relatively high data rates. (2) Network permitting transmission and communication between hardware devices, usually in one building or complex.

A complete map of the application instances required to support the applications architecture.

(1) A data model that represents the normalized design of data needed to support an information system. Data are drawn from the common data model and normalized to support the design of a specific information system.
(2) Actual implementation of a conceptual module in a database. It may take multiple logical data models to implement one conceptual data model.

The framework which outlines all of the data warehouse functions and components for the strategic data warehouse. This includes the data classes, relational and multidimensional databases, meta data repository, ETT components, warehouse management, and client and server processes.

What the business community calls a field. Also see physical naming standards.

The task of designing a system to support business needs without making final decisions regarding the physical implementation. The same logical design should be appropriate for many physical implementations using, for instance, different versions of a database management system.

The appearance and behavior of a system facility as perceived by the end user. This includes the data, the layout, and the user interaction through menus, buttons, text editing, and other devices.