Information Age Architectures Must Be Enterprise Architecture
Abstract
C2 will continue to be plagued by projects that overrun budgets, dissatisfy users, return poor performance, or result in project termination until a critical mass of acquisition professionals understand what John Zachman calls Enterprise Physics. From his investigation of how other professions build complex things he was able to generalize the interaction of all these people into a simple schema. The people fit into a few common roles (planner, owner, designer, builder, and subcontractor). The columns are based on the six primitive interrogatories (who, what, when, where, why, and how). The framework is a powerful mechanism for resolving conflicts during project conception because each cell (role, interrogative pair) is unique. Uniqueness is very important precondition to successful requirements definition and requirements management. Uniqueness allows changes to be made without introducing conflicts that would otherwise arise from the same data variable's data value appearing in multiple locations and possibly holding multiple conflicting values. Uniqueness also allows efficient consistency checks which aid developing a complete set of requirements. These are fundamental relationships between the essential elements of an enterprise and the different organizational roles that are responsible for them. These relationships are not sufficient to guarantee success but if violated the chance for success is dramatically reduced. This paper what characterizes an Information Age architecture and why that architecture must be consistent with John Zachman's Enterprise Architecture Framework.
Document Details
- Document Type
- Technical Report
- Publication Date
- Jun 01, 2004
- Accession Number
- ADA466045
Entities
People
- Thomas H. Augustine
Organizations
- Naval Information Warfare Systems Command