Building and Employing Enterprise Architectures

The Enterprise Architecture work products of the Knowledge Worker Framework (12 cells) represent the essential components necessary to construct such architectures. From the shown diagram Accomplished appropriately about 40% of all IT Business Information Systems can be avoided. The key set of work products are missions, organizations, functions, database objects, business information systems and business events.

The objective of mission development is the identification and description of a hierarchically organized collection of textual documents that represent the essence of the enterprise. The determination as to whether a mission statement belongs is based on whether the enterprise is complete without mission statement. A typical mission document ranges from 25 to 50 pages.

The objective of organization development is the identification and description of the organizations involved in the enterprise. Just the names and descriptions, not what the organizations do. A typical organization document ranges from 10 to 15 pages.

The objective of functions development is the identification and description of the "human" processes that accomplish the essential processes of the enterprise. A typical function document ranges from 30 to 50 pages.

The next step is the association of the missions with organizations. Once associated the functions that represent the the processes accomplished by the mission-organization pairs. The overall collection then represents the set of all critical functions (i.e., processes) performed by organizations and enterprise missions are accomplished.

The next step is the identification of all relevant business information systems that exist or planned to exist that the enterprise uses to accomplish its overall mission through the functions performed by organizations. Each business information system requires between 5 to 10 pages of description, data and process specifications. Collectively the overall document is a few hundred pages.

A final step is identify the existing or planned databases needed by the business information systems in support of the enterprise's missions. During the identification and analysis of the databases the database objects are identified and described. Examples include for example, customers, products, salesmen, inventory, and products.

Once these databases are identified and interrelated, the overall architecture of the enterprise is able to be presented. It is within this architecture that existing and needed changes are able to be known and set within their proper context.



Short Papers

  • Database Objects Brief Overview
  • Database Objects Introduction

TDAN Papers

  • Database Objects: The Foundation Stones of Enterprise Database
  • Great News, The Relational Model is Dead
  • SQL 1999 and its Impact on Database Application Development

For Sales and Corporate: 1-301-249-1142 [email protected]

Whitemarsh Information Systems Corporation

 Bowie, Maryland 20716 USA

Copyright 1981 - 2020 Whitemarsh Information Systems Corporation
Proprietary Data, All rights Reserved