Create a WEB 2.0 banking application. Adaptive Case Management. Secure and scalable.

The “Banking” deposit system
Web 2.0 / cloud
Using
(Adaptive) case management
Workflow / business process modeling
Google DOCS
UI demo & configuration
A major update will become available in May 2014, we’ll create a new presentation:
Harmony in Cloud Banking - introducing the Google Platform

For processes which:
• are unpredictable in their execution,
• are driven by unknown events,
• need actions with unforeseen consequences,
• require the ad-hoc inclusion of new actors,
• Have manual involvement for decisions not in
rules and flows,
• have unknown inbound and outbound content.
Why adaptive case management (ACM)

IT requirements / features
• must enable business users to add rules at any
time,
• Support multiple versions of cases
– Old versions with the original rules & processes
– Old versions with new versions of rules & processes
• need secure, auditable social interactions of
actors,
• must assign actor authority based on ‘need-to-
know,’
• require complete transparency and auditabilty
Adaptive case management

The banking case
• Customers that want to deposit money
– Existing customers -> select a product
– New customers must be added (account details)
• The Bank has rules for approving contracts
– Minimum amounts and contract duration
– Maximum contract duration
– When deposit amount > exceeds banks maximum the bank
manager must approve
• Customer must accept the contract
– Email notification / online access
• Case data is shared with customer
– “case” access is granted
• Management information needs
– Show all new contracts [in a Pivot table]

Google DOCS configuration contains
• The business process (using rules)
– All interactions: workflows and presentation flows
• User Interface (UI) + web parts for
– “Decision support”: displays & next steps
– “History”: displaying all prior actions
• Data
– Customer & contract files (updatable)
– Products reference/master
• Shared via Google DOCS
– All customer & contract changes replicated in spreadsheets
• Authorization – multi level:
– Groups, users, events, case data
• E-mail support
– templates
• Case output
– Data is “put” on ESB – for processing back-office

The “deposit account” process

Start the app: authorization
3
2
1
1. User logs on with LinkedIN:
access limited to customer group
and “identify customer” process
1
2
1. User logs in with Yahoo account:
Admin rights
…. Sees all groups, all events

Identify customer (implementation A)
• By adding the customer key to the dialog we have mulitple options:
1. Enter first and last name and Harmony auto fills [all fields]
2. Enter Customer key and Harmony shows list
3. Select a customer [key] and Harmony auto fills
1
3
2
1
2
3

Select a [deposit] product
1
1
• If amount is too low:
A message is displayed &
case will be closed (both are “rules”)
• When amount is ok ..
Next process step is contract length
1
2
2
2

When length and date are entered:
1. End value is calculated
2. Customer needs to confirm contract
(Can be online or via email)
Enter contract length
1
1
2
2

Customer confirms contract
1. Email is sent …
2. Recipient (customer) activates link
3. Dialog is displayed

Contract confirmed = yes
1. User logs on with Facebook: limited
access to groups and processes

Data replication in Google DOCS
1. Contract for the customer is created
2. Harmony “syncs” data with spreadsheet
3. (key is created using CONCATENATE function in
expression

Case data
1. Harmony collects and time
stamps all data and records
all user access to the case
2. (developers tip)
with one command the
data is output to an ESB

CHANGING THE RULES
We add the country to the application

1. This version of the case doesn’t have country
… we cancel this event (process)
1
1
No country

1. Version doesn’t contain country
2. We add country name to the dialog (and datasheet (REF_Country)
containing all countries)
(we upload the configuration – within 1 minute the application is ready)
1
2
1
2
Adding country

1. Version 1 (the version that doesn’t contain country ) was canceled .
2. Country name support has been added and all country data
uploaded
(the configuration was uploaded – the application being ready in 1-minute)
3. We select the same case: country is added. Country list present.
1
3
2
1
2
3

Create your own “BI“ / pivot table
1. The transactions added to Contract file are immediately reflected
in the Pivot Table contained in the workbook.

HARMONY CONFIGURATION
How do we “create” such a application?

1. Create the dialogs (process steps)

2. Define rules
1
2
Rules control the sequence (well that’s one part they “do”)
1. When Harmony detects a customer’s Social Security Number :
1. it prompts for the dialog “select deposit”
2. It sets the create account to “No”
2. Dialog “account details” are displayed when create account = “Yes”
3. Only when a deposit [product] has been selected will the dialog
“contract length” be displayed
3
1
3
2

3. Create a Product reference file + DT
It’s smart to link Reference files with Decision Tables
1. Product contains the “base” data; product liability is input for the DT
2. The DT generates a percentage point [value] for any present
combination of liability and contract duration

4. Add expression(s)
Familiar use of spreadsheet style expressions
no learning curve

[e-mail] template
Harmony has built-in templates

5. Authorize users
1. Create groups
2. Create users, assign to groups & specify “access”
3. Specify which event (process) can be started by a group
2
1
3

6. Save transactions / updates
1. The banking application contains:
1. Contract file
2. Customer file
2. Harmony automatically adds unique records to file
3. Attributes are filled when data becomes available

WORK TOGETHER
Collaboration improves productivity, lowers costs

Online collaboration: share ‘n’ chat
The advantage of having all configuration data in Google DOCS spreadsheets

AUTOMATED TESTING
Testing the application

All test stories & test cases are stored in Google DOCS
Tests run automatically, results in minutes.
The tests compare
expectations [what should the result be]
with
outcomes [what is the result ]

Configuration overview Banking
Part Number of rows Data (rows)
Rules 25 -
Dialogs (process steps) 40 (55)
Files 4 (6) 1000
MDT none (1)
DT 1 (2) 3
Expressions 3 (6)
Templates 3 (5)
Groups 3 (4)
Development time (hours) < 12 (+ 6)
(in brackets) is the estimate for a fully developed version
MDT = multi-dimensional decision table.

For more information
• Visit
– www.liquidsequence.com
• Contact us
– http://www.liquidsequence.com/contact.html
• The “deposit” configuration (“source code”)
• https://docs.google.com/spreadsheet/pub?key=0Agz0QZs
Eoj64dExUcUx2ZjRXMk9oN0djdmFpM0Z5MHc&output=ht
ml
• The banking lending application (the ultimate,
decision table, implementation):
• http://liquidsequence.com/DecisionModelingNotation-
Lending-Example.html

Create a WEB 2.0 banking application. Adaptive Case Management. Secure and scalable.

More Related Content

Viewers also liked (20)

Similar to Create a WEB 2.0 banking application. Adaptive Case Management. Secure and scalable. (20)

More from Harmony (11)

Recently uploaded (20)

Create a WEB 2.0 banking application. Adaptive Case Management. Secure and scalable.

Editor's Notes