Enterprise Architecture Introduction Why Enterprise Architecture aligning Business

Enterprise Architecture – Introduction… Why Enterprise Architecture - aligning Business with IT 1 6. 11. 2020

… with the intent of avoiding chaos… … and even if an individual house is well architected, if each house is different (e. g. different electricity voltage, water pressure) then the city will not work… 2 6. 11. 2020

Benefits with Enterprise Architecture • Align business and IT objectives and resources • Efficient decision-making through established principles, models, standards, and processes • Improve communication, prioritization, and governance of initiatives • Increase time-to-market by reducing lead time for installing and testing technology (have the technology ready before it is needed) • Simplify integration problems through compliance with architecture • Reduce costs by retiring duplicative or outdated assets • Provide a foundation for skills development • Follow an established roadmap for infrastructure development 3 6. 11. 2020

Following phases are defined for the Enterprise Architecture evolvement es Introduction Input l cip in Pr et rg on si Vi Roadmap Ta • EA Definition • Goals • Structure • Layers • Roles • Governance • Deliverables • Measurements 4 6. 11. 2020 • Problem Statement architecture • business • application • information • technology • infrastructure • governance • processes • Principles • what it is • how to define • what it defines • Perspective • Architectural changes • Business changes • Organization • EA realization • Target Vision • common understanding • definition of architecture • architectural framework • ‘to be’ architecture • ownership of HBG EA

Enterprise Architecture Definition… 5 6. 11. 2020

…. there are several – here is one EA enables: § Alignment between Business and IT § Governance § Transition § Realisation of Business and IT Strategies An IBM study agreed a definition that balances EA’s “upstream” and “downstream” values EA provides reference material in many forms “The EA discipline defines and maintains the architecture models, governance and transition initiatives needed to effectively co -ordinate semi-autonomous groups towards common business and/or IT goals. ” goals. “ EA works at many levels 6 6. 11. 2020 EA ensures the architecture is maintained and used EA can address the business and IT domains EA is not just passive or reactive, it is proactive

Two important aspects of Enterprise Architecture “upstream” (doing the right things) and “downstream” (doing things right) “good navigation” – Upstream: Doing the right things • Identifying, funding & resourcing the most important programmes, in line with the business strategy and within the investment budget, in the right sequence, and with effective programme management and control. – Downstream: Doing things right “good engineering” • Ensuring the solutions delivered by these programmes meet the needs of the business, work within the existing IT environment and contribute towards the realisation of the enterprise’s IT strategy. 7 6. 11. 2020

Enterprise Architecture layers and structure 8 6. 11. 2020

The gap between Business and IT is something that has to be manageable and controlled; how to plan, build and maintain Enterprise Strategy Business Opportunity Bus Strategy IT Strategy Fire & Hope Business Operating Environment and IT Infrastructure Programme Architecture Soln Outline Macro Design Micro Design Devt, etc. Programme Architecture Soln Outline Macro Design Micro Design Change Programs 9 6. 11. 2020 Devt, etc. Technology Availability

Enterprise Architecture can be the ‘vehicle’ to align Business with IT Enterprise Strategy Program Focus Enterprise wide Focus Strategy 10 Business Opportunity Bus Strategy IT Strategy Enterprise Architecture Planning Design and Delivery Business Operating Environment and IT Infrastructure Programme Architecture Soln Outline Macro Design Micro Design Devt, etc. Programme Architecture Soln Outline Macro Design Micro Design Change Programs 6. 11. 2020 Devt, etc. Technology Availability

Good EA planning and good EA engineering can be managed using a EA framework and a EA method Strategy Enterprise Strategy Program Focus 11 Bus Strategy IT Strategy Technology Availability = “the city’s purpose & goals” Enterprise Architecture Enterprise Capabilities Design and Delivery Business Architecture IS Architecture Technology Architecture Business Operating Environment and IT Infrastructure Programme Architecture Soln Outline Macro Design Micro Design Devt, etc. Programme Architecture Soln Outline Macro Design Micro Design Change Programs 6. 11. 2020 = “the city plan” Governance Planning Transition Planning Enterprise wide Focus Strategy Business Opportunity Devt, etc. System Design = “the buildings”

Enterprise Architecture links strategy formulation through ensuring that “the right things are done” - upstream EA Strategy Enterprise Strategy Program Focus Enterprise wide Focus Strategy 12 Business Opportunity Bus Strategy IT Strategy Technology Availability = “the city’s purpose & goals” Doing the right things! Enterprise Architecture ”Upstream EA” Enterprise Architecture Good Navigation = “the city plan” Planning Design and Delivery Business Operating Environment and IT Infrastructure Programme Architecture Soln Outline Macro Design Micro Design Devt, etc. Programme Architecture Soln Outline Macro Design Micro Design Change Programs 6. 11. 2020 Devt, etc. System Design = “the buildings”

Enterprise Architecture assets ensure that “things are done right” when building specific solutions – downstream EA Strategy Enterprise wide Focus Strategy Business Opportunity Bus Strategy IT Strategy Technology Availability = “the city’s purpose & goals” Doing the right things! Enterprise Architecture = “the city plan” Planning ”Downstream EA” Good Engineering Program Focus Doing things right! 13 Design and Delivery Business Operating Environment and IT Infrastructure Programme Architecture Soln Outline Macro Design Micro Design Devt, etc. Programme Architecture Soln Outline Macro Design Micro Design Change Programs 6. 11. 2020 Devt, etc. System Design = “the buildings”

Enterprise Architecture Framework Organising, storing and using architectural information (models and building blocks) in support of transition planning and delivery project guidance 14 6. 11. 2020

The EA Framework consist of horizontal- and vertical aspects… External to architecture Functional Aspect of Architecture Operational Aspect of Architecture Enterprise Capabilities Business Architecture Information Systems Architecture Technology Architecture 15 6. 11. 2020 A good EA is driven from an assessment of the capabilities needed by the enterprise It is helpful to describe external influences in a consistent manner, such as “requirements” We need to include elements that help us deploy our Business & IT systems in a consistent and joined up fashion

…and then sub-dividing it into a number of “vertical” aspects to complement our “horizontal layers” External to architecture (Strategy) Events Operational Aspect of Architecture Functional Aspect of Architecture People Activities Data Location Enterprise Capabilities Business Architecture Information Systems Architecture We need to describe the events that the architecture must support, in terms of their business purpose and their operational characteristics Technology Architecture 16 6. 11. 2020 We need to describe the basic building blocks from which our systems are built. Typically, in an IT centric EA, these can be categorised into… We need to describe the operational structure needed and used by the enterprise; together with the manner in which the enterprise’s building blocks are distributed across this structure . . . And data; and the things required to People, their roles and support their storage skills; and the things and use within the required to give them enterprise’s IT systems access to the. . . Activities and enterprise’s IT Processes; and the systems… things required to automate and support their execution within the enterprise’s IT systems…

This gives us a powerful 2 dimensional EA architecture framework, the WORK PRODUCTS - of the EA Consulting Method’s architecture neighbourhoods Operational Aspect External to architecture Events But what. Strategy is the nature of these work products? Functional Aspect of Architecture People Activities Data Enterprise Capabilities Models? Sets of Building blocks? Both? Business Architecture We need to think again about these relationships… Information Systems Architecture Technology Architecture 17 6. 11. 2020 of Architecture Location Work Product

The EA Framework provides the structure for defining and managing Enterprise Architecture assets and functions as a reference catalog for use in solution architecting 18 Enterprise Capabilities and architecture principles are defined to reflect and be consistent with the business direction i. e. business strategy and IT strategy Business Architecture Business components or activities define “what the business needs to do” to realize the capabilities i. e. a business architecture has no regard for the use of automation Information Systems Architecture Application & data (business-specific) and technology (business-independent) services define “what IT needs to do” to support the business activities. An Information Systems Architecture describes those aspects of the business that are to be automated – sometimes known as the “business dependent IT architecture” Technology Architecture Application and technology components are structured into standard arrangements called Reference Architectures i. e. a Technology Architecture describes the underlying, “business independent” IT architecture needed to support automation 6. 11. 2020

The Enterprise Framework consist of Work Products – called ABB (Architectural Building Blocks) - used for documentation and guiding in system modelling External to architecture Strategy Strategic CBM Enterprise Capabilities EA Guiding Principles Events Business Scenarios People Activities Skills Resources Business Architecture Bus Strategy WPs. Strategy Bus WPs Enterprise KPIs And/or Data Enterprise Info Model Business Activity Mdl Usage matrices Information Systems Architecture Standard Use Cases Skills Activities Business Information Application Groups User Groups Standard IS NFRS Technology Architecture 19 6. 11. 2020 IT Systems Management WPs IT Systems Operational WPs Business Structure And/or Business Operational RAs Data Stores Deployment Unit Matrices Placement Guidelines Application Services Model Function Presentation Services Locations Model AC Map Data Application Services Deployment Units IS) IS Operational RAs IS Functional Reference Architectures IT Strategy WPs Usage matrices Locations List Business Services Model Component Business Functional Reference Architectures IS Strategy WPs Location Information Resources Activity Resources Roles Business Event List Operational Aspect of Architecture Functional Aspect of Architecture Data Services IT Components (s/w & h/w) Technology Functional Reference Architectures IT Nodes Technology Operational RAs

Enterprise Architecture – using a Method 20 6. 11. 2020

The structure of the architecture neighbourhoods in the EA Method Client Objectives Proposal and Engagement Planning Enterprise Capabilities Transition Emerging Opportunities Strategic Gap Analysis Business Architecture Current Environment IS Architecture Technology Architecture Governance 21 6. 11. 2020

The EA Method provides the process of developing the EA Framework Enterprise Capabilities Transition Initiatives Critical issues, opportunities & rec’ns Transition Capability Model Management Action Plan Business Directions Strategic CBM Resources Transition Management Strategy EA Guiding Principles Business Scenarios EA Overview Diagram Integrated Transition Plan Business Architecture Strategic Gap Analysis Business Activity Mdl Usage Matrices EA Neighborhood Gaps Ident’n EA Neighborhood Assessments Enterprise Information Model Roles Technology Architecture Application Groups Standard Use Cases Standard NFRs User Groups 22 6. 11. 2020 Enterprise KPIs Principles, Policies & Guidelines IS Reference Architectures Governance Business Reference Architectures IS Architecture Data Stores IT Nodes Technology Reference Architectures Decision Model Business Structure Locations EA Capability Assessment IT Components Business Event List Architecture Management Processes Architecture Management Roles / Resp Deployment Unit Matrices Deployment Units (IS) Placement Guidelines Architecture Management Metrics

From the ‘Enterprise Architecture’ on ‘one page’ there is a relation to the EA Method and the EA Framework Enterprise Architecture Method Enterprise Architecture on one page Enterprise Capabilities Business Architecture IS Architecture 23 6. 11. 2020 Technology Architecture Enterprise Architecture Framework

Capability Model Business Directions Strategic CBM Resources EA Overview Diagram EA Guiding Principles Showing only a few, representative, work product dependencies Technology Architecture Business Scenarios Enterprise Architecture Framework Business Architecture Business Activity Mdl Enterprise Usage Information Matrices Model Roles Data view Enterprise Capabilities User view Functional view The notion of work product dependencies hints at another dimension in which to think about an EA’s architecture framework Business Event List Business Structure IT Architecture Enterprise KPIs Business Reference Architectures Business Architecture Locations Users IS Architecture Market Business Plans Insured Party Sponsoring Organization Prospects POLICY Insured Objects Policy Claimant Claim Service Providers. Producer Third Parties IT Components IT Nodes Technology Reference Architectures Application Groups Data Stores User Groups 24 6. 11. 2020 Applications IS Architecture. Deployment Standard Use Cases Standard NFRs IS Reference Architectures Unit Matrices Deployment Units (IS) Placement Guidelines Technology Architecture Info Objects Insurance Product. Policy Financials Producer Compensation Business Partners External Agencies. Legal & Recovery. Training, Actions Education, Advice Inquiries Data Technology Architecture

We can develop this way of thinking about an EA architecture framework a little more. Business Architecture Functional Aspect of Architecture Enterprise Architecture Framework A business architecture has no regard for the use of automation Business Architecture IT Architecture Information Systems Architecture A technology architecture describes the underlying, “business independent” IT needed to support automation 6. 11. 2020 Technology Architecture 25 An information systems architecture describes those aspects of the business that are to be automated – sometimes known as the “business dependent IT architecture” “line of automation” Users Market Business Plans Insured Party Sponsoring Organization Prospects POLICY Insured Objects Policy Claimant Claim Service Providers Third Parties Applications Info Insurance Product Policy Financials Objects Claim Producer External Agencies Producer Compensation Business Partners Legal & Recovery Actions. Training, Education, Advice Inquiries Data Technology Architecture “line of business interest”

Enterprise Architecture Deliverables From the abstract EA level to concrete documentations 26 6. 11. 2020

ALL deliverables created by Solution Architects across the business and IT architecture domains should, ideally, be guided by the EA’s framework… PLAN BUILD Enterprise Architecture Programmes & Projects Business Architecture Business Solution Work Products RUN 1 2 n Business Infrastructure BA WP Business and IT environment BA WP IT Solution Requirements Analysis WPs IS Architecture IS Arch WP Information Systems Infrastructure IT Solution Architecture WPs Technology Architecture Technology WP WP Solution Guidance 27 Technology Infrastructure 6. 11. 2020 Solution Deployment

…which may be at its most powerful when the Solution Architect also uses the Work Products PLAN BUILD Enterprise Architecture Business Architecture BA WP RUN 1 Programmes & Projects Business Solution Work Products Business Events Business Process Model BA WP Logical Data Solution Model Business Roles Etc. 2 n Business and IT environment KPIs Solution Business Structure Involved Locations Business Infrastructure IT Solution Requirements Analysis WPs Solution Use Cases IS Architecture IS Arch WP Functional Aspect Technology WP Solution Guidance 28 Etc. Technology WP WP 6. 11. 2020 Solution NFRs Information Systems Infrastructure IT Solution Architecture WPs IS Arch WP Technology Architecture SCD Business Dependent components Component Model Business Independent components Architecture Overview Diagrams Deployment Units Operational Aspect Conceptual Operational Model Specified/ Physical OM Logical Operational Model Etc. Solution Deployment Technology Infrastructure

Enterprise Architecture Governance – ‘doing it right’ “Balancing good Enterprise Design with good Solution Design” 29 6. 11. 2020

EA Governance neighborhood - the Architecture Management Processes, Roles, Responsibilities. Client Objectives Proposal and Engagement Plan Enterprise Capabilities Capability Model Transition Initiatives Critical issues, opportunities & rec’mendation s Managemen t Action Plan Transition Managemen t Strategy EA Neighborhood Assessments Business Architecture Emerging Opportunities ETF Skills Decision Model 6. 11. 2020 Business Reference Architectures Functional Application Services Model IT Nodes User Groups Reference Architectures Functional Infomation Business Structure Business Event List Component Business Model Current Environment EA Capability Assessment Technology Architecture 30 Business Services Model Activities IT Components Business Scenarios EA Overview Diagram Integrated Transition Plan Strategic Gap Analysis EA Neighborhood Gaps Ident’n Resources EA Guiding Principles Business Directions Strategic CBM Locations Operational IS Architecture ACMap Function Data IS deployment units IS Reference Architectures Functional Placement Guidelines Operational Principles, Policies & Guidelines Governance Architecture Management Processes Architecture Management Roles / Resp Architecture Management Metrics

Governance in a context of Enterprise Architecture Strategic intent Are we still moving in the right direction Are our target architecture still right? Business Architecture Governance Enterprise IT Architecture Functional Operational EA Transition "These are the projects we should do” Are we doing these projects the way we said we want them done? "This is the way these projects should be architected” Solution Outline “Business as Usual” project prioritisation & planning Solution Outline Macro Design Micro Design Build Cycle Deployment Solution Projects 31 6. 11. 2020 Build Cycle Deployment Strategic delivery

An enterprise will use its Enterprise Architecture to guide the interpretation of its business and IT strategies across the multiple layers of its development Strategy Architecture Enterprise Architecture Dev’t Programme Infrastructure Architecture Programme, or Solution Architecture Project P P Architecture Dev’t 32 6. 11. 2020 Dev’t Infra. Proj D D D

The Enterprise Architecture Governance consist of ‘three bodies’ § Ensure solution designs comply with the architecture § Maintain the architecture Architecture Review Board § Decides on which architecture is best suited for the needs of the enterprise § Decides when a change in the architecture is needed § Prioritise Initiatives § Uses the architecture to best satisfy the project’s needs 33 6. 11. 2020 Technical Review Board Architecture Sponsors Enterprise Architects Project Design Authority Solution Architects

We have the ‘important peoples’ – approving the architecture… Invited Enterprise Architects Council chair Chief Architecture Review Board Business Representatives Technical Review Board a. k. a. “Architecture Council”: maintaining the authority of the EA ARB TRB Project Design Authorities 34 6. 11. 2020 DA

…and we have the ‘clever peoples’ - creating the architectures Chief Architect Business experts (on secondment) Architecture Review Board Project Architects (on secondment) Project Design Authorities 35 6. 11. 2020 Technical Review Board a. k. a. The Office of the Chief architect: maintaining the vitality and use of the EA Enterprise Architects ARB TRB DA

…and we have the peoples who will use the architecture in the solution projects Architecture Review Board Technical Review Board ARB Solution Projects with Design Authorities TRB Project Design Authorities 36 6. 11. 2020 DA

These three bodies exercise a number of different processes… Is used by the TRB Co nf or m an ce ity ARB Co s on i t p ce mm TRB un Ex Used by all 6. 11. 2020 l a t i V Enterprise Architecture Management Processes Is used by the ARB 37 Is used by the TRB Selec tion Is used by the ARB ica DA tio n

. . that work together to ensure the architecture is managed Co nf or Selec ti on and exploited to the benefit of the enterprise as a whole m an ce Making an EA on pti ce Ex s Using an EA Use Pu ate bli sh e Cr rn 38 6. 11. 2020 … … … Vitality S e P r A o v p l p Ai i l cc c C e i P q y o s c e u R l a r i e W A On Demand –B Technology Overview – l BP t sr. I dpn ao uar Detail View i e ao P sr be s. P o B n d rt L p. C D o ek s et io n a E i to u a o W l df e r gil n. M Tt c o. S s ie l r an ee CC e m L eri n a o r b O c t i M stt o a n sm zr ga r ye w i seaa n p s E n vat A /o Sc t o d i n a e vn it rl e c � Bei h Cnii B e c ecoi c s a. R ar e i c i M Cne n ono e oo� savt s n s S ng t tsn s eiti t l i yt g n. F ne s doci r l v … m ns. Sr e. Sr t ee i S ne a a cne i S cr e Ogs t n t M ttvr a S tm e r i g y n r e ivi v e r … o c o oci v a r rw i v h n o n S g v c i i e sc e e e i r es c c s r m c ek s e t e v e e s s r i n s s a c t t e i s o n ve Go Vitality Enterprise Architecture Management Processes lity Vita Co mm un ic ati o n

Enterprise Architecture as a Management Tool Strategic and long term; Value Proposition General Management Business Vision Product Development Market Needs Operation Architecture Office Technical Vision Business Product Roadmap Planning and Design Product Line Plans Architecture Principle, Vision Architecture Roadmap Construction and Delivery 39 6. 11. 2020

Enterprise Architecture Measurements ”If you can’t measure it, you can’t manage it” 40 6. 11. 2020

Metrics – how do we know EA is providing us value Why should you measure? What should you measure? How do you measure? What should you do with measurements? What are the metric traps? 41 6. 11. 2020

The Value of EA Metrics • Helps us understand how activities contribute to business results • Motivates those responsible to reach highest potential • Guides / Drives decision making and behavior • Leverages strengths – identifies weaknesses / opportunities • Helps in resource allocation • Increases competitive edge through the deployment of technology 42 6. 11. 2020

Metrics –”If you can’t measure it, you can’t manage it” IT and Business Metrics Scorecard EA metrics score cards EA Metrics Scorecard Metrics Value to the Business Cost Savings $6. 3 M Costs in costs savings identified byby having EA mission and team in place $4. 3 M Costs in costs reduction identified byby having EA mission and team in place 15 specific Instances instances of reuse or or integration savings from having EA discipline in place 5 specific Instances instances where thethe risk has been mitigated Cost Avoidance Integrationand and. Reuse Risk Reduction Time to to Market 18 instances where EA has Instances where EA reduced has reduced the time to market Quality Instances EA effected 7 instances where EA effected measurable quality improvement Leverage 43 R 6. 11. 2020 L 3 instances Instances of Leverage Resources not within CIO Office

Measurement – example 44 6. 11. 2020

Hansabank Enterprise Architecture input es Introduction Input l cip in Pr et rg on si Vi Roadmap Ta • EA Definition • Goals • Structure • Layers • Roles • Governance • Deliverables • Measurements • Problem Statement architecture • business • application • information • technology • infrastructure • governance • processes For the ‘Input’ Team Exercise you are asked to use these ‘architecture viewpoints’ 45 6. 11. 2020 • Principles • what it is • how to define • what it defines • Perspective • Architectural changes • Business changes • Organization • EA realization • Target Vision • common understanding • definition of architecture • architectural framework • ‘to be’ architecture • ownership of HBG EA

Defining Principles Fundamental truths or propositions which an organisation will use to make decisions about the selection, utilisation and deployment of all business and IT resources and assets, across the enterprise 46 6. 11. 2020

Enterprise Architecture Principles es Introduction Input l cip in Pr et rg on si Vi Roadmap Ta • EA Definition • Goals • Structure • Layers • Roles • Governance • Deliverables • Measurements 47 6. 11. 2020 • Problem Statement architecture • business • application • information • technology • infrastructure • governance • processes • Principles • what it is • how to define • what it defines • Perspective • Architectural changes • Business changes • Organization • EA realization • Target Vision • common understanding • definition of architecture • architectural framework • ‘to be’ architecture • ownership of HBG EA

Principles are defined as part of the Governance Neighbourhood in the Enterprise Architecture Method Client Objectives Enterprise Guiding Principles Proposal and Engagement Planning Transition Initiatives Transition Enterprise Capabilities Capability Model Management Action Plan Resources EA Guiding Principles Transition Management Strategy Critical issues, opportunities & rec’ns Business Directions Strategic CBM Business Scenarios EA Overview Diagram Integrated Transition Plan Business Architecture Strategic Gap Analysis EA Neighborhood Gaps Ident’n EA Neighborhood Assessments Emerging Opportunities EA Capability Assessment Usage Matrices Enterprise Information Model Roles Application Groups Standard Use Cases IT Nodes Standard NFRs User Groups 48 6. 11. 2020 Decision Model Principles, Policies & Guidelines Business Structure Enterprise KPIs IS Reference Architectures Governance Business Reference Architectures IS Architecture Data Stores Technology Reference Architectures Project Guiding Principles Business Event List Locations Current Environment Technology Architecture IT Components Business Activity Mdl Architecture Management Processes Architecture Management Roles / Resp Deployment Unit Matrices Deployment Units (IS) Placement Guidelines Architecture Management Metrics

It is convenient to classify EA Principles to assist in understanding and communication. 15 De to 2 Pr tail 0 inc ed ipl es 8 Gu to 10 Pr idin inc ipl g es Used for the construction of EA Used by the Solution Data Application Projects Guiding Governance Principles Usage Principles Guiding Principles: § Executive-level focus § Strong business flavour Detailed Principles: § Focus on more detailed and specific principles § Tend to have more of a technology focus • Policies and Standards will affect all levels of Principles • Architecture Decisions are Project Centric 49 6. 11. 2020 Used to control and manage EA

Relation between Policy, Guiding Principle, Principle and Architectural Decision Static Change over time to meet new Requirements Policy Business Guiding Principle Enterprise Architect Principle Architectural Decision IT 50 6. 11. 2020 Solution Architect

Principles have a well-defined structure … • Name – A short name or title to identify the Principle • Rational – A statement of the Principle – The rationale or impetus behind the Principle • Implication – The consequences of adopting the Principle: potential transition initiatives, costs, and other implications 51 6. 11. 2020

Effectiveness of principles is dependent upon some key success factors • Ownership – By Architecture Review Board. • Engagement & Involvement – Created and endorsed by business and IT executives who have the authority to enforce. – Top-down support through leadership and action. • Compliance Process – Compliance to Principles needs to be part of governance process. • Communication – Architecture orientation and training. – Communication to all stakeholders and participants. 52 6. 11. 2020

The process of construction of Principles involves… Input Process Output Strategic Directions Define Principles Capability Model Key Business Requirements Interview Results Define Business Linkages (matrix) Validate Principles Used For Business Architecture IS Architecture IT Architecture Governance § The process is depicted sequentially for the sake of simplicity. In practice considerable iteration is involved. § Maintain a list of issues, decisions, assumptions, and transition considerations 53 6. 11. 2020

Categories for Principles should be selected to address known issues and guide the Business and IS/IT organization in making decisions. Business Customer access and relationships Leverage of shared resources Business flexibility and growth Infrastructure of acquired businesses Data Common data definitions Centralized control Remote access Ownership Placement Industry standard formats Applications New development - level of customization Shared components Buy vs Build Vendor package integration Ease of use Product vs. Process Host/server vs. client centric design point 54 6. 11. 2020 Organization & Management Business - IT partnership Business unit vs. corporate responsibility Business unit vs. IS responsibility Architecture compliance Systems Management Service level agreements Problem, change Configuration, Security Library, distribution Backup and recovery Training and Skills Technology Aggressiveness -Leading edge vs. early adopter vs. mainstream Architecture - Proprietary vs. open, Tiers of client/server Network - Inside, clients, business partners

After Principles are identified and categorised they need to be positioned in terms of impact and acceptance. This facilitates prioritisation and final selection. principle Acceptance of Principle principle explore inclusion principle include principle principle principle exclude principle Not Acceptable No Benefit 6. 11. 2020 principle 55 principle Questions to Consider: How acceptable is this principle? § Will the culture accept it? § Are there barriers or constraints for implementation? § Are there associated business risks? explore acceptance What is the impact of the principle? concerns principle Major Benefit Impact of Principle § How critical is it to achieving benefits? § To what extent has it already been implemented?

The process of developing Principles can … § Describe impact of business goals being promoted by executives. § Clarify how business goals can be implemented effectively. § Principles can guide and simplify the prioritisation and approval of business initiatives. § Facilitate discussion of issues about the way decisions are made and provide a forum to address associated concerns. 56 6. 11. 2020

Enterprise Architecture Target Vision 57 6. 11. 2020

Hansabank Enterprise Architecture Target Vision es Introduction Input l cip in Pr et rg on si Vi Roadmap Ta • EA Definition • Goals • Structure • Layers • Roles • Governance • Deliverables • Measurements 58 6. 11. 2020 • Problem Statement architecture • business • application • information • technology • infrastructure • governance • processes • Perspective • Target Vision • common understanding • Architectural changes • definition of architecture • Business changes • architectural framework • Organization • EA realization • ‘to be’ architecture • ownership of EA

Enterprise Architecture Target Vision Plan and Build EA Common Application Services Common System Services Network Services Platform Services Business Architecture Information architecture Component architecture System Management Services Data A n a l y s e Business User Project Architect or DA a n Business d Requirement Identified U n d e r s t a n d B u s i n e s s §Models TRB R e q u i r e m e n t Arch Review Board IT architecture IT Steering Committee S o l u t A i d o v n i s e / A s d i v s i t s e / Architecture Initiative C o n d u c t D e s i g n / P r o d u c t E v a l u a t i o n R e s e a r c h D e v e l o p / & a. I d n e a nl yt si ef y c p o o n ft e o n r mt i a n gl i m p l e m e n t s y s t Yes e m / Design s Conforms to o Architecture? l u No t i o n R e v i e w M t g ARB Yes Arch Conforming Alternative available? No Vitality Process c a ol nt ef ri nr m a ti ni vg e sa l t e r n a t i v e s §Data Stores TRB §Organisation §User Groups §Enterprise Tech Framework §Transition Plan §Application Function Models §Management Action Plan 6. 11. 2020 D e s i g n A s s i s t §Principles Data architecture 59 Governance Transition System & Infrastructure Development Channels Claim Applications Security Services Interface Services Architecture §Processes §Evaluation & Selection DA

Develop and Define EA Roadmap Building the future of EA 60 6. 11. 2020

Hansabank Enterprise Architecture Roadmap es Introduction Input l cip in Pr et rg on si Vi Roadmap Ta • EA Definition • Goals • Structure • Layers • Roles • Governance • Deliverables • Measurements 61 6. 11. 2020 • Problem Statement architecture • business • application • information • technology • infrastructure • governance • processes • Principles • what it is • how to define • what it defines • Perspective • Architectural changes • Business changes • Organization • EA realization • Target Vision • common understanding • definition of architecture • architectural framework • ‘to be’ architecture • ownership of HBG EA

The main content of the Roadmap • The Roadmap phases: – – – 62 6. 11. 2020 Initiate Assess Envision Plan Deploy

Strategic Dimensions Roadmap – Plan Phase Information Applications Plan Technology Organization Phase III Processes IT – Business Alignment Key Activities – Confirm IT priorities with the business – Determine dependencies – Rationalize new EA initiatives with current IT Plans, review with key stakeholders – Proposed high level project/initiative descriptions including scope, timing, investment/cost range, including project benefit – Develop high-level project plans – High level transition and deployment plan for changes and recommendations – Design implementation oversight governance model (stakeholders / communications) – Strategic governance and communications approach – Review vision, alternatives and plans with the key stakeholders – Transition plans to support recommendations – Develop deployment approach 63 Key Work Products & Deliverables 6. 11. 2020

Strategic Dimensions Roadmap - Deployment I II Information Applications Deploy Technology Organization Processes IT – Business Alignment Key Activities – To be completed in solution projects. 64 Key Work Products & Deliverables – To be completed in solution projects. • Detailed Analysis • Updated artifacts • Recommendations • Updated Vision Document • Suggested changes in Vision Document • Design • Construction • Implementation 6. 11. 2020

EA Roadmap layers Common Activities Business Architecture Information Architecture Application Architecture Technology Architecture 65 6. 11. 2020 Governance, Review, Communication and Quality Assurance activities Business Architecture key activities Information Architecture key activities Application Architecture key activities Technology Architecture key activities

Development and iterative update of the Roadmap is needed and defined relation between the Main Roadmap and its Sub Roadmaps High Level Roadmap used in the EA programme Detailed Roadmaps, delegated from the High Level Roadmap 66 6. 11. 2020

Main activities plotted in the Roadmap Date Common Activities Business Architecture Information Architecture Application Architecture Technology Architecture 67 6. 11. 2020 Date Date

Define Enterprise Architecture Roadmap No Architecture Viewpoint Architecture Roadmap Common Activities Business Architecture Activities Information Architecture Activities Application Architecture Activities Technology Architecture Activities 68 6. 11. 2020 Activity Priority Ownership

Enterprise Architecture conclusion Today’s focus will move to Target Vision and Roadmap for EA es Introduction Input l cip in Pr et rg on si Vi Ta Let’s move forward with small iterative and concrete steps with clear traceability between Business requirements and IT capability to deliver 69 6. 11. 2020 Roadmap

Thank you for your time and contribution - now starts the real work for the Enterprise Architecture evolvement cross the organization 70 6. 11. 2020