1 / 30

Agenda

Agenda . A very first draft on a concrete Extended Enterprise Architecture Framework Frank Goethals – SAP leerstoel 23/04/2003. 1. Overview Classic Zachman Framework 2. Classic Zachman Framework – concrete example 3. Example of an Extended Enterprise process

baeddan-williams
Download Presentation

Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agenda A very first draft on a concrete Extended Enterprise Architecture FrameworkFrank Goethals – SAP leerstoel23/04/2003 • 1. Overview Classic Zachman Framework • 2. Classic Zachman Framework – concrete example • 3. Example of an Extended Enterprise process • 4. Very first draft of an Extended Enterprise Architecture Framework • 5. Why such a framework?/Deliverables PhD A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  2. Basis: The Zachman Framework Basic English Questions Different Persons What How Where Who When Why 1 Contextual 2 Conceptual 3 Logical 4 Physical 5 As Built 6 Functioning Entity Relationship Entity Input Process Output Node Line Node Organization Reporting Organization Event Cycle Event Objective Precedent Objective A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  3. Row 1 – Scope External Requirements and Drivers Business Function Modeling Basis: The Zachman Framework • Row 2 – Enterprise Model Business Process Models • Row 3 – System Model Logical Models Requirements Definition What How Where Who When Why 1 Contextual Contextual • Row 4 – Technology Model Physical Models Solution Definition and Development 2 Conceptual Conceptual 3 Logical Logical • Row 5 – As Built As Built Deployment 4 Physical Physical 5 As Built As Built • Row 6 – Functioning Enterprise Functioning Enterprise Evaluation 6 Functioning Functioning A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  4. Agenda • 1. Overview Classic Zachman Framework • 2. Classic Zachman Framework – concrete example • 3. Example of an Extended Enterprise process • 4. Very first draft of an Extended Enterprise Architecture Framework • 5. Why such a framework? A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  5. Customer Product Producttype Employee Department What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 1Scope/Planner’s View • Data/What High-level data classes related to each function 1 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  6. Sales Production • Network/Where Locations related to each function What How Where Who When Why • People/Who Stakeholders related to each function Contextual Contextual Conceptual Conceptual • Time/When Cycles and events related to each function • Motivation/Why Business goals, objectives and performance measures related to each function Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 1Scope/Planner’s View • Data/What High-level data classes related to each function • Function/How High-level business functions 1 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  7. N Customer 1 Product buys N N 1 contacts Producttype N N N 1 Employee Department 1 What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 2Enterprise Model/Owner’s View • Data/What Business data 2 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  8. Employee Places order Accept/reject Customer Check Credit Customer data Credit not-OK Credit OK Check Stock Product data …. Sales Process • Network/Where Locations related to each process What How Where Who When Why Contextual Contextual • People/Who Roles and responsibilities in each process Conceptual Conceptual Logical Logical • Time/When Events for each process and sequencing of integration and process improvements • Motivation/Why Policies, procedures and standards for each process Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 2Enterprise Model/Owner’s View • Data/What Business data • Function/How Business processes 2 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  9. Customer 1 N Cust-Emp N 1 Employee What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 3System Model/Designer’s View • Data/What Logical data models of data and data relationships underlying information Customer N contacts N Employee 3 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  10. Network/Where Logical representation of the distributed system architecture for locations What How Where Who When Why Contextual Contextual • People/Who Logical representation of access privileges constrained by roles and responsibilities Conceptual Conceptual Logical Logical • Time/When Logical events and their triggered responses constrained by business events and their responses • Motivation/Why Policies, standards and procedures associated with a business rule model Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 3System Model/Designer’s View Employee Places Order Response Customer CheckCredit (Custnr, CustOK) • Data/What Logical data models of data and data relationships underlying information Customer DB IF CustOK • Function/How Logical representation of information systems and their relationships CheckStock (Prodnr, q, StockOK) Product DB 3 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  11. What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 4Technology Model/Builder’s View DB2 Customer, ID= Customernr • Data/What Database management system (DBMS) type requirements constrained by logical data models Employee, ID= Empnr Cust-Emp, ID= Customernr, Empnr 4 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  12. Dell Win 2000 Server Credit Checking (C++) Stock Checking (Visual Basic) • Network/Where Specification of network devices and their relationships within physical boundaries What How Where Who When Why Contextual Contextual • People/Who Specification of access privileges to specific platforms and technologies Conceptual Conceptual Logical Logical • Time/When Specification of triggers to respond to system events on specific platforms and technologies • Motivation/Why Business rules constrained by information systems standards Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 4Technology Model/Builder’s View • Data/What Database management system (DBMS) type requirements constrained by logical data models • Function/How Specifications of applications that operate on particular technology platforms 4 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  13. DBD Name=STDCDBP, Access=HDAM, RMNAME (DLZHDC10,3,100,600) DATASET DD1= STDCBC … What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 5As Built/Subcontractor’s View • Data/What Data definitions constrained by physical data models 5 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  14. Procedure CreditChecking (customernr, Accept); Begin SearchCustomerdata (customernr, limit); if limit > (GetProductPrice(prodnr)*q) then Accept := true else Accept := false;End; • Network/Where Network devices configured to conform to node specifications What How Where Who When Why Contextual Contextual • People/Who Access privileges coded to control access to specific platforms and technologies Conceptual Conceptual Logical Logical • Time/When Timing definitions coded to sequence activities on specific platforms and technologies • Motivation/Why Business rules constrained by specific technology standards Physical Physical As Built As Built Functioning Functioning What How Where Who When Why Zachman Framework – Row 5As Built/Subcontractor’s View • Data/What Data definitions constrained by physical data models • Function/How Programs coded to operate on specific technology platforms 5 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  15. Motivation/Why Operating characteristics of specific technologies constrained by standards What How Where Who When Why Contextual Contextual Conceptual Conceptual Logical Logical Physical Physical Integrated Integrated Functioning Functioning What How Where Who When Why Zachman Framework – Row 6Functioning Enterprise • Data/What Data values stored in actual databases • Function/How Functioning computer instructions • Network/Where Sending and receiving messages • People/Who Personnel and key stakeholders working within their roles and responsibilities • Time/When Timing definitions operating to sequence activities 6 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  16. Agenda • 1. Overview Classic Zachman Framework • 2. Classic Zachman Framework – concrete example • 3. Example of an Extended Enterprise process • 4. Very first draft of an Extended Enterprise Architecture Framework • 5. Why such a framework? A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  17. Company A • Sells to building contractors, do-it-yourself shops,… • - Roof Tiles (dakpannen) - Paving Stones (tegels)- Bricks (bakstenen)- Sand (zand)- Mortar (cement) • To predict their future sales, they could contact a number of architect agencies, but … what is the quality of the data given by these agencies? A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  18. Customer Architect request Check customer profile Make first drafts Check existing drafts Negotiate drafts Update customer profile Check existing drafts Make second version Store material requirements Class 1 Negotiate drafts Update customer profile Make third version Check existing drafts Store material requirements Class 2 Negotiate drafts The Architect’s process: Row2-Column2 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  19. Number of building projects Check customer profile Make first drafts Check existing drafts Check existing drafts Make second version Estimated material requirements Level of trust = 1 Store material requirements Class 1 Make third version Check existing drafts Estimated material requirements Level of trust = 2 Store material requirements Class 2 The Architect’s process: Architect Update customer profile Update customer profile A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  20. The Architect’s process: Company A Architect Process Architect Number of building projects Prediction Process Step 1 Store material requirements Class 1 Estimated material requirements Level of trust = 1 Step 2 Step 3 Step 4 Estimated material requirements Level of trust = 2 Store material requirements Class 2 Step 5 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  21. The Architect’s process: Row?-Column? Public Business Process New project-ID+ projecttype Intermediate Payment Estimated material requirements Level of trust = 1 Estimated material requirements Level of trust = 2 Monthly Payment A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  22. Agenda • 1. Overview Classic Zachman Framework • 2. Classic Zachman Framework – concrete example • 3. Example of an Extended Enterprise process • 4. Very first draft of an Extended Enterprise Architecture Framework • 5. Why such a framework? A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  23. Customer wants one front door to the business Zachman PTX Integrated processes,Gobal data,Location of the PTX, message flows,Contact Persons, … Zachman Company 2 Zachman Company 1 Zachman Company 3 A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  24. Zachman Company 2 Zachman Company 1 Zachman Company 3 Zachman PTX A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  25. Zachman Company 2 Zachman Company 1 Zachman Company 3 Zachman PTX A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  26. A D C B A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  27. Two clearly separated Architecture Descriptions per enterprise ExtendedEnterprise Individual Enterprise A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  28. Agenda • 1. Overview Classic Zachman Framework • 2. Classic Zachman Framework – concrete example • 3. Example of an Extended Enterprise process • 4. Very first draft of an Extended Enterprise Architecture Framework • 5. Why such a framework? A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  29. The concept is universal and is gaining momentum. • They ease the communication, and the working with complex systems. • They can serve as a basis for the third level of integration. WHY this research? • 1. Enterprise Architecture Descriptions are useful. • 2. There has been few academic research on enterprise architecture frameworks. • 3. It interests me… A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

  30. This includes a link to other processes Goal Improve and ease the Extended Enterprise integration exercise Through: 1. an unambiguously defined, well-grounded, easily understandable, integratable architecture model for the Extended Enterprise integration exercise, and 2. a clear, well-grounded, easily understandable method to draw up, maintain, and use the architecture descriptions to their full potential. A very first draft on a concrete Extended Enterprise Architecture Framework - Frank Goethals

More Related