BCF and the Zachman Framework (Complete Enterprise Architecture)

1,581 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,581
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
81
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

BCF and the Zachman Framework (Complete Enterprise Architecture)

  1. 1. 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 dmwelsh@microsoft.com UNITED NATIONS CENTRE FOR TRADE FACILITATION AND ELECTRONIC BUSINESS Under the auspices of United Nations Economic Commission for Europe
  2. 2. 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 UN/CEFACT
  3. 3. Business Alignment in a Collaboration Business Domain Model Business Operations Model Organization A e-Business Organization B Business Operations Collaboration Stack Business Operations Model Alignment Interface Model Alignment Interface Business Goal Alignment Business Process Alignment Business Information Alignment Business Security Infrastructure Business Processes Processes Message Infrastructure Information Flow Requirements UN/CEFACT
  4. 4. Organizational views in a collaboration Stakeholder Business Model Activity Deliverable Focus Management Goal alignment Business agreements & Business commitment metrics and collaboration specification Operations Process Business operation and Business collaboration alignment interaction processes protocol specification Analysts, Information Business object State management, Developers alignment state messaging Systems Integrator, Security Partner authentication Collaboration role and Network Admin. infrastructure and authorization digital signature Application Integrator Messaging Component interaction eBusiness infrastructure sequence diagrams implementation framework
  5. 5. TM ENTERPRISE ARCHITECTURE - A FRAMEWORK DATA What FUNCTION How NETWORK Where PEOPLE Who TIME When MOTIVATION Why SCOPE List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat to the Business Business Performs the Business Operates Important to the Business to the Business SCOPE (CONTEXTUAL) (CONTEXTUAL) Planner ENTITY = Class of Function = Class of Node = Major Business People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Planner Business Thing Business Process Location Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Logistics Network e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan ENTERPRISE ENTERPRISE MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event End = Business Objective Owner Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. "Application Architecture" e.g. "Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture" Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Designer Reln = Data Relationship Cycle = Processing Cycle Designer I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. "System Design" e.g. "System Architecture" e.g. Presentation Architecture e.g. Control Structure e.g. Rule Design TECHNOLOGY TECHNOLOGY MODEL CONSTRAINED (PHYSICAL) MODEL (PHYSICAL) Node = Hardware/System Time = Execute Builder Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People = User End = Condition Reln = Pointer/Key/etc. I/O = Screen/Device Formats Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action e.g. Data Definition e.g. "Program" e.g. "Network Architecture" e.g. Security Architecture e.g. Timing Definition e.g. Rule Specification DETAILED DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF- (OUT-OF CONTEXT) CONTEXT) Sub- Sub- Contractor Ent = Field Proc.= Language Stmt Node = Addresses People = Identity Time = Interrupt End = Sub-condition Reln = Address I/O = Control Block Link = Protocols Work = Job Cycle = Machine Cycle Means = Step Contractor FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE Copyright - John A. Zachman, Zachman Internatio Zachman Institute for Framework Advancement - (810) 231-0531
  6. 6. UN/CEFACT BCF highlighted • BCF covers the business aspects of Business Open - edi Reference Transactions (BOV) Model • Business Operational Comply Business centric and technology View with neutral BOV RELATED • To achieve this the BCF uses a Business aspects of Business transactions Covered by STANDARDS set of architectures, patterns and business semantics • BCF remains precise enough Viewed as to enable legally binding Inter-related business transactions • BCF is a framework that allows Functional Service View Comply with for the transformation of business processes into Information Covered FSV RELATED technology aspects of STANDARDS information definitions; without Business transactions by the loss of business semantics (meaning) or computational integrity. UN/CEFACT
  7. 7. UN/CEFACT BCF Architectural Structure BDV BRV BTV BSV UML IFV Transformation Meta Model Syntax & Rules Semantics Defined Used According By To Business Domain View Business Industry Domain Experts Ontology Business Processes Reification Business Process View Business Requirements View Economic Businesspersons Logical View Ontology Reification Patterns Business Transaction/Service View Business Transaction Business Analysts & Developers Ontology UN/CEFACT
  8. 8. 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) UN/CEFACT
  9. 9. Technology Specific Implementation
  10. 10. 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 UN/CEFACT
  11. 11. 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 UN/CEFACT
  12. 12. UN/CEFACT SIMPLE, TRANSPARENT AND EFFECTIVE PROCESSES FOR GLOBAL BUSINESS http://www.unbcf.org

×