What it means to be ‘thinking in rules’
The quickest way to get an appreciation for why Inrule is such a revolutionary bit of kit to think about business logic as a set of rules or conditions that are held in a centralised repository, (for the sake of argument) similar to the way that content is stored in a content management system. Rules are managed by non-technical business users in a collaborative, organisational fashion. Software engineers no longer need to be engaged in the management of business logic and so the business benefits both from cost saving as well as the reduced time to market to deploy the rules. The software engineer is freed to work on more challenging tasks.
In short the BRMS does for business logic what CMS does for web content (ie puts the business in control) .The company is now enabled to ‘think in rules’. This is a unified collaborative approach to the way that rules are controlled and managed within an organisation.
Such technology calls for an entirely different approach to software development, one that InRule call ‘dynamic decisioning’. In essence, Software can now be designed in such a way that business technology could be changed ahead of a change in the business environment.
For example, if a change in legislation is thought to occur which had a knock on effect on the business processes within the organisation, those changes could be written in advance, tested then activated on the passing of the legislation so that that the business transitions seamlessly.
How would your business benefit from ‘thinking in rules’?
Did you enjoy this post? Why not leave a comment below and continue the conversation, or subscribe to my feed and get articles like this delivered automatically to your feed reader.
[...] Original davebirchall [...]