Case Based Reasoning
Erudine has developed a highly intuitive new approach to creating system behaviour, based on the concept of Case Based Reasoning.
Traditionally in IT, system functionality (or behaviour) is formed up-front by developers, who must painstakingly list the rules required in order for a system to meet requirements. With this approach, there is a high chance of errors or omissions, and significant amounts of time must be devoted to forming system behaviour for rare situations.
With Erudine’s technology, systems are taught behaviour in a way similar to children’s development. Young people learn partly through exposure to situations – they experience, or are told, the outcome of an event and are then told the reason for that outcome. Creating system behaviour with Erudine’s software follows the same approach: a domain expert tells the software the conclusion of a ‘case’ and the software prompts them to justify why the conclusion was made. Repeating this process for a number of cases quickly teaches the software the appropriate system behaviour, as it learns how to treat each case and, importantly, why.
Following the Erudine approach means any new behaviour that is required can be added effortlessly into the base of already existing behaviour. The cost of omissions and errors is dramatically reduced because of the protection offered by the Behaviour Validator, which prevents behaviour clashes, but also because the software learns the precise behaviour required as part of an integrated process, rather than an expert manually coding behaviour from a list of rules.
Case-based Reasoning also offers immense timesavings. Very common cases are dealt with early on, leaving the domain expert free to concentrate on less common cases. The entire process is also inherently much faster than the traditional approach, as it follows a more intuitive, simple method and important exceptions are much easier to add to the system.
Features
- Software learns system behaviour through exposure to cases
- Intuitive process
Benefits
- Very fast Return on Investment
- Behaviour is based on real situations
- Common behaviour is set early in development
- Massive timesavings over traditional requirements capture and coding methods
