CASE (Computer Aided Software Engineering) tools automate activities across the software development lifecycle. They include upper case tools that support analysis and design, lower case tools that support coding, and integrated tools that support all phases. CASE tools play major roles in project management, data modeling, documentation generation, version control, and more. They provide advantages like improved quality, productivity, and cost savings through automation and consistency across the development process.

1. UNIT-5
CASE TOOLS
Dr.V.Sutha Jebakumari,
AP/CSE, KCET
May 15, 2021

2. CASE
> CASE stands for Computer
Aided Software Engineering. It means,
development and maintenance of software
projects with help of various automated
software tools.
2

3. CASE TOOLS
> CASE tools are set of software application programs,
which are used to automate SDLC activities.
> CASE tools are used by software project managers,
analysts and engineers to develop software system.
> Use of CASE tools accelerates the development of
project to produce desired result and helps to uncover
flaws before moving ahead with next stage in software
development
3

4. Objectives of Case
> The various objectives are
> · Improvement in productivity: by reducing the time of
design and development.
> · Improvement in information system quality: by
providing automation.
> · Improvement of effectiveness: performing the right
task with minimal effort.
4

5. 5
Environment having CASE

6. Role of CASE Tools
6
CASE tools play a major role in the following activities:
• Project management
• Data dictionary
• Code generation
• User interface design
• Schema generation
• Creation of meta-data for data warehouse
• Reverse engineering
• Re-engineering
• Document generation
• Version control
• OO analysis and design
• Software testing
• Data modeling
• Project scheduling
• Cost estimation

7. Components of CASE Tools
> Central Repository
> Upper Case Tools
> Lower Case Tools
> Integrated Case Tools
7

8. Components of CASE Tools
> Upper — support analysis and design phases
> Lower — support coding phase
> Integrated — also known as I-CASE support
analysis, design and coding phases
>
8

9. CENTRAL REPOSITORY
9

10. UPPER CASE TOOLS
10

11. LOWER CASE TOOLS
11

12. 12

13. You can also split your content
Black
Is the color of ebony and of
outer space. It has been the
symbolic color of elegance,
solemnity and authority.
13

14. And tables to compare data
14

15. CASE TOOL TYPES
15
Diagram tools
Used to represent system components, data and control flow
among various software components and system structure in a
graphical form.
Eg: Flow Chart Maker tool for creating state-of-the-art flowcharts
Process Modeling Tools
Process modeling is method to create software process model,
which is used to develop the software.
Process modeling tools help the managers to choose a process
model or modify it as per the requirement of software product.
Eg: EPF Composer

16. CASE TOOL TYPES
16
Project Management Tools
• These tools are used for project planning, cost and
effort estimation, project scheduling and resource
planning.
• Managers have to strictly comply project execution
with every mentioned step in software project
management. Project management tools help in
storing and sharing project information in real-time
throughout the organization.
Eg: Creative Pro Office, Trac Project, Basecamp.

17. CASE TOOL TYPES
17
Documentation Tools
• Documentation in a software project starts prior to the
software process, goes throughout all phases of SDLC and
after the completion of the project.
• Documentation tools generate documents for technical
users and end users.
• Technical users are mostly in-house professionals of the
development team who refer to system manual, reference
manual, training manual, installation manuals etc.
• The end user documents describe the functioning and
how-to of the system such as user manual.
Ex: Doxygen, DrExplain, Adobe RoboHelp for documentation.

18. CASE TOOL TYPES
18
Analysis Tools
• Help to gather requirements, automatically check for any
inconsistency, inaccuracy in the diagrams, data redundancies or
erroneous omissions.
• Eg: Accept 360, Accompa, CaseComplete for requirement analysis,
Visible Analyst for total analysis.
Design Tools
• Help software designers to design the block structure of the
software, which may further be broken down in smaller modules
using refinement techniques.
• These tools provides detailing of each module and interconnections
among modules.
• Eg: Animated Software Design
.

19. CASE TOOL TYPES
19
Configuration Management Tools
Deal with –
• Version and revision management
• Baseline configuration management
• Change control management
Eg: Fossil, Git, Accu REV.
Change Control Tools
• Part of configuration management tools.
• Deal with changes made to the software after its baseline is fixed or
when the software is first released.
• CASE tools automate change tracking, file management, code
management and more.
• It also helps in enforcing change policy of the organization.

20. CASE TOOL TYPES
20
Programming Tools
• Consist of programming environments like IDE, in-built modules
library and simulation tools.
• Aid in building software product and include features for simulation
and testing.
Eg: Eclipse.
Prototyping Tools
• Prototyping CASE tools essentially come with graphical libraries.
• They can create hardware independent user interfaces and design.
These tools help us to build rapid prototypes based on existing
information.
• They provide simulation of software prototype.
Eg: Serena prototype composer, Mockup Builder.

21. CASE TOOL TYPES
21
Web Development Tools
Assist in designing web pages with all allied elements like
forms, text, script, graphic and so on.
Provide live preview of what is being developed and how will it
look after completion.
Eg: Fontello, Adobe Edge Inspect, Foundation 3, Brackets.
Quality Assurance Tools
Consist of configuration and change control tools and software
testing tools.
Eg: SoapTest, AppsWatch, JMeter.

22. CASE TOOL TYPES
22
Maintenance Tools
Automatic logging and error reporting techniques,
automatic error ticket generation and root cause
Analysis are few CASE tools, which help software
organization in maintenance phase of SDLC.
Eg: Bugzilla for defect tracking

23. ADVANTAGES OF CASE TOOLS
23
• Use of CASE tools leads to considerable improvements in
quality. This is mainly due to the fact that one can effortlessly
iterate through the different phases of software development
and the chances of human error are considerably reduced.
• CASE tools help produce high quality and consistent
documents.
• CASE tools take out most of the drudgery in a software
engineer’s work.
• CASE tools have led to revolutionary cost saving in software
maintenance efforts.
• Introduction of a CASE environment has an impact on the
style of working of a company, and makes it oriented towards
the structured and orderly approach.