Discussions

Software Development Unit | April 2007

A TOGAF Success Story in Insurance SectorA TOGAF Success Story in Insurance Sector

EA PractitionerEA Practitioner’’s Conference, Pariss Conference, Paris April 23 April 23 –– 25, 200725, 2007

PoornachandraPoornachandra Sarang, Ph.D.Sarang, Ph.D. Director (Architecture)Director (Architecture) [email protected]@kynetia.com

JosJoséé MarMaríía Corsino Escobara Corsino Escobar Software Development ManagerSoftware Development Manager [email protected]@kynetia.com

EA Practitioners Conference, Paris, April 23 – 25, 2007

Background

EA Practitioners Conference, Paris, April 23 – 25, 2007

PastPast

Local Platform developed for a Multinational Insurance Company, providing:

Insurance Claims Management

Facilitates Communication between Insurance Companies and Customers

Policy and Claim Capture

Collaboration Workflow and Process Management

Email / Fax Alerts and Inputs

Supports Multiple Insurance Products

EA Practitioners Conference, Paris, April 23 – 25, 2007

TargetTarget

Success brings the need to globalize the

platform, requiring a re-architecture:

Worldwide users

High standards for Quality of Services:

Performance, Scalability, Serviceability

Security, Manageability, etc.

Multiple stakeholders

Project as part of a Global Project

EA Practitioners Conference, Paris, April 23 – 25, 2007

ApproachApproach

Enterprise Architecture, TOGAF

Adapted methodology

Use of ADM

Iterate over first phases (Prelim > A > B > C) before

completing the firsts full cycles of methodology

Special focus on Opportunities and Solutions

Limited scope, reducing outputs and adapting inputs

to specific project context

Software Development Unit | April 2007

Applying TOGAF FrameworkApplying TOGAF Framework

EA Practitioners Conference, Paris, April 23 – 25, 2007

Applying TOGAFApplying TOGAF

Why did we decide to use TOGAF? Enterprise Strategic IT Projects

Business – IT understanding as key of success

Eases Communication between stakeholders (common vocabulary)

Pragmatic framework, fits our Architecture methodology Requirements Management as enhancer for continuous changing definitions, and centralized repository

Migration and Deployment plans are needed

Governance is required within the Global Projects

ADM can be easily tailored to project context/needs: Define scope of phases and documents

Iteration cycles redefined to reduce risks and improve business – IT understanding

TOGAF is practical, not very complex, easy to implement

A natural process to create architecture

Software Development Unit | April 2007

Framework and PrinciplesFramework and Principles

EA Practitioners Conference, Paris, April 23 – 25, 2007

Business GoalsBusiness Goals

Bring Local Application to Global Platform

Integrate Several Corporate Services

Simplify Workflow

Create Common Application Framework

Reuse Business Entities

Optimize Business Processes

Remove Current Constraints (localization, connectivity,

scalability, flexibility, etc.)

Allow Customized Services for Minor/Local needs

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture Principles Architecture Principles

Global Platform Architecture principles:

Unique and centralized database for business entities

SOA Approach for Global Applications:

Service layer to access the data

Global applications for core business functions

Enterprise Service Bus to expose & access functionality

Unify Front-end components by using:

Common presentation tier technologies (XSL/AJAX/Etc)

Portlets, single sign-on

EA Practitioners Conference, Paris, April 23 – 25, 2007

Framework Definition Framework Definition

ADM / TOGAF adapted for this project:

Including Business Architecture as high priority and key

element in EA

Limited scope for Data and Application Architecture,

considering dynamic projects and open specifications

Iterative methodology for every architectures,

complemented with Software Development methodologies

Conformance to CMMI processes: Governance, Decision

Making, Documentation, Validation and Verification …

EA Practitioners Conference, Paris, April 23 – 25, 2007

Opportunities Opportunities

Opportunities discovered within Preliminary work:

Unified business processes can be defined within the global

platform

Single UI provides better user experience, and increases

performance and efficiency

The need of unifying processes and data structures makes

business units to identify potential enhancements for next

iterations

Cost reduction by decreasing number of local systems

(software solutions and IT infrastructure)

Software Development Unit | April 2007

Architecture Vision Architecture Vision

EA Practitioners Conference, Paris, April 23 – 25, 2007

Statement of Architecture WorkStatement of Architecture Work

Scope and constraints Re-platform and Re-design work is required

Data access through common services

Legacy technology (i.e. EJB 1.1) to be updated/replaced

Replace home-grown MVC by industry standard components

Front-end to be updated with Global presentation services

Full integration with Global services (Document Storage,

Document Generation, Email Input / Output, etc.)

Ensure capacity, availability and performance for Worldwide usage

Construct Global Platform within 2 years

EA Practitioners Conference, Paris, April 23 – 25, 2007

Statement of Architecture WorkStatement of Architecture Work

Primary Finding of Business Principles,

Business Goals and Strategic Drivers

Automate work, collect information and analyze data

to improve business processes and client services

Globalize business solutions and maximize

company’s capacity, rather than optimizing local

performance

Strategic Driver: use corporate knowledge and

capacity to increase services qualities and capacities

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture Vision Architecture Vision

Targeted concurrency is 25,000+ users, after a period

of 5 years

Single-Sign-On: one access for all corporate services

Single database, with exhaustive reporting and mining

Improved Scalability, Extensibility & Performance

Reuse scalable solutions, adapting to the Global

Architecture and Services

Minimize risks by reusing working components, and

transform them into Global services

EA Practitioners Conference, Paris, April 23 – 25, 2007

Business ScenarioBusiness Scenario

Users: Company employees, Clients and third parties

Business Case:

The Client submits a Claim into the system

The workflow activates an alert to Insurance Company

The Insurance Company notifies a suplier to repair the damage

The company tracks the activity, manages and report the client to ensure the service quality

The company gathers information and provides a risk study to the client based on the claims submitted in the last 3 years

EA Practitioners Conference, Paris, April 23 – 25, 2007

Opportunities Opportunities

Opportunities discovered within Architecture Vision

work:

Reliability: global platform could provide a 99.X%

availability, resulting in a better service for core business

processes support

Efficiency: unified data avoids duplication and correction

processes, reducing average processing time

Service Quality: improvement of service quality by

providing uniform UI, high performance and single sign on

Software Development Unit | April 2007

Business ArchitectureBusiness Architecture

EA Practitioners Conference, Paris, April 23 – 25, 2007

Business Goals, DriversBusiness Goals, Drivers

Business Goals

Covering worldwide business requirements

Flexibility to integrate with all global services

Service all corporation employees plus external users as clients and third parties

Generate new services for clients on top of new platform

Unify Business Data: Policy, Claims, Reports, Clients, Users, etc.

Unify Deliverables: Reports, Forms, Documents.

Reuse information and media

Facilitate Corporate reporting and cross-country processes

Strategic Drivers Move forward into a SOA Platform, creating a whole set of enterprise services and abstracting the technical details from end applications

Deletion of hundreds of local systems, reducing maintenance costs and giving a complete governance view

EA Practitioners Conference, Paris, April 23 – 25, 2007

Business ServicesBusiness Services

Claims system must expose Services for:

Create, modify, retrieve and close claims

Get reports from claims data stored in the system

Notifications & Alerts interaction

Submit events for Claim Management Workflow

EA Practitioners Conference, Paris, April 23 – 25, 2007

Gap AnalysisGap Analysis

EA Practitioners Conference, Paris, April 23 – 25, 2007

Potential Sources of GapsPotential Sources of Gaps

People gaps

Training Required

Process gaps

Forms Definition & Workflow Needs Improvements

Information gaps

New Information Must be Captured

Processes and Sources Must be Validated

Facilities gaps

Several New Facilities Required

EA Practitioners Conference, Paris, April 23 – 25, 2007

Gap Analysis ResultsGap Analysis Results

Front-end and Middleware must be re-factored to meet target requirements

Database access method should be modified

Scalability and availability need to be improved

Alerts & Notification system is not fully covered in target architecture

Global solution does not contain a email / Fax alert engine

EA Practitioners Conference, Paris, April 23 – 25, 2007

Technical RequirementsTechnical Requirements

SOA approach in Integration

Use BPEL for defining Business Processes

Re-engineer Solution to Match Target Platform

Re-design System

Provide Unified Front-end by Creating a Portal

Build a flexible and modular platform

Enabled to support functional requirements changes

Open Business Processes (Dynamically changed)

Working with Metadata instead of fixed data structures

Software Development Unit | April 2007

Information System Architecture Information System Architecture

EA Practitioners Conference, Paris, April 23 – 25, 2007

Output Data Architecture and ViewsOutput Data Architecture and Views

Data Principles

Data Management Process Model

Data Entity / Business Function Matrix

Data Interoperability Requirements

Data Lifecycle View

Never delete any data

Archive data for 10 years or more: policy is not fully defined

Data Security View

Data Management View

EA Practitioners Conference, Paris, April 23 – 25, 2007

Data Data ArchitectureArchitecture

EA Practitioners Conference, Paris, April 23 – 25, 2007

Data InteroperabilityData Interoperability

Client Applications Common

Database: Claims Policy Client ...

Reporting Applications

Claims Applications

Other Applications

EA Practitioners Conference, Paris, April 23 – 25, 2007

Data Architecture ConcernsData Architecture Concerns

Data Access Services: Performance, security and availability

Extensibility: does Data definition support future business needs? How easy the services will be adapted to new requirements?

Definition: first iterations leave a open definition for some data entities. Changes on data architecture to be considered along the project

EA Practitioners Conference, Paris, April 23 – 25, 2007

Gap Analysis ResultsGap Analysis Results

Security: Services Require Authentication

Integrity: DAL should Implement Validation Mechanism

Performance: Querying cache to avoid massive WS/XML process

Extensibility: Creating Common Services, redefining current functionality

Availability: Deploying on Cluster Environment

Providing Fault Tolerance, Persistent middleware (MOM)

EA Practitioners Conference, Paris, April 23 – 25, 2007

Impact AnalysisImpact Analysis

Business Architecture:

All local functionality should be unified into the

Global system

Application Architecture:

Security requirements implies application changes

and improvements

Technology Architecture:

DAL technology changes from Dynamic SQL to SOA

Approach using Web Services

EA Practitioners Conference, Paris, April 23 – 25, 2007

Application Architecture and ViewsApplication Architecture and Views

Target Application Architecture

SOA, using a ESB as middleware

Common services providing support functionality

Application must expose services

Application Information View

Application Interoperability View

Application Service View

Application User Location

EA Practitioners Conference, Paris, April 23 – 25, 2007

Application Application ArchitectureArchitecture

EA Practitioners Conference, Paris, April 23 – 25, 2007

Application InteroperabilityApplication Interoperability

EA Practitioners Conference, Paris, April 23 – 25, 2007

Application Information ViewApplication Information View

EA Practitioners Conference, Paris, April 23 – 25, 2007

Application Application Service ViewService View

Services Exposed:

Presentation

Dynamic Forms

Ajax Support

Common Front

Data Services

Entity FindBy…

Listing

CRUD

Functionality

Workflow

Reporting

BI

Documents

I/O Comms

EA Practitioners Conference, Paris, April 23 – 25, 2007

Applications ArchitectureApplications Architecture

Validated Applications Principles:

Reduce Integration complexity

Maximize Data Usage and Performance

Avoid Data Duplication

Security and Simplicity (on Data Access)

Provide Corporate Governance

EA Practitioners Conference, Paris, April 23 – 25, 2007

Applications Architecture (contd.)Applications Architecture (contd.)

Viewpoints addressing key stakeholder concerns:

Performance: System should perform as Real Time

Web Application, but MOM Middleware for Enterprise

bus is slow. Cache and dedicated Message Queues

Security: Business Components should be deployed

as secured application blocks. Usage of JAAS.

Governance and flexibility: Usage of BPEL / BPMN to

design workflow between app. blocks

Serviceability: SOA for middle, back and front ends.

EA Practitioners Conference, Paris, April 23 – 25, 2007

Applications Architecture (contd.)Applications Architecture (contd.)

Gap analysis results

Application blocks should be adapted into a security

framework (JAAS, ITIM, etc.)

Original workflow (ad-hoc, stored in database) must

be replaced by Commercial Workflow Engine, based

on BPEL for further customization

Performance and scalability must be addressed by

implementing MOM and redundancy (build a ESB)

EA Practitioners Conference, Paris, April 23 – 25, 2007

Applications Architecture (contd.)Applications Architecture (contd.)

Impact Analysis

Business Architecture: Usage of BPEL Choreographer

limits the functionality. Customized functions at

business lines workflow requires now specific

development at Workflow Engine

Data Architecture: No impacts, as Database Access

Layer abstracts the applications details

Technology Architecture: Considering Commercial

Software for applications architecture impacts on

technology to use and general implementation

Software Development Unit | April 2007

Technology Architecture Technology Architecture

EA Practitioners Conference, Paris, April 23 – 25, 2007

BaselineBaseline

Technology Architecture Version 0.1:

Technology Architecture – Constraints

Local Application platform is not compliant with

Corporate platform (App Server, Database, Java

Technologies …)

Local Database Access and Structure must be replaced

Scalability: Local capacity is far below desired capacity

Serviceability: Application must expose services

Security: Data and Functionality access to be secured

Application must be integrated with Global Services

EA Practitioners Conference, Paris, April 23 – 25, 2007

BaselineBaseline

Technology Architecture Version 0.1:

Deployment / Packages

EA Practitioners Conference, Paris, April 23 – 25, 2007

BaselineBaseline

Technology Architecture Version 0.1:

EA Practitioners Conference, Paris, April 23 – 25, 2007

ViewpointsViewpoints

Technology Architecture Version 0.2:

Networked Computing/Hardware View

Processing View

Cost View

Standards View: Central Servers:

Unified Platform based on J2EE / Oracle / XML

Low coupling between applications

High redundancy and availability

Easy monitoring & maintenance

Standards View: Local Clients (Countries):

RIA Approaches, based on Web systems

Low response time

No client side component to be deployed (W32)

EA Practitioners Conference, Paris, April 23 – 25, 2007

ViewpointsViewpoints

EA Practitioners Conference, Paris, April 23 – 25, 2007

ViewpointsViewpoints

Technology Architecture Version 0.2

Processing View

EA Practitioners Conference, Paris, April 23 – 25, 2007

ViewpointsViewpoints

Technology Architecture Version 0.2

Cost View

EA Practitioners Conference, Paris, April 23 – 25, 2007

Business goals and objectivesBusiness goals and objectives

Technology Architecture Version 0.5

Technology Architecture - Requirements Traceability

Claims accessible and unified

Able to generate reports and documents

Dynamic definition of insurance products

Complete functionality not available

Unified products for Policy & Other Insurance products

Advanced reporting

EA Practitioners Conference, Paris, April 23 – 25, 2007

Criteria for specification selectionCriteria for specification selection

Technology Architecture Version 0.6

Technology Architecture - Requirements Traceability

Client side: Performance is downgraded due to Service

invocation and response times

Server side: Ad-hoc solutions are not 100% compliant

with corporate technical standards

EA Practitioners Conference, Paris, April 23 – 25, 2007

Gap analysisGap analysis

Technology Architecture Version 1

Technology Architecture - gap report

Some services are still to be integrated in Claims system:

Document Management, Document Render, Messaging

Platform

Existing Functionality GAP will require modifications on current

technology architecture (to cover security, functionality,

technical requirements)

Overall Performance to be revised after integrating with

Common Services (Web Service overhead and XML process)

Extensibility to be tested and probably improved

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture DefinitionArchitecture Definition

Development Architecture

Infrastructure Architecture

Infrastructure Architecture – Network

Integration Architecture

QA Architecture

Security Architecture

Service Architecture

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture DefinitionArchitecture Definition

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture DefinitionArchitecture Definition

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture DefinitionArchitecture Definition

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture DefinitionArchitecture Definition

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture DefinitionArchitecture Definition

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture DefinitionArchitecture Definition

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture DefinitionArchitecture Definition

EA Practitioners Conference, Paris, April 23 – 25, 2007

Gap analysisGap analysis

Some Services are still to be Integrated in

Claims System

New Functionalities

Requirements Definition to be iterated

Business and Information Architectures Impacted

Additional demand on Performance due to the

introduction of Common Services

Extensibility to be tested

Software Development Unit | April 2007

Opportunities and SolutionsOpportunities and Solutions

EA Practitioners Conference, Paris, April 23 – 25, 2007

OpportunitiesOpportunities

Share Business Information between Countries

Global Platform allows to create tons of

Reports, Analysis, Statistics and Extract

information from Business Activities:

New Information Services

Improve Business Processes

B2B Opportunities

Reusing knowledge helps in cost reduction

EA Practitioners Conference, Paris, April 23 – 25, 2007

Impact AnalysisImpact Analysis

Impacts few Global Operations

Corporate and Local Services

Authentication Services

Document & Data Storage

Requires Migration from Local Version

Local Applications replaced by Global Applications

Local Applications using Global Services

Data Migration Impacts all Legacy Systems

EA Practitioners Conference, Paris, April 23 – 25, 2007

OutputsOutputs

High-level implementation plan

Impact Analysis - Project list

This Project impacts on every Global Operations

Corporate services

Local services

Authentication services

Document & Data Storage

Requires synchronization with current Local Version

Software Development Unit | April 2007

Migration PlanningMigration Planning

EA Practitioners Conference, Paris, April 23 – 25, 2007

Cost/Benefit AssessmentCost/Benefit Assessment

Investment per country is returned in 2 years

(average) due efficiency improvement

Common cost for Global infrastructure is

returned in 5 years:

Provides reduction of Maintenance & Infrastructure

Cost (IT systems reduced in more than 50%)

Increases new business opportunities (Global Data

and potential cross-country services)

EA Practitioners Conference, Paris, April 23 – 25, 2007

Risk AssessmentRisk Assessment

Main risk to cover is the feasibility and efficiency of

global platform:

Delivery dates could be delayed. Financial impact

Technical solution can’t satisfy business requirements

(performance, reliability, etc). Time and Financial impact,

due re-work on solution

Under extreme circumstances, the previous systems can

provide service to business needs (No operational risks)

Iterative deployments & validations are required to

minimize previous risks

EA Practitioners Conference, Paris, April 23 – 25, 2007

Implementation RoadmapImplementation Roadmap

EA Practitioners Conference, Paris, April 23 – 25, 2007

Migration PlanMigration Plan

Analyze Project Approach

Replatform Local System (Corporate IT

policies)

Migrate Database, from Local to Global

Iterative Integration Project Migrate Local Database access to Global Services client

Load Data and Test Iterations

Configure Country based data & Requirements

Deploy Version

Software Development Unit | April 2007

Implementation GovernanceImplementation Governance

EA Practitioners Conference, Paris, April 23 – 25, 2007

RecommendationsRecommendations

Reusing Solution Building Blocks

Proof of concept required prior to select reusable solutions

Checkpoints for Architecture Conformance

Quality of Services

Cost / Benefit Assessments

Timeline, progress and dependencies between projects

Conformance Check

Performance as key QoS: updated Technical Architecture

Documentation: impact on overall project and side

projects needs to be confirmed

EA Practitioners Conference, Paris, April 23 – 25, 2007

Architecture ContractArchitecture Contract

Documented Contract with different stakeholders

(Business, IT Developers, partners, etc.)

Statement of work

Project plan, scope and constraints

Architecture Vision

Deliverables

Acceptance criteria (for deliverables and invoices)

Business Users acceptance of:

Timelines, constraints and strategic requirements

SLA and metrics

EA Practitioners Conference, Paris, April 23 – 25, 2007

Governance and ConformanceGovernance and Conformance

Define and manage policies

Change Management process, roles, responsibilities

Audit, Control and formal processes

Monitor, Control and Report

Metrics, Centralized repository, weekly reports

Adjustment of Architecture depending on feedback

Decision making

Independent, well defined process (CMMI)

EA Practitioners Conference, Paris, April 23 – 25, 2007

Governance and Conformance (cont.)Governance and Conformance (cont.)

Compliance / Dispensation

Prioritize and Iterate

Decision Board, selecting key success factors

Environment Management

Ease access to information

Agile communication

Confirmation of changes / key communication

required

Keep updated gap / impact analysis

EA Practitioners Conference, Paris, April 23 – 25, 2007

Governance and Conformance (cont.)Governance and Conformance (cont.)

How feedback modifies Architecture? Every stakeholder has particular vision / viewpoints to be taken into account

Business Users: Checking prototypes, POC

Conformance to first iterations of Architecture Views

Business Analysts: Checking Data and Business Views. Some functional cases were not well understood, or not enough defined to be applied as a global process

Technical Architects: They identified constraints not taken into account in previous iterations / phases, limiting or affecting the business targets

EA Practitioners Conference, Paris, April 23 – 25, 2007

Governance and Conformance (cont.)Governance and Conformance (cont.)

Business Acceptance & Conformity

Responsibility hold by stakeholders:

Define responsibility areas and decision makers

Define acceptance test and validation processes

Change on any vision requires sign-off and:

Arguments and assumption of consequences (cost,

time)

Justify how critic it is: Could the change wait for next

iteration?

Aligning expectations, more than time and costs

Software Development Unit | April 2007

Q & AQ & A

KYNETIA Edificio Alfredo Mahou, Pl 20

Plaza Manuel Gómez Moreno, 2

28020 Madrid

SPAIN

Tel. +34 915 489 444

Fax +34 915 489 445

E-mail. [email protected]

www.kynetia.com