Page 235 -

220 PASTOR, MOLINA, AND IBORRA
would choose to use the JSP Transformation Engine and the EJB Transformation Engine using
MySQL as database.
The JSP Transformation Engine, for instance, would transform each element in the presentation
model view to its corresponding element in the JSP application model (such as JSP pages, servlets,
validation scripts, etc.) and then each element in the JSP application model into the corresponding
text (HTML, JavaScript, etc.).
If the analyst decides to target another platform (i.e., ASP.Net for the presentation layer, C#
in the business logic layer, and SQLServer database for persistence) since her/his OO-Method
conceptual model is truly platform-independent, s/he would only need to “recompile” her/his
model again with the appropriate set of OLIVANOVA Transformation Engines (namely, the ASP.
Net Transformation Engine and the C# Business Logic Transformation Engine using SQLServer
as database) without making any change or modification to it.

CONCLUSIONS

Even though researchers have been talking about the “crisis of software” for the past few decades,
producing an information system today is still a costly process (expensive resources are used over
extended periods), much too slow for modern business conditions, very risky (hard to control, and
with a high failure rate), and highly unsafe (due to the many hidden failure points). Considering
that the software development process has not changed much in the past forty years and that it
has basically centered on the idea of programming, it is time to consider whether there might not
be a better way.
In line with the modern approaches based on MDA, Extreme Non-programming, Conceptual
Schema-Centered Development, and the like, we have presented a method (the OO-Method) with
a supporting set of tools (OLIVANOVA Model Execution) that is based on a different “concept”:
the idea that “the model is the code” instead of the conventional, programming-based idea where
“the code is the model.” This new framework provides a computer-aided software development
environment that is designed to deal with information systems development through the required
processes of model transformation.
Specifically, we have shown how to build a precise conceptual schema and how to convert it
into its corresponding software product by defining the mappings between conceptual primitives
and their software representation counterparts. These mappings are the core of a model compiler
that makes the following statement a reality: “to develop an information system, it is necessary
and sufficient to define its conceptual schema.” The automation of systems building then becomes
an affordable dream that is waiting for tools (such as the ones presented in this chapter) to justify
its adoption in practice.

REFERENCES

Arcstyler. Interactive objects–business–IT transformations. Available at www.arcstyler.com (accessed June
2006).
CARE Model Compiler. CARE Technologies products: transformation engine. Available at www.care-t.com/
products/transengine.html (accessed June 2006).
CARE Modeler. CARE technologies products: modeler. Available at www.care-t.com/products/modeler.
html (accessed April 2007).
Care Technologies. 2007. Care Technologies: OlivaNova: the programming machine. Available at www.
care-t.com (accessed June 2007).
Eakman, G. 2007. MOF Model-to-Text Transformation Language RFP. Available at www.omg.org/cgi-bin/
doc?ad/2004–4-7 (accessed May 2007).