Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more ➡
Standard view
Full view
of .
Add note
Save to My Library
Sync to mobile
Look up keyword or section
Like this
0 of .
Results for:
No results containing your search query
P. 1
Visual Paradigm - UML

Visual Paradigm - UML



|Views: 3,098|Likes:
Published by Kapildev

More info:

Published by: Kapildev on Dec 09, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See More
See less





Software Project Management Assignment(CASE Tool Study with its manual)Visual Paradigm
Submitted by:Indranil NandyDepartment of Computer Sc. & EnggMTech, 2007Roll no. : 06CS6010
CASE & its scope:
A CASE tool is a generic term used to denote any form of automated supportfor software engineering. In a more restrictive sense, a CASE tool can mean any toolused to automate some activity associated with software development. Many CASEtools are now available. Some of these tools assist in phase-related tasks such asspecification, structured analysis, design, coding, testing etc., and others are related tonon-phase activities such as project management and configuration management. The primary objectives of deploying CASE tool are:
To increase productivity
To produce better quality software at lower cost
History of CASE Tools:
CASE tools began with the simple word processor which was used for creating and manipulating documentation. The seventies saw the introduction of graphical techniques and structured data flow diagrams. Up until this point, designand specifications in pictorial form had been extremely complex and time consumingto change. The introduction of CASE tools to aid this process allowed diagrams to beeasily created and modified, improving the quality of software designs. Datadictionaries, a very useful document that holds the details of each data type and processes within a system, are the direct result of the arrival of data flow design andstructural analysis made possible through the improvements of CASE tools. Earlygraphics packages were soon replaced by specialist's packages which enabled editing,updating and printing multiple versions of a design. Eventually, graphic toolsintegrated with data dictionary databases to produce powerful design anddevelopment tools that could hold complete design cycle documents. As a final step,error checking and test case generators were included to validate software design. Allthese processes can know be integrated into a single CASE tool that supports all of the development cycle.Early 80'scomputer aided documentationcomputer aided diagramminganalysis and design toolsMid 80'sautomated design analysis and checkingautomated system information repositoriesLate 80'sautomated code generation from design specificationlinking design automationEarly 90'sintelligent methodology driver habitable user interfacereusability as a development methodology
CASE tools were at their peak in the early 1990s. At the time IBM had proposed AD/Cycle which was an alliance of software vendors centered around IBM'smainframe. The three giants of the time were Atlanta based KnowledgeWare withtheir IEW (software engineering) and ADW tools and Texas Instruments with their IEF tool and Nastec Corporation (later merged with Transform Logic Corporation)and their DesignAid and Lifecycle Manager Tool suites. These tools were fulllifecycle and included Upper CASE and Lower CASE.With the decline of the mainframe, AD/Cycle and the Big CASE tools diedoff, opening the market for the mainstream CASE tools of today. Interestingly, nearlyall of the leaders of the CASE market of the early 1990s ended up being purchased byComputer Associates, including IEW, IEF, ADW, Cayenne, and LBMS.Some typical case tools are:
Code generation tools
UML editors and the like
Refactoring tools
QVT or Model Transformation tools
Configuration Management tools including revision control etc.
CASE environment:
Although individual CASE tools are useful, the true power of a tool set can berealized only when these set of tools are integrated into a common framework or environment. If the different CASE tools are not integrated, then the data generated by one tool would have to input to the other tools. This may also involve formatconversions as the tools developed by different vendors are likely to use differentformats. This results in an additional effort of exporting data from one tool andimporting to another. Also, many tools do not allow exporting data and maintain thedata in proprietary formats.CASE tools are characterized by the stage or stages of software developmentlife cycle on which they focus. Since different tools covering different stages sharecommon consistent view of information associated with the software. This centralrepository is usually a data dictionary containing the definitions of all composite andelementary data items. Through the central repository, all the CASE tools in a CASEenvironment share common information among themselves. Thus a CASEenvironment facilitates the automation of the step-by-step methodologies for softwaredevelopment. In contrast to a CASE environment, a programming environment is anintegrated collection of tools to support only the coding phase of softwaredevelopment. The tools commonly integrated in a programming environment are atext editor, a compiler, and a debugger. The different tools are integrated to the extentthat once the compiler detects an error, the editor automatically goes to the statementsin error and the error statements are highlighted. Examples of popular programming

Activity (7)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
Edy Susanto liked this
Murali Krishna liked this
rajmanohar.m liked this
X Man liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->