Is emotion relevant to requirements engineering?
- 289 Downloads
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.
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.
- 2.Lehman MM (1980) Programs, life cycles, and laws of software evolution. Proc IEEE 68(9):1060–1076Google Scholar
- 3.Esteves J, Pastor J (2001) Enterprise resource planning systems research: an annotated bibliography. Commun Assoc Inform Syst 7(8):1–51Google Scholar
- 4.Dickson GW, DeSanctis G (2000) Information technology and the future enterprise: new models for managers. Prentice-Hall, Englewood CliffsGoogle Scholar
- 5.Palmer I, Hardy C (2000) Thinking about management. Thousand Oaks, SageGoogle Scholar
- 7.Damásio A (1999) The feeling of what happens: body and emotion in the making of consciousness. New York, Harcourt BraceGoogle Scholar
- 8.Parker S, Wall T (1998) Job and work design: organizing work to promote well-being and effectiveness. Thousand Oaks, SageGoogle Scholar
- 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.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.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.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
- 18.Easterbrook SM (1992) SCW: co-operation or conflict? Springer, LondonGoogle Scholar
- 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.Pfeffer J, Salancik G (1978) The external control of organizations: a resource dependence perspective. Harper & Row, New YorkGoogle Scholar
- 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.Boehm BW, Huang LG (2003) Value-based software engineering: a case study. IEEE Computer 36(3):33–41Google Scholar
- 24.Rost J (2004) Political reasons for failed software projects. IEEE Software 21(6):104, 102–103 Google Scholar
- 25.Boehm BW (1981) Software engineering economics. Prentice-Hall, Englewood CliffsGoogle Scholar