The Zachman Framework of Enterprise Architecture The Zachman Framework is an Enterprise Architecture framework for enterprise architecture, which provides a formal and highly structured way of viewing and defining an enterprise. It consists of a two dimensional classification matrix based on the intersection of six communication questions (What, Where, When, Why, Who and How) with six levels of reification, successively transforming the abstract ideas on the Scope level into concrete instantiations of those ideas at the Operations level.The Zachman Framework is a schema for organizing architectural artefacts (in other words, design documents, specifications, and models) that takes into account both whom the artefact targets (for example, business owner and builder) and what particular issue (for example, data and functionality) is being addressed.The Zachman Framework is not a methodology in that it does not imply any specific method or process for collecting, managing, or using the information that it describes.The Framework is named after its creator John Zachman, who first developed the concept in the 1980s at IBM. It has been updated several times since.Enterprise Architecture frameworkenterprise architectureviewingreificationschemamethodologyJohn ZachmanIBM Reference: Zachman Framework, From Wikipedia, the free encyclopedia, e-Gov Frameworks & Models

This framework is explained as, for example: a framework to organize and analyze data, a framework for enterprise architecture. a classification system, or classification scheme a matrix, often in a 6x6 matrix format a two-dimensional model or an analytic model. a two-dimensional schema, used to organize the detailed representations of the enterprise. The Zachman Framework summarizes a collection of perspectives involved in enterprise architecture. These perspectives are represented in a two-dimensional matrix that defines along the rows the type of stakeholders and with the columns the aspects of the architecture. The framework does not define a methodology for an architectureperspectives stakeholders Reference: Zachman Framework, From Wikipedia, the free encyclopedia,

Focus of Columns In summary, each perspective focuses attention on the same fundamental questions, then answers those questions from that viewpoint, creating different descriptive representations (i.e., models), which translate from higher to lower perspectives. The basic model for the focus (or product abstraction) remains constant. The basic model of each column is uniquely defined, yet related across and down the matrix.In addition, the six categories of enterprise architecture components, and the underlying interrogatives that they answer, form the columns of the Zachman Framework and these are: Contextual The data description — What The function description — How The Network description — Where The people description — Who The time description — When The motivation description — Why Physical (Why) Rules Specification – expressed in a formal language; consists of rule name and structured logic to specify and test rule state (How) Process Function Specification – expressed in a technology specific language, hierarchical process elements are related by process calls (What) Data Entity Specification – expressed in a technology specific format; each entity is defined by name, description, and attributes; shows relationships (Who) Role Specification – expresses roles performing work and workflow components at the work product detailed specification level (Where) Location Specification – expresses the physical infrastructure components and their connections (When) Event Specification – expresses transformations of event states of interest to the enterprise Reference: Zachman Framework, From Wikipedia, the free encyclopedia,

Conceptual (Why) Goal Relationship Model – identifies hierarchy of goals that support primary goals (How) Process Model – provides process descriptions, input processes, output processesProcess Model (What) Entity Relationship Model – identifies and describes the organizational materials and their relationshipsEntity Relationship Model (Who) Organizational Unit & Role Relationship Model – identifies enterprise roles and units and the relationships between them (Where) Locations Model – identifies enterprise locations and the relationships between them (When) Event Model – identifies and describes events and cycles related by time Logical (Why) Rules Diagram – identifies and describes rules that apply constraints to processes and entities without regard to physical or technical implementation (How) Process Diagram – identifies and describes process transitions expressed as verb- noun phrases without regard to physical or technical implementationProcess Diagram (What) Data Model Diagram – identifies and describes entities and their relationships without regard to physical or technical implementationData Model Diagram (Who) Role Relationship Diagram – identifies and describes roles and their relations to other roles by types of deliverables without regard to physical or technical implementation (Where) Locations Diagram – identifies and describes locations used to access, manipulate, and transfer entities and processes without regard to physical or technical implementation (When) Event Diagram – identifies and describes events related to each other in sequence, cycles occur within and between events, without regard to physical or technical implementationEvent Diagram Reference: Zachman Framework, From Wikipedia, the free encyclopedia,

e-Government UK Example Reference: government+portals&source=web&cd=3&cad=rja&ved=0CEEQFjAC&url=http%3A%2F%2Fwww.governments- online.org%2Fdocuments%2FUK_Leiden.ppt&ei=-GRRUfbmB8eDOMDNgTg&usg=AFQjCNFwZiQpa9SY68g6GNJ_6SxYcdbFZQ These slides are the part of above reference

Government portal e-Government: components Citizens and businesses Central government information Local government information Access devices Government gateway Intermediaries Interoperability E-business Access GSI

How to Access Citizens and businesses Central government information Local government information GSI Access devices IntermediariesGovernment portal Government gateway Interoperability E-business Access

Type & devices to use services Direct –call centres, DTV, WAP, PC –in person with web-supported staff Indirect –kiosks, UK online centres, communities Content adapted to channel

Government portal e-Business sector/area Citizens and businesses Central government information Local government information GSI Access devices Intermediaries Government gateway Interoperability E-business Access

UK online centres UK online for business UK online Citizen Portal

UK online for business Builds on existing Information Society Initiative Expert, impartial, jargon-free advice –Online –Phone: dedicated helpline –Face-to-face: UK online business advisors in 100 local centres of Small Business Service –Major awareness campaigns: e.g. E-Commerce Awards Scheme

UK online citizen portal Single point of entry to government information and services, 24 hours, 365 days. Services that match the way people live and work Initial site organised around 4 “life episodes” –having a baby - going away –moving house - dealing with crime

www. ukonline.gov.uk

Measuring progress Six monthly progress reports Originally based on key dealings –high volume or high value –567 million transactions Now based on services –PSA and SDA service delivery commitments –457 services E-business strategies

Services available now NHS Direct Online Patent and trademark database Income tax self-assessment Foreign Office advice for travellers

e-Business Citizens and businesses Central government information Local government information GSI Access devices IntermediariesGovernment portal Government gateway Interoperability E-business Access

Intermediaries Intermediaries are already providing access to government information and services

Change of address – multiple intermediaries Citizen Ihavemoved.comSimplyMovePost Office Tax Social Security Driving licence Other services

Strategy processes – towards 2005 Planning for uncertainty –minimising activity is not minimising risk Looking beyond the government monopoly –delivery channels –service providers Separating information from delivery Identifying customers Iteration Embedding e-strategy is strategy

Strategy outcomes Innovation, not automation Design for customers, not producers Diversity of service providers Managing multiple channels e-government is government

e-world There is no ‘new economy’. There is one economy, all of it being transformed by information technology. What is happening is no dot com fad which will come and go – it is a profound economic revolution. Tony Blair 11 September 2000