The Building Blocks-Components of EA part 1- Information and Strategy
1. Zachman Framework
Presented as matrix of Rows and Columns representing domain of interest and level of abstraction.
2. Framework-Domain of Interest
Columns
-Data/ Information
-Function/ Process
-Network
-People
-Time
-Motivation/ Strategy
Framework Rules
Rule 1: Columns have no order
Rule 2: Each column has a simple, basic model
Rule 3: Basic model of each column is unique
Rule 4: Each row represents a distinct view
Rule 5: Each cell is unique
Rule 6: Combining the cells in one row forms a complete description from that view
3. Framework - Level of Abstraction
Business Managers - Strategic
Row 1 - Contextual: External Requirements and Drivers; Business Function Modeling
Row 2 - Conceptual: Business Process Models
Designer & Developers - Operational
Row 3 - Logical: Logical Models; Requirements Definition
Row 4 - Physical: Physical design; Solution Definition and Development
Row 5 - As Built: Constructed Enterprise; Deployment
Row 6 - Functioning Enterprise: Operating Environment; Functioning Enterprise Evaluatoin
4. Zachman Framework
Row 1 - Scope/Planner's View
- Motivation/why
Business goals, objectives and performance (External requirements and drivers)
Measures related to each function (Business Function Modeling)
- Function/How
High-level business functions
- Data/ What
High-level data classes related to each function
- People/ Who
Stakeholders related to each function
- Network/ Where
VA locations related to each function
- Time/ When
Cycles and events related to each function
Row 2 - Enterprise Model/ Owner's View -Business Process Models; Business Function Allocation;
- Motivation/ Why Elimination of Function Overlap and Ambiguity
Policies, procedures and standards for each
process
- Function/ How
Business processes
- Data/ What
Business data
- People/ Who
Roles and responsibilities in each process
- Network/ Where
Locations related to each process
- Time/ When
Events for each process and sequencing of integration and process improvements
Row 3 - System Model/ Designer's View - Logical Models; Project Management; Requirements Definition
- Motivation/ Why
VA policies, standards and procedures
associated with a business rule model
- Function/ How
Logical representation of information systems and their relationships
- Data/ What
Logical data models of data and data relationships underlying VA information
- People/ Who
Logical representation of access privileges constrained by roles and responsibilities
- Network/ Where
Logical representation of the distributed system architecture for VA information
- Time/ When
Logical events and their triggered responses constrained by business events and responses
Row 4 - Technology Model/ Builders' View- Physical Models, Technology Management, Solutions Definition and - Motivation/ Why Development
Business rules constrained by information systems standards
- Function/ How
Specifications of applications that operate on particular technology platforms
- Data/ What
Database management system (DBMS) type requirements constrained by logical data models
- People/ Who
Specification of access privileges to specific platforms and technologies
- Network/ Where
Specification of network devices and their relationships within physical boundaries
- Time/ When
Specification of triggers to respond to system events on specific platforms and technologies
Row 5 - As Built/ Integrator's View- As Built; Configuration Management; Deployment
- Motivation/ Why
Business rules constrained by specific technology standards
- Function/ How
Programs coded to operate on specific technology platforms
- Data/ What
Data definitions constrained by physical data models
- People/ Who
Access privileges coded to control access to specific platforms and technologies
- Network/ Where
Network devices configured to conform to node specifications
- Time/ When
Timing definitions coded to sequence activities on specific platforms and technologies
Row 6 - Functioning Enterprise/ User's View- functioning Enterprise; Operations Management; Continuous
- Motivation/ Why Improvement; Evaluation
Operating characteristics of specific technologies constrained by standards
- Function/ How
Functioning computer instructions
- Data/ What
Data values stored in actual database
- People/ Who
Personnel and key stakeholders working within their roles and responsibilities
- Network/ Where
Sending and receiving massages
- Time/ When
Timing definitions operating to sequence activities
5. Summary
The Zachman Framework
- Is a commonly encountered enterprise architecture tool
- Provide the repository of enterprise artefacts that describe the business
- Is structured as a two dimensional hierarchy high contextual to functional levels of abstraction
