Selecting the appropriate application development methodology
ACM SIGMIS Database the DATABASE for Advances in Information SystemsPublished 1 September 1985
R. N. Burns, Alan R. Dennis
Citations96
SJR quartileQ1
SJR score0.87
SNIP1.14
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
A contingency approach is presented, based on project size and project uncertainty, to selecting the most appropriate application development methodology for a given project.
Abstract
This paper synthesizes many of the recent articles about prototyping and contrasts prototyping with the more traditional systems life cycle approach to application development. As some projects are more suited to one methodology than the other, this paper presents a contingency approach, based on project size and project uncertainty, to selecting the most appropriate application development methodology for a given project.
Keywords
Computer Science
25th International Conference on Software Engineering, 2003. Proceedings.Proceedings 25th International Conference on Software Engineering
507 Citations2003
Communications of the ACMAn assessment of the prototyping approach to information systems development
356 Citations1984Maryam Alavi
A two-phased research project comparing the prototyping approach with the more traditional life cycle approach finds that prototyping facilitates communication between users and designers during the design process, however, the findings also indicate that designers who used prototyping experienced difficulties in managing and controlling thedesign process.
MIS QuarterlyPrototyping: The New Paradigm for Systems Development
340 Citations1982J. David Naumann, A. Milton Jenkins
The authors review published references to prototyping and related concepts, and synthesize a process model for information systems development that addresses today's critical issues and will no doubt raise a new set of research questions for tomorrow.
Communications of the ACMPrototyping interactive information systems
94 Citations1983Rachel Mason, Tom Carey
The prototype development methodology and development tool presented here have been widely applied to the development of interactive information systems in the commercial data processing setting and the effectiveness and relationship to other applications is discussed.
MIS QuarterlySuccessful Development Strategies for Business Application Systems*
91 Citations1983James D. McKeen
Results indicate that systems which spent more time in the analysis phase required less time to code, resulted in greater user satisfaction, and were developed in agreement with established budgets and deadlines.
Journal of Systems and SoftwareDetermining information requirements: A contingency method for selection of a requirements assurance strategy
65 Citations1979J. David Naumann, Gordon B. Davis +1 more
The approach to strategy selection is illustrated by a contingency analysis worksheet for evaluating requirements uncertainty and by examples.
International Conference on Software EngineeringPrototyping vs. specifying: A multi-project experiment
51 Citations1984Barry Boehm, Terence E. Gray +1 more
In this experiment, seven software teams developed versions of the same small-size (2000-4000 source instruction) application software product that yielded products with roughly equivalent performance, but with about 40% less code and 45% less effort.
ACM SIGMIS Database the DATABASE for Advances in Information SystemsThe evolution of information systems development approach
20 Citations1984Maryam Alavi
The underlying premises for prototyping and the interview findings concerning the advantages, practicability, and organizational requirements of prototyping are discussed in this article.
ComputerSpecial Feature Requirements Anaysis in Clinical Research Information Processing —A Case Study
15 Citations1979Groner, Hopwood +2 more
System designers often neglect to do a thorough requirements analysis before beginning development, but this effort shows how such an analysis can improve the usefulness of a new system.
ACM SIGMIS Database the DATABASE for Advances in Information SystemsPrototype systems for accounting, information and control
11 Citations1982Michael J. Earl
Prototypes are seen as a “process-enabler” and as a device by which action researchers themselves can learn more about MIS design, for example as a catalyst to participative design, to organisational experimentation and to learning.