Isolate Business Rule Processing

Create “Library” of Business Rules

Create Infrastructure

Ability to “select” rules

Ability to generate a process with multiple rules

Self Documenting

Current Direction

Bridge ALL functionality using messages for bridging

Isolate Single Module for Single Function

Separate Data Layer

Establish Extensive Re-Use

Build Libraries

Re-Use

The customer information is kept in CORE

Establish Re-Use – Methods should always be designed with Re-Use as a primary consideration. Re-Use allows many different processes to utilize the same Business Rules, while minimizing maintenance due to the fact than only one method has been coded for the single set of rules. A library must be maintained to allow development to use these reusable methods

Establish A Common Set Of Published Documents – A common method of creating  and documenting the system will be established

“On average, 300 hours are lost per year to outages and service degradations:  37% for LANS,  29% for WANS, and 32% for networked applications .”