Computer-Aided Software Engineering (CASE) technologies are tools that provide automated assistance for software development 3. The goal of introducing CASE tools is the reduction of the time and cost of software development and the enhancement of the quality of the systems developed 3, 20. This paper explores the use of CASE tools. We ask several questions. Are CASE tools being used? If yes, what features within the tool are being used? Next, we explore two potential reasons for the expected low use. Do CASE tools change the job of the systems developer in an unattractive way? And are the people who are expected to use CASE tools motivated to use them?233 systems developers were surveyed to answer these questions. We found that CASE tools are being used but not in many companies. Within the companies that have adopted CASE tools, few people are actually using the tools. The systems developers who use CASE tools are using formal methodologies more often than systems developers who do not use CASE tools. Systems developers allocate their time differently depending on whether they are using a CASE tool or not. Those who use the tools are using few of the functions within the tools. Finally we found that people were basically neutral on whether they enjoyed using the tool and whether the tool was useful.
End of preview. The entire article is 14 pages. To view the full-text, please rent this article to continue.
/lp/association-for-computing-machinery/case-tools-understanding-the-reasons-for-non-use-KUv5s72DRY
Welcome to DeepDyve! Rent Premier Research Articles and Save Up to 90%
CASE tools: understanding the reasons for non-use
Chervany, Norman L.; Lending, Diane
Follow ACM SIGCPR Computer Personnel
, Volume 19 (2)
Association for Computing Machinery – Apr 1, 1998
More Info
More Like This Article
View All dataSource[]=actageo&dataSource[]=aspet&dataSource[]=aaos&dataSource[]=aacc&dataSource[]=aacr&dataSource[]=aea&dataSource[]=aip&dataSource[]=ajnr&dataSource[]=ams&dataSource[]=aps_physical&dataSource[]=appi_book&dataSource[]=appi_journal&dataSource[]=apha&dataSource[]=asip&dataSource[]=asm&dataSource[]=asn&dataSource[]=aspb&dataSource[]=avs&dataSource[]=annual_reviews&dataSource[]=arxiv&dataSource[]=acm&dataSource[]=berghahn&dataSource[]=cabi&dataSource[]=clinical_trials&dataSource[]=dailymed&dataSource[]=degruyter&dataSource[]=du_press&dataSource[]=esa&dataSource[]=eu_press&dataSource[]=elsevier&dataSource[]=emerald&dataSource[]=ejtr&dataSource[]=emea&dataSource[]=epo&dataSource[]=faseb&dataSource[]=gsa&dataSource[]=health_affairs&dataSource[]=hindawi&dataSource[]=imanager&dataSource[]=imedpub&dataSource[]=informa_healthcare&dataSource[]=informs&dataSource[]=iop&dataSource[]=iucr&dataSource[]=iospress&dataSource[]=jbjs&dataSource[]=leftcoast&dataSource[]=lu_press&dataSource[]=mesharpe&dataSource[]=mary_ann_liebert&dataSource[]=medline&dataSource[]=mit_press&dataSource[]=nature&dataSource[]=oxford&dataSource[]=pier_professional&dataSource[]=pnas&dataSource[]=portlandpress&dataSource[]=psyc_articles&dataSource[]=psyc_books&dataSource[]=psyc_critiques&dataSource[]=plos_journal&dataSource[]=pubmed_central&dataSource[]=rsna&dataSource[]=rockefeller&dataSource[]=rcn&dataSource[]=ria&dataSource[]=rsc&dataSource[]=sage&dataSource[]=spie&dataSource[]=springer_journal&dataSource[]=springer&dataSource[]=taylor_francis&dataSource[]=aps&dataSource[]=the_scientist&dataSource[]=uc_press&dataSource[]=uspto_abstract&dataSource[]=wiley&dataSource[]=pct
© 2012 DeepDyve, Inc. All rights reserved.
Terms of Service | Privacy Policy
