Synchronizing_your_Business_Architecture ... - Sparx Systems

Synchronizing_your_Business_Architecture ... - Sparx Systems

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 Birol Berkem (Ph.D) TOGAF 9 Certified Enterprise Architect GooBiz.com 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 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 e-mail to [email protected] 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 TOGAFs 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): 329342. DOI:10.1023/A:1015096909316 Nikos C. Tsourveloudi , Kimon P. Valavanis (2002) 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.

What sources to provide inputs data for the Governance Aspects of an EA ? 6 Use Balanced ScoreCards / Strategy Map techniques to specify Governance Aspects of the EA Operating Model What we do have to improve" Tactical and process level KPIs to specify here Shareholder requests Branding displayed to customers What we have to do to enhance value

creation How to implement such governance perspectives using ArchiMate along the phases of TOGAF 9 ? Birol Berkem GooBiz 2011/2012 7 Business & IT Alignment using TOGAF 9 and ADM 2.0 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.

The TOGAF 9 ADM (Architecture Development Method) for developing an Enterprise Architecture 8 Phases in TOGAFs ADM A Summary Governance of implementation and Architecture Change Management 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 ,

Detailed Implementation and Migration Plan Work Packages and Transition Architectures Consolidating architecture descriptions Definition of the Roadmap Identifying opportunities for re-use and potential solution components 9 TOGAF 9 / SOA Initial Content MetaModel Elements Q : So, how to link such concepts to increase business agility ? A : Need a language that ensures coherence, traceability, completeness ! From the Open Groups TOGAF 9.1 Specifications 10 ArchiMate 2.0 adds value to TOGAF 9.1 Artifacts bringing consistency, traceability, completeness !

11 From the Open Groups 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 TOGAFs architecture artifacts TOGAF does not provide a specification ArchiMate 2.0 Layers to support TOGAF 9s Capability-Based Planning of the Enterprise Architecture 13 From the Open Groups TOGAF 9.1 and ArchiMate 2.0 Specifications Basic ArchiMate Concepts (Very Simplified !) BIZ.FUNCTION

14 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 Application Usage Viewpoint Infrastructure Viewpoint Organization Viewpoint Infrastructure Usage Viewpoint Actor Co-Operation Viewpoint Implementation and Deployment Stakeholder Viewpoint Viewpoint Goal Realization Viewpoint Information Structure Viewpoint Goal-Contribution Viewpoint Project Viewpoint Principle Viewpoint Service Realization Viewpoint

Requirement Realization Viewpoint Layered Viewpoint Motivation Viewpoint Landscape Map Viewpoint Business Function Viewpoint Migration Viewpoint Business Process Viewpoint Implementation and Migration Business Process Co-operation Viewpoint Viewpoint Product Viewpoint Application Behavior Viewpoint A viewpoint in ArchiMate is a selection of a relevant Application Co-operation Viewpoint subset of the ArchiMate concepts and the representation of that part of an architecture Application Structure Viewpoint Application Usage Viewpoint On the basis of the previous Balanced Score Card example input data, let us use some of these viewpoints within Sparx EA Reminder : Contents of the Balanced Score Cards to guide the Governance Aspects of the WebSale EA Operating Model

What we do have to improve" Tactical and process level KPIs to specify here Shareholder requests What we have to do to enhance value creation Branding displayed to customers How to handle such governance perspectives using TOGAF and ArchiMate ? Birol Berkem GooBiz 2011/2012

1 6 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 Business Drivers and Goals Principles, initial Requirements 18 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 20 ? In the Business Architecture Phase (Phase B) : Business Capabilities can be structured to be easily adapted to changes and align SOA BUSINESS CAPABILITY ORCHESTRATOR 21 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 class Functional Requirements by Serv ice Point Business Capability Visitor [Registration] {Goal-Value = 100 Registrants / week} G 3.2.2.a : If

Questionnaire [Filling] is aborted and abandon rate > 50%, ask the Marketing to review the questionnaire extend CAPABILITY ORCHESTRATOR GDBS include G 3.2.2 : Fill questionnaire {Incite Visitor to continue to fill the Questionnaire} Service Point Questionnaire [Filling]

include G 3.2.1 : Enter Visitor {Motivate Visitor to Complete Registration} Service Point Questionnaire [Review] G 3.3 : Review Questionnaire {Motivate Visitor to Complete its Registration Process} Service Point Visitor [Entry] Visitor [Registration]

include Service Point Bonus [Assignment] include Service Point Registration [Notification] Service points allow capabilities to interact with their environment (cf. Phase G - Implementation Governance slide) G 3.2.3 : Assign bonus G 3.2.3.a - If bonus_rate > 30 % then review bonus assignment rule G 3.2.5 : Send notification to the Visitor by e-mail

G 3.2.6 : Notify Sales by adding the new visitor to the list of visitors to turn into buyer... 22 The Orchestration of Service Points activities may be precisely described using UML or BPMN Process Descriptions act Description of the Visitor [Registration] Changes may be expressed using {constraints} applied to Business Capabilities BUSINESS CAPABILITY ORCHESTRATOR GDBS Visitor [Registration] {Goal-Value = 100 Registrants / week} Process Actions are to be reconfigured by considering

new contraints to apply realize G3.2-REGISTER VISITOR {MOTIVATE TO COMPLETE} VISITOR :ENTER VISITOR ASSIGN FIRST A BONUS TO MOTIVATE VISITOR TO COMPLETE ITS ENTRY THEN ADVERTISE ABOUT THE LOTTERY SYSTEM AT THE END OF THE REGISTRATION VISITOR [REGISTERED]

SYSTEM :ASSIGN BONUS :NOTIFY VISITOR MARKETING [QUESTIONNAIRE FILLED] :FILL QUESTIONNAIRE [ABORT & ABANDON_RATE > 50 % ] test questionnaire :REVIEW QUESTIONNAIRE [ABORT & ABANDON RATE <=

50%] Abandon End of review questionnaire Actions of the orchestrator service makes call to its service point behaviors to realize the Register Visitor Capability 23 The Sparx EA Architecture Repository is continously enriched since definition of the Goals, Strategies, etc (from OMGs BMM) through Process Descriptions BUSINESS GOAL STRATEGY Tactic level KPIs TACTIC

BUSINESS PROCESS SYSTEM REQUIREMENTS (based on process level KPIs) 24 Birol Berkem GooBiz 2013 Reminder : New Requirements were assigned to capitalize on the Business Capabilities Managing Visitor Registration and Targeted Mailing Baseline Biz.Capabilities business Motiv ation View point : Transform Visitors into B... Target Biz.Capabilities CRM SYSTEM class Motiv ation View point : T...

Archi Mate_Requi rem... Requirements::Send Targeted Mailing to Visitors using their Products of Interest implementation Proj ect View point TARGETED MAILING TO VISITORS FOR PRODUCTS OF THEIR INTEREST CRM SYSTEM class Motiv ation View point... MANAGING VISITOR REGISTRATION WITH THEIR PRODUCTS OF INTEREST AND MINIMIZING "ABANDON" Archi Mate_Requi re... Notify the Marketing and

Sales Units w ith Registered Visitors class M otiv ation View poi... Archi M ate_Requi r... Requirements::Register Visitors w ith their products of interest 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 Development of the Architecture Views across domains 26 In Phases C, D : The Layered Viewpoint supports the Technical Impact Analysis for Implementing the Managing Visitor Registration Capability Development of the

Architecture Views across domains 27 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 28 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

29 Deliverables and Work Package Actions are finally determined for the Target Architecture (2/2) Traceability links that are automatically displayed for the selected deliverable are useful for Consolidating architecture descriptions How to use these deliverables to discover Organizational and IT Projects ? 30 Phase F : Planning Implementation Projects How to guide and align Projects by Architectural Constraints on the basis of Business Capabilities ? 31 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) Lets apply this step on our case study 32 32 In Phase G : The Architectural Backbone of the system may be detailed on the basis of previous specifications of the Capabilities BUSINESS CAPABILITY ORCHESTRATOR USE CASE (UC) Service/Request Point (UC

Comp) Service/Request Point (SRV Comp) BUSINESS CAPABILITY BUSINESS CAPABILITY ORCHESTRATOR BUSINESS CAPABILITY ORCHESTRATOR B.C.O B.C.O UC and Service Behaviours may be specified using a choreography BUSINESS LAYER I_Entry <> GOAL-DRIVEN Visitor [Entry]

Visitor <> Visitor [Notification] [Registration] FUNCTIONAL LAYER UI B.C.O SERVICE <> Enter Visitor BUSINESS & DATA LAYER <>

<> <> Visitor act Description of actor / system interactions for rea... <> Question naire SRV-Comp UC-Comp Process Entry entry request <>

[form found] Fill Form UNCTIONAL LAYER VISITOR [REGISTRATION] Validate Form [form fill ed] DATA SERVICES Form [entry corrected] [i nvali d entry] Complete Fields

[form_checked_ok] Register Form Thanks for entry Service and UC-Comp interactions may be implemented by a couple of (web service and its client) port components End-of-entry We transform Actions of Service and Use Case partitions into methods of the corresponding components (cf. next) 34 In Phase G : Behaviors of the Components are plugged into the Architecture backbone to implement capabilities BUSINESS CAPABILITY ORCHESTRATOR

Service/Request Point (UC Comp) Service/Request Point (SRV Comp) BUSINESS CAPABILITY BUSINESS CAPABILITY ORCHESTRATOR BUSINESS CAPABILITY ORCHESTRATOR <> <> SRV-Cmp UC-Cmp GdS_Comp

Visitor_Registration:: Visitor_Entry 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 - 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 B.C.O B.C.O 35 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 : www.goobiz.com 36

Recently Viewed Presentations

  • The Northern Virginia HIV Service and Financing System

    The Northern Virginia HIV Service and Financing System

    The Northern Virginia HIV Service and Financing System Assessing Resources to Address an Era of Constrained Funding
  • CLB-Based Assessment Tools Centre for Education & Training

    CLB-Based Assessment Tools Centre for Education & Training

    Canadian Language Benchmark Literacy AssessmentCLBLA. ... Learners can test their receptive skills. ... Continuous support and maintenance of CLB-OSA and NCLC-AEL. Promotional materials available. Ongoing system generated survey of test users .
  • Program - ucviden.dk

    Program - ucviden.dk

    PROFESSIONAL ETHICS - IN PRACTICAL SOCIAL WORK Jens Eistrup School of Social Work UNBC October 12th 2017
  • &quot;Kill the Indian, Save the Man&quot; - tessa-nicolephotography.com

    "Kill the Indian, Save the Man" - tessa-nicolephotography.com

    What constitutes Cultural Genocide . Systematical destroying, eroding, or undermining of the integrity of a culture. Weakening and destruction of cultural values and practices
  • 5 Types of Empowerment - ednet.ns.ca

    5 Types of Empowerment - ednet.ns.ca

    1930's Changes & Affects 8.3.1 Analyze the impact of changing technology and socioeconomic conditions on differing prosperities and lifestyles in Canada in the 1930s.
  • Study Guide Review

    Study Guide Review

    Study Guide Review. Democracy . Every person has worth and all people are equal under the law. Athens. All free men over 18 were citizens. They all participated in the assembly where all citizens met to discuss issues.
  • Diapositive 1

    Diapositive 1

    Cette technique est encore utilisée - bien que modifiée - dans les trieuses modernes qui sélectionnent les fruits. À l'origine, on cueillait les canneberges à la main. Les producteurs ont ensuite utilisé des pelles en bois, munies d'une sorte de...
  • Diapositiva 1 - ESPE

    Diapositiva 1 - ESPE

    D-ViewCam ™ software de vigilancia IP de la cámara es un sistema de vigilancia integral diseñado para gestionar de forma centralizada múltiples cámaras IP para el hogar, pequeñas oficinas y oficina en casa (SOHO), o Pequeñas y Medianas Empresas (SMB)...