Appligenics White Paper (page 5)

   1   2   3   4   [5]   6   7  

It is important to note that rules are purely calculations based on elements - and not based on programs, as is the traditional way of building logic. This means that an event can be associated with the element, for example:

• Edit rule - output a message if the values are incorrect
• Default rule - output to-day's date if the input is blank
• Display rule - highlight that the bank balance is negative
• Update rule - update derived elements from base elements
• Transient rule - convert from a foreign to a local currency

The rule is no more complex than a spreadsheet calculation - and users understand the logic. It is not coding as programmers would know it and to place the complexity in perspective only half a day on a five-day training course is devoted to rules!

Do not assume that because the rules are not complex, the computations and programs cannot handle complex processes. Most of the program logic associated with traditional logic is automatically generated:

• Getting screen forms
• Redefining element names within functions
• Reading and writing to entities
• Handling translation of text elements
• Prescribing user formats
• Handling screen and element security

Step 4: Programs and User Guide

The screen programs are now defined. Programs are defined in minutes from one of many templates, such as:

• Single Record, Multi-Line and Parent-Child
• Enquiries
• Menus
• Breakouts from one program to many others

The deduction logic is already defined in the database and in the rules so entering the program name and text is the main effort.

The system evolves around the re-use of common objects such as the following:

• e-mail
• web
• image
• video
• sound
• phone
• fax

The logic, editing, and actions associated with these objects are activated automatically. We are constantly combining logic to make implementation of complex objects easier for customers on the simple concept of "design once, deploy many times".

User Guide

The User Guide is now printed. It is an automatic by-product of the design.

The User Guide is a critical document in the process. It contains every screen and report with the help text for the elements. In our Process we use it as a working document so that the users can make changes and approve the application.

   1   2   3   4   [5]   6   7