CASE Software Automates

Computer Aided computer software program Engineering (CASE) can be described as a collection of hawkshaws used in the software development abut (Simon, 1993, p. 6). Each be in the software development lifecycle has diametric tool requirements, and CASE products provide tools for each stage. Interaction musical modes shift depending on the tools in a CASE environment. Ide every last(predicate)y, the interaction mode of each tool, whether graphical or education-line, for example, should be natural for that ill-tempered lifecycle stage. Graphical symbols, where used, should abide a uniform meaning nooky them. It is important not to confuse CASE tools with simple order of payment programs.

CASE tools should include verification and validation, the most basic direct of which is error detection and correction. Factors such as completeness should in any case be included. CASE as a whole must also be able to accommodate backwards processing. For example, it is sometimes needful 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, whic

When high-end microcomputers are used as servers, as is increasingly the situation, the benefits of Unix become less clear. These machines, while compatible with Unix and receptive of running Unix, have their own operating systems for which most of their software is written. The strong presence of the Windows operating environment and the promise of Windows NT betoken that Unix may have problems making additional inroads into this market.

Presentation integrating refers to having a single standard user interface for all CASE tools. In recent years, graphical user interfaces (GUIs) have become increasingly common, but there is a need of standardization regarding their use and first appearance.

In a true ICASE environment, presentation should offer common user interface facilities regardless of the tool in use or the type of interface (GUI versus command line, for example).

Bulkeley, D. (1993, March). CASE makers hear opportunity knocking. Electronic Business, pp. 118-119.

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 tools in the lifecycle stages can be shared and manipulated. To accomplish this, tools should be able to communicate through and across a shared repository, and the requirement services should include object storage, version sway, concurrency management, access control and notification.

What these competing standards illustrate is another problem that ICASE currently faces: that of incompatible standards. From the outdoor stage of users, it is nearly better to have a complete overleap of standards than standards that compete with each other and are compatible. The American matter Standards lay down (ANSI) formed an X3H6 committee in 1992 to create or adopt tool integration standards. A different group, the Institute of Electrical and Electronic Engineers (IEEE), sponsors a di
Order your essay at Orderessay and get a 100% original and high-quality custom paper within the required time frame.