Compuware launches OptimalJ 3.1

Compuware has released version 3.1 of its OptimalJ development tool, which offers automatic generation of web services applications.

Version 3.1 is the first development environment to fully implement the new web services security standard. It also includes the ability to develop models from scratch in the universal modelling language (UML) within the development tool.

OptimalJ uses the model-driven architecture (MDA) approach to produce Java 2 Enterprise Edition (J2EE) applications from UML models, incorporating standard code - called 'patterns' - for deploying on different systems.

This keeps design models and documentation synchronised with application code, while using patterns to handle complex repetitive tasks such as some J2EE functions.

Ruud Grotens, OptimalJ product manager, told vnunet.com: "Customers want a tool they are comfortable with, and standards-based as they hate vendor lock-in."

He said this approach could lead to major productivity gains, citing analyst research that 75 per cent of large-scale J2EE projects missed both time and budget projections.

Release 3.1 implements web services security using simple tick-box clicks to select the different types of security required - such as encryption. Web services applications can be completely generated.

Bola Rotibi, lead analyst at Ovum, said: "The web services capability, particularly with security, is good. But its use of patterns to implement J2EE for seasoned Java developers is its strongest feature."

OptimalJ still lacks basic profiles for web services interoperability, although there is little call for this as yet, she added.

"The problem is [still] requiring people to take a different approach to development which is less about code than high-level thinking," said Rotibi.

Version 3.1 also provides the J2EE code variations for BEA WebLogic 8.1, IBM WebSphere 5, Oracle and SunONE, and the open source JBoss and Jonas application servers.

Expanded utilities support model importing and exporting in the XML metamodel interchange format from Borland Together Control Center 6.1, IBM Rational Rose 2002 and Sparx Systems Enterprise Architect 3.51.

Currently OptimalJ supports UML 1.3, with full UML 2.0 support scheduled for its next release.