Location of Repository

Reconsidering the Notion of Requirements Engineering for Enterprise System Selection and Implementation

By Michael Rosemann, Iris Vessey, Ron Weber and Boris Wyssusek
Topics: 080600 INFORMATION SYSTEMS, Information System Development, Requirements Engineering
Publisher: Australasian Chapter of the Association for Information
Year: 2005
OAI identifier: oai:eprints.qut.edu.au:24115

Suggested articles

Preview

Citations

  1. (1993). A reappraisal of structured analysis: design in an organizational context,
  2. (2004). Alignment in enterprise systems implementations: the role of ontological distance”
  3. (2000). Amethodical systems development – The deferred meaning of systems development methods,
  4. (2000). Bridging the gap between organizational needs and ERP functionality,
  5. (1995). Challenges in requirements engineering”
  6. (1993). Configurations: crystallizing contingency,
  7. (2004). COTS tenders and integration requirements”
  8. (2005). COTS-based systems: a methodology for evaluating data and output misfits”
  9. (2000). Cultural fits and misfits: is ERP a universal solution?,
  10. (2001). Desperately seeking the “IT” in IT research—a call to theorizing the IT artifact,
  11. (2003). ERP modeling: a comprehensive approach,
  12. (2000). Examining an ERP implementation through myths: a case study of a large public organization”
  13. (2004). Fit measurement: how to distinguish between fit and misfit”
  14. (1994). Formative contexts and information technology: understanding the dynamics of innovation in organizations,
  15. (1997). How to survive ERP,
  16. (2000). Implementing enterprise resource planning systems: the role of learning from failure,
  17. (2003). Improvisation in action: making sense of IS development in organizations”
  18. (1998). Incremental method engineering with modeling tools: theoretical principles and empirical evidence, PhD thesis,
  19. (1987). Information systems failures: a survey and classification of the empirical literature,
  20. (1992). Information systems success: the quest for the dependent variable,
  21. (1994). Learning by trying: the implementation of configurational technology,
  22. (2002). Learning to implement enterprise systems: an exploratory study of the dialectics of change,
  23. (2002). Managing risks in enterprise systems implementations,
  24. (1996). Method engineering: engineering of information systems development methods and tools,
  25. (2001). Modelling off-the-shelf information systems requirements: an ontological approach,
  26. (2002). Out of alignment,
  27. (1987). Plans and situated actions: the problem of human-machine communication,
  28. (1983). Power, politics and MIS implementation,
  29. (1990). Prospects for an engineering discipline of software,
  30. (2003). Requirements Engineering and Agile Software Development”
  31. (1992). Requirements engineering: reconciliation of technical and social issues,
  32. (1995). Science and substance: a challenge to software engineers,
  33. (2002). Severity assessment of ERP–organization misalignment: honing in on ontological structure and context specificity”
  34. (1979). Sociological paradigms and organizational analysis. Elements of the sociology of corporate life,
  35. (1992). Software development as reality construction” in
  36. (1981). Software engineering economics, Prentice-Hall, Upper Saddle River.
  37. (1969). Software engineering: a report on a conference sponsored by
  38. (2004). Strategic alignment revisited: connecting organizational architecture and IT infrastructure”
  39. (1992). Systems without method: the impact of new technologies on information systems development projects”
  40. (2002). The foundational role for theories of agency in understanding of information systems design,
  41. (1982). The meta model hierarchy: a framework for information systems concepts and techniques,
  42. (2002). The phenomenology of information systems evaluation: overcoming the subject/object dualism”
  43. (1994). The software-research crisis,
  44. (1974). Theory in practice: increasing professional effectiveness, Jossey Bass,
  45. (1987). Understanding the elements of system design”
  46. (1993). Understanding Turing’s universal machine: personal style in program description,

To submit an update or takedown request for this paper, please submit an Update/Correction/Removal Request.