CASE, as a key technology in information system (IS) industries, has received increasing attention. With CASE, designers can interactively shape, inspect and change their creations instantly. In the development of business process reengineering (BPR), the group of designers includes business executives who are responsible for designing or reengineering business processes, but generally are not efficient with IS technologies. Existing CASE techniques and tools are not well oriented for this type of end user. As a consequence, the business person's involvement in BPR development is obstructed. The 'End User Oriented Business Flow Editor' (EUOBFE) approaches this problem by supporting business people with: (1) a familiar language and notation to model business processes; (2) a knowledge base to validate the model; (3) a typed predicate scheme and object lifecycles to develop business rules; (4) a form composer and database to electronically create, tailor and manipulate the business forms and data; and (5) a pen-based user interface to provide a natural and easy way to use EUOBFE.>

The evolution support environment (ESE) system, which provides a framework for capturing and making available semantic information about software components of an evolving software system, is described. The goal in the design of the ESE system was to provide integrated support for management of software architecture configuration, life-cycle configuration, and version control. Software architecture configuration management allows tracking of interconnections among software components that make up a system. Life-cycle management allows traceability among specifications, design, code, and test cases during software development. Adding version control allows specific versions of software objects and their associated objects, such as specifications and test cases, to be retrieved. The authors' experience with the use of the system is discussed.>

In the past, a number of methods have been proposed to model and validate communication protocols that have already been designed. However, design criteria and design aids are still lacking for designing correct protocols. The objective of developing automated protocol synthesizers is to provide a systematic way of designing new communication protocols such that their correctness can be ensured.