Packaged software: Implications of the differences from custom approaches to software development

Research output: Contribution to journalArticle

85 Scopus citations

Abstract

This paper contributes to the literature on software development in two ways. First, by discussing the packaged software domain relative to the more commonly studied custom information systems (IS) domain.Second, this paper presents our speculations on the implications of these differences between packaged and custom IS development. Regarding the first issue, while the two domains share many commonalities, the differences are also important to understand. To make this clear we discuss the differences at four levels: industry forces, approaches to software development, work culture and development team efforts.At each level, data from three case studies are used to illustrate the differences between the two domains.To develop our speculations, we contend that the differences between packaged software and the traditional, custom, approach to information systems development will be profound for five stakeholder groups: software development organizations, software development teams, software developers, software consumers and for researchers interested in software development.

Original languageEnglish (US)
Pages (from-to)47-58
Number of pages12
JournalEuropean Journal of Information Systems
Volume9
Issue number1
DOIs
StatePublished - Mar 2000
Externally publishedYes

ASJC Scopus subject areas

  • Information Systems
  • Library and Information Sciences

Fingerprint Dive into the research topics of 'Packaged software: Implications of the differences from custom approaches to software development'. Together they form a unique fingerprint.

  • Cite this