The ability to increase volumes of data and numbers of users to the data warehouse solution. This is a critical capability for the data warehouse architecture and technical architecture.

An information model implemented in a database. A schema may be a logical schema, which will define, for example, tables, columns, and constraints, but which may not include any optimization. It may be a physical schema that includes optimization, for example, table clustering.

The boundaries of a project expressed in some combination of geography, organization, applications and/or business functions.

A change to project scope. A scope change requires an adjustment to the project work plan, and nearly always impacts project cost, schedule or quality.

The common phenomenon where additional requirements are added after a project has started without reconsidering the resourcing or timescale of the project. Scope creep arises from the misapprehension that such small additions will not affect the project schedule.

A workshop, usually attended by the project sponsor and developers, with the objective of defining the boundaries of the scope for an intended project and prioritizing requirements within the scope.

A person, group, or business unit that has a share or an interest in a particular activity or set of activities.

A set of rules for ensuring quality. Usually standards are defined for products, deliverables or deliverable components and processes.

The ANSI internationally accepted standard for relational database systems, covering not only query but also data definition, manipulation, security, and some aspects of referential and entity integrity.

An area of major interest or importance to the enterprise. It is centered on a major resource, product, or activity. The subject areas provide reference information when conducting detailed requirements gathering.