Despite over a decade of study, little is really known about information systems development and the use of systems development methodologies. There has been little evaluation of methodologies in use or examination of the selection, development, adaptation or use of methodologies in practice. This paper discusses this lack of knowledge and its ramifications for research and practice.
Get full access to this article
View all access options for this article.
References
1.
AlaviM. (1984). An assessment of the prototyping approach to information systems development. Communications of the ACM, 27(6), 556–63.
2.
AngellI.O., and StraubB.H. (1993). Though this be madness, yet there is method in't. Journal of Strategic Information Systems, 2(1), 5–14.
3.
AvisonD.E., and FitzgeraldG. (1988). Information systems development: current themes and future directions. Information and Software Technology, 30(8), 458–66.
4.
AvisonD.E., and Wood-HarperA.T. (1991). Information systems development research: an exploration of ideas in practice. The Computer Journal, 34(2), 98–112.
5.
BankerR.D., DatarS.M., and KemererC.F. (1991). Amodel to evaluate variables impacting the productivity of software maintenance projects. Management Science, 37(1), 1–18.
6.
BantlemanJ.P., and JonesA.H. (1984). Systems analysis methodologies: a research project, in Beyond Productivity: Information Systems Development for Organizational Effectiveness, BemelmansT.M.A. (ed.) (North-Holland, Amsterdam) pp. 213–54.
7.
BaskervilleR., TravisJ., and TruexD. (1992). Systems without method: the impact of new technologies on information systems development projects, in The Impact of Computer Supported Technologies on Information Systems Development, KendallK.E., LyytinenK., and DeGrossJ.I. (eds) (North-Holland, Amsterdam) pp. 241–69.
8.
BeckL.L., and PerkinsT.E. (1983). A survey of software engineering practice: tools, methods and results. IEEE Transactions on Software Engineering, SE-9 (5), 541–61.
9.
BoehmB.W., GrayT., and SeewaldtT. (1984). Prototyping versus specifying: a multiproject experiment. IEEE Transactions in Software Engineering, SE-10(3), 290–302.
10.
BolandR.J.Jr. (1978). The process and product of system design. Management Science, 24(9), 887–98.
11.
BubenkoJ.A.Jr. (1986). Information systems methodologies –a research view, in Information Systems Design Methodologies: Improving the Practice, OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, Amsterdam), pp. 89–302.
12.
BurchJ.G. (1992). Systems Analysis, Design, and Implementation (Boyd and Fraser, Boston).
13.
BurnsR.N., and DennisA.R. (1985). Selecting the appropriate application development methodology. Data Base, 16(4), 19–23.
14.
CameronJ.R., CampbellA., and WardP.T. (1991). Comparing software development methods: example. Information and Software Technology, 23(6), 386–402.
15.
ChecklandP., and ScholesJ. (1990). Soft Systems Methodology in Action (John Wiley & Sons, Chichester).
16.
ColterM.A. (1984). A comparative examination of systems analysis techniques. MIS Quarterly, 8(1), 51–66.
17.
ConnorsD.T. (1992). Software development methodology and traditional and modern information systems. Software Engineering Notes, 17(2), 43–9.
18.
CurtisB., KrasnerH., and IscoeN. (1988). A field study of the software design process for large systems. Communications of the ACM, 31(11), 1268–87.
19.
DavisG.B. (1982). Strategies for information requirements determination. IBM Systems Journal, 21(1), 4–30.
20.
DeklevaS.M. (1992). The influence of the information systems development approach on maintenance. MIS Quarterly, 16(3), 355–72.
21.
DeMarcoT. (1978). Structured Analysis and System Specification (Yourdon, New York).
22.
EdwardsH.M., ThompsonJ.B., and SmithP. (1989a). Results of survey of use of SSADM in commercial and government sectors in United Kingdom. Information and Software Technology, 31(1), 21–8.
23.
EdwardsH.M., ThompsonJ.B., and SmithP. (1989b). Experiences in use of SSADM: series of case studies. Part 1: first time users. Information and Software Technology, 31(8), 411–19.
24.
EdwardsH.M., ThompsonJ.B., and SmithP. (1989c). Experiences in use of SSADM: series of case studies. Part 2: experienced users. Information and Software Technology, 31(8), 420–8.
25.
El LouadiM., PollalisY.A., and TengJ.T.C. (1991). Selecting a systems development methodology: a contingency framework. Information Resources Management Journal, 4(1), 11–19.
26.
EpiskopouD.M., and Wood-HarperA.T. (1986). Towards a framework to choose appropriate IS approaches. The Computer Journal, 29(3), 222–8.
27.
FazlollahiB., and TanniruM.R. (1991). Selecting a requirement determination methodology – a contingency approach revisited. Information & Management, 21, 291–303.
28.
FinkelsteinC. (1989). An Introduction to Information Engineering (Addison-Wesley, New York).
29.
FitzgeraldG., StokesN., and WoodJ.R.G. (1985). Feature analysis of contemporary information systems methodologies. The Computer Journal, 28(3), 223–30.
30.
FloydC. (1986). A comparative evaluation of system development methods, in Information Systems Design Methodologies: Improving the Practice, OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, Amsterdam) pp. 19–54.
31.
FlynnD.J., and Fragoso-DiazO. (1993). Conceptual Euromodelling: how do SSADM and MERISE compare?European Journal of Information Systems, 2(3), 169–83.
32.
HackathornR.D., and KarimiJ. (1988). A framework for comparing information engineering methodologies. MIS Quarterly, 12(2), 203–21.
33.
HirschheimR.A. (1985). Office Automation: A Social and Organizational Approach (John Wiley, New York).
34.
HumphreyW.S. (1989). Managing the Software Process (Addison-Wesley, Reading, MA).
35.
IEEE (1987). Software Engineering Standards (Wiley Inter-science, New York).
36.
JacksonM.A. (1983). System Development (Prentice-Hall, Englewood Cliffs, NJ).
37.
JayartnaN. (1988). Guide to methodology understanding in systems practice. International Journal on Information Management, 8(1), 43–53.
38.
KaramG.M., and CasselmanR.S. (1993). A cataloging framework for software development methods. Computer, 26(2), 34–45.
39.
KeyesJ. (1992). How software is developed undergoing basic changes. Software Magazine, 12(1), 38–40, 43–7, 55–6.
40.
KleinH.K., and HirschheimR. (1991). Rationality concepts in information system development methodologies. Accounting, Management & Information Technology, 1(2), 157–87.
41.
KumarK., and WelkeR.J. (1992). Methodology engineering: a proposal for situation-specific methodology construction, in Challenges and Strategies for Research in Systems Development, CottermanW.W., and SennJ.A. (eds) (John Wiley, New York) pp. 257–69.
42.
LantzK.E. (1985). The Prototyping Methodology (Prentice-Hall, Englewood Cliffs, NJ).
43.
LoyP. (1993). The method won't save you (but it can help). Software Engineering Notes, 18(1), 30–4.
44.
LyytinenK. (1987a). A taxonomic perspective of information systems development: theoretical constructs and recommendations, in Critical Issues in Information Systems Research, BolandR.J., and HirschheimR.A. (eds) (John Wiley, New York) pp. 3–41.
45.
LyytinenK. (1987b). Different perspectives on information systems: problems and solutions. ACM Computing Surveys, 19(1), 5–46.
46.
LyytinenK. (1988). Expectation failure concept and systems analysts’ view of information system failures: results of an exploratory study. Information & Management, 14(1), 45–56.
47.
LyytinenK. (1989). New challenges of systems development: a vision of the 90's. Data Base, 20(1), 1–12.
48.
McLaughlinR. (1993). Does CASE make the customer happier?Software Engineering Notes, 18(2), 18.
49.
MahmoodM. (1987). System development methods: a comparative investigation. MIS Quarterly, 11(3), 293–311.
50.
MalouinJ.L., and LandryM. (1983). The mirage of universal methods in systems. Journal of Applied Systems Analysis, 10, 47–62.
51.
MenardJ.B. (1980). Exxon's experience with the Michael Jackson design method. Data Base, 11(1), 88–92.
52.
MendesK.S. (1980). Structured systems analysis: a technique to define business requirements. Sloan Management Review, 21(4), 51–63.
53.
MeredithD.C. (1986). Don't gamble when choosing a system development methodology. Data Management, 24(7), 36–9.
54.
MiddletonP. (1994). Euromethod: the lessons learned from SSADM, in Proceedings of the Second European Conference on Information Systems, BachW.R.J. (ed.) (Nijenrode University Press, Breakeleu) pp. 359–66.
55.
NeccoC.R., GordonC.L., and TsaiN.W. (1987). Systems analysis and design: current practices, MIS Quarterly, 11(4), 461–76.
56.
NielsenP.A. (1989). Reflections on development methods for information systems: a set of distinctions between methods. Office: Technology and People, 5(2), 81–104.
57.
OlleT.W. (1982). Comparative review of information systems design methodologies, in Informations Systems Design Methodologies: A Comparative Review, OlleT.W., SolH.G., and Verrijn-StuartA.A. (eds) (North-Holland, Amsterdam) pp. 1–14.
58.
OlleT.W., SolH.G., and Verrijn-StuartA.A. (1982). Information Systems Design Methodologies: A Comparative Review (North-Holland, Amsterdam).
59.
OlleT.W., SolH.G., and TullyC.J. (1983). Information Systems Design Methodologies: A Feature Analysis (North-Holland, Amsterdam).
60.
OlleT.W., SolH.G., and Verrijn-StuartA.A. (1986). Information Systems Design Methodologies: Improving the Practice (North-Holland, Amsterdam).
61.
OlleT.W., HagelsteinJ, MacdonaldL.G., RollandC., SolH.S., Van AsscheF.J.M., and Verrijn-StuartA.A. (1988). Information Systems Methodologies (Addison-Wesley, Wokingham, UK).
62.
PalviaP., and NosekJ.T. (1990). An empirical evaluation of system development methodologies. Information Resources Management Journal, 3(3), 23–32.
63.
PlylerR.W., and KimY.G. (1993). Methodology myths: four tenets for systems developers. Information Systems Management, 10(2), 39–44.
64.
RossD.T. (1985). Applications and extensions of SADT. IEEE Computer, 18(4), 24–34.
65.
RussoN.L., and KlomparensR. (1993). Formal Applications Development Methodologies in the ‘90's. Working paper, Northern Illinois University, DeKalb, IL.
66.
SauerC., and LauC. (1994). The adoption of information systems methodologies – an analytical framework and a case study, in Proceedings of the Fifth Australasian Conference on Information Systems.
SharpieR.C., and CohenS.S. (1993). The object-oriented brewery. Software Engineering Notes, 18(2), 60–73.
69.
SmolanderK., TahvanainenV., and LyytinenK. (1987). How to combine tools and methods in practice – a field study, in Information Systems Engineering, SteinholtzB., SolvbergA., and BergmanL. (eds) (Springer-Verlag, Berlin) pp. 195–285.
TeichroewD., and HersheyE.A.III, (1977). PSL/PSA: a computer-aided technique for structured documentation and analysis of information processing systems, IEEE Transactions on Software Engineering, SE-3(1), 42–8.
72.
ThayerR.H., PysterA.B., and WoodR.C. (1981). Major issues in software engineering project management. IEEE Transactions in Software Project Management, SE–7, 333–42.
73.
TurnerJ.A. (1987). Understanding the elements of system design, in Critical Issues in Information Systems Research, BolandR.J.Jr., and HirschheimR.A. (eds) (John Wiley and Sons, Chichester) pp. 97–111.
74.
Van De VeldeR. (1992). CASE adoption at Imperial Oil. Journal of Systems Management, 43, 24–38.
75.
WestrupC. (1993). Information systems methodologies in use. Journal of Information Technology, 8, 267–75.
76.
WhittenJ.L., BentleyL.D., and BarlowV.M. (1989). Systems Analysis and Design Methods, 2nd edition (Irwin, Homewood, IL).
77.
WoodB., PethiaR., GoldL., and FirthR. (1988). A Guide to the Assessment of Software Development Methodologies (Software Engineering Institute, Pittsburgh).
78.
Wood-HarperA.T., and FitzgeraldG. (1982). A taxonomy of current approaches to systems analysis. The Computer Journal, 25(1), 12–16.
79.
YourdonE. (1986). Whatever happened to structured analysis?Datamation, 32(11), 133–8.
80.
ZagorksyC. (1990). Case study: managing the change to CASE. Journal of Information System Management, 7(3), 24–32.
