1. CASE1 Computer-Aided Software Engineering Advanced Software Engineering COM360 University of Sunderland © 2000

2. CASE2 Why Do We Need CASE? Poor project management Incorrect feasibility assessment Incomprehensible code Lack of engineering discipline Poor quality control

3. CASE3 Evolution of Software Tools Assemblers, Core Dump Analyzers Compilers, execution profilers Symbolic Debugger, Subroutine Packages Source Code Control Systems Requirements Analysis & Design Tools Source Code Generators

4. CASE4 In its idealized form, CASE combines; –as a set of software development tools, –integrated with a database, –to form an environment.

5. CASE5 Data store Data Dictionary Structured Diagramming Tools Report Generator Skeleton code generator query language facilities Form generator Design analysis tool I/O facilities A Generalised CASE Architecture

6. CASE6 CASE Tools Most CASE tools implement structured design methodologies developed during the 1960s and 70s. Design specification tools generally use the structured analysis and structured design methodologies of DeMarco and Yourdon. These can be used to specify and design almost any piece of software.

7. CASE7 Software Development Tools The tools each address important step in the software engineering process - based on the existing structed design methodologies.

8. CASE8 Software Development Tools Development Phase –Requirements Analysis –Design Specification –Implementation –Maintenance Specialised Tools –User interface and Prototyping & Strctrd Analysis Tools –Data Modelling and Design Spec tools –Compilers, Editors, Debuggers, Control

9. CASE9 Specification Phase Two important classes –Data flow diagramming tools. –Data dictionary - A tool that stores the name of format of every component of every data item in the system

10. CASE10 Requirements Analysis Design Code Test Maintain SEE- High end CASE PSE- Low end CASE

11. CASE11 The Type of Demand for CASE PC user ->Individual Tools Small project ->Integrated tools Large / Complex System ->Integrated Project Support Environment

12. CASE12 Characteristics of Good CASE Tools Simplify the job Aid communication between developers/customers Save time and money Produce verifiable designs Support design changes.