The effective use of automated application development tools

被引:33
作者
Guinan, PJ
Cooprider, JG
Sawyer, S
机构
[1] BENTLEY COLL,CIS DEPT,WALTHAM,MA 02154
[2] SYRACUSE UNIV,SCH INFORMAT STUDIES,CTR SCI & TECHNOL 4206,SYRACUSE,NY 13244
关键词
D O I
10.1147/sj.361.0124
中图分类号
TP [自动化技术、计算机技术];
学科分类号
0812 ;
摘要
In this paper we report on the results of a four-year study of how automated tools are used in application development (AD). Drawing on data collected from over 100 projects at 22 sites in 15 Fortune 500 companies, we focus on understanding the relationship between using such automated AD fools and various measures of AD performance-including user satisfaction, labor cost per function point, schedule slippage, and stakeholder-rated effectiveness. Using extensive data from numerous surveys, on-site observations, and field interviews, we found that the direct effects of automated tool use on AD performance were mixed, and that the use of such tools by themselves makes little difference in the results. Further analysis of key intervening factors finds that training, structured methods use, project size, design quality, and focusing on the combined use of AD tools adds a great deal of insight into what contributes to the successful use of automated tools in AD. Despite the many grand predictions of the trade press over the past decade, computer-assisted software engineering (CASE) tools failed to emerge as the promised ''silver bullet'' The mixed effects of CASE tools use on AD performance that we found, coupled with the complex impact of other key factors such as training methods, and group interaction, suggest that a cautious approach is appropriate for predicting the impact of similar AD tools (e.g., object-oriented, visual environments, etc.) in the future, and highlight the importance of carefully managing the introduction and use of such tools if they are to be used successfully in the modem enterprise.
引用
收藏
页码:124 / 139
页数:16
相关论文
共 55 条
  • [1] AMBROSIO J, 1989, DIGITAL REV, V6, P40
  • [2] [Anonymous], WORK REDESIGN
  • [3] BALL S, 1987, 1 ENG WORKSH CAS IEE, V1, P128
  • [4] A SURVEY OF SOFTWARE ENGINEERING PRACTICE - TOOLS, METHODS, AND RESULTS
    BECK, LL
    PERKINS, TE
    [J]. IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, 1983, 9 (05) : 541 - 561
  • [5] BIRD C, 1991, SOFTWARE MAGAZINE, V11, P8
  • [6] BOEHM B, 1987, IEEE COMPUT, V18, P43
  • [7] Boehm B. W., 1981, SOFTWARE ENG EC
  • [8] Brooks FP., 1975, MYTHICAL MAN MONTH
  • [9] BRYANT J, 1990, SYSTEMS INT, V18, P75
  • [10] BURKHARD D, 1988, UNPUB ROLE STRUCTURE