Zachman Framework Applied to Administrative Computing Services
The Zachman Framework has gained wide acceptance in the industry. Federal Government IT of the United States, in response to the Clinger-Cohen Act, must demonstrate architectural planning
for the budgeting process. The States have organized architectural bodies that govern and
control IT architecture in conformance with the Clinger-Cohen Act. Much of their work
utilizes to the Zachman framework.
The SNAP Portal initiative (corresponding to column 4 of
the Zachman Framework), is an effort
to achieve many goals, however, it defines a technology, not a model, for achieving enterprise
wide architecture. Zachman framework is a model that describes how to select or justify this technology investment and trace back to specific goals.
The framework can help AdCom achieve some of the goals in a
more organized and sustainable manner, across technology shifts.
Some points worth noting about this framework also include:
Initiatives are the result of multiple functions that are common across projects or
applications (SNAP is an example). Initiatives identify Architecture Gaps and can
provide the "Transitional Roadmap" to desired state.
Alignment of IT with Business: Row 6 (Operational Systems and Applications) must reflect Rows 1(Scope) and most critically, Row 2 (Business Model)
Integration of Systems occurs across columns: Especially across Column 1 (Data/Information), 2 (Processes and Functions) and 6 (Motivation - Goals and strategy).
Why Zachman?
No product or consulting as with Meta or Gartner - it is product neutral.
Used heavily by Ford, Volkswagon, Firestone, GM, DOD, US Treasury, State CIOs.
Comprehensive, working model that aligns IT with business by looking at
pieces that fit into the whole of an enterprise puzzle.
Simple, logical model. Not technical.
It is a language that helps people think about complex
concepts and communicate
in non-technical terminology.
It is a Planning Tool.
It is a Problem Solving tool that enables abstraction and
simplification without neglecting the complexity of the Enterprise as a whole.
Rows are views defined by and for a specific audience. Integration occurs between columns. Primitive data definition (defining everything ONLY once in each Zachman cell) is the foundation of the framework.
AdCom will need to focus on the high-level modeling of each row to
achieve one of the most important goals: IT Alignment with A&BS Business Unit goals.
Consider documenting how current projects (internal and external) align with NBA goals,
A&BS goals, and AdCom Goals. All projects should be traceable to
functions which trace back to goals. Task: check how closely our Row
6 (working systems) are aligned with Row 1( Scope) and Row 2 (Business Models).
This analysis will indicate "gaps".
Glossary:
Goal:
Ends or Targets that an organization is dedicated to achieving.
Function:
Activities performed by the enterprise to achieve its goals.
Framework Applied to AdCom - excercise from Zachman Workshop, Nov 13-15 in Scottsdale, Arizona
