TOGAF 9 and ArchiMate 2.0 for aligning SOA with Changing Strategies and Capabilities using Sparx EA A presentation on a short Case Study using Sparx EA Enterprise Architect User Group – Nurnberg Oct 8, 2013 B irol Berkem (Ph.D) – TOGAF 9 Certified Enterprise Architect GooBiz.com Note : TOGAF (The Open Group Architecture Framework) and ArchiMate are trademarks of the Open Group This work by Birol Berkem (GooBiz.com) is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License. Permissions beyond the scope of this license may be available by to This presentation aims at showing how to use the ArchiMate ® 2.0 notations throughout TOGAF® 9’ ADM phases in order to align SOA implementation components with changing business strategies and capabilities using Sparx EA

Structure of this Presentation Business Agility – Definitions Enterprise Architecture : Goals and Roles Balanced ScoreCards / Strategy Map techniques to specify Governance Aspects of the EA Operating Model Business & IT Alignment using TOGAF 9.1 and ADM 2.0 – Phases in TOGAF’s ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – Why use ArchiMate 2.0 ? – Basic Concepts, Layers and Viewpoints in ArchiMate 2.0 – Modeling with ArchiMate 2.0 throughout TOGAF 9.1’ ADM phases – Structuring Capabilities to align SOA components – Impacts of Capabilities upon the Application and Infrstructure layers – Updating the Architecture Repository – Modeling the Roadmap, Transition Architectures and Work Packages – Modeling Implementation Projects Planning – The SOA Architectural Backbone at the Implementation Governance Phase Conclusion

Business Agility : Definitions Business agility is the ability of a business to adapt rapidly and cost efficiently in response to changes in the business environment. Business agility can be maintained by adapting goods and services to meet customer demands, adjusting to the changes in a business environment and taking advantage of human resources. "On the Measurement of Enterprise Agility". Journal of Intelligent and Robotic Systems 33 (3): 329–342. DOI: /A: Nikos C. Tsourveloudi, Kimon P. Valavanis (2002)DOI /A:

Business Agility : Needs ! The alignment of organisations with the changing needs of their customer requires: – Communicating key requirements, principles and models of the futur state of the enterprise (vision, strategies, …) in order to ensure a coherent evolution, – Propagation of the changes to ensure a coherent reactivity Such an alignment necessitates an architecture framework that includes : – process, users, information and technology, but also their internal and external relationships with their environment 4

What methodologies, architectures and specification languages to ensure a business agility ? How to use them to capitalize on the business knowledge and align IT with the changing strategies ?

Enterprise Architectures : Goals and Roles ! Enterprise Architecture is usualy done to identify gaps between current and target architecture state of an organisation. Enterprise Architecture enables effective execution of the enterprise strategy to achieve change of an organization ! It provides roadmap to achieve goals and deliver objectives to guide current and futur projects of the organisation. 6 What sources to provide inputs data for the Governance Aspects of an EA ?

7 Shareholder requests “What we do have to improve…" “What we have to do to enhance “value creation” Branding displayed to customers Use ‘Balanced ScoreCards’ / ‘Strategy Map’ techniques to specify Governance Aspects of the EA Operating Model Tactical and process level KPIs to specify here… © Birol Berkem GooBiz 2011/2012 How to implement such governance perspectives using ArchiMate along the phases of TOGAF 9 ?

TOGAF 9 ® : An Enterprise Architecture Framework proposed by the Open Group to align Enterprise Ressources, IT Systems and Technologies with the changing Business Strategies and Business Capabilities. ArchiMate 2.0 ® : Brings you a specification language and viewpoints that allows formalization of the artifacts used within this Alignment Process. 8 Business & IT Alignment using TOGAF 9 and ADM 2.0 The TOGAF ® 9 ADM (Architecture Development Method) for developing an Enterprise Architecture

Phases in TOGAF’s ADM – A Summary 9 Architecture Planning : Business Drivers and Goals Concerns of the Stakeholders Principles, Requirements, Capability Assesment, Readiness Factors,… Development of the Enterprise Architecture, Views of the Architecture across domains, Risk Mitigation,… Consolidating architecture descriptions Definition of the Roadmap Identifying opportunities for re-use and potential solution components Governance of implementation and Architecture Change Management Detailed Implementation and Migration Plan Work Packages and Transition Architectures

TOGAF ® 9 / SOA Initial Content MetaModel Elements 10 Q : So, how to link such concepts to increase business agility ? A : Need a language that ensures coherence, traceability, completeness ! From the Open Group’s TOGAF ®9.1 Specifications

ArchiMate 2.0 adds value to TOGAF 9.1 Artifacts bringing consistency, traceability, completeness ! 11 From the Open Group’s TOGAF ®9.1 Specifications

What is ArchiMate 2.0 ? Why use ArchiMate 2.0 ? – ArchiMate is a modeling language for describing enterprise architectures – Broader scope than UML (essentially designed for software engineering) – Supports EA frameworks like TOGAF 9 & Zachman – ArchiMate 2.0 adds valueto TOGAF 9.1 by bringing consistency, traceability, completeness ! – ArchiMate viewpoints are more detailed than TOGAF’s architecture artifacts – TOGAF does not provide a specification language for descriptions and examples

ArchiMate 2.0 Layers to support TOGAF 9’s « Capability-Based Planning of the Enterprise Architecture » 13 From the Open Group’s TOGAF ®9.1 and ArchiMate ®2.0 Specifications

Basic ArchiMate Concepts (Very Simplified !) 14 BIZ.FUNCTION Simplified ArchiMate Elements adapted from « EA Modeling with ArchiMate & Sparx » - A. Sikandar Cap Gemini Canada

ArchiMate 2.0 – Some Important Viewpoints useful for the Concern of IT / Business Alignment Introductory Viewpoint Organization Viewpoint Actor Co-Operation Viewpoint Stakeholder Viewpoint Goal Realization Viewpoint Goal-Contribution Viewpoint Principle Viewpoint Requirement Realization Viewpoint Motivation Viewpoint Business Function Viewpoint Business Process Viewpoint Business Process Co-operation Viewpoint Product Viewpoint Application Behavior Viewpoint Application Co-operation Viewpoint Application Structure Viewpoint Application Usage Viewpoint Introductory Viewpoint Organization Viewpoint Actor Co-Operation Viewpoint Stakeholder Viewpoint Goal Realization Viewpoint Goal-Contribution Viewpoint Principle Viewpoint Requirement Realization Viewpoint Motivation Viewpoint Business Function Viewpoint Business Process Viewpoint Business Process Co-operation Viewpoint Product Viewpoint Application Behavior Viewpoint Application Co-operation Viewpoint Application Structure Viewpoint Application Usage Viewpoint Infrastructure Viewpoint Infrastructure Usage Viewpoint Implementation and Deployment Viewpoint Information Structure Viewpoint Project Viewpoint Service Realization Viewpoint Layered Viewpoint Landscape Map Viewpoint Migration Viewpoint Implementation and Migration Viewpoint Application Usage Viewpoint Infrastructure Viewpoint Infrastructure Usage Viewpoint Implementation and Deployment Viewpoint Information Structure Viewpoint Project Viewpoint Service Realization Viewpoint Layered Viewpoint Landscape Map Viewpoint Migration Viewpoint Implementation and Migration Viewpoint On the basis of the previous Balanced Score Card example input data, let us use some of these viewpoints within Sparx EA A viewpoint in ArchiMate is a selection of a relevant subset of the ArchiMate concepts and the representation of that part of an architecture

16 Shareholder requests “What we do have to improve…" “What we have to do to enhance “value creation” Branding displayed to customers Reminder : Contents of the ‘Balanced Score Cards to guide the Governance Aspects of the WebSale EA Operating Model Tactical and process level KPIs to specify here… © Birol Berkem GooBiz 2011/2012 How to handle such governance perspectives using TOGAF and ArchiMate ?

In the Preliminary Phase of TOGAF 9 : We start by modeling Baseline Architecture Capabilities of the WebSale Company

In the Preliminary Phase : Drivers, Assessments and Initial Goals of the EA may be modeled using the ‘Stakeholder Viewpoint’ 18 Business Drivers and Goals Principles, initial Requirements, …

In the Architecture Vision (Phase A) : Requirements can be discovered by decomposing Goals using the ‘Goal Realization’ and ‘Motivation ‘Viewpoints (1/2) 19

In the Architecture Vision (Phase A) : Business Functions are discovered by applying the ‘Goal Realization’ and ‘Motivation ‘Viewpoints (2/2) 20 How to better structure Capabilities to adapt them to changing requirements and align SOA components ?

In the Business Architecture Phase (Phase B) : Business Capabilities can be structured to be easily adapted to changes and align SOA 21 «BUSINESS CAPABILITY ORCHESTRATOR » How to describe process activities and guide SOA service level specifications on the basis of such a Capability Configuration ?

On the basis of the previous capability structure, requirements are assigned to ‘Service Points’ that are controled by the Capability Orchestrator 22 Service points allow capabilities to interact with their environment (cf. Phase G - Implementation Governance slide) « CAPABILITY ORCHESTRATOR »

Changes may be expressed using {constraints} applied to Business Capabilities Process Actions are to be reconfigured by considering new contraints to apply The Orchestration of Service Points activities may be precisely described using UML or BPMN Process Descriptions 23 Actions of the orchestrator service « makes call » to its service point behaviors to realize the « Register Visitor » Capability «BUSINESS CAPABILITY ORCHESTRATOR »

24 The Sparx EA Architecture Repository is continously enriched since definition of the Goals, Strategies, etc… (from OMG’s BMM) … through Process Descriptions BUSINESS GOAL STRATEGY BUSINESS PROCESS © Birol Berkem GooBiz 2013 Tactic level KPIs TACTIC SYSTEM REQUIREMENTS (based on process level KPIs)

Reminder : New Requirements were assigned to capitalize on the Business Capabilities « Managing Visitor Registration… » and « Targeted Mailing… » 25 Baseline Biz.Capabilities Target Biz.Capabilities As Capabilities require a combination of organization, people, processes and technology, we need to look for impacts of these target capabilities upon the Application and Infrastructure layers…

In Phases B and C : The ‘Layered’ Viewpoint supports the Impact Analysis for Implementing the « Managing Visitor Registration » Capability 26 Development of the Architecture Views across domains…

In Phases C, D : The ‘Layered’ Viewpoint supports the Technical Impact Analysis for Implementing the « Managing Visitor Registration… » Capability 27 Development of the Architecture Views across domains…

In Phase E : The Roadmap and underlying capabilities for Transition and Target Architectures are consolidated from phases B,C,D 28 Consolidating architecture descriptions Definition of the Roadmap Identifying opportunities for re-use and potential solution components

29 Deliverables and Work Package Actions are determined for the Transition Architecture (1/2) Consolidating architecture descriptions Definition of the Roadmap Identifying opportunities for re-use and potential solution components

Deliverables and Work Package Actions are finally determined for the Target Architecture (2/2) 30 How to use these deliverables to discover Organizational and IT Projects ? Traceability links that are automatically displayed for the selected deliverable are useful for Consolidating architecture descriptions

Phase F : Planning Implementation Projects 31 How to guide and align Projects by Architectural Constraints on the basis of Business Capabilities ?

32 Phase G – IMPLEMENTATION GOVERNANCE  In Phases B and C : We have seen how to structure Business Capabilities to establish the bridge toward SOA and assigned functional service expectations to related service points  In Phase G : We transform them into SOA Architectural Backbone elements (components, ports with required and provided interfaces) Let’s apply this step on our case study… 32

USE CASE (UC) Service/Request Point (UC Comp) BUSINESS CAPABILITY Internal Structures of Business Capabilities are kept « as is » to their previous descriptions in Phases A,B and C. Now, how to fill out Use Case and Service behaviors of these components ? «BUSINESS CAPABILITY ORCHESTRATOR » « B.C.O » « BUSINESS CAPABILITY ORCHESTRATOR » In Phase G : The Architectural Backbone of the system may be detailed on the basis of previous specifications of the ‘Capabilities’ Service/Request Point (SRV Comp) 33

UC and Service Behaviours may be specified using a choreography Visitor Question naire > Visitor [Registration] > Enter Visitor Visitor [Notification] Visitor [Entry] > Form > DATA SERVICES FUNCTIONAL LAYER UI « Service » and « UC-Comp » interactions may be implemented by a couple of (web service and its client) port components I_Entry « GOAL-DRIVEN SERVICE » BUSINESS LAYER BUSINESS & DATA LAYER 34 « B.C.O » We transform Actions of Service and Use Case partitions into methods of the corresponding components (cf. next)

Service/Request Point (SRV Comp) Service/Request Point (UC Comp) «GdS_Comp» Visitor_Registration:: Visitor_Entry -entry_processed: boolean -entry_requested: boolean -form_registered: boolean -form_validated: boolean +enter_visitor() : void -process_entry() : void {pre: entry_requested} -register_form() : void -validate_form() : void > In Phase G : Behaviors of the Components are plugged into the Architecture backbone to implement capabilities 35 «UC_Comp» Visitor_Registration:: Visitor_Entry -complete_fields: boolean -form_incomplete: boolean -visitor_entered: boolean +enter_visitor() : void -complete_fields() : void -fill_form() : void {pre : form_found} -thanks_for_entry() : void > BUSINESS CAPABILITY SRV-Cmp UC-Cmp « B.C.O » «BUSINESS CAPABILITY ORCHESTRATOR » « B.C.O » « BUSINESS CAPABILITY ORCHESTRATOR »

Conclusion The alignment of organisations with the changing needs of their customer requires: – Communicating key requirements, principles and models of the futur state of the enterprise (vision, strategies, principles, …) in order to ensure a coherent evolution, – Propagation of the changes to ensure a coherent reactivity until SOA Components Sparx EA ensures this alignment supporting the Business Motivation Model (BMM), Balanced Score Cards, Strategy Map, TOGAF 9, ArchiMate 2.0 and SoaML It also permits organizations to capitalize on their business knowledge by the means of Business Capabilities Complementary information to this presentation about the Agile Enterprise Modeling, IT and System Specifications can be found on our website : 36