MDA Radar

Issue #2 [February 27-March 05, 2006]

MDA Tools Evaluation - Part I: Evaluating ArcStyler

In the first edition of the MDA Radar, we briefly categorized the tools, listed the reputed ones, and provided a template to capture all of the important MDA aspects of the Object Management Group’s MDA specification. This week we will evaluate the tool, ArcStyler.

Tool Background

ArcStyler is a product of Interactive Objects Software GmbH, founded in 1990. Currently, ArcStyler supports and recognizes the following products during installation: BEA Weblogic 8.1 SP2, IBM Websphere 5.1, JBoss 3.2, Oracle 9.1.0, DB2 8.1, JDK 1.2 and above. The installation procedure suggests a minimum requirement of 512 MB RAM and 400 MB free disk space.

ArcStyler Architecture in Brief

Arcstyler supports different ways of modeling: creating new models from scratch using UML, and importing existing XMI-compatible models from C#, C++, CIL, CORBA IDL, DDL, EJB, Java (common Java classes, java.awt, java.lang, java.rmi, java.util, javax.ejb, javax.servlet, javax.swing), MOF, WAE, WSDL and XML.

CARAT (Cartridge Architecture) is the heart of ArcStyler architecture, based on the JMI specification and created in Jython language. It defines the interface and provides runtime framework. MDA Cartridge Engine (MCE) is responsible for the model transformation based on selected pluggable Cartridge. Arcstyler also provides graphical support for creation of customized Cartridges for a new technology or platform such as CORBA, VB, VC, and so on.

Arcstyler provides a Tool Adapter Standard (TAS) for integration with other modeling tools. TAS works as a container that defines the interfaces and services for different tasks such as interaction with plugged tools, GUI integration, management of profiles and cartridge management etc.

ArcStyler also provides a test suite that is modeled as an ordinary UML class with the stereotype TestSuite. You can add a test suite to any package using the package’s MDA Cartridge Wizards.

ArcStyler Fact Sheet

After going through the evaluation version of ArcStyler 5-0-1-021, June 20 2005, the following fact sheet is generated:





Suggested Improvements

ArcStyler holds a lot of promise in the MDA community. Their success story is also very impressive. After going through our evaluation process, it is identified that the following pieces of functionality will make it a more comprehensive and robust tool for the MDA community:

  • Explicit CIM support.
  • Explicit PSM support.
  • Explicit conversion wizards.
  • Widening the Marks feature, aligning with the MDA specification.
  • Widening the transformation feature, aligning with MDA specification.
  • GOF Pattern support in code generation phase.
  • Domain specific modeling templates.
  • Domain extensions.
  • CWM Compatibilities.
  • QVT compatibilities.
  • Pervasive services.
  • Explicit model merging.
  • Improved documentation explaining everything from an MDA point-of-view. The current approach uses the UML way, giving way to the impression that ArcStyler is a better UML tool. Documentation style should focus on MDA oriented style, examples using UML.
  • Product feature sheet needs to be more attractive to appeal to the community.

Conclusion

ArcStyler is a promising modeling initiative with several good features. At the moment ArcStyler provides mostly PIM specific modeling, marking and transformation. However, the ArcStyler flexible extension API is an excellent extensibility approach geared towards integration with other tools. ArcStyler is continuously aiming to reduce the process complexities and increasingly perpetuating best modeling practices. ArcStyle is evolving very fast and is highly likely that ArcStyler will eventually address all other missing MDA issues. ArcStyler user manuals require more thought and examples to draw user interest. The modeling industry will be greatly aided by ArcStyler modeling themes, initiatives and extensibility.

References