T

Information Management's 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

Tactical data warehouse development
The process of selecting a portion of an enterprise and implementing a data warehouse. The process includes constructing a data model for the area, determining the data warehouse architecture, constructing the physical model, and populating the warehouse database. It also includes creating or buying the applications to access the data warehouse, prototyping the tactical warehouses (access definitions, views, etc.) and incorporating end-user feedback.


TANSTAAFL
There Ain't No Such Thing As A Free Lunch! In developing a data warehouse, there is work involved, and there is no "free lunch."


Target database
The database in which data will be loaded or inserted.


Technical architecture
One of the four layers of the information systems architecture. The technical architecture defines and describes the interfaces, parameters and protocols used by the product and systems architecture.


Telnet
A terminal emulation program for TCP/IP networks such as the Internet.


Time variant
A time-variant system has explicit dependence on time, does not have an impulse response in the normal sense and is not stationary. A time-variant value refers to cryptography, when a value changes with each transaction or with each message value.


Tool encyclopedias
Encyclopedias, repositories or dictionaries used by application development tools. The non-definable "repository" used by a tool.


Total cost of ownership (TCO)
The cost to own a product throughout its life.*


Transaction activity data
Transaction activity data represents the transactions that operational systems are designed to automate.


Transaction audit data
Transaction audit data tracks the progress of an individual transaction, such as Web logs and database logs.


Transactional system
An information system designed to store and record day-to-day business information, often structured around events, business processes or business activities. These systems are optimized for storing large volumes of data, but not for analyzing that data.*


Transformers
Rules applied to change data.


Triggering data
Data that selects and loads data on a scheduled basis