What kind of Rules/Checks Undraleu Covers?

There are various rules that Undraleu provides. These are a result of constant collaboration between our customers and our research and interaction with the ETL Development community. We typically classify the rules into categories (for Qualitative Impact) and criticality (for Severity Impact). Undraleu rules address a range of categories and criticalities including data loss, error handling, performance, maintenance, documentation and show stoppers, critical, major etc.

We have completed our evaluation of Undraleu and would like to preserve our customization and move to a Production License. Is it possible?

Yes, this is a common requirement for all our customers who have done an evaluation and moved to a production version.

We provide two paths to production installation of Undraleu:
1. Fresh Install (First time install)
2. Upgrade from Evaluation Version.
We can help you follow the path #2 and preserve your evaluation environment and migrate your evaluation environment to a production environment very easily, at no additional cost.

Who do you think are target users for 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

Can we customize the rules/checks?

Yes. There are some rules that can be customized e.g. naming convention. There are other rules that are looking for a selected option e.g. “Aggregator Sorted Input Enabled”. We appreciate that each organization may have adopted different standards and also within each organization different code sets/projects may adopt different standards. Undraleu allows you to customize as per your projects’ requirement.

Let us go over an example to illustrate the naming standards for mappings. We provide a default prefix of “m_” for a mapping name. You may want to adopt a “MP_” across your organization. You can override our value to apply instead “MP_” as your standard. Yet, there may be some legacy projects that may have used a naming convention of “MAP_” for mappings. You can allow a further override at the legacy project level to accept “MAP_” as the standard and still allow the rest of the organization to conform to “MP_”. This allows you to embrace your own standards seamlessly yet allow enough flexibility in a controlled manner.

Most of our ETL work is done offshore, how can Undraleu assist?

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.