Using Stakeholders, Domain Knowledge, and Responsibilities to Specify Information Systems' Requirements

Journal of Organizational Computing and Electronic Commerce

Volumn 9, Issue 4, 1999, Pages 287-296

  Blyth, Andrew ^a  

^a UNIVERSITY OF GLAMORGAN   (United Kingdom)

Author keywords

Domain knowledge; Requirements analysis; Responsibility modeling; Stakeholder analysis

Indexed keywords

EID: 0005329241     PISSN: 10919392     EISSN: None     Source Type: Journal    
DOI: 10.1207/S153277440904_3     Document Type: Article

References (33)

1. P. Ehn, Work-Oriented Design of Computer Artifacts. Almquist & Wiksell, 1988.
2. B. Friedman and N. Nissenbaum, "Bias in computer systems," ACM Trans. on Information Systems, vol. 14, no. 3, pp. 330-347, 1996.
3. D. Vaughan, The Challenger Launch Decision: Risky Technology, Culture and Deviance at NASA. Chicago: University of Chicago Press, 1996.
4. F. Shipman and R. McCall, "Supporting knowledge-base evolution with incremental formalisation in human factors in computer systems," in Int. Conf. on Human Computer Interaction (INTERCHI '94), 1994, pp. 285-291.
5. R. O. Mason and I. T. Mitroff, Challenging Strategic Planning Assumptions. New York: Wiley, 1981.
6. B. Dahlborm and L. Mathiassen, Computers in Context: The Philosophy and Practice of Systems Design. London: Blackwell, 1994.
7. A. G. Sutcliffe and N. A. M. Maiden, "Exploiting reusable specifications through analogy," Communications of the ACM, vol. 35, no. 4, pp. 55-64, 1992.
8. J. Greenbaum and M. Kyng, Design at Work: Co-operative Design of Computer Systems. Hillsdale, NJ: Lawrence Erlbaum Associates, Inc., 1991.
9. T. Winograd and F. Flores, Understanding Computers and Cognition: A New Foundation for Design. Reading, MA: Addison-Wesley, 1987.
10. B. Curtis, H. Krasner, and N. Iscoe, "A field study of the software development process for large systems," Communications of the ACM, vol. 31, no. 11, pp. 1268-1287, 1988.
11. D. C. Cause and G. M. Weinburg, Exploring Requirements: Quality Before Design. London: Dorsethouse, 1989.
12. L. R. Wiener, Digital Woes: Why We Should Not Depend on Software. Reading, MA: Addison-Wesley, 1993.
13. J. A. Wise and A. Debons, Information Systems: Failure Analysis. London: Springer-Verlag, 1987.
14. K. E. Emam and N. H. Madhavji, "A field study of requirements engineering practices in information systems development," in Proc. of the Second IEEE Int. Symposium on Requirements Engineering (RE '95), 1995.
15. P. Checkland, Systems Thinking - Systems Practice. New York: Wiley, 1986.
16. P. Checkland and J. Scholes, Soft Systems Methodology in Action. New York: Wiley, 1990.
17. A. Tuzhilin, "Templar: A knowledge-based language for software specification using temporal logic," ACM Trans. on Information Systems, vol. 13, no. 3, pp. 269-304, 1995.
18. E. Besmuller, "Office modelling based on petri nets," in Proc. of ESPRIT-1988, 1998, pp. 977-987.
19. K. Lyytinen, E. Auramaki, and R. Hirschheim, "Modelling offices through discourse analysis: The SAMPO approach," The Computer Journal, vol. 35, no. 4, pp. 342-352, 1991.
20. G. L. Rein and B. Singh, "Interaction nets (RINs): A process description formalism," MCC Micro-Electronics and Computer Technology Corp., TX, Tech. Rep. CT-083-92, 1992.
21. K. Lyytinen and R. A. Hirscheim, "Information systems failures: A survey and classification of empirical literature," Oxford Surveys in Information Tech., vol. 4, pp. 257-309, 1987.
22. P. Mellor, "CAD: Computer aided disaster," High Integrity Systems, vol. 1, no. 2, pp. 101-156, 1994.
23. A. Dardenne, A. Van Lamsweerde, and S. Fickas, "Goal direct requirements acquisition," Science of Computer Programming, vol. 20, no. 1-2, pp. 3-50, 1993.
24. A. G. Sutcliffe and N. A. M. Maiden, "Bridging the gap policies, goals and domains," in Proc. of the Seventh Int. Workshop on Software Specification and Design (IWSSD), 1993.
25. J. Mylopoulos and E. S. K. Yu, "Using goals, rules and methods to support reasoning in business process re-engineering," in Proc. of the 27th Hawaii Int. Conf. on System Sciences, 1994.
26. K. Beck and W. Cunningham, "A laboratory for teaching object oriented thinking," in Proc. of the ACM Conf. on Object Oriented Programming Systems and Languages and Applications (OOPLSA), 1989, pp. 1-6.
27. E. Jaques, Measurement of Responsibility: A Study of Work, Payment and Individual Capacity. London: Tavistock, 1956.
28. M. Gluckman, The Allocation of Responsibility. Manchester, England: Manchester University Press, 1972.
29. T. Cannon, Corporate Responsibility. New York: Pitman, 1992.
30. A. Blyth, "Responsibility modelling and its application to the management of change," Journal of Focus on Change Management, vol. 17, pp. 7-11, 1995.
31. R. Strens and J. E. Dobson, "Responsibility modelling as a technique for requirements definition," Intelligent Systems Engineering, vol. 3, no. 1, 1994.
32. L. M. Applegate, C. W. Holsapple, R. Kalakota, F. J. Radermacher, and A. B. Whinston, "Electronic commerce: Building blocks for new business opportunity," Journal of Organisational Computing and Electronic Commerce, vol. 6, no. 1, pp. 1-10, 1996.
33. A. Crainer, Zeebrugge: Learning from Disaster. London: Herald Charitable Trust, 1993.