Blog

We have some new updates. Version 2.3.0 includes several new features. But also some under the hood changes.

The engine that creates the titles for elements has been completely rewritten. It now is linked directly to the elements themselves. This means that titles can be customised for any element. Previously, they were tied to their own file that looked at the type of the element.

Another service, the ScoringEngine, has also been overhauled. This system takes in the elements and calculates it's score based on the configuration. Previously, all scores were stored in a JSON file. This was horrible to keep control of. Now, all Scale of Values are stored in a CSV format, making it so much easier to understand.

Feature wise, A new chart has been added that allows you to see how a program has developed. This means you can see the cumulative score, compared with the maximum achievable score, making it easier to see where you can make improvements.

Bug fixes…These were mainly just scoring issues, which have been rectified by the new ScoringEngine.

Under the hood, the validation algorithm works by comparing the inputted bundle of elements against a number of metrics. The bundle is then given a score, and a confidence value. The requirement with the highest score is then chosen as the requirement. The inputted bundle is then validated against this requirement, producing the result.

The requirement is then used as the guide for the inputted bundle. Any deductions are then applied to it, and a result is returned.