Most organizations have been using ETL Tools since a long time and have a lot of legacy code that undergo maintenance along with more recent code. From our experience, we realize that most companies have challenges in production environment. One quick win in having Undraleu run on production environment is to identify and learn from the findings and not repeat those mistakes in new deployments. This will ensure stemming any new issues from cropping up in production environment.

While there are development shops which are very well structured and conduct code reviews thoroughly, in all possibility it is a manual review. Such shops which pride themselves in their personnel and code reviews can benefit even further by automating their code reviews and spare themselves with at least a few hours of the time they spend in performing the code reviews and deliver more projects and improve their overall value from their stake holders’ perspective. In short, using Undraleu, you can develop more of the good code you have been developing without Undraleu.

Anybody or everybody who has an interest in the quality of the code being developed, maintained or supported. Some of the roles' of folks who are currently using Undraleu are:

Developers

Technical Leads

Administrators

Project Managers

Application Managers

Quality Assurance

Deployment Managers

Operations/Platform Managers

Architects

CTO’s

Off-shoring has been embarked by various organizations for multiple reasons. Some reasons have been questioned and some proven. One pain-point we see in off-shoring, outsourcing, near-shoring, right-shoring or whatever the arrangement is, there is no transparent definition and monitoring of quality. Undraleu was built to bring in code quality monitoring in a self-service manner. This allows everybody and anybody to monitor the code quality. Through Undraleu, you can now make it mandatory for your offshore service providers to enforce quantified, measurable and consistent code governance. The standards can be decided by your team and communicated to the offshore team. The offshore team can scan the code against the agreed standards to ensure they are in conformance to them before they deliver the code. The client can double check to ensure what has been delivered meets the standards agreed. In a multi-vendor arrangement Undraleu can be also used to evaluate the quality of the different vendors and take a decision to continue or discontinue a vendor’s services using facts.

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.

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.

Rules

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.

RuleLists

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.

Category

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

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.