|
OLTP
|
|
Databases support OLTP systems. Online transaction processing systems (OLTP) are traditional automated data processing systems where the focus is on the recording of transactions produced by business applications. This section describes the architecture and methodology used to produce traditional, stove-pipe application database and then provides a methodology to integrate those stove-pipes into the enterprise data architecture. In the application database architecture, an application database supports a single, automated business function or activity. It contains both functionally dependent and functionally independent data, stored in related data sets called tables, using a relational database architecture. It is designed using a methodology called Normalization and is documented using a tool called a Logical Data Model. In the enterprise data architecture, an application database contains only functionally dependant data. Functionally dependant data are created by or used by a single business function or activity. These data only have meaning in the context of the business function or activity. The enterprise database supports many, ideally all, business functions and activities. It is a collection of data, stored in related data sets called tables, using a relational database architecture. The enterprise database is logically and/or physically linked to many application databases. Each application database is connected to the enterprise database via database links or software. An enterprise database contains functionally independent data. Functionally independent data exist in nature and are used by many business functions or activities. These data have meaning outside the context of the business function or activity. They are designed using a methodology called Abstraction and are documented using a Logical Data Model. Enterprise and application databases are constructed from the nine components and eight patterns contained in this website. A coupled enterprise and application database are referred to as the enterprise/application database pair.
|