A thing of significance about which information is recorded; a component at the most useful, basic level.

Element Type

Any element held in the repository is classified as a particular type. Examples of element type are entity, attribute, program module, process, table, diagram, text, softbox. Occurrences or instances of these are called elements.


Extract, transform, and load (ETL). The collection if processes that are used to prepare data for another purpose. This is used for Data Warehouse where the extract process connects and collects data from the appropriate underlying source systems.

The Transformation processes perform cleansing, manipulation, and reorganization of the data in preparation for its intended use.

Finally, the load process put the data into the data structures where it is held for delivery to downstream systems which can be either internal to the organization or external to any third party organizations.

ETL processes is not only used for Data Warehouse projects but it can also be used for moving and manipulating data for a variety of other purposes with in the organization.

End-User Layer

The user interface and layout of the multidimensional structures designed for the data access tools. This includes the customization of the tools for the users.


A group of departments, divisions, or companies which make up an entire business.

Enterprise Support Systems

The set of all computer-based systems, documents, and procedures used in support of business enterprise operations.

Enterprise Technical Architecture (ETA)

A series of rules, guidelines, and principles used by an organization to direct the process of acquiring, building, modifying, delivering, and integrating Information Technology resources throughout the enterprise. These resources can include equipment, software, business processors, protocols, standards, methodologies, IT organizational structures and more.


A thing of significance, whether real or imagined, about which information eeds to be known or held. It is implemented in a database as one or more tables.

Entity Relationship Diagram (ERD)

A diagram that pictorially represents entities, the relationships between them and the attributes used to describe them.

Entity Relationship Model

A type of data model. Part of the business model that consists of many Entity Relationship Diagrams.


An occurrence in a business’s environment to which that business must respond.

Executive Information System (EIS)

A reporting application targeted for use by executives. Usually such applications have extremely user-friendly, graphical interfaces with a small local data store derived from connection to a data warehouse. It is often used synonymously with decision support system.


The ability to add new components, technology, and increments to the data warehouse solution. This is a critical capability for the data warehouse architecture and technical architecture.

External Data Source

A system or data file provided by an organization external to the client. This includes parent companies or subsidiaries, alliances, partners, and data brokers.


Extended Binary-Coded Decimal Interchange Code. A coded character set of 256, eight-bit characters commonly used in mainframe systems.


Executive Information Systems. Applications specially designed for senior executives to perform information look-up and trend analysis.

ERP Systems

Enterprise Resource Planning Systems. Large packaged applications offered by leading vendors, such as SAP and People soft. ERP applications are built with proprietary software and they usually cover the entire range of a company’s business.


Enterprise network using web technologies for collaboration of internal users and selected external business partners.


Extract, Transform and Move. Another acronym used in place of ETL.


Extract, Transform and Transfer. Another acronym used in place of ETL.

Evolutionary Development

A software development life cycle model wherein development is carried out in an evolutionary manner. Initially, only a small subset or a module’s requirements are provided and those will be implemented and then some more features are added and so on. This method is also known as incremental building. A good model to be followed for complex Data warehouse requirements.