I think we would benefit a lot from having Undraleu but need help in quantifying the benefits of Undraleu for creating a business case, can you assist?

There are some clear benefits from using Undraleu® that include all the benefits you expect by following set best practices. However, there are some hard to measure benefits that we can’t quantify examples include reduction in support, maintenance and on-call costs.

Please contact us and we can help quantify the benefits and help build a business case for you.

Is Undraleu easy to learn?

While building Undraleu, we kept simplicity as the core objective. We can’t dispute the findings of Heisenberg’s Uncertainty principle but in our goal to make ETL in general and Informatica Development in particular more productive, this tool does cause one extra step (i.e. login and select the code to review) but the outcome of the review should improve the long term code quality, supportability, maintainability and other key aspects of code quality.

Our Development Team has built a similar tool? Why should we consider Undraleu?

We are twins! We are always looking for opportunities to improve Undraleu further. Also, taking a look at Undraleu may also provide some pointers to improve your tool. However, here are some benefits of not doing it on your own:
1. Unless your company’s business is developing such a tool, you are not directly working for its strategic goals.
2. It needs a lot of maintenance and unless you have an entire team working on it you will perhaps be not enhancing it much.
3. It is also possible that some key folks are just managing the software and not developing systems that your business needs.
4. Industry collaboration – Undraleu’s customers have been critical for its features and enhancements. From couple of hundred rules to now more than 500 rules we wouldn’t have been able to do it alone. We benefit from more than 1500 users across our customers and their feedback to make Undraleu constantly evolve and provide value to our customers.
5. It provides better ROI.
6. You don’t have to worry about upgrades etc.

Undraleu Terminology


A rule is a single best practice. You can pick the rule or group of rules you want your code to be checked against and create a rulelist.


A rulelist is a group of rules or checks that you would like to use to measure your code against. A rulelist can have one or more rules. This is a good way to group rules that perform a particular set of checks. For example a rulelist can be created for Development activities of a project. Another rulelist can be created for Production checks or for performance etc. This enables checking different aspects of code for more insight into specific anomalies. Rulelists can be managed at site, project or user level. Site level rulelists are also referred to as Shared Rulelists. Shared rulelists are available to all projects and all users.


Each rule or best practice has a reason or area that it will impact if not followed. Undraleu refers to them as Category. Examples of Categories are: Maintainability, Readability, Supportability, Complexity etc. Each rule or best practice may belong to one or more Category. For example not following naming conventions may make the code not easy to maintain and not easy to read.


Criticality is a way of assessing the impact of violating a best practice. Undraleu allows managing the Criticality level of each rule (it can be user defined). Examples of Criticality are: Show-Stopper, Severe, Major, and Minor. By marking a best practice to one level of criticality allows a quick assessment of the code to be of a certain level of quality.

Criticality levels can drive whether the quality of the software is meeting expected standards and whether the code should promoted to production or refactored.