Tech Acc Soft Life

8/9/2019 Tech Acc Soft Life

http://slidepdf.com/reader/full/tech-acc-soft-life 1/30

Copyright © 2010 Accenture All Rights Reserved. Accenture, its logo, and High Performance elivered are trademar!s of Accenture.

Accenture "oft#are

A$%P &echnical Presentation



Technology/ArchitecturePrimary Features/Design Principles

2Copyright © 2010 Accenture All Rights Reserved.

Customizable'usiness ()perts can innovate #ithoutthe delay and high costs of traditionalprogramming

Modular &hin presentation supports multiplechannels

A*stract componenti+ed design resistso*solescence

Based on Standards"tandard developmenttools languages

"tandard infrastructure administration"tandard communication formats

Platform eutral Avoids third-party loc!-in%ncludes small footprintenvironments

!penPu*lished AP% and ata*ase"implifies integration"implifies upgrades

Simple"trong /eep it "impleapproachCareful use of 2(($et the platform handle thehard #or!



Technology/Architecture"ogical "ayers of Applications

Copyright © 2010 Accenture All Rights Reserved.

3oundation of pre-*uilt $ife%nsurance components

Common infrastructure andservices4ser driven assem*ly of*usiness processes

Achieve many *enefits of a

full "5A no# #hilepositioning for the future



Physical Tiers"ogical "ayers of Application


Presentation&hin

Application/Model(ase 4% development(ncapsulate sessionstateCache AP% re7uests

Process/AP#5rchestration

eclarative &ransactionseclarative ()posure

Component'usiness $ogic (ngines

ecoupled andReplaeca*le

Data Access%solate ata from $ogic



A"#P Architecture $ "ogical


A"#P Front %nd

e& Business 'nder&riting Customer Ser(icing Policy ser(icing)or*flo& and

business processmanagement

Ser(ice "ayer

+rd PartyPolicyAdministration%ngine

A"#P Bac* %nd

Product Factory

#ndi(idual policy management

Common Calculation%ngine

Products,ules

'ser definedFunctions Tables

!therCommonFunctions

!ptional usage of A"#P calculationengine by + rd party system

-roup policy management

Batch treatments

Claims processingThird party management

Collection/Disbursement

Accounting

Commissioning

Printing

,eporting Authorization

,einsurance

# n t e r f a c e s

!rganization



A"#P Architecture $ Physical


)eb Ser(er

. %% Application Ser(er

Static Content/#mages/0TM"

)eb Application 1)A,2

%.B Application 1%.B3.A,2

!ther Components1.A,2 Product Component 1.A,2

Product #nterface

Product Calc %ngine

Database Ser(er

Product ,ules

Calculation %ngine

!ther Components1.A,2

Presentation

Business4Product4andData Flo&

Data Access



De(elopment Tools 5 "anguages

:Copyright © 2010 Accenture All Rights Reserved.

Presentation "ayer "Pava"cript

Application "ogicavaBac* %nd Components

avaCo*ol 2

Database

";$

6ersion Control"u*versionClearCase

#D%s / Debugging(clipse, RA<et()press % (

Build=aven, Ant&C$

7ualityPurify, Pro*e, unit, AC;&HP ;uality Center 3ind'ugs, P=

Data ModelingataArchitect, (R>in

evelopment &ools$anguages



Supported Platforms

?Copyright © 2010 Accenture All Rights Reserved.

)eb Ser(er IBM HTTP Server (bundled with WebSphere)

Apache 2.0 %%" 8.0@

Application Ser(er WebSphere 6.1>e*$ogic 10.)&omcat 9 3or laptop deployments of the front-endB

.a(a JDK 1.5the / *undled #ith the application "erver.B

Database !r"#le 1$%5racle 11g

'2 .) (nterprise (ditioner*y open source data*ase for front-end on laptopsB

Messaging Middle&are IBM M& Serie'J I S b l * b l +nterpri'e%ntegrated =" server #ith application server.

Apache Active=; D6.1@ 3or laptop deploymentsB

!perating System A#8 9:+/;Solaris <=

>indo#s 200 "erver, >indo#s EP$inu) F Red Hat $inu) (nterprise edition or "4"(BIb, -*!' 1. r hi%her (/ r b l l"0er)

Commonly usedSer(er 0ard&are

#BM P9 series"un "olaris & "eries Gava 4ltra"parc2B"un "olaris = series non-Gava "parc96B%ntel *ased serversM"in/r",e (/ r b l l"0er)

ALIP was validated onzLinux/s390x using Web phe!e".#$ %&2 9.# and ' ( (nte!p!ise

#0. uppo!t is not )et available *o!this plat*o!+.Dersions listed in it"li# b ld are preferred



,ules %ngine Architecture


'usiness users design pages using thePage 'uilder

Pages can invo!e the Rules (ngine forvalidations and follo# up 7uestions

Rules (ngine can invo!e underlying

'usiness AP% through E=$ payloadsPages can *e grouped and tied togetherto form a #or!flo#

>or!flo# can leverage the Rules (ngineto route to the user through differentpaths depending on the process or user s

ans#ers&he entire orchestration layer uses E=$,allo#ing the configura*le process to frontnon-A$%P systems, such as an ("' orthird-party policy administration system

Rules can *e auto-deployed as #e*

service operations



,ules Management!(er(ie&


Product ,ules/ey %I5 ena*ler Configura*le coverage definitionCentrali+ed features utili+ed across coverage *ase,Ro*ust calculation support and transactional events

Page -roup ,ules for Data Collection

ata collection needs to support *usiness processes<uanced support for a varia*ility of data capture #or!flo#sCreate and maintain #ith ease

Business ,ules Configuration to drive process innovation

rive #or!flo# and follo# up automation%nsight into *usiness rule e)ecution to transform processes()pose as #e* services to support ease of integration andena*lement of rules centricity



,ules ManagementProduct ,ules


ata driven product engine to roll products out tomar!et in fast efficient manner

/ey %I5 ena*ler %ncludes

Coverage definitionCentrali+ed features

Ro*ust calculation support&ransactional eventsProduct structure and composition rules&ariffs definitionCalculations Rules4nder#riting Rules

&est and simulation environments support thevalidation phase *efore the e)ecution environment



,ules ManagementPage De(elopment


&he Page =anagement %nterface supports thecreation of Pages, ;uestions, Ans#ers, Conditions,Refle)ive ;uestions, 3ormatting, etc.

Pages"pecify page name and description

description displayed at run timeB Attach rules to *e run #hen entering orleaving the pagePages can *e inserted *et#een other pagesor added to end of list

;uestions

Ro*ust and fle)i*le interface for configuring7uestions=any types of ans#er controls supported

&e)t *o)es, rop do#n list *o)es, Radio*uttons, as #ell as pre-defined controlsB<umerous properties to *e set *ased onpurpose and type of 7uestion



,ules ManagementBusiness ,ules


Customi+ation is supported acrossJata collection needs to support *usinessprocesses

Darious design templates and features toleverageDaria*ility of data capture #or!flo#s to supportany nuancesCreate and maintain configura*le *usinessprocesses

'usiness rules to drive process innovation'usiness edits that leverage product engine

rive #or!flo# automation, follo# up

automation(na*le data mining of *usiness rule totransform decision-ma!ing processes()pose as #e* services to support ease ofintegration and ena*lement of rules centricity



,ules Management)or*flo& De(elopment


>or!flo#s that control all *usiness processes in thesystem can also *e configured

efines the #or!flo# for a given *usinessprocess. ()amples includeJ

Application entry

3inancial transactions entry4nder#riting e)ecutionClaims management

>or!flo# services drive the front end flo#according product type and channel

Routing *ased on product and *usinesso*Gect state4ser Authori+ations to perform specificprocess tas!s *ased on profiling structure



,ules ManagementPromotion4 6ersion Control4 and Migration


Promotion tool migrates configuration bet&een A"#P systems&reat configuration the same as code4ses >e* "ervices to communicate #ith multiple A$%P systems"imple directory *ased repository *y defaultConfiguration artifacts stored as E=$

esigned for simple integration #ith e)isting third party source control.



,ules Management,eplicating in Multiple %n(ironments


"ta*le &run! version for ongoingdevelopment

3eature *ranches used forenhancements

eployed and tested in isolation*efore merging to trun!

&run! state is tagged during releases

3i)es are made against releaseversion

%f applica*le, fi)es are merged *ac! to

&run! for the ne)t version'oth code and configuration can *epatched or promoted respectively



Change Management Process


Change re7uest, Assignedto developer

"pecification or efectB

%s changere7uestlargeenough to

re7uire a*ranchK

!ne %nhancement S6 Branch <;A tests on*ranch siteL peer code

revie#

eveloper Configurator

ma!eschanges

'ranchfrom&run!

5nceapproved,=erge to&run!

!ne %nhancement S6 Branch >;A tests on*ranch siteL peer code

revie#


ma!eschanges

'ranchfrom&run!

5nceapproved,=erge to&run!

%nhancement %nters7ueue to be mergedbac* to trun*

Changes made directly on Trun*Changes aresigned intotrun! assinglechangeset


ma!eschanges

evelopergets latestcode

Change re7uests large enough to re7uire a separate *ranch may ta!e a fe# days or#ee!s. (ach enhancement has its o#n timeline for completion independent of trun!development lifecycle.

All changes for an enhancement, including data configuration are signed in as a singlechangeset.Change re7uests small enough not to re7uire a separate *ranch are typically *ug fi)es orminor enhancements. ()ampleJ change format on a data element on a page.

1:


http://slidepdf.com/reader/full/tech-acc-soft-life 18/30Copyright © 2010 Accenture All Rights Reserved.

System De(elopment 3 T&o )ee* "ifecycle

&he lifecycle a*ove represents the main development trun! of the system. (achenhancement has an independent lifecycle.

uring any development cycle, the development manager may elect to not merge codeand s!ip a cycle to focus on ma!ing corrections to trun!.&he performance test is planned to *e e)ecuted once every other cycle.=erges are not scheduled during the final t#o #ee! development cycle *efore a systemrelease.

1?



Process Benefits

Process significantly reduces #asted la*or *y concurrent changesadversely impacting each other on a daily development *asis.

(nhancements large enough re7uiring a *ranch are isolatedfrom trun! activity, insulate *oth the developer and the rest ofthe development team.

Process is fle)i*le enough to allo# development to *e nim*le, toallo# direct change vs. 7ueued change as directed *y thedevelopment manager.Change process using "u*version allo#s isolation of distinctchangesets to *e rolled *ac! or ported to other A$%P versions.

evelopment cycle allo#s 7ueuing of merging disruptive largeenhancements to trun! at discretion of the development manager.

Allo#s development manager to control trun! sta*ility.Regression testing *efore and after ma!es it easy to identifydefects introduced *y the enhancement.




'ser %?perience




#nternationalization


Features"ingle installation supports multiplelanguages4nicode 4&3-?"ame #e* pages for all languages

$ocale tied to each re7uestate, Currency formats, Collationurisdictions, Addresses

&a) Calculations=aintenance *y &ranslators nonprogrammingB

'atch operations *y region



Scalability and Failo(er


Clustering"tateless design"eriali+a*le #e* session"upports seamless fail-over

Best Practices<o single point of failure$arge-grain interfaces&ransfer o*Gect design pattern

Al#ays rely on pooling



#ntegration)eb Ser(ices and #ntegration Mechanisms


'ser interface integration=ashups%maging systems

Message Based Accept E=$, transform and communicate Adapters for standard formats li!e AC5R3le)i*le transports

)eb Ser(ices %nabled AP#3ull AP% e)posed as >"-% compliantservices()pose 4ser Created Rules as "ervices

Application/Programming "e(el

"#ap out or e)tend internal components=any technical options!pen relational database

Provided tools to simplify e)tracts andreports



#ntegration!pen ,elational Database


20@ $ogical "chemas=ap to Components

esign Conventions<ormali+ed=aster etail<amed Dalues for ynamic"e7uential /eys%solated Customi+ations

efault ata$oo!up &a*les

%nitial ata%nitial 4sers Iroups"ample Rules



#ntegration,ules as )eb Ser(ices




#ntegrationFrom the Traditional to the Modern Approach

2?Copyright © 2010 Accenture All Rights Reserved.

Traditional Approach A$%P acts as a hu* and handles datatransformation internally&ransformations are too comple) to do inconfiguration, re7uiring code

A$%P must handle multiple transport types"5AP, =", CustomB

"ome transports li!e "5AP endpoints aretoo comple) to handle #ithout generatingcode so they are custom.

Modern Approach A$%P communicates #ith an ("' using itso#n canonical data formats

Custom code no longer needed sincetransformation and communication ise)ternali+ed to the ("'

A$%P needs only a small num*er of generictransports "5AP, ="B("' &ools can handle transformations#ithout code.



#ntegrationA"#P S!A / %SB Strategy


Scenario@ A$%P is a front end to several e)isting*ac! end systems$everage process-driven design todelegate service re7uests

)ebSphere %SBHosts mediation layer andtransformations leveraging A$%Pschema.

Allo# the customer to manage theintegration layer

Reduce comple)ity and customi+ation#ithin A$%P4se third party transformation tools

>e*"phere &ransformation ()tenderBCustomer chose AC5R as a standardformat #ithin the ("'

A$%P AC5R mappings maintained aspart of *ase



Future S!A ,elated %nhancements

Continued PathContinued direction to ena*le our customers toleverage third-party "5A infrastructure and tools

()pose A$%P data and functionality toencourage the creation of composite andsituational *usiness applications outside of A$%P

$everage dynamic rules as a fle)i*le #ay toimplement services

%?ample

oint demonstration #ith %'= using >e*"phereProcess server

$everage standard 'P($ to design an Agent Approval process.

"eamless mi) of A$%P services in a largerprocess flo#.

"hared 2(( platform advantages transactions,ava "CA service *indingsB

Augment and em*ellish #ith other services#ithout modifications to A$%P (mailnotificationB.

Tech Acc Soft Life

Documents

Transcript of Tech Acc Soft Life