OTCL: Best object-conversion CASE tool for softwr developers

OTCL is all about generating object-conversion source code. It’s a new language executed by the OTCL Engine to generate the object conversion code required in your software projects. A developer will have to spend only a few minutes to create the OTCL files through an automated process and the engine will execute the OTCL files and generate all that object conversion code for you in just few seconds.

If you are in the management managing software projects, one of the many objectives you have is to minimize project costs and maximize the revenue. A few thousand $$$ saved in every software project could add up to the savings of a sizable amount at the organization level. The developers in your organization, or if you happen to be a software developer yourself, would have performed activities of writing object-conversion code in your software projects. Typical scenarios would have been converting entity-objects loaded from the database to business-domain objects for use in the service layer, and also the reverse of it for the reverse flow. Similarly, you would have also written object conversion code to do conversions when data has to be sent-to, or received-from a B2B, or a B2C, or a legacy or a UI application. Having all this object conversion code generated automatically is a great idea.

A simple search on object-mapping frameworks gives at least 15 projects intending to solve the same problem. However, there may not have been so many attempts to solve the same problem, if all the requirements were rightly met.

In my search, I couldn’t find a tool that had the crucial features to solve the developer’s problem in its entirety. Let me explain this in few points – a framework should handle deep-object paths that contains all kinds of collections including map-keys and map-values in the object path. And all mixes and matches of all such complex object-paths between the source and target also should be handled well.

Constructing a composite object from assorted object-paths in the source object is another flexibility that is expected in an object-mapping framework.

Consider another scenario where there are multiple collection types in the object-paths in both the source and the target. Now, which one of the collections in the source be matched to which one in the target? As the requirement in each software project can vary, the tool should make the choice flexible enough without consuming much of a developer time and effort. Don’t worry if you were not able to grasp what I just said as it will become clear in a couple of minutes when I will introduce a very productive feature in OTCL.

An object mapper should not demand much of the time and effort writing too verbose configuration, or mandate writing any kind of code such as interfaces etc.

Lastly a framework should give a great performance and should be as light-weight as possible.

The absence of all these benefits and the lack of flexibility inhibits a software programmer or the organization from adopting such a framework.

OTCL is a great solution which stands out with immense benefits.