ENTERPRISE ARCHITECURE. Fattore abilitante la Digital Trasformation

Transcription

1 ENTERPRISE ARCHITECURE Fattore abilitante la Digital Trasformation

2 Il relatore Daniele Di Lazzaro Laurea in Scienze dell Informazione Università Pisa 1977 Master in Business Administration IMD Lausanne 1996 Master in Public Sector HRMS Luiss Roma 1999 Membro del Club Dirigenti Tecnologie dell Innovazione Volontario e Certificatore di Bilancio dell AIDO Attore teatrale professionista Socio Club Alpino Italiano daniele.dilazzaro@triopen.it

3 Agenda Enterprise Architecture Definition & Goals Building Enterprise Architecture Business Architecture Application Architecture Data Architecture Technology Architecture

4 Enterprise Architecture - definitions Enterprise Space: the final frontier. These are the voyages of the star ship Enterprise. Its five-year mission: to explore strange new worlds, to seek out new life and new civilizations, to boldly go where no man has gone before. (Star Trek, quotes) Origin: late Middle English: from Old French, 'something undertaken', feminine past participle (used as a noun) of entreprendre, based on Latin prendere, prehendere 'to take (OED) An undertaking, especially one of some scope, complication, and risk (thefreedictionary.com) A business organisation (thefreedictionary.com)

5 Enterprise Architecture - definitions Architecture The art or practice of designing and constructing buildings (OED) The complex or carefully designed structure of something (OED) The conceptual structure and logical organization of a computer or computer-based system (OED) Winchester Mystery House From the blank piece of paper to the last nail in the wall

6 What is an Enterprise Architecture? A structured design to ensure alignment between the business and IT strategies Without EA Quick build Difficult to scale Difficult to apply security With EA Design for scale and maintain Secure architecture for growth

7 What is an Enterprise Architecture? Inefficient IT Complex and Delay Response Productive IT Cloud, Big Data, Social, Mobile

8 Types of Architectures

9 Key Benefits from Enterprise Architecture

10 Enterprise Architecture Maturity Model

11 Why do we need Enterprise Architecture - (EA)?

12 Why do we need Enterprise Architecture - (EA)? IT Silos make inefficient to scale the business Human tasks Interaction Information Sharing require ad hoc solutions. No Holistic approach to Audit, Compliance or ISO certification. IT Bottleneck slow down business-driven waves. What-if & impact analysis is quite impossible.

13 Enterprise Architecture - Why do we need it? Originally (reactive): System complexity Organisations were spending more and more money building IT systems; and Poor business alignment Organisations were finding it more and more difficult to keep those increasingly expensive IT systems aligned with business need Even More Cost, Even Less Value Today (proactive, too): Fragmented to Integrated optimise across the enterprise the often fragmented legacy of processes (both manual and automated), into an integrated environment that is responsive to change and supportive of the delivery of the business strategy IT and business success effective management and exploitation of information through IT is a key factor to business success, and an indispensable means to achieving competitive advantage Achieving the right balance between IT efficiency and business innovation

14 Enterprise Architecture The scope Understanding the knows and don t knows of the Enterprise that it needs to know to survive and to succeed:... there are known knowns; there are things we know that we know. There are known unknowns; that is to say, there are things that we now know we don't know. But there are also unknown unknowns there are things we do not know we don't know. (United States Secretary of Defense, Donald Rumsfeld, 2002) Έτσι, δεν γνωρίζω (Greek philosopher, Socrates, 420 b.c.) Complex Problems; Simple Solutions Everything should be made as simple as possible, but no simpler than that (attributed to Einstein)

15 Enterprise Architecture Road map the ladder more like a semiotic snake to me Human Information Functions VALUE PRODUCING The Real World? SOCIAL W ORLD beliefs, expectations, commitments, contracts, law, culture,... PRAGMATICS intentions, communication, conversations, negotiations,... SEMANTICS meanings, propositions, validity, truth, signification, denotations,... SYNTACTICS formal structure, language, logic, data, records, deduction, software, files,... EMPIRICS patterns, variety, noise, entropy, channel capacity, redundancy, efficiency, codes,... PHYSICAL W ORLD signals, traces, physical dimensions, hardware, component density, speed, economics The Computer World Enterprise Architecture The Technology Platform COST IMPOSING

16 Agenda Enterprise Architecture Definition & Goals Building Enterprise Architecture Business Architecture Application Architecture Data Architecture Technology Architecture

17 There are many of related standards/guidelines

18 Digital Transformation Reference Model

19 Architecture Principles (1/2) N Name Statement 1 Primacy of These principles of information management apply to all organizations within the enterprise. Principles 2 Maximize Benefit to Information management decisions are made to provide maximum benefit to the enterprise as a whole. the Enterprise 3 Information Management is All organizations in the enterprise participate in information management decisions needed to accomplish business objectives. Everybody's Business 4 Business Continuity Enterprise operations are maintained in spite of system interruptions. 5 Common Use Applications Development of applications used across the enterprise is preferred over the development of similar or duplicative applications which are only provided to a particular organization. 6 Compliance with Enterprise information management processes comply with all relevant laws, policies, and regulations. Law 7 IT Responsibility The IT organization is responsible for owning and implementing IT processes and infrastructure that enable solutions to meet user defined requirements for functionality, service levels, cost, and delivery timing. 8 Protection of Intellectual Property The enterprise's Intellectual Property (IP) must be protected. This protection must be reflected in the IT architecture, implementation, and governance processes. 9 Data is an Asset Data is an asset that has value to the enterprise and is managed accordingly. 10 Data is Shared Users have access to the data necessary to perform their duties; therefore, data is shared across enterprise functions and organizations.

20 Architecture Principles (2/2) N Name Statement 11 Data is Accessible Data is accessible for users to perform their functions. 12 Data Trustee Each data element has a trustee accountable for data quality. 13 Common Vocabulary and Data Definitions Data is defined consistently throughout the enterprise, and the definitions are understandable and available to all users. 14 Data Security Data is protected from unauthorized use and disclosure. In addition to the traditional aspects of national security classification, this includes, but is not limited to, protection of pre-decisional, sensitive, source selection-sensitive, and proprietary information. 15 Technology Independence Applications are independent of specific technology choices and therefore can operate on a variety of technology platforms. 16 Ease-of-Use Applications are easy to use. The underlying technology is transparent to users, so they can concentrate on tasks at hand. 17 Requirements- Only in response to business needs are changes to applications and technology made. Based Change 18 Responsive Change Changes to the enterprise information environment are implemented in a timely manner. Management 19 Control Technical Diversity Technological diversity is controlled to minimize the non-trivial cost of maintaining expertise in and connectivity between multiple processing environments. 20 Interoperability Software and hardware should conform to defined standards that promote interoperability for data, applications, and technology

21 Zachman Framework In the 1980s Zachman developed a structure or framework for defining and capturing an architecture This framework provides for 6 perspectives or windows from which to view the enterprise

22 TOGAF Architecture Development Method (1/4) The ADM method consists of eight main phases. As preliminary work, the enterprise architecture framework and architecture principles are fixed for the effort. In the following, a short description of the phases. 1) Architecture vision is the analysis phase of EA project. The project is organized; the scope and domain requirements and constraints are stated. Business scenarios can be used for this. 2) In the Business architecture phase, the current baseline architecture is stated, target architecture is designed and a gap analysis between the two takes place. 3) Information systems architecture consists of the parts Data and Applications. For Data architecture, the types and sources of data needed in the enterprise are defined and a data model is created. A gap analysis is conducted and data model is compared with the business architecture. As to the applications, the applications needed to meet the specified business requirements and data model are turned into an applications architecture and are checked back with the business architecture.

23 TOGAF Architecture Development Method (2/4) 4) For Technology architecture, the previous phases deliver inputs. In this phase, a baseline architecture is stated, and the target technology architecture is designed. 5) Opportunities and solutions is the evaluation phase, where the solutions are selected. 6) Migration planning is the point for checking dependencies in the environment and preparing for implementation of the target architecture. 7) Implementation and Governance is about the administration of implementation and deployment phase of the development project. 8) Architecture change management is the maintenance phase. A new baseline is created and changes in business environment are monitored as well as new technology opportunities.

24 TOGAF Architecture Development Method (3/4)

25 TOGAF Architecture Development Method (4/4)

26 Anyway Incremental vs. Iterative

27 The Enterprise Reference Model (1/2) Help make repeated viewing of conformity between Business and IT in the cursus of work, both at at high and low Level for: 1. Help make your IT from a repeated. Business picture 2. See the new service. and the related Business process relationship 3. Referring the Business Line with varying levels of IT Strategic.View 4. Analyze details in next phase

28 The Enterprise Reference Model (2/2)

29 Key Deliverables from Enterprise Architecture

30 Business Architecture & IT Architecture