Meta CASE Tool - Real Benefits of Using Meta-CASE Tools

Real Benefits of Using Meta-CASE Tools

Jackson recognises the vital difference between an application’s domain and its code: two different worlds, each with its own language, experts, ways of thinking etc. A finished application forms the intersection between these worlds. The difficult job of the software engineer is to build a bridge between these worlds, at the same time as solving problems in both worlds.

Empirical studies have consistently shown that only around half of all development projects use methods. Among those using methods, over 50% either modify the methods to better fit to their need or even develop their own methods

In a standard CASE tool, the method supported by the tool is fixed: it cannot be changed. In a meta-CASE tool, there is complete freedom to change the method, or even develop an entirely new method. Both models and metamodels (method descriptions) are stored as first-class elements in the repository. This allows an organisation to develop a method that suits their situation and needs, and to store and disseminate that knowledge to all developers. The tool and method then guide developers, provide a common framework for them to work in, and integrate the work of the whole team.

Research prototypes and even commercial meta-CASE tools have existed for many years, but only recently have there been tools which are mature, user-friendly and stable for both the method developer and the method user. One of the most widely known and used meta-CASE tools is MetaEdit+.

Following list represents several kinds of ways how these tools can be used within software development:

• can reduce the time and cost to develop a computer-aided environment
• can support formal software development methods
• can support comparison of development environments
• can used as an information systems modeling tool
• can support structured methods
• can support object-oriented analysis and design
• can be used as a logistic modeling tool
• can support a wide variety of methods
• can support CASE training

These tools should also possess the following characteristics:

• enabling users to create method support for their own software engineering methods with low learning curve
• to have easy to use graphics CASE tools to support simple and efficient user interactions
• to have the capability to check the consistency of a model, even at run-time
• to have standard report generation facility
• to possess transformation capability to transform from one method to other
• to possess capability to inject CASE metrics
• to possess complexity management tool that provides restricted views and granular model representations
• to possess sophisticated input dialogs for creation and modification of model data
• to possess customizable multi-method support