Computer-aided software engineering (CASE)—sometimes called computer-aided systems engineering—provides software tools to automate the methodologies we have just described to reduce the amount of repetitive work the developer needs to do. CASE tools also facilitate the creation of clear documentation and the coordination of team development efforts. Team members can share their work easily by accessing each other‘s files to review or modify what has been done. Modest productivity benefits can also be achieved if the tools are used properly. Many CASE tools are PC-based, with powerful graphical capabilities.
Computer-aided software engineering (CASE), also called, computer-aided systems engineering provides software tools to automate the system development process by reducing the amount of repetitive work developer normally needed. CASE tools also facilitate the creation of necessary documentation and the coordination of development team. Team members can share their work easily by accessing each other‘s files to review or modify what has been done. Significant productivity can be achieved if the tools are used properly. Generally, CASE tools are PC-based, with powerful graphical capabilities.
CASE tools automatically tie data elements to the processes where they are used. If a data flow diagram is changed from one process to another, the elements in the data dictionary would be altered automatically to reflect the change in the diagram. CASE tools also contain features for validating design diagrams and specifications. CASE tools thus support iterative design by automating revisions and changes and providing prototyping facilities. A CASE information repository stores all the information defined by the analysts during the project. The repository includes data flow diagrams, structure charts, entity-relationship diagrams, UML diagrams, data definitions, process specifications, screen and report formats, notes and comments and test results.
It also tools provides automated graphics facilities for producing charts and diagrams, screen and report generators, data dictionaries, extensive reporting facilities, analysis and checking tools, code generators, and documentation generators. In general, CASE tools increases productivity and quality by doing the following:
• Enforce a standard development methodology and design discipline
• Improve communication between users and technical specialists
• Organize and correlate design components and provide rapid access to them using a design repository
• Automate tedious and error-prone portions of analysis and design
• Automate code generation and testing and control rollout
Many CASE tools have been classified in terms of whether they support activities at the front end or the back end of the systems development process. Front-end CASE tools focus on capturing analysis and design information in the early stages of systems development, whereas back-end CASE tools address coding, testing, and maintenance activities. Back-end tools help convert specifications automatically into program code.
CASE tools provide automated graphics facilities for producing charts and diagrams, screen and report generators, data dictionaries, extensive reporting facilities, analysis and checking tools, code generators, and documentation generators. In general, CASE tools try to increase productivity and quality by doing the following:
• Enforce a standard development methodology and design discipline
• Improve communication between users and technical specialists
• Organize and correlate design components and provide rapid access to them using a design repository
• Automate tedious and error-prone portions of analysis and design
• Automate code generation and testing and control rollout
CASE tools automatically tie data elements to the processes where they are used. If a data flow diagram is changed from one process to another, the elements in the data dictionary would be altered automatically to reflect the change in the diagram. CASE tools also contain features for validating design diagrams and specifications. CASE tools thus support iterative design by automating revisions and changes and providing prototyping facilities. A CASE information repository stores all the information defined by the analysts during the project. The repository includes data flow diagrams, structure charts, entity-relationship diagrams, UML diagrams, data definitions, process specifications, screen and report formats, notes and comments and test results.
CASE tools provide some of the following facilities:
• Diagramming tools are used to draw the system models required or recommended in most methodologies.
• Description tools are used to record, delete, edit, and output non-graphical documentation and specifications.
• Prototyping tools are used construct system components including inputs, outputs, and programs.
• Inquiry and reporting tools are used to extract models, descriptions, and specifications from the repository.
• Quality management tools analyze models, descriptions, and prototypes for consistency, completeness, or conformance to accepted ‗rules‘ of the methodologies that the CASE tools support.
• Decision support tools provide information for various decisions that occur during systems development.
• Documentation organization tools are used to assemble, organize, and report repository information that can be reviewed by system owners, users, designers, and builders.
• Design generation tools automatically generate first-draft designs for various system components based on the business requirements recorded in the repository, and technology standards provided by the system designer.
• Code generator tools automatically generate application programs, or significant portions of those programs.
• Testing tools help the system designers and builders test databases and application programs.
• Data sharing tools provide for import and export of repository information to and from other software tools that cannot directly access the repository.
• Version control tools maintain the integrity of the repository by preventing unauthorized or inadvertent changes, and saving prior versions of various information stored in the repository.
• Housekeeping tools establish user accounts, privileges, repository subsets, tool defaults, backup and recovery, and other essential facilities.