Zachman Framework Row 2 : The Owner Perspective

1. CS 6899 Zachman FrameworkRow 2 : The Owner Perspective By: Viral Rathod AmanGoyal

2. Organization Enterprise Architecture. History of Enterprise Architecture Overview of Zachman Framework The Owner’s Perspective (Row 2) Security in Owner’s Perspective. Criticism of Zachman Framework Other Framework / Approaches.

3. 1. Enterprise Architecture What is Enterprise? What is Enterprise Architecture? Why to use an Enterprise Architecture? What are currently available solutions? WebSphere SAP – ERP Oracle Enterprise Manager An Example Business of a hypothetical car manufacturing company.

4. 1. Enterprise Architecture Market Research Company Most basic Work Flow Diagram for Car Manufacturing. Cars

5. 1. Enterprise Architecture Car Manufacturing company Design Regulation Check HR Finance Testing Manufacturing for Testing Marketing Manufacturing Sales

6. 2. History of Enterprise Architecture • 1980-1990 • 1990-2000 • 2000-2010 • A framework for information systems architecture,' John Zachman article in IBM Systems Journal. • CapgeminiIntegrated Architecture Framework (IAF) • DoD Technical Architecture Framework for Information Management (TAFIM) • Federal CIO Council introduces Federal Enterprise Architecture Framework (FEAF) • TOGAF 7.0 Technical Edition • Zachman 2003 • DoDAF 1.0 • TOGAF 8.0 EE • FEA mostly complete • TOGAF 9 • DoDAF 2.0 Development of various Enterprise Architecture:

7. 2. History of Enterprise Architecture Zackman 1987 TAFIM 1994 Relationships between various Enterprise Architecture: EAP 1992 TOGAF 1995 TISAF 1997 FEAF 1999 C4ISR 1996 DODAF 2003 TEAF 2000

8. 3. Overview of Zachman Framework Classification schema. Tabular tool / matrix. Provides Rational for decisions made. Clear understanding of what is happening. Clear understanding of why is happening. Problem solving kit. What is Zachman Framework?

9. 3. Overview of Zachman Framework Any complex problem involving multiple individual components. E.g. Flight Reservation System. E.g. Building a rail road. E.g. Building Empire State Building. What problems does it solve?

10. 3. Overview of Zachman Framework

11. 3. Overview of Zachman Framework • Data/What: Business goals, objectives and performance measures related to each function . • It mostly comprises of the important things with respect to customer and product • What data are needed for the car manufacturing??? Row 1: The Planner Perspective

12. 3. Overview of Zachman Framework • Function/How: High-level business functions • In this cell we mostly concentrate on the all the aspects of the activity to achieve the goal. • Ex: How to meet the market needs for the car??? • How to provide quality car??? Row 1: The Planner Perspective

13. 3. Overview of Zachman Framework • Network/Where : The locations related to each function. • Ex: Head office, Manufacturing Units, Dealer Locations • Where should be Head office of my Car Company ??? Row 1: The Planner Perspective

14. 3. Overview of Zachman Framework • People/Who: Stakeholders related to each function • Ex: Roles & Responsibilities in the Process. • Who should be appointed for the particular designation??? Row 1: The Planner Perspective

15. 3. Overview of Zachman Framework • Time/When : Cycles and events related to each function • Ex: External events, Process execution. • When should company brings car in the market??? Row 1: The Planner Perspective

16. 3. Overview of Zachman Framework • Motivation/Why: Business goals, objectives and performance measures related to each function • Ex: Company Core Values, Mission Statement, Strategic Goals • Why company is producing car??? Row 1: The Planner Perspective

17. 3. Overview of Zachman Framework • Data/What: Business data • Ex: Inputs & Outputs for each functioning Unit. • What security level should be provided to different data??? Row 2: The Owner Perspective

18. 3. Overview of Zachman Framework • Function/How: Business Process • One of the most important block in the Zachman Framework Architecture. • Ex: Use Cases are used to meet the requirements Row 2: The Owner Perspective

19. 3. Overview of Zachman Framework • Network/Where: Locations related to each process • Ex: Communication may be through email, mail, fax, VoIP • Where should we provide high level of security in the network??? Row 2: The Owner Perspective

20. 3. Overview of Zachman Framework • People/Who: Roles and responsibilities in each process • At this stage we are not concerned about this row. Row 2: The Owner Perspective

21. 3. Overview of Zachman Framework • Time/ When: Events for each process and sequencing of integration and process improvements. • Owner will go through the life cycle of the product i.e. Corporate calendar • Planner will propose various proposals . Row 2: The Owner Perspective

22. 3. Overview of Zachman Framework • Motivation/Why:Policies, procedures and standards for each process . • Ex: We already have collected a set of company policies Row 2: The Owner Perspective

23. 3. Overview of Zachman Framework • Data /What:Data models of data and data relationships underlying information • The data received from the owner is now verified by the designer. • The designer may schedule data backup at this stage. Row 3: The Designer Perspective

24. 3. Overview of Zachman Framework • Function/How: Information systems and their relationships • Ex: The designer defines the functions of different modules of the enterprise. • The designer checks the process for access control, recovery control . Row 3: The Designer Perspective

25. 3. Overview of Zachman Framework • Network/Where: Distributed system architecture for locations • Ex: The designer now designs the network and depending on the security of the data provides security end to end or link to link or both. Row 3: The Designer Perspective

26. 3. Overview of Zachman Framework • People/Who: Access privileges constrained by roles and responsibilities • Ex: Role are assigned to different users based on their skillset. • A hierarchy is built for better result. • The end product of every employer is decided. Row 3: The Designer Perspective

27. 3. Overview of Zachman Framework • Time/When : Events and their triggered responses constrained by business events and their responses • Ex: Designersdefines the timely events of the enterprise and the up gradation of product to be done on timely basis. Row 3: The Designer Perspective

28. 3. Overview of Zachman Framework • Motivation/Why: Policies, standards and procedures associated with a business rule model • Ex: The designer defines the rules based on the jurisdiction. Row 3: The Designer Perspective

29. 3. Overview of Zachman Framework • Data/What: DBMS type requirements constrained by logical data models • Ex: Requirement are expressed in technology format. • The main goal of this cell is to make sure that the data is available in proper format i.e. secured for various technologies. Row 4: The Builder Perspective

30. 3. Overview of Zachman Framework • Function/How :Specifications of applications that operate on particular technology platforms • Ex:The builder decides what technology to be used for the particular process and its counter measures. • This cell also checks how to provide security??? Row 4: The Builder Perspective

31. 3. Overview of Zachman Framework • Network/Where: Specification of network devices and their relationships within physical boundaries • Ex: This cell decides which hardware to use for networking and where they should be installed. Row 4: The Builder Perspective

32. 3. Overview of Zachman Framework • People/Who: Specification of access privileges to specific platforms and technologies . • Ex: What access control should be provided to different people for different technology?? • Also the workflow is decided . Row 4: The Builder Perspective

33. 3. Overview of Zachman Framework • Time/When: Specification of triggers to respond to system events on specific platforms and technologies • This stage decides when to trigger which process. • Ex: When to make a back up?? • When to release a particular data for a particular process??? Row 4: The Builder Perspective

34. 3. Overview of Zachman Framework • Motivation/Why: Business rules constrained by information systems standards • Ex: This cell deals with the constrained due to the limitation of resources and technology. Row 4: The Builder Perspective

35. 3. Overview of Zachman Framework • Data/What: Data definitions constrained by physical data models • Ex: Row 5: The Sub-Contractor Perspective

36. 3. Overview of Zachman Framework • Function/How: Programs coded to operate on specific technology platforms • Ex: Row 5: The Sub-Contractor Perspective

37. 3. Overview of Zachman Framework • Network/Where: Network devices configured to conform to node specifications • Ex: Row 5: The Sub-Contractor Perspective

38. 3. Overview of Zachman Framework • People/Who:Access privileges coded to control access to specific platforms and technologies • Ex: Row 5: The Sub-Contractor Perspective

39. 3. Overview of Zachman Framework • Time/When: Timing definitions coded to sequence activities on specific platforms and technologies • Ex: Row 5: The Sub-Contractor Perspective

40. 3. Overview of Zachman Framework • Motivation/Why: Business rules constrained by specific technology standards . • Ex: Row 5: The Sub-Contractor Perspective

41. 4. The Owner’s Perspective (Row 2) Who is Owner? What is Owner’s Perspective? Business Process Business Model Entities & Relationships The Complete facts about business & processes.

42. 4. The Owner’s Perspective (Row 2) Owner’s Problems in Enterprises. Business Process Internal & External Entities Analyzing changes in the business processes. Business Entities Adding Removing Merging

43. 4. The Owner’s Perspective (Row 2) How does this model solve these problems? Holistic Objective Complete Understanding Revisiting the Car Company.

44. 4. The Owner’s Perspective (Row 2)

45. 4. The Owner’s Perspective (Row 2)

46. 4. The Owner’s Perspective (Row 2)

47. 4. The Owner’s Perspective (Row 2)

48. 4. The Owner’s Perspective (Row 2)

49. 4. The Owner’s Perspective (Row 2)

50. 4. The Owner’s Perspective (Row 2) What is important in business. Classification of Data: Highly Sensitive Ex: Financial Data / Future Strategies Very few people have access (Access control & Authorization) Secrecy (Strict Confidentiality) Validity (Integrity & Availability) Sensitive Ex: Operational Information Comparatively large group knows (Access Control & Authorization) Secrecy (Confidentiality) Validity (Integrity & Availability)