Is There Only One Systems Development Life Cycle?
This paper contributes to the literature on information systems development life cycle (SDLC) by presenting an enhanced SDLC model, which integrated three interdependent and complementary, but different SDLCs. It is based on integration of the traditional and well-established idea of custom development with package development and commercially off the shelf (COTS) selection and implementation. Package development includes all software made for a market, whereas COTS selection and implementation refers to the selection and implementation of package software. Although there are many similarities between the life cycles, many differences are important to understand. We highlight both the differences and the intersection between the life cycles and outline an integrated SDLC model, which will be used to discuss future research and curricula issues.
KeywordsPackage Development Package Software Life Cycle Model Information System Development Methodological Support
The authors appreciate the helpful comments from the anonymous reviewers.
- Alter, S. (1999) A general, yet useful theory of information systems. Communications AIS 1(13) .Google Scholar
- Andersson, B. and Hedman, J. (2006) Issues in the development of a mobile based communication platform for the Swedish Police Force and appointed security guards. 3rd International Conference on Information Systems for Crisis Response and Management, Newark.Google Scholar
- Andersson, R. and Nilsson, A. (1996) The standard application package market – An industry in transition? In: M. Lundeberg and B. Sundgren (Eds.). Advancing Your Business: People and Information Systems in Consert. Sweden: EFI, Stockholm School of Economics.Google Scholar
- Avison, D.E. and Fitzgerald, G. (2006) Information Systems Development: Methodologies, Techniques, and Tools, 4th ed. New York, NY: McGraw-Hill.Google Scholar
- Boehm, B.W. (1988) A spiral model of software development and enhancement. IEEE Computer 21(5), 61–72.Google Scholar
- George, J. (2000) The origins of software: Acquiring systems at the end of the century. In R. Zmud (Ed.).Framing the Domains of IT Management: Projecting the Future…Through the Past. Cincinnati, Ohio: Pinnaflex Educational Resources, pp. 263–284.Google Scholar
- Hedman, J. (2003) On enterprise systems artifacts: Changes in information systems development and evaluation, Doctoral thesis, Department of Informatics, School of Economics and Management, Lund University, Sweden. .Google Scholar
- Hedman, J. (2004) Understanding ERP implementation methods: The case of ASAP. 27th IRIS, Falkenberg.Google Scholar
- Lind, M. (2002) Dividing businesses into processes – Foundations for modelling essentials. In: K. Liu, R.J. Clarke, P.B. Andersen, R.K. Stamper, E. Abou-Zeid (Eds.). IFIP TC8/WG8.1 Working Conference on Organizational Semiotics: Evolving a Science of Information Systems. Boston: Kluwer.Google Scholar
- Markus, L. and Tanis, C. (2000) The enterprise systems experience – From adoption to success. In:R. Zmud (Ed.). Framing the Domains of IT Management: Projecting the Future…Through the Past. Cincinnati, Ohio: Pinnaflex Educational Resources, pp. 173–207.Google Scholar
- Rosemann, M. (2001) Requirements engineering for enterprise systems. 7th Americas Conference on Information Systems, Boston, MA.Google Scholar