TOGAF 9 Fundamental: 4. Key Terminology

1. TOGAF9 Fundamental:4. Key Terminology Romi Satria Wahonoromi@romisatriawahono.nethttp://romisatriawahono.net

2. Romi Satria Wahono • SD SompokSemarang (1987) • SMPN 8 Semarang (1990) • SMA Taruna NusantaraMagelang (1993) • B.Eng, M.Eng and Dr.Eng(on-leave)Department of Computer ScienceSaitama University, Japan (1994-2004) • Research Interests: Software Engineering and Intelligent Systems • Founder IlmuKomputer.Com • LIPI Researcher (2004-2007) • Founder and CEO PT BrainmaticsCiptaInformatika

3. Course Outline • Introduction • Basic Concepts • Core Concepts • Key Terminology • ADM Introduction • UML Introduction • TOGAF Case Study

4. 4. Key Terminology

5. Contents 4.1 Key Learning Points 4.2 Key Terms 4.3 Summary 4.4 Test Yourself Question

6. 4.1 Key Learning Points

7. Key Learning Points • This chapter will help you understand the key terminology of TOGAF • This chapter will help you to answer the following questions: • What are the key terms for TOGAF 9 Foundation? • Where are these terms used within this Study Guide?

8. 4.2 Key Terms

9. Key Terms • Application • A deployed and operational IT system that supports business functions and services; for example, a payroll. • Applications use data and are supported by multiple technology components but are distinct from the technology components that support the application. • Application Architecture • A description of the major logical grouping of capabilities that manage the data objects necessary to process the data and support the business.

10. Key Terms • Architecture • Architecture has two meanings depending upon its contextual usage: • A formal description of a system, or a detailed plan of the system at component level to guide its implementation • The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time • Architecture Continuum • A part of the Enterprise Continuum. • A repository of architectural elements with increasing detail and specialization.

11. Key Terms • Architecture Continuum • This Continuum begins with foundational definitions such as reference models, core strategies, and basic building blocks. • From there it spans to Industry Architectures and all the way to an organization's specific architecture. • Architecture Building Block (ABB) • A constituent of the architecture model that describes a single aspect of the overall model.

12. Key Terms • Architecture Development Method (ADM) • The core of TOGAF. • Architecture Development Method (ADM) • A step-by-step approach to develop and use an enterprise architecture. • Architecture Domain • The architectural area being considered. • There are four architecture domains within TOGAF:Business, Data, Application, and Technology. • Architecture Framework • A conceptual structure used to develop, implement, and sustain an architecture.

13. Key Terms • Architecture Principles • A qualitative statement of intent that should be met by the architecture. • Has at least a supportingrationale and a measure of importance. • Architecture Vision • A succinct description of the Target Architecture that describes its business value and thechanges to the enterprise that will result from its successful deployment. • It serves as anaspirational vision and a boundary for detailed architecture development.

14. Key Terms • Baseline • A specification that has been formally reviewed and agreed upon, that thereafter serves as thebasis for further development or change and that can be changed only through formal changecontrol procedures or a type of procedure such as configuration management. • Building Block • Represents a (potentially re-usable) component of business, IT, or architectural capability thatcan be combined with other building blocks to deliver architectures and solutions.

15. Key Terms • Building Block • Building blocks can be defined at various levels of detail, depending on what stage ofarchitecture development has been reached. • For instance, at an early stage, a building block cansimply consist of a name or an outline description. • Later on, a building block may bedecomposed into multiple supporting building blocks and may be accompanied by a fullspecification. • Building blocks can relate to “architectures” or “solutions”.

16. Key Terms • Business Architecture • A description of the structure and interaction between the business strategy, organization,functions, business processes, and information needs. • Business Governance • Concerned with ensuring that the business processes and policies (and their operation) deliverthe business outcomes and adhere to relevant business regulation. • Capability • An ability that an organization, person, or system possesses.

17. Key Terms • Capability • Capabilities are typically expressedin general and high-level terms and typically require a combination of organization, people,processes, and technology to achieve; or example, marketing, customer contact, or outboundtelemarketing. • Concerns • The key interests that are crucially important to the stakeholders in a system, and determine theacceptability of the system. • Concerns may pertain to any aspect of the system's functioning,development, or operation, including considerations such as performance, reliability, security,distribution, and evolvability

18. Key Terms • Constraint • An external factor that prevents an organization from pursuing particular approaches to meet itsgoals; for example, customer data is not harmonized within the organization, regionally ornationally, constraining the organization's ability to offer effective customer service. • Data Architecture • A description of the structure and interaction of the enterprise's major types and sources of data,logical data assets, physical data assets, and data management resources.

19. Key Terms • Deliverable • An architectural work product that is contractually specified and in turn formally reviewed,agreed, and signed off by the stakeholders. • Deliverables represent the output of projects andthose deliverables that are in documentation form will typically be archived at completion of aproject, or transitioned into an Architecture Repository as a reference model, standard, orsnapshot of the Architecture Landscape at a point in time.

20. Key Terms • Enterprise • The highest level (typically) of description of an organization and typically covers all missionsand functions. • An enterprise will often span multiple organizations. • Enterprise Continuum • A categorization mechanism useful for classifying architecture and solution artifacts, bothinternal and external to the Architecture Repository, as they evolve from generic FoundationArchitectures to Organization-Specific Architectures.

21. Key Terms • Foundation Architecture • Generic building blocks, their inter-relationships with other building blocks, combined with theprinciples and guidelines that provide a foundation on which more specific architectures can bebuilt. • Gap • A statement of difference between two states. • Used in the context of gap analysis, where thedifference between the Baseline and Target Architecture is identified.

22. Key Terms • Governance • The discipline of monitoring, managing, and steering a business (or IS/IT landscape) to deliverthe business outcome required. • Information • Any communication or representation of facts, data, or opinions, in any medium or form,including textual, numerical, graphic, cartographic, narrative, or audio-visual.

23. Key Terms • Information Technology (IT) • The lifecycle management of information and related technology used by an organization. • An umbrella term that includes all or some of the subject areas relating to the computerindustry, such as Business Continuity, Business IT Interface, Business Process Modelingand Management, Communication, Compliance and Legislation, Computers, ContentManagement, Hardware, Information Management, Internet, Offshoring, Networking,Programming and Software, Professional Issues, Project Management, Security,Standards, Storage, Voice and Data Communications. • Various countries and industriesemploy other umbrella terms to describe this same collection.

24. Key Terms • Information Technology (IT) • A term commonly assigned to a department within an organization tasked withprovisioning some or all of the domains described in (2) above. • Alternate names commonly adopted include Information Services, Information Management, etc. • Logical (Architecture) • An implementation-independent definition of the architecture, often grouping related physicalentities according to their purpose and structure; for example, the products from multipleinfrastructure software vendors can all be logically grouped as Java application server platforms.

25. Key Terms • Metadata • Data about data, of any sort in any media, that describes the characteristics of an entity. • Metamodel • A model that describes how and with what the architecture will be described in a structured way. • Method • A defined, repeatable approach to address a particular type of problem.

26. Key Terms • Methodology • A defined, repeatable series of steps to address a particular type of problem, which typicallycenters on a defined process, but may also include definition of content. • Model • A representation of a subject of interest. • A model provides a smaller scale, simplified, and/orabstract representation of the subject matter. • A model is constructed as a “means to an end”.

27. Key Terms • Model • Inthe context of enterprise architecture, the subject matter is a whole or part of the enterprise andthe end is the ability to construct “views” that address the concerns of particular stakeholders;i.e., their “viewpoints” in relation to the subject matter. • Modeling • A technique through construction of models which enables a subject to be represented in a formthat enables reasoning, insight, and clarity concerning the essence of the subject matter.

28. Key Terms • Objective • A time-bounded milestone for an organization used to demonstrate progress towards a goal; forexample, “Increase Capacity Utilization by 30% by the end of 2009 to support the plannedincrease in market share”. • Physical • A description of a real-world entity. • Physical elements in an enterprise architecture may still beconsiderably abstracted from Solution Architecture, design, or implementation views.

29. Key Terms • Reference Model (RM) • A reference model is an abstract framework for understanding significant relationships amongthe entities of [an] environment, and for the development of consistent standards orspecifications supporting that environment. • A reference model is based on a small number ofunifying concepts and may be used as a basis for education and explaining standards to a nonspecialist.

30. Key Terms • Reference Model (RM) • A reference model is not directly tied to any standards, technologies, or other concreteimplementation details, but it does seek to provide common semantics that can be usedunambiguously across and between different implementations. • Repository • A system that manages all of the data of an enterprise, including data and process models andother enterprise information. Hence, the data in a repository is much more extensive than that ina data dictionary, which generally defines only the data making up a database.

31. Key Terms • Requirement • A statement of need that must be met by a particular architecture or work package. • Segment Architecture • A detailed, formal description of areas within an enterprise, used at the program or portfoliolevel to organize and align change activity. • Solution Architecture • A description of a discrete and focused business operation or activity and how IS/IT supportsthat operation.

32. Key Terms • Solution Architecture • A Solution Architecture typically applies to a single project or project release,assisting in the translation of requirements into a solution vision, high-level business and/or ITsystem specifications, and a portfolio of implementation tasks. • Solution Building Block • A candidate solution which conforms to an Architecture Building Block (ABB). • Solutions Continuum • A part of the Enterprise Continuum.

33. Key Terms • Solutions Continuum • A repository of re-usable solutions for futureimplementation efforts. • It contains implementations of the corresponding definitions in theArchitecture Continuum. • Stakeholder • An individual, team, or organization (or classes thereof) with interests in, or concerns relative to,the outcome of the architecture. • Different stakeholders with different roles will have differentconcerns.

34. Key Terms • Strategic Architecture • A summary formal description of the enterprise, providing an organizing framework foroperational and change activity, and an executive-level, long-term view for direction setting. • Target Architecture • The description of a future state of the architecture being developed for an organization. • Theremay be several future states developed as a roadmap to show the evolution of the architecture toa target state.

35. Key Terms • Technical Reference Model (TRM) • A structure which allows the components of an information system to be described in aconsistent manner. • Technology Architecture • A description of the structure and interaction of the platform services, and logical and physicaltechnology components. • Transition Architecture • A formal description of one state of thearchitecture at an architecturally significant point intime.

36. Key Terms • Transition Architecture • One or more Transition Architectures may be used to describe the progression in time fromthe Baseline to the Target Architecture. • View • The representation of a related set of concerns. • A view is what is seen from a viewpoint. • Anarchitecture view may be represented by a model to demonstrate to stakeholders their areas ofinterest in the architecture. • A view does not have to be visual or graphical in nature.

37. Key Terms • Viewpoint • A definition of the perspective from which a view is taken. • It is a specification of theconventions for constructing and using a view (often by means of an appropriate schema ortemplate). • A view is what you see; a viewpoint is where you are looking from – the vantagepoint or perspective that determines what you see.

38. 4.3 Summary

39. Summary • This chapter lists and defines the key terms used in this Study Guide and the TOGAF 9Foundation Syllabus. • These terms are used as part of the learning outcomes within otherchapters of this Study Guide.

40. 4.4 Test Yourself Question

41. Test Yourself Questions Which one of the following is an architecture of generic services and functions? • Application Architecture • Foundation Architecture • Segment Architecture • Solution Architecture

42. Test Yourself Questions Which one of the following describes a statement of difference between two states? • Baseline • Constraint • Deliverable • Gap • Viewpoint

43. Test Yourself Questions Which one of the following is defined as a categorization model for classifyingarchitecture and solutions artifacts? • Architecture Principle • Architecture Repository • Enterprise Continuum • Foundation Architecture

44. Test Yourself Questions Which one of the following best defines an entity with interests in, or concerns relative to,the outcome of an architecture? • Architect • Sponsor • Stakeholder

45. Test Yourself Questions Which one of the following is defined as formal description of the enterprise, providingan executive-level long-term view for direction setting? • Baseline Architecture • Business Architecture • Foundation Architecture • Segment Architecture • Strategic Architecture

46. Test Yourself Questions Which one of the following is defined as describing the state of an architecture at anarchitecturally significant point in time during the progression from the Baseline to theTarget Architecture? • Capability Architecture • Foundation Architecture • Segment Architecture • Solution Architecture • Transition Architecture

47. References • Rachel Harrison, Study Guide TOGAF® 9 Foundation 2nd Edition, The Open Group, 2011 • Rachel Harrison, Study Guide TOGAF® 9 Certified 2nd Edition, The Open Group, 2011 • Open Group Standard, TOGAF® Version 9.1 (G116), The Open Group, 2011 • Open Group Standard, TOGAF® Version 9.1 – A Pocket Guide (G117), The Open Group, 2011 • Daniel Minoli, Enterprise Architecture A to Z: Frameworks, Business Process Modeling, SOA, and Infrastructure Technology, Taylor & Francis, 2008 • Jon Holt and Simon Perry, Modelling Enterprise Architectures, The Institution of Engineering and Technology, 2010 • Alan Dennis et al, Systems Analysis and Design with UML 4th Edition, John Wiley and Sons, 2013