top of page



As a business user testing tool, ODM Decision Validation Services (DVS) plays a central role in the rule governance process. It has the potential not only to be used for rule validation by business stakeholders throughout the life of the rule application, but  also for regression testing whenever technical refactoring or tuning is performed by IT stakeholders.


However, the inherent potential of DVS is not realized as it lacks some critical capabilities that inhibit its adoption through the project lifecycle. Business users frequently run into challenges and ask these questions:


  • Invalid Excel input data leads to nasty Java exceptions that are detected only during test execution. How do I validate my input Excel data?

  • The data relating to a scenario spans across multiple tabs. How can I easily navigate across tabs for a specific scenario?

  • Data records are often shared across scenarios. Can I identify which scenarios will be impacted when I modify a data record?

  • My business object model has evolved. How can I apply these changes to existing DVS files?

  • The development team is changing the execution object model, ruleflow and other details for performance reasons. How can I ensure that business functionality has not been compromised?

  • My DVS file has been corrupted due to copy and paste from other DVS files. How can I repair this file?

  • Can I remove unused data records that clutter my DVS spreadsheets?

  • Over time, as I create several DVS files, how can I reorganize the scenarios contained in them?


DVSBoost provides the capabilities to empower a business user to deal with all these issues. It is an Excel Add-in that seamless integrates with DVS to enhance the usability and managabiliy of test scenarios, thereby maximizing its effectiveness. 

DVSBoost in Action


Upon installation of DVSBoost, it is easily accessible in the Data ribbon on your Excel spreadsheet.

To glimpse DVSBoost in action, check out this short video:

DVSBoost Benefits


With DVSBoost, the rule validation function can truly be accomplished by business stakeholders with minimal involvement from IT staff.



  • Put the business users in control of the test scenarios by allowing them to easily navigate even complex object models through hyperlinks.

  • Prevent accidental scenario modifications by enabling business users to easily identify which scenarios use a data record and comprehend the impact of data changes across multiple scenarios.

  • Through automatic refactoring, enable the continued use of DVS scenario files even after the business object model significantly evolves.

  • Prevent clutter from building up in scenario files by identify and removing orphan data records that are not used in any scenarios.

  • Enable testers to easily verify or share a test case with other teams by generating a report containing the complete scenario.

  • Improve efficiency by allowing testers to identify and correct any input data errors prior to submitting the data for execution.

  • Enable business users to safely create a variation of a scenario by allowing them to extract that scenario to a separate file.

  • Allow users to structurally repair DVS files that have been accidentally corrupted.

  • Improve effectiveness of business users by enabling them to perform housekeeping activities (merging or splitting) DVS files.

RuleScape DVSBoost Evaluation
bottom of page