WHERETO FROM ZACHMAN Architecture Practitioners conference

Transcription

1 WHERETO FROM ZACHMAN Practitioners conference ARCHITECTURE-AFRAMEWORK TM April 2004 DATA What FUNCTION How NETWORK Where PEOPLE Who When MOTIVATION Why TIME List of Things Important to the Business List of Processes the Business Performs List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat the Business Operates Important to the Business to the Business ENTITY=Clasof Business Thing Function = Class of Business Process Node = Major Business Location Ends/Means=Major Bus. Goal/ People = Major Organizations Time = Major Business Event Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics System e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle End = Business Objective Means = Business Strategy e.g. LogicalData Model e.g. Application e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model Node = I/S Function Ent = Data Entity Proc.= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Reln = Data Relationship I/O = User Views Link = Line Characteristics Work = Deliverable Cycle = Processing Cycle Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology e.g. Presentation e.g. Control Structure e.g. Rule Design Node = Hardware/System Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People=User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action e.g. Data Definition e.g. Program e.g. Network e.g. Security e.g. Timing Definition e.g. Rule Specification (OUT-OF- Builder (OUT-OF Contractor Ent = Field Reln = Address Proc.= Language Stmt I/O = ControlBlock Node = Addresses Link = Protocols People = Identity Work=Job Time = Interupt End = condition Cycle = Machine Cycle Means=Step Contractor e.g. DATA e.g. FUNCTION e.g.network e.g.organization e.g. SCHEDULE e.g.strategy John A. Zachman, Zachman International (810) VISH VISWANATHAN Managing Consultant- CCANDC Solutions Regional Partner- The Open Group (Australia/ New Zealand /ASEAN) Vice Chair-Asia/Pacific, Forum

2 CURRENT STATE OF PLAY OF EA IN AUSTRALASIA ROI Pressures On CIO CIO champions EA As the solution Appoints Enterprise Architect Requires EA to be developed ASAP Enterprise Architect looks for help Consultants Web based information Seminars

3 TYPICAL EA PROJECT START UP PROCESS Investigation Phase Reports Initial Implementation Full Implementation In-house investigation Take over implementation (in source) Use in-house resources OR Employ first tier consultants (outsource) Select Framework, methodology & tools Assistance from specialist consultants QA Review /audit By specialist consultants Get training & hand holding Assistance from specialist consultants

4 A WELL KNOWN HIGH LEVEL FRAMEWORK. ZACHMAN FRAMEWORK De-facto standard for classifying the Enterprise architectural artifacts Logical structure for analysing and presenting artifacts from a management perspective Draws parallels from the well understood Engineering or Construction paradigm Widely recognised as a management tool for checking architectural completeness and maturity No processes for implementation Difficult to implement in total No ready examples or checklists Extent of coverage of the cells unclear

5 A DISCIPLINED PROCESS TOGAF Focuses on implementation cycle (ADM) and processes Has a foundation architecture as a part of Enterprise continuum Rich in the technical architecture area Resource base provides a lot of reference materials Supported by a set of certification processes Being positioned as the benchmark for EA best practice

6 and AN EASY-TO-USE TOOL. ARCHITECT Certified formally as TOGAF support tool / Ongoing commitment for future versions Comprehensive support for Zachman Framework Can be customised and extended to facilitate a hybrid approach Has a variety of built-in EA related models and artifacts Easy to learn

7 List of Things Important to the Business e.g. Semantic Model Ent = Business Entity Reln = Business Relationship e.g. Logical Data Model Ent = Data Entity Reln = Data Relationship e.g. Physical Data Model Ent = Segment/Table/etc. Reln = Pointer/Key/etc. e.g. Data Definition Ent = Field Reln = Address e.g. DATA List of Processes the Business Performs Function = Class of Business Process e.g. Business Process Model Proc. = Business Process I/O = Business Resources e.g.application Proc.= Application Function I/O = User Views e.g. System Design Proc.= Computer Function I/O = Data Elements/Sets e.g. Program Proc.= Language Stmt I/O = Control Block e.g. FUNCTION List of Locations in which the Business Operates Node = Major Business Location e.g. Business Logistics System Node = Business Location Link = Business Linkage e.g. Distributed System Node = I/S Function e.g. Technology Node = Hardware/System e.g. Network Node = Addresses Link = Protocols e.g. NETWORK List of Organizations Important to the Business People = Major Organizations e.g. Work Flow Model People = Organization Unit Work = Work Product e.g. Human Interface People = Role Work = Deliverable e.g. Presentation People = User Work = Screen Format e.g. Security People = Identity Work = Job e.g. ORGANIZATION List of Events Significant to the Business Time = Major Business Event e.g. Master Schedule Time = Business Event Cycle = Business Cycle e.g.processingstructure e.g. Control Structure Time = Execute Cycle = Component Cycle e.g. Timing Definition Time = Interrupt Cycle = Machine Cycle e.g. SCHEDULE List of Business Goals/Strat e.g. Business Plan End = Business Objective Means = Business Strategy e.g., Business Rule Model e.g. Rule Design End = Condition Means = Action e.g. Rule Specification End = condition Means = Step e.g. STRATEGY Practical Enterprise implementation using a hybrid approach TOGAF8 P A B C H D G E F VALUE ADDS Step by Step process Templates / checklists Customised features Training & professional services ZACHMAN FRAMEWORK Builder ARCHITECTURE - A FRAMEWORK DATA What FUNCTION How NETWORK Where PEOPLE Who When MOTIVATION Why ENTITY = Class of Business Thing (Processor, Storage, etc) Link = Line Characteristics Software Link = Line Specifications John A. Zachman, Zachman International (810) TIME Time = System Event Cycle = Processing Cycle TM Ends/Means=Major Bus. Goal/ Critical Success Factor End = Structural Assertion Means =Action Assertion Builder (OUT-OF (OUT-OF- Contractor Contractor

8 Architectural Development Planning Principles Rules Guidelines Models Building Blocks Standards Business Application Data Technology EA Version 1.0 EA Version 2.0 EA Version 3.0 EA Version 4.0 8

9 The Enterprise Shell Governance Principles /Rules/Guidelines Building Blocks Information Base Standards Information Base S Principles /Rules/Guidelines S Principles /Rules/Guidelines S Principles /Rules/Guidelines TRM Business Application( Systems) Information (Data) Technology (Infrastructure) 9

10 SIMPLIFIED COVERAGE ARCHITECTURE OF ALL FOUR - A FRAMEWORK EA LAYERS TM DATA What FUNCTION How NETWORK Where PEOPLE Who When MOTIVATION Why TIME List of Things Important to the Business List of Processes the Business Performs List of Locations in which the Business Operates List of Organizations Important to the Business List of Events Significant to the Business List of Business Goals/Strat ENTITY = Class of Business Thing Function = Class of Business Process Node = Major Business Location People = Major Organizations Time = Major Business Event Ends/Means=Major Bus. Goal/ Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics System e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan Ent = Business Entity Reln = Business Relationship Proc. = Business Process I/O = Business Resources Node = Business Location Link = Business Linkage People = Organization Unit Work = Work Product Time = Business Event Cycle = Business Cycle End = Business Objective Means = Business Strategy e.g. Logical Data Model e.g. Application e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model Ent = Data Entity Reln = Data Relationship Proc.= Application Function I/O = User Views Node = I/S Function (Processor, Storage, etc) Link = Line Characteristics People = Role Work = Deliverable Time = System Event Cycle = Processing Cycle End = Structural Assertion Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology e.g. Presentation e.g. Control Structure e.g. Rule Design Builder (OUT-OF- Ent = Segment/Table/etc. Reln = Pointer/Key/etc. e.g. Data Definition Proc.= Computer Function I/O = Data Elements/Sets e.g. Program Node = Hardware/System Software Link = Line Specifications e.g. Network People = User Work = Screen Format e.g. Security Time = Execute Cycle = Component Cycle e.g. Timing Definition End = Condition Means = Action e.g. Rule Specification Builder (OUT-OF Contractor Ent = Field Reln = Address e.g. DATA Proc.= Language Stmt I/O = Control Block e.g. FUNCTION Node = Addresses Link = Protocols e.g. NETWORK John A. Zachman, Zachman International (810) People = Identity Work = Job e.g. ORGANIZATION Business Time = Interrupt Cycle = Machine Cycle e.g. SCHEDULE End = condition Means = Step e.g. STRATEGY Application Contractor Planning/Vision Data Technology

11 EA deliverables Planning Checklists/ templates Customised Change processes Customised Governance processes Framework and principles P Change maintenance Implementation& Governance G 11 H Touch points to Existing PMO processes Migration planning F EA services (ADM plus) EA services (ADM plus) EA workshops Architectural Vision A Requirements Management Opportunities & solutions E SENIOR EXECUTIVES ARCHITECTS PROJECT MANAGERS EA USERS Business B EA Objects Information Systems Technology D Collaborative Creation processes C

12 List of Things Important to the Business e.g. Semantic Model Ent = Business Entity Reln = Business Relationship e.g. Logical Data Model Ent = Data Entity Reln = Data Relationship e.g. Physical Data Model Ent = Segment/Table/etc. Reln = Pointer/Key/etc. e.g. Data Definition Ent = Field Reln = Address e.g. DATA List of Processes the Business Performs Function = Class of Business Process e.g. Business Process Model Proc. = Business Process I/O = Business Resources e.g.application Proc.= Application Function I/O = User Views e.g. System Design Proc.= Computer Function I/O = Data Elements/Sets e.g. Program Proc.= Language Stmt I/O = Control Block e.g. FUNCTION List of Locations in which the Business Operates Node = Major Business Location e.g. Business Logistics System Node = Business Location Link = Business Linkage e.g. Distributed System Node = I/S Function e.g. Technology Node = Hardware/System e.g. Network Node = Addresses Link = Protocols e.g. NETWORK List of Organizations Important to the Business People = Major Organizations e.g. Work Flow Model People = Organization Unit Work = Work Product e.g. Human Interface People = Role Work = Deliverable e.g. Presentation People = User Work = Screen Format e.g. Security People = Identity Work = Job e.g. ORGANIZATION List of Events Significant to the Business Time = Major Business Event e.g. Master Schedule Time = Business Event Cycle = Business Cycle e.g.processingstructure e.g. Control Structure Time = Execute Cycle = Component Cycle e.g. Timing Definition Time = Interrupt Cycle = Machine Cycle e.g. SCHEDULE List of Business Goals/Strat e.g. Business Plan End = Business Objective Means = Business Strategy e.g., Business Rule Model e.g. Rule Design End = Condition Means = Action e.g. Rule Specification End = condition Means = Step e.g. STRATEGY PRACTICAL EA DEVELOPMENT PROCESS SPECIFIC ARCHITECTURE ZACHMAN FRAMEWORK ARCHITECTURE - A FRAMEWORK TM DATA What FUNCTION How NETWORK Where PEOPLE Who When MOTIVATION Why TIME ENTITY = Class of Business Thing Ends/Means=Major Bus. Goal/ Critical Success Factor P TOGAF RESOURCES -Foundation -TRM /SIB -Checklists -Templates -Case studies Etc., H G A F B E C D Builder (Processor, Storage, etc) Link = Line Characteristics Software Link = Line Specifications Time = System Event Cycle = Processing Cycle End = Structural Assertion Means =Action Assertion John A. Zachman, Zachman International (810) Steps towards Enterprise 1. TOGAF Phase P plus: Creation of the EA shell & initial management agreement 2. Snapshot study of current architecture & Concerns analysis to highlight the need for EA Builder (OUT-OF (OUT-OF- Contractor Contractor 3. Customise ADM / Customise Zachman cell checklists 4. Training of Architects and other key stake holders 5. TOGAF Phase A 6. TOGAF phases B/C/D: Complete Version 1 of Reference Models 7. Identify,Create and store Building Blocks ( ABB/SBB) 8. Refer to relevant Zachman cells for completeness at the end of each phase 9. TOGAF ADM Phases E/F: Provide touch points to existing processes 10. Complete processes for phases G/H

13 SAMPLE EA Business Customer contact Service request Service delivery Service fulfillment Service pricing Account receivable Service request Service billing collection Customer interface Service Billing A/c receivable Application Customer history Pricing Finance Service Standard Data Customer Service Finance Technology UIS DMS DIS DTS System process Manual process

14 ARCHITECTURE BUILDING BLOCKS & SOLUTION BUILDING BLOCKS ABB1 SBB1 VIEW 1 ABB2 SBB2 ABB3 SBB3

15 SAMPLE ARCHITECTURE BUILDING BLOCK FORMAT (Technology domain) Name Header Body Tail Links Domain SME Principles /Rules/ Guidelines Strategy Implementation plan Interim Retiring (Legacy) Current V/L Date of creation / change Change history Links to SBB (s) and any other detailed information / models

16 SAMPLE SOLUTION BUILDING BLOCK FORMAT (Technology domain) Name Header Body Solution Domain SME Rules/ Guidelines/standards Rationale for inclusion Implementation plan Tail Links V/L Date of creation / change Change history Links to any other detailed information / technical data

17 VALUE ADDED SERVICES FROM CCAND C SOLUTIONS Training : One day TOGAF appreciation course (group / customised) 4/5 days TOGAF practical implementation course (group/ customised) Other Special training / personalised training services ( general): Linking into vertical architectures Linking into ITIL/OMG/Zachman / other architectures and processes Linking into existing / strategic vendor architectures Modeling / tools: Tool (s) selection / Tolls embedding ABB / SBB structures & rules Data modeling BBIB repository systems Processes: Process maps for creation/ governance/change management Process maps to suit outsourcing contracts / SLA s Processes & content of RFIs / RFPs for selecting tools, methodologies or service providers Resourcing : Short term / permanent resources for implementation

18 WHERETO FROM ZACHMAN Practitioners conference ARCHITECTURE-AFRAMEWORK TM April 2004 DATA What FUNCTION How NETWORK Where PEOPLE Who When MOTIVATION Why TIME List of Things Important to the Business List of Processes the Business Performs List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat the Business Operates Important to the Business to the Business ENTITY=Clasof Business Thing Function = Class of Business Process Node = Major Business Location Ends/Means=Major Bus. Goal/ People = Major Organizations Time = Major Business Event Critical Success Factor e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics System e.g. Work Flow Model e.g. Master Schedule e.g. Business Plan Ent = Business Entity Proc. = Business Process Node = Business Location People = Organization Unit Time = Business Event Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle End = Business Objective Means = Business Strategy e.g. LogicalData Model e.g. Application e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model Node = I/S Function Ent = Data Entity Proc.= Application Function (Processor, Storage, etc) People = Role Time = System Event End = Structural Assertion Reln = Data Relationship I/O = User Views Link = Line Characteristics Work = Deliverable Cycle = Processing Cycle Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology e.g. Presentation e.g. Control Structure e.g. Rule Design Builder John A. Zachman, Zachman International (810) Node = Addresses People = Identity Time = Interupt End = condition Link = Protocols Work=Job Cycle = Machine Cycle Means=Step e.g.network Contact: e.g.organization e.g. SCHEDULE e.g.strategy Node = Hardware/System Builder Ent = Segment/Table/etc. Proc.= Computer Function Software People=User Time = Execute End = Condition Reln = Pointer/Key/etc. I/O = Data Elements/Sets Link = Line Specifications Work = Screen Format Cycle = Component Cycle Means = Action e.g. Data Definition e.g. Program e.g. Network e.g. Security e.g. Timing Definition e.g. Rule Specification (OUT-OF- Contractor Ent = Field Proc.= Language Stmt Reln = Address I/O = ControlBlock e.g. DATA e.g. FUNCTION (OUT-OF Contractor VISH VISWANATHAN Vish.viswanathan@opengroup.org vish@primus.com.au /