Presentation is loading. Please wait.

Presentation is loading. Please wait.

How to align IT/SOA on the basis of Changing Strategies and Capabilities ? TOGAF 9 and ArchiMate 2 on a short Case Study to drive SOA (Excerpts from the.

Similar presentations


Presentation on theme: "How to align IT/SOA on the basis of Changing Strategies and Capabilities ? TOGAF 9 and ArchiMate 2 on a short Case Study to drive SOA (Excerpts from the."— Presentation transcript:

1 How to align IT/SOA on the basis of Changing Strategies and Capabilities ? TOGAF 9 and ArchiMate 2 on a short Case Study to drive SOA (Excerpts from the « Goal-Driven and Capability-Based Development using ArchiMate 2 and UML ») Extended Version of the Enterprise Architect User Group Presentation – Nuremberg Oct 8, 2014 Birol Berkem (Ph.D) – Open Group Certified Enterprise Architect (TOGAF 9, ArchiMate 2) GooBiz.com Note : TOGAF 9 (The Open Group Architecture Framework) and ArchiMate 2 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 ArchiMate ® 2 and UML Models throughout TOGAF® 9 ADM phases in order to align IT with changing business strategies and capabilities It will also be presented soon as a webinar in the context of our partnership with iCMG :

2 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – TOGAFs Capability-Based Planning and ArchiMate 2 Layers – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and align related SOA process components – Updating the Architecture Repository – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Modeling the Roadmap, Transition Architectures and Work Packages – Modeling Implementation Projects Planning – The SOA Architectural Backbone at the Implementation Governance Phase Conclusion 2

3 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 assets (organization, person, process, technology). Adapted from "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:

4 Business Agility : The needs ! The alignment of organizations with the changing needs of their customers and environment requires: – Architecting business and IT resources of the extended enterprise to ensure a value-driven solution to these needs and capitalize on these structures in face of changes, – Communicating key requirements, principles and models of the future state of the enterprise (vision, goals, strategies, …) until the IT level to ensure a coherent evolution, Such an alignment makes necessary building an architecture framework that includes : – users, processes, information and technology, but also their internal and external relationships with their environment 4

5 What methodologies, architectures and specification languages to ensure a business agility ? What are the roles of the EA in capitalizing on the business knowledge and aligning IT with the changing strategies ? 5

6 Enterprise Architectures : Goals and Roles ! Enterprise Architecture enables effective execution of the enterprise strategy to achieve change of an organization ! Enterprise Architecture is usualy done to identify gaps between current and target architecture state of an organisation. It provides roadmap to achieve goals and deliver objectives to guide current and future projects of the organisation. 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. 6 What are the phases of TOGAFs Architecture Development Method (ADM) to ensure these goals and roles ?

7 Phases in TOGAFs ADM – A Summary 7 Architecture Planning : Business Drivers and Goals Concerns of Stakeholders, Principles, Requirements, Capability Assesment, Business Transformation 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 What sources to provide business inputs for the Governance Aspects of an EA ?

8 8 Shareholder requests What we do have to improve…" What we have to do to enhance value creation Branding displayed to customers Use Balanced ScoreCards (BSC) / Strategy Map techniques to specify Governance Perspectives for the EA Operating Model Tactical and process level KPIs to specify here… © Birol Berkem GooBiz 2012/2014 How to implement such governance perspectives along the phases of TOGAF 9 ?

9 9 Governance Perspectives of the BSC can be realized throughout Business, IS and Technology Capabilities using ADM Activities and processes to support the BSCs Business Process and Resource Perspectives ? How to implement actions that are part of the BSC Perspectives and monitor risks ? What systems will allow efficient execution of these processes in order to support related Perspectives ? What technical infrastructures will allow availability and security of the IT systems ? How to ensure integration and coherence of the B, C, D phase outcomes and find solutions during transformation programs ? Drivers and Goals to support the BSCs Financial & Customer Perspectives ? How to adapt business, IS and Technology Architecture Capabilities using such governance perspectives to increase business agility ? Business agility is the ability of a business to adapt rapidly and cost efficiently in response to changes in the business environment.

10 – 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 adds value to TOGAF 9.1 by bringing consistency, traceability, completeness ! – ArchiMate viewpoints are more detailed than TOGAFs architecture artifacts – TOGAF does not provide a specification language for descriptions and examples Use ArchiMate 2 for the Business & IT Alignment 10

11 Driving IT/SOA on the basis of Changing Strategies and Capabilities – Part I Business Agility & 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model & – TOGAFs Capability-Based Planning and ArchiMate 2 Layers – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and align related SOA process components – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Updating the Architecture Repository – Modeling the Roadmap, Transition Architectures and Work Packages – Coordinate Implementation Projects Planning on the basis of Architecture constraints – Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance Phase – Plug-in solution building-blocks (components) to achieve service behaviors with expected service levels … Conclusion 11

12 12 Q : So, how to link such concepts to increase business agility ? A1 : Need a Goal driven and Capability-Based methodology to adapt SOA implementation components to changes A2 : Need also a language to ensure coherence, completeness and traceability to support this continuous adaptation The Content MetaModel from the Open Groups TOGAF ®9.1 Specifications Capabilities are delivered by Functions that are accessed thru governed Interfaces provided by Business Services Drivers and Goals drive Capabilities Parameters are considered to control execution of processes that orchestrate functions to deliver Capabilities Application, Data and Technology layer components support Business Services that allow access to Business functions to deliver Capabilities Business & IT Alignment using TOGAF ® 9 / SOA Capabilities are abilities of the Organization that require a combination of Organization, People, Processes and Technology to achieve (TOGAF 9.1 Definition)

13 Use the TOGAFs « Capability-Based Planning » with ArchiMate 2 From the Open Groups ArchiMate ®2 Specifications 13 Goals and Objectives are initially fixed in the Preliminary and Architecture Vision Phases Capabilities are structured to mitigate Risks upon their internal functions, also to make impact analysis throughout IS and Technology layers Incremental RoadMap to reach the Target Architecture by reusing existing capabilities Work Packages of Actions to implement these Increments as well as to coordinate Implementation Projects Capability-Based SOA Backbone where solution components plugged into the architecture ones are orchestrated to realize related functions… How can this Goal & Capability-Driven Approach be realized by the Open Groups ArchiMate 2 Concepts and Relationships ? Capability Based Planning from the Open Groups TOGAF ®9.1 ArchiMate 2 adds value to TOGAF 9.1 by bringing consistency, completeness and traceability to support this Goal-Driven and Capability-Based continuous adaptation! (also by guiding application projects upon the enterprise architecture decisions)

14 Basic ArchiMate Concepts (Simplified !) 14 BIZ.FUNCTION Simplified ArchiMate Elements adapted from « EA Modeling with ArchiMate & Sparx » - A. Sikandar Cap Gemini Canada ArchiMate 2 brings consistency (well established notation with unambiguous relationship types), completeness (explicit modelling of requirements, principles, constraints,work packages, transition architectures), traceability (relationships to architecture components using views across multiple- domains).

15 ArchiMate 2 – 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 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 15

16 Driving SOA on the basis of Changing Strategies and Capabilities – Part II Business Agility & 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – TOGAFs Capability-Based Planning and ArchiMate 2 Layers – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and align related SOA process components – Updating the Architecture Repository – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Modeling the Roadmap, Transition Architectures and Work Packages – Coordinate Implementation Projects Planning on the basis of Architecture constraints – Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance Phase – Plug-in solution building-blocks (components) to achieve service behaviors with expected service levels … Conclusion 16

17 17 Shareholder requests What we do have to improve…" What we have to do to enhance value creation Branding displayed to customers Reminder : The Balanced ScoreCards (BSC) Governance Perspectives for the EA Operating Model © Birol Berkem GooBiz 2014 How to implement such governance perspectives along the phases of TOGAF 9 ? Tactical and process level KPIs to specify here… (cf. the Content of the Architecture Repository in Part III)

18 In the Preliminary Phase of TOGAF 9 : We start by modeling Baseline Architecture Capabilities of the Web Sale Company 18 How to adapt and structure these capabilities using a « Capability-Based Planning » ?

19 Reminder : TOGAFs ADM Phase Objectives and the « Capability-Based Planning » to align EA with Business Goals and Capabilities 19 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 © Birol Berkem GooBiz 2014 From the Open Groups TOGAF ®9.1 Specifications Lets start by considering Goals and Objectives Initially provided as part of the BSC Financial and Customer perspectives within the ADM Preliminary & the Architecture Vision Phases

20 In the Preliminary Phase : Drivers, Assessments and Initial Goals of the EA may be modeled using the ArchiMate Stakeholder Viewpoint 20 Business Drivers, Goals Principles, initial Requirements, … 20 How to discover Requirements on the basis of Stakeholders, Drivers and Goals ?

21 In Phase A : Requirements can be discovered by decomposing Goals using the ArchiMate Goal Realization and Motivation Viewpoints (1/2) 21 How to initiate Capability Assessment on the basis of Changing Strategies ?

22 Capability Assessment may be initiated here by assigning appropriate responsibilities to Baseline Capabilities on the basis of Changing Goals Business functions to deliver Target Capabilities can also be discovered using ArchiMate Viewpoints (cf. next slide) Baseline State assessment and Future State aspiration of the performance level of each capability, as well as impacts to the business organization resulting from the successful deployment of the Target Architecture may be modeled on the basis of these assignments within target capabilities (to be continued…) 22

23 In Phase A : Business Functions can also be discovered by applying the ArchiMate Goal Realization and Motivation Viewpoints (2/2) How to structure these Capabilities until the Technology Layer to mitigate risks, adapt them to changing requirements and align related SOA process components ?

24 Driving IT/SOA on the basis of Changing Strategies and Capabilities – Part III Business Agility & 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – TOGAFs Capability-Based Planning and ArchiMate 2 Layers – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and align related SOA process components – Updating the Architecture Repository – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Modeling the Roadmap, Transition Architectures and Work Packages – Coordinate Implementation Projects Planning on the basis of Architecture constraints – Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance Phase – Plug-in solution building-blocks (components) to achieve service behaviors with expected service levels … Conclusion 24

25 Structure capabilities until the Technology Layer on the basis of requirements and risks & align related SOA Processes 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – Basic Concepts, Layers and Viewpoints in ArchiMate 2 – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to mitigate risks, adapt them to changing requirements and align related SOA components – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Updating the Architecture Repository – Modeling the Roadmap, Transition Architectures and Work Packages – Modeling Implementation Projects Planning – Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance Phase – Plug-in solution building-blocks (components) to achieve service behaviors with expected levels … Conclusion 25 Lets continue by structuring Capabilities to mitigate risks upon functions that compose them and also to analyze impacts of their evolution throughout Application and Technology layers

26 In the Business Architecture Phase (Phase B) : Capabilities are structured to mitigate risks and to be easily adapted to changes… «BUSINESS CAPABILITY ORCHESTRATOR » How to guide corresponding functional service level expectations in order to align SOA process components then describe related process orchestration ? 26

27 On the basis of the previous capability structure, assign expectations to Service Points that are controled by the Capability Orchestrator (Phases B and C) Service points allow business capability components to interact with their environment (cf. Phase G - Implementation Governance focusing on the SOA Backbone) « CAPABILITY ORCHESTRATOR » 27 Then to describe the orchestration of service point activities we will use a process model (cf. next slide)

28 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 28 Actions of the orchestrator service « makes call » to its service point behaviors to realize the « Register Visitor » Capability «BUSINESS CAPABILITY ORCHESTRATOR »

29 29 The EA Repository is continously enriched since definition of the Goals, Strategies, etc… from the Business Plan and BSC Perspectives throughout Processes BUSINESS GOAL STRATEGY BUSINESS FUNCTION TO DELIVER THE « EXTENDED CRM CAPABILITY » © Birol Berkem GooBiz 2014 Tactic level KPIs from « BSC Business Process Perspectives » Some Actions of « BSC Business Process Perspectives » Identified as Tactics SYSTEM REQUIREMENTS (based on process level KPIs captured on the «BSC Business Process Perspectives ») 29 Now, we need to perform an impact analysis for implementing each required business capability until the Technology Layer using ArchiMate (cf. for Register Visitor function presented next) BUSINESS FUNCTION TO DELIVER THE « PORTFOLIO MANAGEMENT CAPABILITY » BUSINESS FUNCTION TO DELIVER THE « PORTFOLIO MANAGEMENT CAPABILITY »

30 In Phases B and C : The Layered Viewpoint supports the Impact Analysis for Implementing the « Managing Visitor Registration » Capability 30 © Birol Berkem GooBiz 2014 The impact analysis should continue to be performed until the Technical layer (cf. next slide) Development of the Architecture Views across Business and IS domains…

31 In Phases C, D : The Layered Viewpoint supports the Technical Impact Analysis for Implementing the « Managing Visitor Registration… » Capability 31 Development of the Architecture Views across IS and Technical domains… © Birol Berkem GooBiz 2014 How to consolidate the gap on the basis of this impact analysis and design the roadmap (cf. Part IV)

32 Driving SOA on the basis of Changing Strategies and Capabilities – Part IV Business Agility & 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – TOGAFs Capability-Based Planning and ArchiMate 2 Layers – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and align related SOA process components – Updating the Architecture Repository – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Modeling the Roadmap, Transition Architectures and Work Packages – Coordinate Implementation Projects Planning on the basis of Architecture constraints – Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance Phase – Plug-in solution building-blocks (components) to achieve service behaviors with expected service levels … Conclusion 32

33 Modeling the Roadmap, Transition Architectures and Work Packages to coordinate Implementation Projects 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – TOGAFs Capability-Based Planning and ArchiMate 2 Layers – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and align related SOA process components – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Updating the Architecture Repository – Modeling the Roadmap, Transition Architectures and Work Packages – Coordinating Implementation Projects Planning on the basis of Architecture constraints – Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance Phase – Plug-in solution building-blocks (components) to achieve service behaviors with expected levels… Conclusion 33 In this third step, we consider the consolidated RoadMap to reach the Target Architecture. Capability Increments for Transition Architectures will extend the existing business capabilities (initially starting by the Baseline ones) Work Packages of Actions to realize them as well as the Planning of the Implementation Projects will be coordinated on the capability basis… Lets start by drawing the Roadmap and its underlying capabilities for transition architectures

34 In Phase E : The Roadmap and underlying capabilities for Transition and Target Architectures are consolidated from phases B,C,D Consolidating architecture descriptions Definition of the Roadmap Identifying opportunities for re-use and potential solution components Lets continue by determining deliverables and work package actions to deliver the capability increments of the transition architecture

35 35 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 35 © Birol Berkem GooBiz 2014 And finally determined for the target architecture… (next slide)

36 Deliverables and Work Package Actions are finally determined for the Target Architecture (2/2) How to use these capability-driven deliverables to coordinate Organizational and IT Projects ? Traceability links that are automatically displayed for the selected deliverable are useful for Consolidating architecture descriptions 36 © Birol Berkem GooBiz 2014

37 Phase F : Coordinate the Implementation Projects Implementation Projects will be realized in Phase G on the basis of business, IS and technologic constraints imposed to the Architecture from phases B to E 37 © Birol Berkem GooBiz 2014 «BUSINESS CAPABILITY ORCHESTRATOR » B.C. MODEL FRAGMENT

38 Driving IT/SOA on the basis of Changing Strategies and Capabilities – Part V Business Agility & 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – TOGAFs Capability-Based Planning and ArchiMate 2 Layers – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and align related SOA process components – Updating the Architecture Repository – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Modeling the Roadmap, Transition Architectures and Work Packages – Coordinate Implementation Projects Planning on the basis of Architecture constraints – Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance Phase – Plug-in solution building-blocks (components) to achieve service behaviors with expected service levels … Conclusion 38

39 Structuring the Goal-Driven and Capability Based SOA Backbone 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 ArchiMate 2 – Phases in TOGAFs ADM – A Summary – TOGAF for SOA - Initial Content Meta-Model – TOGAFs Capability-Based Planning and ArchiMate 2 Layers – Modeling with ArchiMate 2 throughout TOGAF 9.1 ADM phases – Structuring Capabilities to track risk mitigation by function, adapt them to changing requirements and align related SOA process components – Performing Impact Analysis of Business Capabilities upon the Application and Technology layers – Updating the Architecture Repository – Modeling the Roadmap, Transition Architectures and Work Packages – Modeling Implementation Projects Planning – Structuring the Goal-Driven and Capability Based SOA Backbone at the Implementation Governance Phase – Plug-in solution building-blocks (components) to achieve service behaviors with expected levels… Conclusion 39 In this last step (Phase G), we focus on the Goal-Driven and Capability-Based SOA Backbone (of Architecture Building Blocks) where solution components (building-blocks) are to be plugged within Service Ports whose behaviors are to be orchestrated by Capability Orchestrators to realize related functions…

40 USE CASE (UC) Service/Request Point (UC Comp) Business Capability Component «BUSINESS CAPABILITY ORCHESTRATOR » « B.C.O » « BUSINESS CAPABILITY ORCHESTRATOR » In Phase G : The SOA Backbone of the system is specified being aligned on the business functions, requirements and expected service levels to deliver Capabilities Service/Request Point (SRV Comp) © Birol Berkem GooBiz 2013 Internal Structures of the SOA Business Capability Component are kept conform to the published Capability Model Fragments (Phases B to F) - Thus, we just have to describe SBBs to plug-in into these ABBs (UC and service points above ) 40

41 UC and Service Solution Building Blocks (SBBs) may be specified using a service choreography Visitor Question naire > Visitor [Registration] > Visitor [Entry] Visitor [Notification] Visitor [Entry] > Form > DATA SERVICES FUNCTIONAL LAYER UI « UC-Comp » and « SRV-Comp » interactions for the User Story « Enter Visitor » may be implemented by a couple of web service port components I_Entry « GOAL-DRIVEN SERVICE » BUSINESS LAYER BUSINESS & DATA LAYER « B.C.O » To fill-in use case and service ABBs of the Architecture Backbone by the corresponding solution behaviors, we will transform actions of UC-Comp and SRV-Comp partitions into methods before plugging them as SBBs (cf. next) 41

42 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 : Solution Components (SBBs) are plugged into the Service Points (ABBs) of the Architecture backbone to implement business functions 42 «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 Component SRV-Cmp UC-Cmp « B.C.O » «BUSINESS CAPABILITY ORCHESTRATOR » « B.C.O » « BUSINESS CAPABILITY ORCHESTRATOR » 42

43 Summary - Driving SOA through TOGAFs ADM Phases using ArchiMate and UML 43 In Phase E : The Roadmap and capabilities are consolidated from phases B,C,D In Phase B,C,D : Impact Analysis of new Capabilities is performed across Architecture Layers In Phases B & C : SOA Architecture Constraints are also considered within Capability Structures In Phases Prelim. & A : Capabilities are assessed on the basis of Goals, Principles,Requirements,… In Phases E & F : Implementation Projects are planned to realize Capabilities In Phases G & H : Capability Driven SOA Backbone Components are Implemented to realize expected functions and Changes are Managed In Phase B : Capabilities are first structured depending on the risks and requirement basis

44 Conclusion The alignment of organizations with their changing environment requires a Goal and Capability Driven Development that allows : – Communication of key requirements of the future state of the enterprise (strategies, principles, vision …) on Goal and Capability basis to ensure a coherent evolution, – Propagation of the changes to ensure a coherent reactivity until the Technology layer SOA solution building-blocks (components) EA ensures this alignment by its support to the Business Motivation Model (BMM), Balanced Score Cards, Strategy Map, TOGAF 9, ArchiMate 2 and SoaML standards 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 : Its complementary presentation as a webinar entitled How to increase business agility using TOGAF and ArchiMate will be organized soon in the context of our partnership with iCMG : 44


Download ppt "How to align IT/SOA on the basis of Changing Strategies and Capabilities ? TOGAF 9 and ArchiMate 2 on a short Case Study to drive SOA (Excerpts from the."

Similar presentations


Ads by Google