A Taxonomy of Stakeholders: Human Roles in System Development

International Journal of Technology and Human Interaction (IJTHI)

Volumn 1, Issue 1, 2005, Pages 23-59

  Alexander, Ian F ^a  

^a Scenario Plus Ltd   (United Kingdom)

Author keywords

actor; model; onion metaphor; requirements elicitation; role; stakeholder; stakeholder identification; surrogacy; surrogate; taxonomy; template; user; viewpoint

Indexed keywords

EID: 85001777479     PISSN: 15483908     EISSN: 15483916     Source Type: Journal    
DOI: 10.4018/jthi.2005010102     Document Type: Article

References (41)

1. Alexander, I. (2002). Initial industrial experience of misuse cases in trade-off analysis. IEEE Joint International Requirements Engineering Conference, 9–13 September 2002, Essen, Germany, 61–68.
2. Alexander, I. (2003, April). Stakeholders: Who is your system for? Computing & Control Engineering, 14(1), 22–26.
3. Alexander, I., & Maiden, N. (Eds.). (2004). Scenarios, stories, use cases through the system development life-cycle. John Wiley.
4. Alexander, I., & Robertson, S. (2004, January/February). Understanding project sociology by modeling stakeholders. IEEE Software, 21(1), 23–27.
5. Alexander, I., & Stevens, R. (2002). Writing better requirements. Addison- Wesley.
6. Avison, D., & Wood-Harper, A. T. (1990). Multiview: An exploration in information systems development. Oxford: Blackwell Scientific Publications.
7. Bennetts, P. D. C., & Wood-Harper, A. T. (2000). Software process improvement through the lens of multiview 2: The development of a contingent factors model. Tenth Conference on Business Information Technology, Manchester, UK.
8. Boehm, B., Grünbacher, P., & Briggs, B. (2003, May/June). Developing groupware for requirements negotiation: Lessons learned. IEEE Software, 46–55.
9. Bowker, G. C., & Leigh Star, S. (1999). Sorting things out: Classification and its consequences. MIT Press.
10. Checkland, P., & Scholes, J. (1999). Soft systems methodology in action (New ed.). John Wiley.
11. Coakes, E., & Elliman, T. (1999, July). Focus issue on legacy information systems and business process engineering: The role of stakeholders in managing change. Communications of the AIS, 2(1).
12. Damian, D. E., & Zowghi, D. (2002). The impact of stakeholders' geographical distribution on managing requirements in a multi-site organization. Proceedings of the IEEE Joint International Requirements Engineering Conference, Essen, Germany, September 2002, 319–328.
13. Donaldson, T., & Preston, L. E. (1995). The stakeholder theory of the corporation: Concepts, evidence, and implications. Academy of Management Review, 20(1), 65–91.
14. Fowler, M., & Scott, K. (1999). UML distilled: A brief guide to the standard object modeling language. Addison-Wesley.
15. Gause, D., & Weinberg, G. (1989). Exploring requirements: Quality before design. Dorset House.
16. Hirschheim, R., & Klein, H. K. (2003). Crisis in the IS field? A critical reflection on the state of the discipline. Journal of the Association for Information Systems, 4(5), 237–293.
17. Ibsen, H. (1992). Peer Gynt. Theatre Communications Group. (Original work published 1867)
18. Jackson, M. (1995). Software requirements & specifications: A lexicon of practice, principles and prejudices. Addison-Wesley.
19. Kitapci, H., & Bhuta, J. (2004). EasyWinWin negotiations: Guidelines and EasyWinWin report. Retrieved April 20, 2004, from http://sunset.usc.edu/classes/cs577a_2003/a s s i g n m e n t s / T e a m /EasyWinWin%20Negotiations.htm
20. Kotonya, G., & Sommerville, I. (1998). Requirements engineering: Processes and techniques. John Wiley.
21. Koyré, A. (1968). From the closed world to the infinite universe. Baltimore & London: The Johns Hopkins University Press. (Paperback reprinted from 1957)
22. Levine, R., Locke, C., Searls, D., & Weinberger, D. (2000). The ClueTrain manifesto: The end of business as usual. London: FT.com.
23. Lovejoy, A. O. (1990). The great chain of being. Cambridge, MA: Harvard University Press. (Paperback reprinted from 1936)
24. Mason, R., & Mitroff, I. (1981). Challenging strategic planning assumptions: Theory, cases, and techniques. New York: John Wiley & Sons.
25. McGraw, K., & Harbison, K. (1997). Usercentered requirements: The scenariobased engineering process. Lawrence Erlbaum Associates.
26. Midgley, G. (1992). The sacred and profane in critical systems thinking. Systems Practice, 5(1), 5–16.
27. Mumford, E. (1996). Systems design: Ethical tools for ethical change. Macmillan.
28. Potts, C. (1995). Invented requirements and imagined customers: Requirements engineering for off-the-shelf software (Invited workshop introduction paper). Proceedings of RE'95: Second International Symposium on Requirements Engineering, York, England. IEEE Computer Society Press. Retrieved April 20, 2004, from http://www.cc.gatech.edu/fac/Colin.Potts/p u b s / 1 9 9 5 / r e 9 5 /re95InventedReqtsOTS.pdf
29. Pouloudi, A. (1999). Aspects of the stakeholder concept and their implications for information systems development. Proceedings of the 32nd Hawaii International Conference on System Sciences, Volume 7, January 5–8 1999, Maui, Hawaii. Retrieved April 20, 2004, from http://www.computer.org/proceedings/h i c s s / 0 0 0 1 / 0 0 0 1 7 /00017030abs.htm?SMIDENTITY=NO
30. Pouloudi, A., & Whitley, E. A. (1997). Stakeholder identification in inter-organizational systems: Gaining insights for drug use management systems. European Journal of Information Systems, 6(1), 1–14.
31. Robertson, S., & Robertson, J. (1999). Mastering the requirements process. Addison-Wesley.
32. Robertson, S., & Robertson, J. (2004). Requirements-led project management. Addison-Wesley.
33. Scenario Plus. (2004). Scenario Plus Web site (onion model tool for Telelogic DOORS, stakeholders template for Microsoft Word, etc.). Retrieved April 20, 2004, from http://www.scenarioplus.org.uk
34. Sharp, H., Finkelstein, A., & Galal, G. (1999). Stakeholder identification in the requirements engineering process. DEXA Requirements Engineering Process Workshop, 387–391.
35. Sommerville, I., Sawyer, P., & Viller, S. (1998). Viewpoints for requirements elicitation: A practical approach. Proceedings of Third IEEE International Conference on Requirements Engineering.
36. Sutcliffe, A. (2002). User-centred requirements engineering, theory and practice. Springer.
37. Volere. (2004). Volere stakeholder analysis template. Retrieved February 20, 2004, from http://www.volere.co.uk
38. Wood, D. (1999). Trends in stakeholder management & measurement in the public sector. Retrieved April 20, 2004, from http://www.navigate.co.nz/ newsreti.htm
39. Young, R. R. (2004). The requirements engineering handbook. Artech House.
40. Younkins, E. W. (2001, Spring). Morality and character development: The roles of capitalism, commerce, and the corporation [Electronic version]. Journal of Markets & Morality, 4(1), 94–111. Retrieved April 20, 2004, from http://www.acton.org/publicat/m_and_m/2001_spring/ pdf/mm-v4n1-younkins.pdf
41. Yu, E., & Mylopoulos, J. (1998). Why goaloriented requirements engineering? Requirements Engineering Foundation for Software Quality Workshop 1998. Retrieved April 20, 2004, from http://www. c s. t o r o n t o. e d u / p u b / e r i c /REFSQ98.html