in a CASE environment. Ideally, the interaction mode of each tool, whether graphical or command-line, for example, should be natural for that particular lifecycle stage. Graphical symbols, where used, should have a uniform meaning behind them. It is important not to confuse CASE tools with simple drawing programs.
CASE tools should include verification and validation, the most basic level of which is error detection and correction. Factors such as completeness should also be included. CASE as a whole must also be able to accommodate backwards processing. For example, it is sometimes necessary to take code back to a design stage for manipulation, or to recreate prior release of software that has already been distributed. There also needs to be an aspect of openness in that most CASE tools come from multiple vendors in today's environment, and interfaces among these tools should avoid proprietary conventions. This element lends itself to the integrated CASE situation, which builds on basic CASE elements.
A CASE environment needs to support multiple users working on the same component, such as design, code or documentation. CASE should be object-oriented and highly automated, although the current state of the market reflects a more "semi-automated" approach (Simon, 1993, p. 7).
Implemented effectively, CASE can result in improved system development productivity, reduced productivity time, reduced maintenance costs, and enhanced information technology development. Since documentation is often generated automatically by CASE products, there is traceability which enables companies to recreate how programs work long after programmers have departed, and the automated aspect of CASE reduces some of the human error which can creep into system development. In addition, since CASE tools are used to facilitate grater standardization of work procedures and adherence to design structure, greater flexibility can occur in the workfor...