MarkDiehl.com
Health Information Architecture, Data Modeling, and Enterprise Architecture Planning
FEAF Level IV Matrix
The FEAF Level IV identifies and categorizes the models that describe the business, data, applications, and technology architectures in a matrix derived from the Zachman Framework. the FEAF Level IV Matrix incorporates the five perspective views and three architectural artifacts from the Zachman Framework. The architectural artifacts used (data, application, and technology) form the columns and are the Level IV design architectures - the Zachman Framework who, when, and why columns have not been incorporated into the FEAF. The perspective views (planner, owner, designer, builder, and subcontractor) form the rows. The FEAF Level IV artifacts populate the cells of this matrix.
The following table describes the cells of the FEAF Level IV Matrix.
| Perspectives | Data Architecture | Application Architecture | Technology Architecture |
|
Planner (Scope) |
Business Objects Provides a list of things, or assets in which the enterprise is interested.
|
Business Processes Capture the processes, activities, and functions performed by the enterprise or its components. |
Business Locations Documents the locations at which the organization performs specific processes. |
|
Owner (Enterprise) |
Semantic Model
Description of the actual things of interest to the organization
|
Business Process Model
Provides a concise description of those things an organization performs, present or future, independent of implementation
|
Business Logistics
Identifies the locations of enterprise components along with their interconnections (i.e., voice, data, fax; physical means like postal, courier service; and transportation modes.). The logistics model identifies all of the types of facilities at the organizational nodes like branches, headquarters, warehouses, etc. |
|
Designer (Systems) |
Logical Data Model Provides a logical representation of the objects about which the enterprise records information.
|
Application Architecture Describes the information processing components that supports the business processes, including the human-machine boundaries, processing controls, enablers, and inputs and outputs. |
System Deployment Architecture
Presents a logical model of the business logistics system, depicting the types of systems components and controls at the nodes and lines of communication. |
|
Builder (Technology) |
Physical Data Model Presents the data model tailored for the technology specific to the implementation database management system.
|
System Design Starting from a high-level the system design presents the abstract structure of the system, e.g. system layers and components. At lower levels, this presents the design details of the logical system, or application architecture. |
Technology Architecture Models the physical environment for the enterprise technology, identifying and locating the actual hardware and software components.
|
|
Subcontractor (Detailed Specification) |
Data Definition Model An optimized physical data model, presented in SQL code and ready for implementation.
|
Application Software Consists of the actual program code for the applications.
|
Network Architecture Identifies the specific definition of the node addresses and the line identification. bridges, routers, firewalls, bandwidth, etc. |
The following table describes the artifacts that populate the FEAF Level IV Matrix cells.
| Perspectives | Data Architecture | Application Architecture | Technology Architecture |
|
Planner (Scope) |
Business Objects List of products and services, business objects, and conceptual data entities. |
Business Processes List of business processes, functions and activities.
|
Business locations Listing of organizational details, wire diagrams, etc.
|
|
Owner (Enterprise) |
Semantic Model Conceptual Data Model
|
Business Process Model Activity Model, Process Flows, Process Decomposition, Flowcharts, Functional and Process Hierarchy, Process-entity matrix, etc. |
Business Logistics Business concept diagram, and optionally an organization-function matrix.
|
|
Designer (Systems) |
Logical Data Model Expanded conceptual data model as a keyed, fully attributed, normalized entity relationship diagram.
|
Application Architecture Business and Application Use Case Diagrams; Data flow diagram, system context diagram, etc.
|
System Deployment Architecture A System Area Map, or a UML Component Diagram, identifying processors, operating systems, storage devices, DBMS's, peripherals/drivers, etc. |
|
Builder (Technology) |
Physical Data Model Physical ER diagram, or if an OO implementation, a UML Class Diagram.
|
System Design System Structure Charts, Use Case Diagrams, flowcharts, etc. UML artifacts (class diagram, state chart, activity diagram, etc.) with methods reflected. |
Technology Architecture A Network Concept Diagram or a A UML deployment Diagram identifying system components abd nodes, including operating systems and middleware. |
|
Subcontractor (Detailed Specification) |
Data Definition Model DBMS Schema or if an OO implementation an ODL script. |
Application Software Application code.
|
Network Architecture Network Concept Diagram and UML Deployment Diagram |
The As-Is system components may be reverse engineered to provide the basis for many of these models to describe the existing architecture.
All content copyright © 2002, 2003 by Mark Diehl. All rights reserved.