What is this?
This is a FREE framework to make you able to externalize some parts of your software; such as your software rules and logics and then
extend your software dynamically without any recompile.
New Language?
We support Xml and SExpression as an extension point into your software.
Not Enough?
We provide mechanism allows you to develop your independent language and extend your software.
What Engines?
We have Procedural, Inference and Flow engines
Any Security?
You are able to Sign and Encrypt your externalized codes by provided Power Shell based on certificate (private/public keys) or password
Interesting?
|
|
|
|
Why a BRMS?
Software is complex by its nature and changes are inevitable
part of a business environment. Each change may affect on different part of the
software which is deriving business. so we need to be responsive to changing business
conditions. Building a system based on a BRMS solution is the only option that would
give you the agility required to meet your complex tasks and keep costs down.
More often than not, business rules are embedded in software programs. When changes
are called for, the change cycle from requirements to coding, testing, and deployment
would often take months to implement. With our BRMS, we?ve reduced the process to
days and sometimes hours.
|
|
Use a FREE Express one
Our express version is free for everyone.
Embed the flexibility into your application and enjoy being responsive to changes.
Click here for Express Features
|
When do you use a rules engine?
Not all applications should use a rules engine. If your business logic code includes
a bunch of if-else statements, you should consider using one. Maintaining
complex Boolean logic can be a difficult task, and a rules engine can help you organize
this logic. Changes are significantly less likely to introduce errors when you can
express the logic using a declarative approach instead of an imperative programming
language.
You should also consider a rules engine if code changes can cause major financial
losses
. Many organizations have strict rules about deploying compiled code in their hosting
environments. For instance, if you need to modify the logic in a Java class, usually
a long, tedious process must occur before the change makes it to the production
environment: The application code must be recompiled. The code is dropped in a test
staging environment. The code is inspected by data-quality auditors. The change
is approved by the hosting environment architects. The change is scheduled for deployment.
Even a simple change to one line of code can cost an organization thousands of dollars.
If you need to follow such strict rules and find yourself making frequent changes
to your business logic code, then it would make sense to consider a rules engine.
|
|
|
|
|
|