• PROJECT SCHEDULING AND TRACKING

• Basic concepts
• Relation between people and effort
• Defining task set for the software project
• Selecting software engineering task
• SOFTWARE CONFIGURATION MANAGEMENT
• Basics and standards
 USER INTERFACE DESIGN

• Rules
 COMPUTER AIDED SOFTWARE ENGINEERING TOOLS
• CASE building blocks
• Taxonomy of CASE tools
• Integrated CASE environment

Module VI 1
 COMPUTER AIDED SOFTWARE ENGINEERING TOOLS
• CASE building blocks
• Taxonomy of CASE tools
• Integrated CASE environment

COMPUTER AIDED
SOFTWARE ENGINEERING
TOOLS 2
• Computer-aided software engineering (CASE) tools assist software engineering
managers and practitioners in every activity associated with the software process.

• CASE is the name given to software used to support software process

activities such as
• Requirements engineering
• Design
• Program development and testing
• CASE tools include
• Design editors
• Data dictionaries
• Compilers
• Debuggers
• System building tools and so on.

Introduction 3
• CASE tool is a tool that is used for providing
automated support for s/w engineering
• It is used to automate the activities associated with
s/w development
• CASE tools assist phase related tasks such as
• Specification
• Structured analysis
• Design
• Coding
• Testing
• CASE tools that focus on non phase activities such as

CASE tools and its

• Project management
• Configuration management

scope 4
• CASE tools are used to improve software
development & maintenance
• It reduces the efforts of s/w development &
maintenance
• Help to develop better quality products more
efficiently
• Increase productivity
• Help produce better quality s/w lower cost

CASE tools and its

scope[2] 5
•  CASE classifications help us understand
• The types of CASE tools
• Their role in supporting software process activities.
• CASE tools can be classified based on three
perspectives:
• Functional perspective
• Process perspective
• Integration perspective

CASE classification 6
•  Fuggetta proposes that CASE systems  should be
classified in three categories:
• Tools
• Workbenches
• Environments

Classification of CASE
systems 7
•  Tools support individual process tasks such as
• Checking the consistency of a design,
• Compiling a program
• Comparing test results.
• Tools may be general-purpose.
• Standalone tools
• Grouped into workbenches.

Tools 8
• They support process phases or activities such as
• Specification
• Design
• They normally consist of a set of tools with some
greater or lesser degree of integration.

Workbenches 9
• Environments support all or at least a substantial
part of the software process.
• They normally include several integrated
workbenches.

Environments 10
Classification of CASE
systems 11
• Individual CASE tools are integrated to a common
framework or environment
• If different CASE tools are not integrated,
• Data generated by one tool has to be inserted to
other tool
• Involve format conversions as the data developed
by different tools will have different formats
• This result in additional effort of exporting data
from one tool & importing to another

CASE environment 12
CASE environment 13
• CASE environment provide a central repository
• This is to have a consistent view of information's
produced by different CASE tools
• Different tools cover different stages of s/w
development
• They all access the info from this central repository
• This is a data dictionary that contains the definitions
of all data items
• Through this central repository, all CASE tools in an
environment shares the common info

14
• CASE environment
• Facilitates the automation of step by step methodologies of s/w development
• Programming environment
• It is an integrated collection of tools to support only the coding phase of s/w
development
• Tools integrated in programming environment
• Text editor
• Compiler
• Debugger

• Eg:
• Turbo C environment
• Visual Basic
• Visual C++

CASE environment Vs
programming environment 15
• Components of CASE environment
• User interface
• Tool set
• Object management system (OMS)

Architecture of a CASE environment 16

17
• User interface
• Provides a consistent framework for accessing
different CASE tools
• This helps user to interact with different tools
• reduces overhead of learning how different tools are
used
• Object management system
• CASE tools represent s/w products as a set of entities
• OMS maps these entities into the underlying storage
management system (repository)

18
• Cost saving through all s/w development phases
• Effort reduction of 30 -40%
• Improvements in quality
• Less effort needed in every phases
• Reduction of human errors
• Produce high quality & consistent documents
• Since data is stored in central repository, redundancy is
reduced & maintain consistency
• Reduces the drudgery of engineers work while
creating and balancing DFD’s
• Cost saving in maintenance

Benefits of CASE
• Creates an impact on the working style of a company
19
THANK YOU
20