The Open Group South Africa

Transcription

1 The Open Group South Africa Working towards realising Boundaryless Information Flow Stuart Macgregor Certified TOGAF Practitioner

2 Agenda The Open Group - South African TOGAF Review Information Architecture An Architecture of Enterprise Architecture The Open Group Forums and Workgroups Conclusion 2 The Open Group 2008

3 South African Member Review Two day review of TOGAF s next release by South African Members Sasol Letsema Eskom Real IRM University of Pretoria Over 100 change suggestions logged 439 comments were submitted globally ll

4 South African Member Review The face-to-face member review of TOGAF led to great dialogue on EA fundamentals, raised numerous questions What is the generally accepted definition of Enterprise Architecture? How has our thinking evolved since TOGAF 8.1.1? Are we placing sufficient emphasis on the Business value of EA? Have we made adequate progress in raising the level of excellence of TOGAF s coverage of the Business Architecture Domain to a level comparable with that of the other domains? Are we not confusing a repository (physical storing of EA artifacts e.g. models) with the enterprise continuum (a mental framework or thought construct)? To what extent has the new release addressed the TOGAF customer requirement articulated in Paris during 2007? Where is the information architecture domain addressed in TOGAF? Business Architecture (Phase B)?, Information Systems Architecture (Phase C)? Or Phase A F? Are The Open Group s forums and workgroups paying sufficient attention to the Information Architecture Domain given The Open Group s vision of Boundaryless information flow? and change suggestions while enhancing both cross-organisationalorganisational and individual learning.

5 South African Member Review

6 South African Member Review

7 Semantic Interoperability Workgroup Information Architecture! Semantic Interoperability is the ability of two or more computer systems to exchange information and have the meaning of that information accurately and automatically interpreted by the receiving system. The Open Group 2008

8 Essential Problem Where is the wisdom? Lost in the knowledge Where in the knowledge? Lost in the information T.S Elliot Where is the information? Lost in the data Where in the data? Where in the data? Lost in database Joe Celko

9 Relationship between Information and Data Knowledge about objects, etc. Subject of information Information Information Representation of information Interpretation of data Data Data Source: Keith Gordon - DAMA UK (Spring 2008)

10 (Un)intended Consequences The dream behind the Web is of a common information space in which we communicate by sharing information. Its universality is essential: the fact that a hypertext link can point to anything, be it personal, local, or global, be it draft or highly polished. There was a second part of the dream, too, dependent on the Web's being so generally used that it become a realistic mirror of the ways in which we work, play, and socialize. Tim Berners-Lee Feb. 8, 1993 July 25, 1994 Sep. 27, 1999 "Our ability to create information has far outpaced our ability to search, organise, and publish it. Information management - at the individual, organisational, and even societal level - may turn out to be one of the key challenges we face. It is the next stage of literacy. Peter Lyman

11 Human-Centered Information Management Information Architectures Focus on computerized data Emphasize information provision Assume permanence of solutions Assume single meaning of terms Stop when design is done or when system is built Build enterprise-wide structures Assume compliance with policies Control users information environments Human-centered Approaches Focus on broad information types Emphasize information use and sharing Assume transience of solutions Assume multiple meanings of terms Continue until desired behavior is achieved enterprise-wide Build point-specific structures Assume compliance is gained over time through influence Let individuals design their own information environments Source: Thomas H. Davenport Saving IT s Soul: Human-Centered Information Management Harvard Business Review March 1994

12 The Semantic Interoperability Problem * At present, this problem is typically addressed within the services, and by use as far as possible of enterprise-standard and industry-standard vocabularies. In the future, it may be addressed by semantic technology that is incorporated in the infrastructure, which will be a more scalable way to deliver the ideal of Boundaryless Information Flow. * Extract from The Open Group SOA White Paper

13 Information Architecture The Open Group Information Architecture defines from a content perspective how information is related to business and how it must be organized to achieve added value to the business. This works within the context of a business domain on the assumption that the information objects in the architecture are understood in a common semantic context. Journal of the American Society for Information Science & Technology Information architecture has recently emerged an important meta-discipline i concerned with the design, implementation, and maintenance of digital information spaces for human access, navigation, and use...the term has been used for several years to describe the mix of competencies required to produce information resources that enhance human abilities to locate information.

14 Len Fehskens Caveats The graphics that follow are meant to suggest a way to think about Enterprise Architecture; they are not meant to be prescriptive or descriptive models of Enterprise Architecture. The names of things should be intuitive and consistent, but ultimately naming is arbitrary, and there are only so many words available. Any name I choose is likely to feel wrong to someone, but the specific names are less important than the principle suggested by these graphics: A place for everything, and everything in its place The sizes of the graphic elements do not represent anything e s es o t e g ap c e e e ts do ot ep ese t a yt g about their content or relative significance.

15 An Architecture of Enterprise Architecture EA EA: Enterprise Architecture Literally, the architecture of an Enterprise. Not just its IT. Source: Len Fehskens

16 An Architecture of Enterprise Architecture EA EA: Enterprise Architecture EBA EBA: Enterprise Business Architecture There may be many business unit or functional unit architectures that are refinements of or that inherit from the EBA. Scope of concern: Enterprise Nature of concern: Business * Subject to change without notice Source: Len Fehskens Business is used here to mean those things that express and implement the enterprise s aspirations, strategies, values, etc., and that are shared by all architectures that together constitute the EA. *

17 An Architecture of Enterprise Architecture EA EBA EA: EBA: E<tbd>A: Enterprise Architecture Enterprise Business Architecture Enterprise <tbd> Architecture E<tbd1>A There may be many other enterprise-wide architectures that parallel the EBA.... Scope of concern: Enterprise Nature of concern: <tbd> E<tbdn>A There may be many business unit or functional unit architectures that are refinements of or that inherit from each E<tbd>A. Source: Len Fehskens

18 An Architecture of Enterprise Architecture EA EA: Enterprise Architecture EBA EBA: EISA: Enterprise Business Architecture Enterprise Information Systems (EIS) Architecture Scope of concern: Enterprise Nature of concern: Information Systems EISA Systems comprise more than just technology. Source: Len Fehskens

19 An Architecture of Enterprise Architecture EA EA: Enterprise Architecture EBA EBA: EISA: EITA: Enterprise Business Architecture Enterprise IS (EIS) Architecture Enterprise IT (EIT) Architecture EITA EISA Scope of concern: Enterprise Nature of concern: Information Technology Source: Len Fehskens

20 An Architecture of Enterprise Architecture EA EA: Enterprise Architecture EBA EIA EBA: Enterprise Business Architecture EIA: Enterprise Information Architecture Scope of concern: Enterprise Nature of concern: Information EITA EITA: Enterprise IT (EIT) Architecture Source: Len Fehskens

21 An Architecture t of Enterprise Architecture t EA EA: Enterprise Architecture EBA EIA EBA: Enterprise Business Architecture EIA: Enterprise Information Architecture EITA: Enterprise IT (EIT) Architecture EITA EITIA EITIA: EIT Information Architecture (possibly = data architecture?) EITAA EITAA: EIT Application Architecture EITTA: EIT Technology Architecture EITTA Source: Len Fehskens

22 An Architecture t of Enterprise Architecture t EA EBA EITA EITIA EITAA SBA1 SBA2 SBAn SAn: Solution Architecture <n> SBAn: Solution Business Architecture <n> EITTA SA1 SA2 SAn Source: Len Fehskens

23 An Architecture of Enterprise Architecture EA EA: Enterprise Architecture EBA EBA: Enterprise Business Architecture EITA: Enterprise IT (EIT) Architecture EITIA: EIT Information Architecture EITA EITIA EITAA EITAA: EITTA: EIT Application Architecture EIT Technology Architecture EITTA EITSIA EITHIA EITSIA: EITHIA: EIT Software Infrastructure Architecture EIT Hardware Infrastructure Architecture Source: Len Fehskens

24 An Architecture of Enterprise Architecture EA EA: Enterprise Architecture EBA S A EBA: EITA: Enterprise Business Architecture Enterprise IT (EIT) Architecture EITIA: EIT Information Architecture EITA EITIA EITAA EITAA: EITTA: EIT Application Architecture EIT Technology Architecture EITTA EITSIA EITHIA EITSIA: EITHIA: EIT Software Infrastructure Architecture EIT Hardware Infrastructure Architecture SA: Solution Architecture (one of many) Source: Len Fehskens

25 An Architecture t of Enterprise Architecture t EA EA: Enterprise Architecture EBA S A EBA: EITA: Enterprise Business Architecture Enterprise IT (EIT) Architecture EITIA: EIT Information Architecture EITA EITIA EITAA EITAA: EITTA: EIT Application Architecture EIT Technology Architecture TOGAF EITTA EITSIA EITHIA EITSIA: EITHIA: EIT Software Infrastructure Architecture EIT Hardware Infrastructure Architecture SA: Solution Architecture (one of many) Source: Len Fehskens

26 Real IRM s EA Cube EA Continuum Ente erprise Archi itecture Doma ains Business Architecture t Information Architecture Real IRM Solutions Data Architecture Applications Architecture Technology Architecture Products an nd Services People Conte ent Processes Tools Copyright Real IRM Solutions (Pty) Ltd All Rights Reserved

27 Zachman Framework Strategic Scope Model [Contextual] (Planner) Data Function Network People Time Values (What?) (How?) (Where?) (Who?) (When?) (Why?) List of things important to the business List of processes the business performs List of locations in which the business operates List of organisation units or users List of business events/ cycles List of business goals/ strategies Model of the Business [Conceptual] (Owner) Entity Relationship diagram Business process flow diagram Logistics network Organisation Chart Business event/ trigger chart Business plan System Model [Logical] (Designer) Data model Data flow diagram Distributed systems architecture Human Interf ace Architecture State transition dependency diagram Business rules Technology Model [Physical] (Builder) Data design Module structure chart Systems architecture Human technology interface Control flow/ structure diagram Knowledge design Detailed Representations (Sub-contractor) Data design description Program Network architecture Security architecture Timing/ interrupts Rules/ Knowledge definition Functioning System Data Function Communications Users Dependencies/ (User) schedule Rules/Strategy John Zachman

28 TOGAF and Information Architecture

29 Semantic Interoperability Working Group The mission of the Semantic Interoperability Working Group is to enable semantic interoperability onaglobal lscale by fostering the development and take-up of vendor-neutral semantic interoperability standards, best practices, and technologies. Information Architecture Project Semantic and SOA project of SI workgroup Information Architecture for SOA The Information Architecture project deliverable will be able to be used as a TOGAF artifact, and will be appropriate to the development of Service- Oriented Architectures (SOA).

30 Information Architecture Project Enterprise architects Solution architects need: need: A standard Information Reference Model to incorporated in context- specific solution architecture (whether that information be source internally to the enterprise provide conceptual clarity on how enterprise information systems produce, exchange and consume information A detailed and comprehensive Information Reference Architecture that can be used as the basis for the development of Solution Architectures. To understand how the enterprise information lifecycle should be or external) A set of standards and technical guidance on how to implement solution components to produce, exchange and consume information.

31 Ontologies for SOA

32 Essential Problem Where is the wisdom? Lost in the knowledge Where in the knowledge? Lost in the information T.S Elliot Where is the information? Lost in the data Where in the data? Where in the data? Lost in database Joe Celko

33 Acknowledgements Len Fehskens Chris Harding John Zachman Ron Schuldt South African Open Group Members SOA Workgroup Semantic Interoperability Workgroup Architecture Forum Real IRM Information Architecture Workgroup Keith Gordon - DAMA UK Thomas H. Davenport 33 The Open Group 2008

34