Erudine

Inhibits Legacy

Legacy systems are likely to occur when those who develop or maintain a system lack sufficient knowledge to alter the system safely, or at all. This is likely to occur when:


Erudine’s technology has a number of automated features aimed at overcoming the critical issues that create legacy systems.

Automatic code modelling

With Erudine's Behaviour Engine, a developer need never be concerned with how changes to an IT system will affect its overall operation. The technology maintains a model of the system and ensures changes will not unintentionally alter existing behaviour.

Automatic code modelling means developers can alter projects of far greater complexity than was previously possible, with far less risk of breaking system functionality.

Automatic requirements management

Uncovering new requirements towards the end of a project is inevitable and the ability to quickly add new requirements to an existing project is almost essential to allow for changing conditions.

The Behaviour Engine technology has features for automating all stages of requirements from entry, to removal and change. Requirements management is one area likely to turn modern, well-managed systems into legacy. Automation is critical to prevent legacy problems for large or complex projects.

Automatic workflow auditing

In complex projects, it is very important that the flow of data through the system is understood and can be reliably tested to detect any changes that alter the flow of data.

Erudine’s technology can track data and create a full audit trail. When changes are made to a system, a full set of audit data can be run through the system to check, at several different levels, whether data is passing through the system correctly.

Any system constructed using Erudine Behaviour Engine technology remains fully agile and easy to change – it will never become legacy.