The Benefits of the IDIOM Approach

Navigation:  About IDIOM >

The Benefits of the IDIOM Approach

Previous pageReturn to chapter overviewNext page

The IDIOM approach to systems development offers both technical and commercial benefits. These are outlined in Tables 1-3 and 1-4, respectively.

Technical benefits

Description

Systems Development is simplified and accelerated

Rules are developed by business people, which results in a better distribution of development responsibilities and better value for effort, reduced programming, and the parallel development of the application and the rules.        

Reduced effort when maintaining systems

As rule changes need no or minimal programming and systems are more adaptable, they remain useful for a longer period of time - in fact, for the life of the business.

Ease of adoption

IDIOM does not dictate platforms, languages, or database design and has minimal platform and product dependencies – it generates code in standard languages.

Enables the use of industry standards for data exchange

Industry standard XML schemas (e.g. ACORD, HL7, UBL, MDDL) can sometimes be used for rules development; this gives a head-start for applications that are required to support business-to-business communication.

Table 1-3: Technical benefits of IDIOM's approach to systems development

 

Business benefits

 

Business Agility

With IDIOM, some business practices can be changed by simply changing the business rules. This can be done easily, quickly, and with minimal expense or risk because programming is eliminated, minimal testing is required, there is minimal impact on the system, and the accuracy of the business rules is easily verifiable.

Protection of IT investment

IDIOM ensures that the business rules survive system change. Following system replacement, the IDIOM rules repository can simply be `plugged into' the new system. IDIOM also enables you to extend the life of legacy systems and improve their adaptability.

Demonstrable compliance

With IDIOM, business practice is documented and accessible. Standards, statutes and regulatory requirements increasingly influence business practice and the ability to demonstrate compliance is becoming increasingly important. IDIOM facilitates auditing because it documents business practice and guarantees that the deployed system matches the documentation.

Cost-effective  

The IDIOM strategy of business rules developed by business people reduces programming and results in a better distribution of effort and better value for effort. Additionally, the effort to maintain deployed systems is reduced as rule changes are made more easily and systems remain viable for longer.

Table 1-4: Commercial benefits of the IDIOM approach to systems development.