CASE Tools

By: Janhvi J Kagrana

Deepika GroverMBA-IT( Sem-III)

CASE Tool Evolution

1980 1984 1987 1990

Computer-aided documentationComputer-aided diagrammingAnalysis and design tools

Automated design analysisAutomated central repository

Automated code generationLinked design automation

Intelligent methodology driversReusable code libraries

Classification of Case tools Dimensions

CASE Tool Components

Process Modeling Tools

Detailed Analysis Tools

Transformation Tools

Database/Application Design Tools

Application Generation Tools

Cen

tral

R

epo

sito

ry

CASE tools Repository

Integrated CASE Environmentspart 1

• Provide mechanism for sharing information among all tools contained in the environment

• Enable changes to items to be tracked to other information items

• Provide version control and overall configuration management

• Allow direct access to any tool contained in the environment

Integrated CASE Environmentspart 2

• Establish automated support for chosen software process model, integrating CASE tools into a standard work break down structure

• Gives users of each tool a consistent look and feel at the human-computer interface level

• Collect both management and technical metrics to improve the process and the product

Integration Architecture - part 1

• User interface layer– interface toolkit

• contains software for UI management and library of display objects

– common presentation protocol• guidelines that give all CASE tools the same look and feel

(icons, mouse behavior, menu names, object names)

• Tools layer– tools management services - control behavior of tools

inside environment

Integration Architecture - part 2

• CASE tools themselves• Object management layer (OML)

– performs the configuration management function, working with the CASE repository OML provides integration services

• Shared repository layer – CASE database and access control functions enabling

the OML to interact with the database

CASE Repository Functions - part 1

• Data integrity– includes functions to validate entries to the repository

and ensure consistency among related objects

• Information sharing– provides mechanism for sharing information among

multiple developers and multiple tools, controls modification of information

• Data-tool integration– establishes shared data model and performs

configuration management functions

CASE Repository Functions - part 2

• Methodology enforcement– the E-R model used to define steps needed to be

conducted to build the repository contents

• Document standardization– definition of objects in the database leads directly to a

standard approach for creation of engineering documents

DBMS Features Relevant to CASE Repositories

• Non-redundant data storage• High-level access• Data independence• Transaction control• Ad hoc data queries and reports• Openness• Multi-user support

CASE tools with SDLC

USE CASE using CASE tools

Class Diagram using CASE tools

Comparative Software Development Costs

Product Cost $ Effort (man years)

Lines of Code

Lotus 1-2-3 V 3.0 22,000,000 263 400,000

NASA Space Shuttle 1,200,000,000 22,096 25,600

2000 Lincoln Continental 2,800,000 37 93,500

Modern Automatic Teller Machine

13,200,000 150 780,000

IBM Retail Checkout Scanner

3,000,000 58 90,000

CASE Tool Adoption Objectives

 

           Create development process standards          Improve overall application quality          Decrease design time and improve time to market          Decrease required effort and time in application testing          Encourage integration of development projects          Improve effectiveness of project management activities          Decrease required effort and time in application maintenance activities          Promote organization-wide reusable program code          Improve portability of applications across platforms and operating environments 

Good and Bad News

The Good News The Bad News

 • Development  process  productivity  and 

quality increases are realizable• Portability  of  new  systems  to  other 

platforms is greatly enhanced• Analyst  skill  set  will  improve  due  to 

greater understanding of the process• Time to delivery of new applications will 

decrease• Conformity  to  development  standards 

will increase 

 • CASE  acquisition  costs  are  extremely 

high• Training of analysts and administrators 

is costly and time-consuming• Most  organizations  do  not  have  clear 

standards for application development• CASE tools can be viewed as a threat 

to job security• CASE  tools  do  not  have  a  great 

reputation  due  to  early  benefits  not being realized

ConstraintsExamples of Constraints

Process Modeling• A DFD either must be a context diagram or have a parent process on a higher-level DFD• A parent process must be specified before its child processes• External entities must be connected only to a process• Each data store on a set of DFDs must be uniquely namedData Modeling• Entity must be specified before its relationship• Entity and relationship must be specified before their attributes• Cardinality must be shown at each end of a relationship• Associative entities must have one or more attributes

Thank You

Any Queries??