Top Banner
UNITED NATIONS CENTRE FOR TRADE FACILITATION AND ELECTRONIC BUSINESS Under the auspices of United Nations Economic Commission for Europe UN/CEFACT BCF and the Zachman Framework (Complete Enterprise Architecture) Dave Welsh Chair UN/CEFACT TMG Business Process Work Group UN/CEFACT Standards Liaison Rapporteur [email protected]
12

BCF and the Zachman Framework (Complete Enterprise Architecture)

Nov 01, 2014

Download

Technology

Aamir97

 
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: BCF and the Zachman Framework (Complete Enterprise Architecture)

UNITED NATIONS CENTRE FOR TRADE FACILITATION AND ELECTRONIC BUSINESSUnder the auspices of United Nations Economic Commission for Europe

UN/CEFACT

BCF and the Zachman Framework(Complete Enterprise Architecture)

Dave WelshChair UN/CEFACT TMG Business Process Work Group

UN/CEFACT Standards Liaison [email protected]

Page 2: BCF and the Zachman Framework (Complete Enterprise Architecture)

UN/CEFACT

Agenda

• Appreciating the complexity of e-Business Collaborations

• Brief overview of the Zachman Framework for Enterprise Architectures

• Very brief summary of the BCF architectural structure

• The BCF architecture mapped to the Zachman Framework

• Conclusions

• How the BCF is comprehensive for enterprises

• The business value of the BCF

Page 3: BCF and the Zachman Framework (Complete Enterprise Architecture)

UN/CEFACT

Business Alignment in a Collaboration

Business Domain Model

Organization ABusiness Operations

Model

Organization BBusiness Operations

Model

Business Operations Model

e-Business Collaboration Stack

Business Process Alignment

Business Information Alignment

Business Goal Alignment

Security Infrastructure

Message Infrastructure

Business Processes

Business Processes

Align

me

nt In

terface

Align

me

nt In

terface

RequirementsInformation Flow

Page 4: BCF and the Zachman Framework (Complete Enterprise Architecture)

Application Integrator

Systems Integrator,Network Admin.

Analysts,Developers

Operations

Management

Collaboration role anddigital signature

Partner authenticationand authorization

Securityinfrastructure

eBusinessimplementationframework

Component interactionsequence diagrams

Messaginginfrastructure

State management,messaging

Business objectstate

Informationalignment

Business collaborationprotocol specification

Business operation andinteraction processes

Processalignment

Business commitmentand collaborationspecification

Business agreements &metrics

Goal alignment

Stakeholder DeliverableModel ActivityBusinessFocus

Organizational views in a collaboration

Page 5: BCF and the Zachman Framework (Complete Enterprise Architecture)

e.g. DATA

ENTERPRISE ARCHITECTURE - A FRAMEWORK

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = FieldReln = Address

e.g. Physical Data Model

Ent = Segment/Table/etc.Reln = Pointer/Key/etc.

e.g. Logical Data Model

Ent = Data EntityReln = Data Relationship

e.g. Semantic Model

Ent = Business EntityReln = Business Relationship

List of Things Importantto the Business

ENTITY = Class ofBusiness Thing

List of Processes theBusiness Performs

Function = Class ofBusiness Process

e.g. "Application Architecture"

I/O = User ViewsProc .= Application Function

e.g. "System Design"

I/O = Screen/Device FormatsProc.= Computer Function

e.g. "Program"

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business ProcessI/O = Business Resources

List of Locations in which the Business Operates

Node = Major BusinessLocation

e.g. Logistics Network

Node = Business LocationLink = Business Linkage

e.g. "Distributed System

Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics

e.g. "System Architecture"

Node = Hardware/SystemSoftware

Link = Line Specificationse.g. "Network Architecture"

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture"

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYCONSTRAINED

MODEL(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

e.g. Rule Specification

End = Sub-conditionMeans = Step

e.g. Rule Design

End = ConditionMeans = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals/Strat

Ends/Means=Major Bus. Goal/Critical Success Factor

List of Events Significant

Time = Major Business Event

e.g. Processing Structure

Cycle = Processing CycleTime = System Event

e.g. Control Structure

Cycle = Component CycleTime = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization UnitWork = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Architecture

People = UserWork = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportant to the Business

What How Where Who When Why

Copyright - John A. Zachman, Zachman International

SCOPE(CONTEXTUAL)

Architecture

e.g. STRATEGY ENTERPRISE

e.g. Business Plan

TM

Zachman Institute for Framework Advancement - (810) 231-0531

Page 6: BCF and the Zachman Framework (Complete Enterprise Architecture)

UN/CEFACT

UN/CEFACT BCF highlighted

• BCF covers the business aspects of Business Transactions (BOV)

• Business centric and technology neutral• To achieve this the BCF uses a

set of architectures, patterns and business semantics

• BCF remains precise enough to enable legally binding business transactions

• BCF is a framework that allows for the transformation of business processes into information definitions; without the loss of business semantics (meaning) or computational integrity.

Open -edi Reference Model

Viewed as

Functional Service View

Information technology aspects of Business transactions

Business Operational View

Business aspects ofBusiness transactions

Covered by

Comply with

Comply with

Covered by

BOV RELATEDSTANDARDS

FSV RELATEDSTANDARDS

Inter-related

Page 7: BCF and the Zachman Framework (Complete Enterprise Architecture)

UN/CEFACT

Meta Model

BDV

IFV

BSVBTVBRV

UML

Business Domain ViewIndustry Domain Experts

Business Transaction/Service ViewBusiness Analysts & Developers

Business Requirements ViewBusinesspersons

Business TransactionOntology

BusinessOntology

EconomicOntology

Reification

Reification

Transformation Rules

Syntax & Semantics

Patterns

Business Processes

Business Process View

Logical View

Defined According

ToUsed By

UN/CEFACT BCF Architectural Structure

Page 8: BCF and the Zachman Framework (Complete Enterprise Architecture)

UN/CEFACT

Framework to Framework mapping(BCF to Zachman)

• As an exercise, to see the completeness of the BCF, we used the Zachman Framework to check the BCF meta model.

• The results can be used to identify which BCF components are used in an enterprise architecture, to those not familiar with the BCF.

• We mapped the structural components of the BCF meta model onto the Zachman Framework, as the BCF would be used when building a new business collaboration.

• The BCF primarily covers the upper 3 rows of the Zachman Framework.

• The BCF’s Business Domain View (BDV) aligns with Row 1 (Context View) of the Zachman Framework

• BCF’s Business Requirements View (BRV) aligns with Row 2 ( Concept View) of the Zachman Framework

• BCF’s Business Transaction View (BTV) and the BCF Business Service View (BSV) both align to Row 3 (Logical View) of the Zachman Framework

• The BCF’s Implementation Framework View (IFV) defines a set of elements needed to specify a target technology, and is aligned to the lower rows of Zachman Framework (Physical layer)

Page 9: BCF and the Zachman Framework (Complete Enterprise Architecture)

Technology Specific Implementation

Page 10: BCF and the Zachman Framework (Complete Enterprise Architecture)

UN/CEFACT

Conclusions(Adopting of Enterprise Architectures)

• Growing adopting of Enterprise Architectures

• Justify budgets

• Promote common processes, interoperability and information sharing

• In the United States, the Clinger-Cohn Act of 1996 mandates Federal Agencies develop and maintain an Enterprise IT architecture

• In Canada, the Treasury Board of Canada uses the BCF and Zachman in developing the Canadian Government Services Reference Model (GSRM)

• Other countries adopting Enterprise Architectures

Page 11: BCF and the Zachman Framework (Complete Enterprise Architecture)

UN/CEFACT

Conclusions(Adopting of Enterprise Architectures)

• To protect investments, as technology continues to evolve, industry and government need to adopt a technology neutral business enterprise architecture.

• The Business Collaboration Framework (BCF)

• When compared to the Zachman Framework, the BCF is a complete architecture

• Builds on more than 12 years of continuing evolution with input from

• UN/CEFACT, ISO, ITU, the Legal and Accounting professions and more

Page 12: BCF and the Zachman Framework (Complete Enterprise Architecture)

UN/CEFACT

SIMPLE, TRANSPARENT AND EFFECTIVE PROCESSESFOR GLOBAL BUSINESS

http://www.unbcf.org