Advertisement

Requirements Engineering

, Volume 10, Issue 3, pp 238–242 | Cite as

Is emotion relevant to requirements engineering?

  • Isabel Ramos
  • Daniel M. BerryEmail author
Viewpoints

Abstract

This viewpoint argues that the introduction of most computer-based system to an organization transforms the organization and changes the work patterns of the system’s users in the organization. These changes interact with the users’ values and beliefs and trigger emotional responses which are sometimes directed against the software system and its proponents. A requirements engineer must be aware of these emotions.

Notes

Acknowledgements

We thank the anonymous referees of our previous papers for their helpful comments. Daniel Berry’s work was supported in part by a Canadian NSERC grant, NSERC-RGPIN227055-00.

References

  1. 1.
    Ramos I, Berry DM, Carvalho JA (2005) Requirements engineering for organizational transformation. J Inform Softw Technol 47(5):479–495CrossRefGoogle Scholar
  2. 2.
    Lehman MM (1980) Programs, life cycles, and laws of software evolution. Proc IEEE 68(9):1060–1076Google Scholar
  3. 3.
    Esteves J, Pastor J (2001) Enterprise resource planning systems research: an annotated bibliography. Commun Assoc Inform Syst 7(8):1–51Google Scholar
  4. 4.
    Dickson GW, DeSanctis G (2000) Information technology and the future enterprise: new models for managers. Prentice-Hall, Englewood CliffsGoogle Scholar
  5. 5.
    Palmer I, Hardy C (2000) Thinking about management. Thousand Oaks, SageGoogle Scholar
  6. 6.
    Bergman MB, King JL, Lyytinen K (2002) Large-scale requirements analysis revisited: the need for understanding the political ecology of requirements engineering. Requirements Eng J 7(3):152–171CrossRefGoogle Scholar
  7. 7.
    Damásio A (1999) The feeling of what happens: body and emotion in the making of consciousness. New York, Harcourt BraceGoogle Scholar
  8. 8.
    Parker S, Wall T (1998) Job and work design: organizing work to promote well-being and effectiveness. Thousand Oaks, SageGoogle Scholar
  9. 9.
    Snizek WE (1995) Virtual offices: some neglected considerations. Commun ACM 38(9):15–17CrossRefGoogle Scholar
  10. 10.
    Markus ML (1983) Power, politics and MIS implementation. Commun ACM 26:430–444CrossRefGoogle Scholar
  11. 11.
    Huff C (2002) Gender, software design, and occupational equity. Inroads, SIGCSE Bull 34(2):112–115CrossRefGoogle Scholar
  12. 12.
    Boehm BW, Ross R (1989) Theory W software project management: principles and examples. IEEE Trans Softw Eng SE 15(7):902–916CrossRefGoogle Scholar
  13. 13.
    Boehm B, Bose P, Horowitz E, Lee MJ (1994) Software requirements as negotiated win conditions. In: Proceedings of the first international conference on requirements engineering (ICRE94) IEEE Computer Society, Colorado Springs, CO, pp 74–83Google Scholar
  14. 14.
    Goguen JA (1993) Requirements engineering as the reconciliation of technical and social issues. Technical Report, Centre for Requirements and Foundations, Programming Research Group, Oxford University Computing Lab, modified version later published as 15, Oxford, UKGoogle Scholar
  15. 15.
    Goguen JA (1994) Requirements engineering as the reconciliation of technical and social issues. In: Goguen JA, Jirotka M (eds) Academic Press, London, pp 165–199Google Scholar
  16. 16.
    Ramos IMP (2000) Aplicações das Tecnologias de Informaçãoque Suportam as Dimensões Estrutural, Social, Política e Simbólica do Trabalho. PhD Dissertation, Departamento de Informática, Universidade do Minho Guimarães, PortugalGoogle Scholar
  17. 17.
    Santos I, Carvalho JA (1998) Computer-based systems that support the structural, social, political and symbolic dimensions of work. Requirements Eng J 3(2):138–142CrossRefGoogle Scholar
  18. 18.
    Easterbrook SM (1992) SCW: co-operation or conflict? Springer, LondonGoogle Scholar
  19. 19.
    Krumbholz M, Galliers J, Coulianos N, Maiden NAM (2000) Implementing enterprise resource planning packages in different corporate and national cultures. J Inform Technol 15:267–279CrossRefGoogle Scholar
  20. 20.
    Krumbholz M, Maiden NAM (2000) The implementing of ERP packages in different organisational and national cultures. Inform Syst J 26(3):185–204Google Scholar
  21. 21.
    Pfeffer J, Salancik G (1978) The external control of organizations: a resource dependence perspective. Harper & Row, New YorkGoogle Scholar
  22. 22.
    Sickenius de Souza C, Prates RO, Barbosa SDJ (2003) Adopting information technology as a first step in design, lessons learned from working with Brazilian social volunteers. Interactions X(2):72–79 Google Scholar
  23. 23.
    Boehm BW, Huang LG (2003) Value-based software engineering: a case study. IEEE Computer 36(3):33–41Google Scholar
  24. 24.
    Rost J (2004) Political reasons for failed software projects. IEEE Software 21(6):104, 102–103 Google Scholar
  25. 25.
    Boehm BW (1981) Software engineering economics. Prentice-Hall, Englewood CliffsGoogle Scholar
  26. 26.
    Lutz RR, Mikulski IC (2004) Empirical analysis of safety-critical anomalies during operations. IEEE Trans Softw Eng SE 30(3):172–180CrossRefGoogle Scholar

Copyright information

© Springer-Verlag London Limited 2005

Authors and Affiliations

  1. 1.Departamento de Sistemas de InformaçãoUniversidade do MinhoGuimarãesPortugal
  2. 2.School of Computer ScienceUniversity of WaterlooWaterlooCanada

Personalised recommendations