Computer Aided Software Engineering

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 documentat

. . .
(GUI versus command line, for example). Control integration is concerned with the formal, standard tool notification system that crosses tools and keeps the entire development process under control. In this way, announcements and details of modifications on one tool are sent to all other tools concerned with those changes. Such integration capabilities may include event notification when appropriate, a formal intertool communication mechanism, and formal application programming interfaces (APIs). Process integration means that the tool is oriented toward the practice of formal software engineering techniques. This means that the additional processes required to complete the software engineering process (those that are required in addition to the software tools themselves) should be integrated into the overall procedures. These mean that the tools should be directed related to tasks in the software process, and that the processes themselves should form the basis for future CASE environments (Sullivan-Trainor 72). Finally, data integration is critical to the ICASE environment, and is generally the area that receives the most attention in the case arena. Data integration requires that data and relationships among the many to
. . .

Some common words found in the essay are:
Software Engineering, Engineers IEEE, APIs Process, NT Chicago, PowerPCs Pentiums, Hewlett-Packards RISC, Institute ANSI, Design August, Computerworld April, Business March, platform integration, data integration, icase environment, software engineering, lack standards, true icase, user interface, presentation integration, client/server environment, control integration,
Approximate Word count = 1219
Approximate Pages = 5 (250 words per page)

More Essays on Computer Aided Software Engineering