TOGAF Reference Models

19,732 views

Published on

Summary of TO

Published in: Technology, Business

TOGAF Reference Models

  1. 1. TOGAF – A SummaryReference Models<br />
  2. 2. Where Reference Models fits into TOGAF?<br />
  3. 3. There are two reference models<br />TRM<br />Technical Reference Model<br />III-RM<br />Integrated Information Infrastructure <br />
  4. 4. What is the TRM- Technical Reference Model?<br />The TOGAF’s TRM is a reference model and a foundational architecture<br />A reference model has a taxonomy that’s describes components and the conceptual structure of the model and a graphic which provides a visual representation of the taxonomy as to aid understanding<br />A foundation architecture is an architecture of generic services and functions that provides a foundation on which more specific architectures can be built<br />
  5. 5. Uses of TRM<br />Objective of TRM is to enable structured definition of the standardized application platform and its associated interfaces.<br />Provides a starting point or reference for organisation to develop their own reference models by extending or adapting the TRM<br />Provides a consistent taxonomy to aid a means of communication between stakeholders<br />Can be used as a taxonomy to develop a standards information base within an organisation.<br />
  6. 6. Overview of TRM<br />Application Portability<br />How applications call or use the services available in the platform.<br />Done through the application platform interface<br />Interoperability<br />How the application platforms can communicate with each other<br />Done through the communication infrastructure interface<br />Diversity should be minimised between the application platform and the communications infrastructure<br />
  7. 7. TRM in detail<br />Application Software<br />Contains two categories of software , business applications and infrastructure applications. The standards for the application platform will be strongly influenced by this application software.<br />Business Applications<br />Specific to a particular enterprise or vertical industry, model elements of an enterprise domain of activity or business process<br />Infrastructure Applications<br />Provide General purpose business functionality, uneconomic to customise but instead develop extensions, Interoperability and user interface are key attributes<br />Application Platform Interface<br />A complete interface between Application Software and the Application Platform. Needs to consist of the programming interface, protocols and data structures. Platforms provides and API that the application must comply with. An Application could call different APIs in order to conform with different platforms<br />Application Platform<br />A conceptual platform that contains all the platform services required to exist in order for the application software to work. e.g. A union of all operating systems services, security services, user interface services etc.<br />Communications Infrastructure Interface<br />Effectively becoming a standard of IP based communications that the application platform uses to talk to the communications infrastructure.<br />Communications Infrastructure<br />Basic mechanism of the transfer of data. Hardware and software elements that allow for the networking and physical links ( switches, routers) used by a system to interact with the network<br />Qualities<br />Attributes that are applicable across all the components. Qualities need to defined in detail when developing the target architecture e.g. Security, Locale, performance <br />
  8. 8. What is III-RM ?<br />The TRM focuses on the Application Platform space, III-RM main focus is the Applications space particularly the “Common Systems Architecture” <br />Like the TRM it is a reference model with a taxonomy and a graphic however it is a subset of the scope of TRM but expands on certain parts<br />Helps provide a solution to the common problem called the Boundaryless information flow <br />Foundation Architecture that can be adapted be organisations as architecture building blocks<br />
  9. 9. What is the Boundaryless Information Flow?<br />Getting the right information to the right people in the right time in a secure, reliable manner, in order to support the operations that are core to the extended enterprise<br />The problem is that departments are siloed with their own processes, their own systems, their own data. <br />The trends in business now requires faster and better integration between these silos in to be responsive to changing markets, which requires access to systems and data across these silos.<br />Cross functional teams help but how do they get access to the information to help them solve a business problem or to exploit a business opportunity<br />
  10. 10. Boundaryless Information Flow – the problem it solves<br />Imagine a simple organisation with multiple departments, each with systems and data<br />Procure <br />Space<br />Internal Space<br />Sell Space<br />Systems<br />Systems<br />Systems<br />Systems<br />Systems<br />data<br />data<br />data<br />data<br />data<br />Customer <br />Support<br />Assembling<br />Manufacturing<br />Procurement<br />Finance <br />and Legal<br />
  11. 11. Issues with implementing a cross functional group<br />How does it understand the big picture?<br />Cross functional Group<br /><ul><li>Cannot be trained on all the systems!
  12. 12. All the systems are propriety and have different means of access
  13. 13. Time spent co-ordinating with teams, slows down group</li></ul>Systems<br />Systems<br />Systems<br />Systems<br />Systems<br />data<br />data<br />data<br />data<br />data<br />Customer <br />Support<br />Assembling<br />Manufacturing<br />Procurement<br />Finance <br />and Legal<br />Internal Space<br />Procure <br />Space<br />Sell Space<br />
  14. 14. Overview of III-RM<br />Focus of III-RM<br />Subset of TRM<br />No focussed on O/S, Network or communications<br />Expands the Applications and API areas<br />
  15. 15. Overview of III-RM<br />Infrastructure applications<br />
  16. 16. Information Provider Applications (IPA)<br />Solves: All the systems are propriety and have different means of access<br />Liberate Data by providing a open interface to a system via its propriety interface, make it the data more accessible.<br />These applications tend to work on a request, response architecture where an open interface is called, which in turn calls a propriety interface at run-time, a response is returned which is converted into the open interface response.<br />Abstracts the caller function from the system’s propriety interface calls. Also if the propriety system is replaced the IPA will need to change but the caller function may not.<br />
  17. 17. Liberating the data using IPA<br />Introducing information provider applications(IPA)<br />Cross functional Group<br />However still too many interfaces <br />Open interfaces<br />IPA<br />IPA<br />IPA<br />IPA<br />IPA<br />Propriety interfaces<br />Systems<br />Systems<br />Systems<br />Systems<br />Systems<br />data<br />data<br />data<br />data<br />data<br />Customer <br />Support<br />Assembling<br />Manufacturing<br />Procurement<br />Finance <br />and Legal<br />Internal Space<br />Procure <br />Space<br />Sell Space<br />
  18. 18. Brokerage Applications<br />If the number of IPA interfaces is too many and the information requirements are broad it is likely that many interfaces may be called to satisfy one type of information request. <br />Brokerage Applications serve up a single request that has many information sources. It does this by breaking up a request into multiple dispatches and collates all the responses<br />Brokerage Applications can also be used to allow external partners access to information<br />
  19. 19. Orchestrating the data using BA<br />Introducing brokerage applications(BA)<br />Cross functional Group<br />External Partner<br />Where is the user interface, as Brokerage applications does not have one?<br />Open interfaces<br />BA<br />BA<br />BA<br />Open interfaces<br />IPA<br />IPA<br />IPA<br />IPA<br />IPA<br />Propriety interfaces<br />Systems<br />Systems<br />Systems<br />Systems<br />Systems<br />data<br />data<br />data<br />data<br />data<br />Customer <br />Support<br />Assembling<br />Manufacturing<br />Procurement<br />Finance <br />and Legal<br />Procure <br />Space<br />Internal Space<br />Sell Space<br />
  20. 20. Information Consumer Applications (ICA) <br />Provides the information to the end user in the format that they need it, in a secure manner<br />Communicates with the BA or IPA via open interfaces, in some cases via a firewall.<br />An example of a ICA is an UI components of an Enterprise Portal<br />
  21. 21. Presenting the data using ICA<br />Introducing Information Consumer Applications<br />Cross functional Group<br />External Partner<br />ICA<br />ICA<br />ICA<br />How do we develop these interfaces? How to be management these applications?<br />Open interfaces<br />firewall<br />BA<br />BA<br />BA<br />Open interfaces<br />IPA<br />IPA<br />IPA<br />IPA<br />IPA<br />Propriety interfaces<br />Systems<br />Systems<br />Systems<br />Systems<br />Systems<br />data<br />data<br />data<br />data<br />data<br />Customer <br />Support<br />Assembling<br />Manufacturing<br />Procurement<br />Finance <br />and Legal<br />Procure <br />Space<br />Internal Space<br />Sell Space<br />
  22. 22. Infrastructure Applications<br />There are two infrastructure applications:-<br />Development Tools<br />Provides all the necessary modelling, design and construction capabilities to develop and deploy applications that require access to the integrated information infrastructure in a manner that is consistent with the environment<br />Management utilities<br />Tune and manage the run-time environment in order to meet the demands of the ever changing business environment<br />
  23. 23. Application Platform<br />There are a number of platform services required to make the III-RM work<br />Software Engineering Services <br />Programming Languages, Libraries etc<br />Security Services<br />Single Sign on, firewalls etc<br />Location and Directory Services<br />Naming, Discovery, registering<br />Data Exchange Services<br />Application-to-Application messaging<br />UI Services<br />Browser<br />Data Management Services<br />Search, file, query<br />Workflow and event services<br />

×