TOGAF diagram examples featuring ArchiMate

Transcription

1 You may share as the link to this presentation If you want to share or show the pdf, TOGAF diagram examples featuring ArchiMate Includes a best fit mapping of diagrams in the ArchiMate v2.1 standard to diagram definitions in TOGAF 9.1 Including diagrams and definitions edited from the ArchiMate 2.1 standard. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

2 TOGAF students ask Q) can you show us better illustrations of TOGAF diagram definitions than those in on the OG web site and/or our training course? Yes to follow. Copyright Ltd 2013

3 ArchiMate v 2.1 says "TOGAF and ArchiMate can easily be used in conjunction But the standard doesn t make these diagram to diagram correspondences clear. TOGAF/AM Vision diagrams Value Chain Solution Concept/ Vision TOGAF/AM Business diagrams Goal/Objective/Service Business Use-case Events Process Flow Business Service/Information Product Lifecycle Functional Decomposition Organization Decomposition Business Footprint TOGAF/AM Data diagrams Conceptual Data (aka business data model) Logical Data Data Dissemination Data Security Data Migration Data Lifecycle TOGAF/AM Application diagrams Application Use Case Application Communication Application & User Location Process/Application Realization Software Engineering Enterprise Manageability Application/Migration Software Distribution: composite of Software Engineering and the Application-User Location diagrams. TOGAF/AM Technology diagrams Environments and Locations Platform Decomposition Processing Network Computing Hardware Communications Engineering ArchiMate equivalent example by Pieter Van Ostaeyen example by Pieter Van Ostaeyen Product Viewpoint, Service Realization Viewpoint Business Process Co-operation Viewpoint Business Process Viewpoint Business Function Viewpoint Organization Viewpoint, Actor Co-operation Viewpoint Introductory Viewpoint, Layered Viewpoint Information Structure Viewpoint example by Pieter Van Ostaeyen Application Usage Viewpoint Application Co-operation Viewpoint example by Pieter Van Ostaeyen Application Usage Viewpoint, Application Behavior Viewpoint Application Structure Viewpoint Application Structure Viewpoint Infrastructure Viewpoint Infrastructure Usage Viewpoint Implementation and Deployment Viewpoint Copyright Ltd 2013

4 ArchiMate v 2.1 says: "and they appear to cover much of the same ground although with some differences in scope and approach. Hmm TOGAF is a management framework for enterprise architecture transformation work - divided into 52 chapters centred on a process (the ADM). ArchiMate is a modelling language that corresponds most directly to one TOGAF chapter on architecture artefacts. Copyright Ltd 2013

5 ArchiMate v 2.1 says: Some of the viewpoints that are defined in TOGAF cannot easily be mapped onto ArchiMate viewpoints OK, but I don't see any practical difficulty here. All but one of the ArchiMate artefacts can be readily mapped to TOGAF artefacts. ArchiMate is weak for data architecture, but models other architecture domains much as TOGAF does And the remaining TOGAF artefacts are readily drawn as cartoons, or tables, or using well-established industry tools (e.g. for data modelling, UML etc). Copyright Ltd 2013

6 This slide show Illustrates all the TOGAF diagram types. Maps ArchiMate standard diagram types to TOGAF ones Does not recommend any particular diagram type. E.g. Some ArchiMate diagrams could well be replaced by alternatives, say. BPMN for process flow, UML sequence diagrams for process-app realisation Copyright Ltd 2013

7 By the way It helps to understand this generic meta model Service Interface Data Object Location Process Component You can find an explanation of this figure in the Formal System Description paper at avancier.co.uk Copyright Ltd 2013

8 TOGAF Phase A A: Vision B: Business C: Data C: Applications D: Technology TOGAF/AM Vision diagrams Value Chain ArchiMate equivalent example by Pieter Van Ostaeyen Solution Concept/ Vision Copyright Ltd 2013

9 Value Chain diagram provides a high-level orientation view of an enterprise and how it interacts with the outside world. focuses on presentational impact. to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand the high-level functional and organizational context of the architecture engagement. THIS AND ALL TEXT IN GREY IS EDITED FROM TOGAF 9.1 CHAPTER 35 ARCHITECTURE ARTEFACTS Copyright Ltd 2013

10 Value Chain diagram as a conceptual reference architecture from TOG example World Class EA Copyright Ltd 2013

11 AM: Value Chain/Stream diagram: an illustration Less formal than a flow chart with step-to-step transitions. You may draw a cartoon instead. Marketing Customer identification Sales Customer Service Order Payment Delivery Vision & Strategy Product identification Product Supply Copyright Ltd 2013

12 ArchiMate version drawn by Pieter Van Ostaeyen Copyright Ltd 2013

13 TOGAF: Solution Concept/ Vision diagram What is a proposed solution; what does it do? Should be an engaging summary description. TOGAF says Provides high-level orientation of solution that is envisaged in order to meet objectives of architecture engagement Pencil sketch" of expected solution at outset of engagement This diagram may Embody key objectives, requirements, and constraints Highlight work areas to be investigated in more detail Objective Gain stakeholder support for a particular change initiative All participants understand What the architecture engagement is seeking to achieve How a particular solution approach will meet the needs of the enterprise Copyright Ltd 2013

14 AM: Solution Concept/Vision diagram: MODAF style Based around a rich picture or cartoon Copyright Ltd 2013

15 TOGAF Phase and Architecture Domain/Layer A: Vision B: Business C: Data C: Applications D: Technology Environment Business layer usually a human activity system, with people/actors playing roles in processes Business architects are concerned with the structure and behaviour of human activity systems. Application layer Technology layer Copyright Ltd 2013

16 TOGAF/AM Business diagrams Goal/Objective/Service Business Use-case Events Process Flow Business Service/Information Product Lifecycle Functional Decomposition Organization Decomposition Business Footprint ArchiMate equivalent example by Pieter Van Ostaeyen Product Viewpoint, Service Realization Viewpoint Business Process Co-operation Viewpoint Business Process Viewpoint Business Function Viewpoint Organization Viewpoint, Actor Co-operation Viewpoint Introductory Viewpoint, Layered Viewpoint Copyright Ltd 2013

17 TOGAF business architecture entities and relationships Functions provide a logical organisation taxonomy Organisation units form the physical management structure NOTE: Some relationships to Actor would better be related to Role Business Service Business Process Business Function Actor interacts with Function Actor Performs Function Organisation Location Actor operates in Location Actor belongs to Organization Unit Actor participates in Process Actor performs task in Role Actor consumes Service Role Actor Copyright Ltd 2013

18 s model of structured analysis Not exactly TOGAF s model, but will be used to indicate the content of diagrams Aim Business Event or Service Note: it is impractical to draw all possible relationships Business Process Business Function Data Entity Activity Organisation Role Actor Copyright Ltd 2013

19 TOGAF suggests three approaches to Business Architecture Aim Process Modeling Business Event or Service Functional decomposition Data Entity Business Process Activity Business Function Organisation Business Interaction matrix Organisation decomposition Role Use-case Analysis Actor Structured Analysis Copyright Ltd 2013

20 TOGAF ADM Phase B: Diagrams AIMS Goal/Objective/Service diagram BEHAVIOUR: SERVICES & PROCESSES Use-Case diagram Event diagram Process Flow diagram Business Service/Information diagram Product Lifecycle diagram STRUCTURE: COMPONENTS Functional Decomposition diagram Organization Decomposition diagram SCOPE/OVERVIEW Business Footprint diagram Data Entity Business Process Aim Business Event or Service Activity Business Function Organisation Role Actor Copyright Ltd 2013

21 TOGAF: Goal/Objective/Service Diagram to define the ways in which a service contributes to the achievement of a business vision or strategy. Services are associated with the drivers, goals, objectives, and measures that they support, allowing the enterprise to understand which services contribute to similar aspects of business performance. Aim also provides qualitative input on what constitutes high performance for a particular service. Data Entity Business Process Business Event or Service Activity Business Function Organisation Role Actor Copyright Ltd 2013

22 AM: Goal/Objective/Service diagram: illustration Executive level EA level Driver Mission Vision SMART Goal Goal Aims Objective Objective Goal Goal Goal Service Objective Objective A directed graph rather than a hierarchy SA level Objective Objective Objective Service Service Service Service Service Objective Service Service Service Copyright Ltd 2013

23 AM: ArchiMate version drawn by Pieter Van Ostaeyen Copyright Ltd 2013

24 TOGAF: Business Use-case Diagram displays the relationships between consumers and providers of business services. Business services are consumed by actors or other business services The diagram provides added richness in describing business capability by illustrating how and when that capability is used. to help to describe and validate the interaction between actors and their roles to processes and functions. As architecture progresses, use-cases can evolve from the business level to include data, application, and technology details. Architectural business use-cases can also be re-used in systems design work. Data Entity Business Process Aim Business Event or Service Activity Business Function Organisation Role Actor Copyright Ltd 2013

25 Business Use-case Diagram Plenty more examples on the web! Use case = a system process that an actor engages with Use case diagram = system scoping tool Copyright Ltd 2013

26 This example is a kin to a Business Use Case diagram ArchiMate: Product Viewpoint Stakeholders: Product developers, product managers, process and domain architects Concerns: Product development, value offered by the products of the enterprise Product used by Actor Better Role than Actor Product defined as a group of services, supported by business (information) object Subtype product extends super type Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

27 ArchiMate: Service Realization Viewpoint Cf. Business Scenario or Use Case diagram Stakeholders: Process and domain architects, product and operational managers Concerns: Added-value of business processes, consistency and completeness, responsibilities Role Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Role uses Service Service realised by Process Copyright Ltd 2013

28 TOGAF: Events Diagram To depict the relationship between events and process. Events [represent] Arrival [capture] of information (e.g., customer submits sales order) Points in time (e.g., end of fiscal quarter) Events cause work and actions need to be under taken within the business. Events are considered as triggers for a process. It is important to note that the event has to trigger a process and generate a business response or result. Data Entity Note: the processing of an event can be viewed as a service Business Process Aim Business Event or Service Activity Business Function Organisation Role Actor Copyright Ltd 2013

29 AM: Event diagram: illustration Draw here using the style of a UML sequence diagram Could drawn as a process flow diagram with swim lanes Event diagram Sales Billing Delivery See Communication Modelling under Techniques Sale Event Event p r o c e s s Event p r o c e s s p r o c e s s Event Event p r o c e s s Copyright Ltd 2013

30 TOGAF: Process Flow Diagram to depict all models and mappings related to the process metamodel entity. show sequential flow of control between activities may utilize swimlane techniques to represent ownership and realization of process steps. can be used to detail the controls that apply to a process, events that trigger or result from of a process products generated from process execution. useful in elaborating the architecture with subject specialists, as they allow the specialist to describe how the job is done for a particular function. each process step can become a more finegrained function and can then in turn be elaborated as a process. Data Entity Business Process Aim Business Event or Service Activity Business Function Organisation Role Actor Copyright Ltd 2013

31 Cf. Process flow diagram ArchiMate: Business Process Co-operation Viewpoint Stakeholders: Process and domain architects, operational managers Concerns: Dependencies between business processes, consistency and completeness, responsibilities Role uses Service Service realised by Process Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Service used by Process Copyright Ltd 2013

32 Note on service and process granularity The symbols may show coarse-grained processes/steps/activities Manage event Organise conference Run conference Process comments And fine-grained processes/steps/activities Book seat Apply for seat Check application Accept booking Apply for seat Obtain booking form Complete form Put form in letter box The same is true of services (which encapsulate processes) But the notation is not designed to show service rules or process logic Copyright Ltd 2013

33 Graphical symbols for business rules and logic 1 Process flow rules: conditions and parallel paths [No] UML activity diagram notation Get up Drink coffee Do crossword Cup empty Complete [Yes] [Yes] Got to work [No] ArchiMate (note solid arrow head) Drink coffee (not empty] [empty] Get up Got to work Do crossword [complete] (incomplete] Copyright Ltd 2013

34 TOGAF: Business Service/Information Diagram shows the information needed to support one or more business services. shows what data is consumed by or produced by a business service and may also show the source of information. Aim shows an initial representation of the information present within the architecture and therefore forms a basis for elaboration and refinement within Phase C (Data Architecture). Business Process Business Event or Service Business Function Data Entity Activity Organisation Role Actor Copyright Ltd 2013

35 ArchiMate: Business Process Viewpoint Cf. Business Service/Information Diagram Stakeholders: Process and domain architects, operational managers Concerns: Structure of business processes, consistency and completeness, responsibilities This access arrow shows direction of flow (not access) Transition arrow Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Note: process rather than function symbol Copyright Ltd 2013

36 TOGAF: Product Lifecycle Diagram to assist in understanding the lifecycles of key entities within the enterprise. Understanding product lifecycles is becoming increasingly important with respect to environmental concerns, legislation, and regulation where products must be tracked from manufacture to disposal. Equally, organizations that create products that involve personal or sensitive information must have a detailed understanding of the product lifecycle in order to ensure rigor in design of controls, processes, and procedures. Examples include credit cards, debit cards, store/loyalty cards, smart cards, user identity credentials (identity cards, passports, etc.). Data Entity A lifecycle views an entity as a long-term process Business Process Aim Business Event or Service Activity Business Function Role Organisation Actor Copyright Ltd 2013

37 AM: Product Lifecycle diagram: illustration Boxes = states Lines = transitions between states Annotations = events that trigger transitions UML State Chart First State State Event State machine State Last State Asset Lifecycle Specify Specified Make Made Receive In stock Loan On loan Return Renew Retire Retired Scrap Scrapped Copyright Ltd 2013

38 TOGAF: Functional Decomposition Diagram to show on a single page the capabilities of an organization that are relevant to the consideration of an architecture. By examining the capabilities of an organization from a functional perspective, it is possible to quickly develop models of what the organization does without being dragged into extended debate on how the organization does it. Once a basic Functional Decomposition diagram has been developed, it becomes possible to layer heat-maps on top of this diagram to show scope and decisions. For example, the capabilities to be implemented in different phases of a change program. Data Entity Business Process Aim Business Event or Service Activity Business Function Organisation Role Actor Copyright Ltd 2013

39 ArchiMate: Business Function Viewpoint Could show goods and service flows between logical business functions Stakeholders: Enterprise, process, and domain architects Concerns: Identification of competencies, identification of main activities, reduction of complexity Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

40 TOGAF: Organization Decomposition Diagram describes the links between actor, roles, and location within an organization tree. should provide a chain of command of owners and decision-makers in the organization. Although it is not the intent to link goal to organization, it should be possible to intuitively link the goals to the stakeholders from the Organization Decomposition diagram. Business Process Aim Business Event or Service Business Function Data Entity Activity Organisation Role Actor Copyright Ltd 2013

41 ArchiMate: Organization Viewpoint Organisation decomposition Or management structure Stakeholders: Enterprise, process and domain architects, managers, employees, shareholders Concerns: Identification of competencies, authority, and responsibilities Actor = Org Unit Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

42 ArchiMate: Actor Co-operation Viewpoint Could show goods and service flows between physical org units Stakeholders: Enterprise, process, and domain architects Concerns: Relationships of actors with their environment Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

43 TOGAF: Business Footprint Diagram describes the links between business goals, organizational units, business functions, and services, maps these functions to the technical components delivering the required capability. provides a clear traceability between a technical component and the business goal that it satisfies demonstrates ownership of the services identified. demonstrates only the key facts linking organization unit functions to delivery services and is utilized as a communication platform for senior-level (CxO) stakeholders. Copyright Ltd 2013

44 ArchiMate: Introductory Viewpoint Cf. Business footprint diagram Stakeholders: Enterprise architects, managers Concerns: Make design choices visible, convince stakeholders Note this arrow does not have the proper ArchiMate meaning, so the diagram is a cartoon Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

45 Cf. Business footprint diagram ArchiMate: Layered Viewpoint Stakeholders: Enterprise, process, application, infrastructure, and domain architects Concerns: Consistency, reduction of complexity, impact of change, flexibility Look like application services rather than platform services Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

46 TOGAF Phase and Architecture Domain/Layer A: Vision B: Business C: Data C: Applications D: Technology Environment Business layer Application layer External entities and events Business entities and events Digital data The data architect is concerned with data at rest, data in motion, and data qualities (meta data) Technology layer Copyright Ltd 2013

47 TOGAF ADM Phase C: Diagrams TOGAF/AM Data diagrams Conceptual Data (aka business data model) ArchiMate equivalent Information Structure Viewpoint ARCHIMATE v2.0 ONLY? Logical Data Data Dissemination Data Security Data Migration example by Pieter Van Ostaeyen Data Lifecycle Copyright Ltd 2013

48 TOGAF: Conceptual Data Diagram (aka business data model) to depict the relationships between critical data entities within the enterprise. developed to address the concerns of business stakeholders. City Council Conceptual/Business Data diagram Ward Claimant Directorate * Building * Business * * * * Transaction Worker Member Of Public * * Enquiry Copyright Ltd 2013

49 ARCHIMATE v2.0 ONLY? ArchiMate: Information Structure Viewpoint A strange kind of Business Data Model Stakeholders: Domain and information architects Concerns: Structure and dependencies of the used data and information, consistency and completeness Application data object Naive use of aggregation Redundant relationship? Strange use of realisation Business (information) object What is the object aside from its representation? Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

50 TOGAF: Logical Data Diagram to depict logical views relationships among the critical data entities (or classes) within the enterprise. The audience is Application developers Database designers Copyright Ltd 2013

51 AM: Logical Data diagram: IDEF style This graphical summary of a logical data model is drawn as an entity relationship diagram using the IDEF data model notation Copyright Ltd 2013

52 AM: Logical Data Model Relational style CUSTOMER entity Customer number Primary Key Customer name Customer address PRODUCT entity Product type Product description Unit price OLTP database Primary Key Entities Attributes & Relationships Usually defining the content of one persistent data store ORDER entity Customer number Order number Order amount Product type Foreign Key Primary Key Foreign Key Copyright Ltd 2013

53 TOGAF: Data Dissemination Diagram to show the relationship between data entity, business service, and application components. shows how the logical entities are to be physically realized by application components allows effective sizing to be carried out and the IT footprint to be refined. can indicate the business criticality of application components may show data replication and application ownership of the master reference for data. can show two copies and the master-copy relationship between them. Copyright Ltd 2013

54 AM: Data Dissemination diagram: illustration Tabulate data entities against data components (sources / stores) Define which data component is the master for each entity. Application database Data entity (1) until Order Closed (2) after Order Closed. CRM database ERP database Billing database Data warehouse Customer Master Copy Copy Copy Order Master (1) Copy Master (2) Copy Invoice Master Copy Note that attributes of an entity may be mastered in different data stores. Gaps (columns and rows with no entries) may indicate where further analysis is needed. Copyright Ltd 2013

55 TOGAF/AM: Data Security Diagram to depict which actor (person, organization, or system) can access which enterprise data. can be shown in a matrix between objects or as a mapping. Role/actor HR manager Data entity Customer Product Invoice Employee Can read Product manager Can read Salesman Can read Can read Can read 1 st line support Can read Can read Can read Fulfilment agent Can read Can read can be used to demonstrate compliance with data privacy laws and other applicable regulations (HIPAA, SOX, etc). should also consider any trust implications where an enterprise s partners or other parties may have access to the company s systems Copyright Ltd 2013

56 TOGAF/AM: Data Migration Diagram to show the flow of data from the source to the target applications. provide a visual representation of the spread of sources/targets and serve as a tool for data auditing and establishing traceability. For example, just an overall layout of migration landscape or could go into individual application metadata element level of detail. CRM SCM Operational database Operational database Other File Store Procurement ETL ETL ETL ETL Report Staging Area Or stream ETL Central DWH Report ETL ETL ETL Mart Mart Mart Report Report Report Report Report Other Data stream Copyright Ltd 2013

57 ArchiMate version drawn by Pieter Van Ostaeyen Copyright Ltd 2013

58 TOGAF/AM: Data Lifecycle Diagram an essential part of managing business data through its lifecycle from conception to disposal within the constraints of the business process. Each change in state is represented on the diagram which may include the event or rules that trigger that change in state. Product Lifecycle diagram UML State Chart Registration In assembly First State Completion State Event State Loan In stock With customer Return Disposal State machine Last State Renew Scrapped Copyright Ltd 2013

59 TOGAF Phase and Architecture Domain/Layer A: Vision B: Business C: Data C: Applications D: Technology Environment Business layer Application layer contains digital information systems Technology layer Applications architects focus on business apps, inc. rationalisation integration applications road map Copyright Ltd 2013

60 TOGAF s Applications architecture relationships Actor Location contains Physical Application Component Logical Application Component operates on Data Entity Logical Application Component DECOMPOSES Logical Application Component Logical Application Component communicates with Logical Application Component Logical Application Component is extended by Physical Application Component Logical Application Component implements Service Physical Application Component is hosted in Location Physical Application Component extends Logical Application Component Physical Application Component encapsulates Physical Data Component Physical Application Component DECOMPOSES Physical Application Component Physical Application Component communicates with Physical Application Component Service is realized through Logical Application Component Data Entity Logical Data Component Physical Data Component Location [IS] Service Logical Application Component Physical Application Component Copyright Ltd 2013

61 TOGAF ADM Phase C: Diagrams TOGAF/AM Application diagrams ArchiMate equivalent Application Use Case Application Communication Application & User Location Process/Application Realization Software Engineering Enterprise Manageability Application/Migration Application Usage Viewpoint Application Co-operation Viewpoint example by Pieter Van Ostaeyen Application Usage Viewpoint, Application Behavior Viewpoint Application Structure Viewpoint Software Distribution: composite of Software Engineering and Application-User Location diagrams. Application Structure Viewpoint Copyright Ltd 2013

62 TOGAF: Application Use Case Diagram displays the relationships between consumers and providers of application services. Application services are consumed by actors or other application services and the Application Use-Case diagram provides added richness in describing application functionality by illustrating how and when that functionality is used. to help to describe and validate the interaction between actors and their roles with applications. As the architecture progresses, the use-case can evolve from functional information to include technical realization detail. Application use-cases can also be re-used in more detailed systems design work. Copyright Ltd 2013

63 Application use case diagrams Plenty more such diagrams on the web! Shows the uses that actors can make of an application Each use cases is a process that delivers a result or service Use case = a system process that an actor engages with ain_use_case_diagram_v2.jpg Use case diagram = system scoping tool Copyright Ltd 2013

64 Application use case diagrams articletype/articleview/articleid/353/enterprise-architect-for- Business-Analysts.aspx Plenty more such diagrams on the web! Use case = a system process that an actor engages with Optional process Shared process A use case can be extended with use case elements that are optional And/or include use case elements that are reused in other use cases Some shared elements may be fully automated services Copyright Ltd 2013

65 ArchiMate: Application Usage Viewpoint Cf. Application Use Case diagram Stakeholders: Enterprise, process, and application architects, operational managers Concerns: Consistency and completeness, reduction of complexity Business process Process uses App Service Service realised by Component Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. 1 component provides > 1 service Copyright Ltd 2013

66 TOGAF: Application Communication Diagram to depict all models and mappings related to communication between applications in the metamodel entity. shows application components and interfaces between components. Interfaces may be associated with data entities where appropriate. Applications may be associated with business services where appropriate. Communication should be logical and should only show intermediary technology where it is architecturally relevant.. Copyright Ltd 2013

67 ArchiMate: Application Co-operation Viewpoint Cf. Application communication diagram Stakeholders: Enterprise, process, application, and domain architects Concerns: Relationships and dependencies between applications, orchestration/choreography of services, consistency and completeness, reduction of complexity Used by Could be data flow? Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Composed of Copyright Ltd 2013

68 Application Communication Diagram w Interface Catalogue CRM 1a 1c 1b Sales 2a Stock 3a 3c 3b Billing 4a 1d N2 model, or Node Connectivity diagram Federal Enterprise Architecture Framework 3d 4b Data Wrhs Interface id Source App Destination App Data content Triggers event 1a CRM Sales Sales order request New sales order 1b Sales CRM Sales order confirmation Order created in the backend Sales system 2a Sales Stock Requisition Subscribe/Publish timer Copyright Ltd 2013

69 TOGAF: Application & User Location Diagram to clearly depict the business locations from which business users typically interact with the applications, but also the hosting location of the application infrastructure. The diagram enables: Identification of the number of package instances needed Estimation of the number and the type of user licenses Estimation of the level of support needed Selection of system management tools, structure, and management system Appropriate planning for the technological components of the business Performance considerations while implementing solutions Copyright Ltd 2013

70 AM: Application and User Location diagram: illustration Customer location Laptop Kitchen Drawing app Kitchen Ordering app Printer PAN WAN LAN HQ location Product Catalogue Order Management System Copyright Ltd 2013

71 ArchiMate version drawn by Pieter Van Ostaeyen Copyright Ltd 2013

72 TOGAF: Process/Application Realization Diagram to clearly depict the sequence of events when multiple applications are involved in executing a business process. enhances the Application Communication diagram by augmenting it with any sequencing constraints, and hand-off points between batch and real-time processing. would identify complex sequences that could be simplified possible rationalization points in the architecture in order to provide more timely information to business users. May also identify process efficiency improvements that may reduce interaction traffic between applications. Copyright Ltd 2013

73 Process/Application Realization diagram What applications cooperate in the execution of a process? How and when are applications triggered by invocations? What data flows or messages are passed along with an invocation? Useful in analysing the efficiency of a process Shows the overall sequence of a process Limited representation of logic (loops, options & quits) Applications architecture behaviour TOGAF Process Application Realisation diagram UML Interaction/Sequence diagram See Communication Modelling under Techniques Process ERP CRM DW / BI Component cooperating in the process Process Copyright Limited

74 ArchiMate: Application Usage Viewpoint Cf. Process/Application Realization diagram. Stakeholders: Enterprise, process, and application architects, operational managers Concerns: Consistency and completeness, reduction of complexity Business process Process uses App Service Service realised by Component Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. 1 component provides > 1 service Copyright Ltd 2013

75 ArchiMate: Application Behavior Viewpoint Cf. Process/Application Realization diagram? Stakeholders: Enterprise, process, application, and domain architects Concerns: Structure, relationships and dependencies between applications, consistency and completeness, reduction of complexity In the application domain, process step shown using function symbol A kin to a use case header Service realised by Process Function accesses data Transition arrow Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

76 Note on that function appears to = process ArchiMate standard diagrams use different symbols for processes in the business layer Post Letter Find Pen And Paper Write Letter Put in Letter Box And in the application layer Process shown using function symbol Client App Display Template Send Validate Fields Send Copyright Ltd 2013

77 Software Engineering Diagram breaks applications into packages, modules, services, and operations from a development perspective. enables more detailed impact analysis when planning migration stages, and analyzing opportunities and solutions. ideal for application development teams and application management teams when managing complex development environments. Copyright Ltd 2013

78 ArchiMate: Application Structure Viewpoint Cf. SW engineering OR Application communication diagram Stakeholders: Enterprise, process, application, and domain architects Concerns: Application structure, consistency and completeness, reduction of complexity Provides interface Accesses data Requires interface Could be used by or data flow? Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

79 TOGAF: Enterprise Manageability Diagram shows how one or more applications interact with application and technology components that support operational management of a solution. a filter on the Application Communication diagram, specifically for enterprise management class software. Analysis can reveal duplication and gaps, and opportunities in the IT service management operation of an organization. Copyright Ltd 2013

80 AM: Enterprise/System Manageability diagram: illustration Shows deployment of monitoring software. Cf. Processing /Deployment Diagram in the Infrastructure artefacts Copyright Ltd 2013

81 TOGAF Phase C: Two more diagram types Application/Migration Diagram Identifies application migration from baseline to target application components. enables a more accurate estimation of migration costs used to identify temporary applications, staging areas, and the infrastructure required to support migration Software Distribution Diagram a composite of the Software Engineering diagram and the Application-User Location diagram. Depending on the circumstances, this diagram alone may be sufficient, or may not be needed. Copyright Ltd 2013

82 TOGAF Phase and Architecture Domain/Layer A: Vision B: Business C: Data C: Applications D: Technology Environment Business layer Application layer Technology layer contains infrastructure or platform applications used by business applications Deployment of business applications to Platform applications, computers and networks Standardisation The technology road map Copyright Ltd 2013

83 TOGAF s technology architecture relationships Actor Location contains Physical Technology Component Logical Technology Component DECOMPOSES Logical Technology Component Logical Technology Component is dependent on Logical Technology Component Logical Technology Component is extended by Physical Technology Component Logical Technology Component supplies Platform Service Data Entity [IS] Service Platform Service Logical Technology Component provides platform for Service Physical Application Component is realized by Physical Technology Component Physical Technology Component is hosted in Location Logical Data Component Logical Application Component Logical Technology Component Physical Technology Component extends Logical Technology Component Physical Technology Component realizes Physical Application Component Physical Technology Component DECOMPOSES Physical Technology Component Physical Data Component Physical Application Component Physical Technology Component Physical Technology Component is dependent on Physical Technology Component Platform Service is supplied by Logical Technology Component Service is implemented on Logical Technology Component Location Copyright Ltd 2013

84 TOGAF ADM Phase D: Diagrams TOGAF/AM Technology diagrams ArchiMate equivalent Environments and Locations Platform Decomposition Processing Network Computing Hardware Infrastructure Viewpoint Infrastructure Usage Viewpoint Implementation and Deployment Viewpoint Communications Engineering Copyright Ltd 2013

85 TOGAF: Environments and Locations Diagram depicts which locations host which applications, identifies what technologies and/or applications are used at which locations, and finally the locations from which business users typically interact with the applications. should also show the existence and location of different deployment environments, including non-production environments, such as development and pre production. Copyright Ltd 2013

86 AM: Environments and Locations diagram: as a catalogue Remember s/w licence costs can rise with each real CPU and each virtual machine or LPAR Environment type Purpose Physical platform Prototyping To test/demonstrate a specific technology or design concept Development To enable developers to write code 1 System test Integration test Performance test Data migration User acceptance test Production Production support To enable system testers to the product To test how the system integrates with others To test how the system performs when fully loaded To enable cleansing and migration of data To enable user representatives to test to the product To enable live operation of the system(s) To enable fault replication and investigation, and minor changes Hosted at Location Contains Application Components Contains Technology Components Copyright Ltd 2013

87 TOGAF/AM: Platform Decomposition Diagram depicts the technology platform that supports the operations of the IS Architecture. covers all aspects of the infrastructure platform an overview of the enterprise s technology platform can be expanded to map the technology platform to appropriate application components within a specific functional or process area. may show details such as product versions, number of CPUs, etc. or simply an informal eye-chart - an overview of the technical environment. Load Balancer SAN Load Balancer DR Copyright Ltd 2013

88 ArchiMate: Infrastructure Viewpoint Cf. Platform Decomposition Diagram Stakeholders: Infrastructure architects, operational managers Concerns: Stability, security, dependencies, costs of the infrastructure Dodgy use of ArchiMate symbols. System Software (Platform App) Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd

89 Service is a very slippery concept See Issues and remarks presentation Sadly, there is little shared understanding of the distinction between services and interfaces how they relate to processes and components Copyright Ltd

90 TOGAF/AM: Processing Diagram focuses on deployable units of code/configuration and how these are deployed on the technology platform. addresses the following: Which application components need to be grouped to form a deployment unit How deployment units connect/interact (LAN, WAN, and the applicable protocols) How application configuration and usage patterns generate load or capacity requirements for different technology components The organization of deployment units depends on separation concerns of the presentation, business logic, and data store layers and servicelevel requirements of the components. Copyright Ltd 2013

91 ArchiMate: Infrastructure Usage Viewpoint Cf. Processing diagram Stakeholders: Application, infrastructure architects, operational managers Concerns: Dependencies, performance, scalability Better interface than service; and redundant? System Software (Platform App) Application uses platform service Service realised by system software Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Copyright Ltd 2013

92 TOGAF: Network Computing Hardware Diagram to show the "as deployed" logical view of logical application components in a distributed network computing environment. The diagram is useful for the following reasons: Enable understanding of which application is deployed where Establishing authorization, security, and access to these technology components Understand the Technology Architecture that support the applications during problem resolution and troubleshooting Isolate performance problems encountered and perform necessary upgrade to specific physical technology components Identify areas of optimization Enable application/technology auditing and prove compliance Serve as an important tool supporting effective change management Copyright Ltd 2013

93 Cf. Networked Computing Hardware Diagram ArchiMate: Implementation and Deployment Viewpoint Stakeholders: Application and infrastructure architects, operational managers Concerns: Dependencies, security, risks System software entity realises business application entity? Surely a business app, not system software? Copyright The Open Group, All Rights Reserved. ArchiMate is a registered trademark of The Open Group. Dodgy use of realisation arrow Copyright Ltd

94 Realisation is a very slippery concept See Issues and remarks presentation Can an entity in a lower layer realise an entity in a higher layer? Copyright Ltd

95 TOGAF: Communications Engineering Diagram describes the means of communication between assets in the Technology Architecture takes logical connections between client and server components and identifies network boundaries and network infrastructure required to physically implement those connections. does not describe the information format or content, but will address protocol and capacity issues. Copyright Ltd 2013

96 DR Site Andover AM: Communication engineering diagram: Visio style Replica of Live site servers and LAN VPN connection 4Mbit using exiting leased line Live Site Telco 2 Mbit leased line Web users and VPN Internet Telco ESP Configuration Application Management Bristol J Backup DMZ Option 2 K System management VPN connection Development Team Slough Trials LAN Public web users F Dev. Server VPN connection Vendor-hosted servers for Trial applications Telco Network A Portal Server G ESP Supplier Servers H Vendor Supplier Servers Local Telco connection ESP LAN Test LAN B Rating & Proxy Server C Report Server D Database Server Copyright Ltd 2013 E E Test Server Dev/Test Server

97 AM: Communication engineering diagram: MODAF style A kin to the Channel catalogue Copyright Ltd 2013

98 AM: Communication Engineering diagram: tabular style Might be documented on the platform technology diagram or in a supporting table of this kind The network between platform nodes Platform Applications Protocols Network Required Bandwidth Work station Browser, Ajax http/tcp/ip WAN DMZ Firewall http/tcp/ip WAN and LAN Web servers http/tcp/ip LAN DMZ Firewall http/tcp/ip LAN Application server Java App LAN Database server LAN Copyright Ltd 2013

99 Beware the duplication between TOGAF diagrams Application and User Location Diagram shows the geographical distribution of applications, where applications are used by the end user; where the host application is executed and/or delivered in thin client scenarios; where applications are developed, tested, and released; etc. Application/Technology Matrix documents the mapping of business systems [i.e applications] to technology platform. Processing Diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform. Software Distribution Diagram shows how application software is structured and distributed across the estate shows how physical applications are distributed across physical technology and the location of that technology enables a clear view of how the software is hosted Environments and Locations Diagram depicts which locations host which applications what technologies and/or applications are at which locations Networked Computing/Hardware Diagram to document the mapping between logical applications and the technology components (e.g., server) that supports the application both in the development and production environments to show the as deployed logical view of logical application components in a distributed network computing environment Enable understanding of which application is deployed where in the distributed network computing environment. Copyright Ltd 2013

100 Note There is far from a common understanding of the four concepts at the heart of this diagram: process, service, component and interface Service Interface Data Object Location Process Component For an explanation of this figure, find the Formal System Description paper at avancier.co.uk Copyright Ltd 2013

101 EA domains and entities Methods can be used on their own and/or to supplement any architecture framework that shares similar domains and entities ArchiMate Language Framework CSC s domains of change (POLDAT) BCS E&SA reference model Methods TOGAF The Open Group IBM s view EA EA as Strategy MIT You may share as the link to this presentation If you want to share or show the pdf, then grahamberrisford@bulldoghome.com Copyright Ltd 2013