TOGAF Conceptual framework/rationale

Transcription

1 TOGAF Conceptual framework/rationale Logical to Physical in TOGAF and ArchiMate It is illegal to copy, share or show this document (or other document published at without the written permission of the copyright holder

2 Logical and physical The Logical/Physical distinction has many possible meanings Some meanings follow (Other meanings are discussed in training)

3 Logical and physical data entities in data architecture The traditional idealisation hierarchy in data architecture Idealisation hierarchy Architecture entity Artifact Documents Conceptual Business objects/entities Business data model Things the business needs to remember (often duplicated in different systems). Logical Data objects/entities Logical data model Data structure for discrete business domain or information system Physical Database tables Physical data schema Data structure for storage using selected database technology Real Rows in tables Database

4 Logical and physical components in EA Processes, Roles and Actors Required Behaviors Logical s Physical s Business Process Role (Human/Org) Actor (Human/Org ) Application Process Log App Phys App Technology Process Log Tech Phys Tech

5 Logical and physical components in TOGAF A simple meta model deducible from text and artefacts Required Behaviors Logical s Physical s Business Function N N Org Unit Why N to N? Org units and actors are not governed by EA Process Role N N Actor Org Units and Actors are instances Data Entity IS Platform Log App Log Tech Phys App Phys Tech Why 1 to 1? These are governed by EA and can be made to correspond. Physical components are not instances.

6 TOGAF s Conceptual framework/rationale The method proposed by systems theory is to model complex entities (multiple interacting components) by abstracting from certain details of structure and component. (Laszlo and Krippner) TOGAF s conceptual framework for describing the architecture of any enterprise or system is essentially: 1. Requirements <are for the products of> regular behaviors 2. Behaviors <are assigned for performance to> logical components 3. Logical components <are realised by hiring, buying or building> physical components These generic architectural entities have different generic attributes. E.g. behaviours run over time, and physical components occupy space.

7 Definitions of service TOGAF s definition ArchiMate s definition Generally speaking, a service is an element of behaviour that provides specific functionality in response to requests from actors or other services. A logical representation of a repeatable business activity, has a specified outcome, is self-contained, is a black box to its consumers. a unit of functionality that a system exposes to its environment, hides internal operations, provides a value, accessible through interfaces. A discretely invokable behaviour (short or long) that is triggered by an event/input received from client actors or components, is defined in a service contract that encapsulates internal process(es), produces results of value to clients, and is presented for access in one or more interfaces.

8 TOGAF s conceptual framework Conceptual framework Generic entities Specific entities Required behaviours Sevices, regardless of internal processes or structure Business Business IS Platform Logical components portfolios, independent of any specific vendor or technology solution Logical Business Function Role Logical Application Logical Technology Physical components Physical Organisat n Unit Actor Physical Application Physical Technology

9 Realisation of logical elements by physical elements Vocabulary Regular behaviors assigned to Logical building blocks realised by Generic attributes TOGAF & ArchiMate Run over time Business s / Processes Encapsulated collections of services/processes Functions Roles Other Value Streams Capabilities TOGAF IS s Logical Application s ArchiMate Application s Application Interfaces Physical building blocks Occupy space and do work Organisation Units Actors Physical Application s Application s Other Use Cases / User Stories User Interfaces Applications TOGAF Platform s Logical Technology s Physical Technology s ArchiMate Infrastructure s Infrastructure Interfaces Other APIs Nodes (System Software, Devices)

10 TOGAF Conceptual framework/rationale Logical to Physical in TOGAF s ADM It is illegal to copy, share or show this document (or other document published at without the written permission of the copyright holder

11 Logical to physical in TOGAF TOGAF regards the enterprise as a system (or system of systems) to be described abstractly. Architecture Requirements Specification Logical Architecture Definition Doc Architecture Building Blocks Physical Solution Options The physical elements in an enterprise architecture may still be considerably abstracted from Solution Architecture Solution Building Blocks

12 Required behaviours Domain Aspect Business Data/ Information Applications Infrastructure technology Requirements Management Haircut What services or information do external entities want? I/O data flow Record Sales Prospect Phases B to D Phases E to G

13 Required behaviours <are assigned for performance to> logical components Domain Aspect Business Data/ Information Applications Infrastructure technology Requirements Management Haircut I/O data flow Record Sales Prospect Phases B to D Role Shop Function Logical Data Entity CRM Interface FTP Interface s specified in a vendor and technology-neutral way by services delivered and (where relevant) by data maintained. Phases E to G

14 Logical components <are realised by> physical components Domain Aspect Business Data/ Information Applications Infrastructure technology Requirements Management Haircut I/O data flow Record Sales Prospect Phases B to D Role Shop Function Logical Data Entity CRM Interface FTP Interface Person Organisation Phases E to G Joe Shop in High Street Database Table Sales force.com FTP Server App Server Device Hired, bought or built or realise the logical components.

15 TOGAF Conceptual framework/rationale Logical to Physical in TOGAF s Enterprise Continuum It is illegal to copy, share or show this document (or other document published at without the written permission of the copyright holder

16 TOGAF Enterprise Continuum with quotes and references Enterprise Continuum Requirements & context Architecture Continuum: a repository of architectural elements Logical Logical: An implementationindependent definition of the architecture, often grouping related physical entities according to their purpose and structure. Architecture Building Block (ABB): a constituent of the architecture model. Architecture Building Blocks: Architecture documentation and models Solutions Continuum: contains implementations of definitions in the Architecture Continuum. Physical Physical: A description of a real-world entity. Physical elements in an enterprise architecture may still be considerably abstracted from Solution Architecture, design, or implementation views. Solution Building Block (SBB) : a candidate physical solution for an Architecture Building Block (ABB) Solution Building Blocks: Implementationspecific building blocks Figure 2-3 Enterprise Continuum Figure 6-2 Management Frameworks to Co-ordinate with TOGAF Figure 6-3 Interoperability and Relationships between Management Frameworks Figure 28-2 Consolidated Gaps, Solutions, and Dependencies Matrix Figure 40-1 Summary Classification Model for Architecture Landscapes AND Figure 40-2 Summary Classification Model for Solutions.

17 TOGAF Enterprise Continuum mapped to ArchiMate Enterprise Continuum Conceptual framework ArchiMate Requirements & context Required behaviour A requestable activity/operation/process, definable in a contract, and ideally found in only one ABB service portfolio. Architecture Continuum: a repository of architectural elements Logical Solutions Continuum: contains implementations of definitions in the Architecture Continuum. Physical Logical An "architecture building block" (ABB) An ideal or potential component Defined by services offered (or activities performed) Vendor and technology neutral. Physical A solution building block" (SBB) A real component that can perform activities and implements logical component(s) Vendor or technology specific. Role Function Actor, Node

18 E.g. Business architecture TOGAF business architecture Enterprise Continuum ArchiMate Business What does a customer want? Requirements Business service Haircut Role or Function What role or function do we need to provide the service? Architecture continuum Role Function Role Role Shop Function Actor or Organisation Unit What actor or organisation unit can we acquire to play the role or perform the function? Solution continuum Actor Actor Actor Joe Shop in High Street Person Organisation

19 E.g. Applications Architecture TOGAF information systems architecture IS Your sales Organisation unit require 20 IS s (use cases) from a logical component. IS ArchiMate Application Customer Order History Logical Application You call it a customer relationship management system, which could be realised by a human activity system or by any of several COTS ( packaged ) computer applications. Physical Application You choose a specific physical application because it offers 18 of the 20 of the required services. It offers 5 other services you never thought to ask for, which are opportunities. Logical Application Physical Application Application Function CRM Function or Interface Application Sales force.com

20 E.g. Infrastructure technology architecture TOGAF technology architecture ArchiMate Platform Ideally, selected from the enterprise TRM Platform Infrastructure Logical Technology Defined by "service portfolio the ABB is to provide. E.g. the IETF standard FTP interface. Logical Technology Infrastructure Function FTP Function or Interface Physical Technology The (SBB) you hire, buy or build to realise the ABB. E.g. the particular FTP server you deploy on your device(s). Physical Technology Node FTP Server App Server Device System Software Device

21 ArchiMate entities in TOGAF s Enterprise Continuum TOGAF Enterprise Cont. Business Applications Infrastructure technology Context & Requirements Haircut Customer OrderHistory Architecture Continuum Logical Role Shop Function CRM FTP Solution Continuum Physical Joe Shop in High Street Sales force.com FTP Server App Server Device Person Organisation