User viewpoint modelling: Understanding and representing user viewpoints during requirements definition

Information Systems Journal

Volumn 7, Issue 3, 1997, Pages 213-219

  Darke, P ^a   Shanks, G ^a  

^a MONASH UNIVERSITY   (Australia)

Author keywords

Requirements analysis; Requirements definition; Viewpoints

Indexed keywords

EID: 0001827054     PISSN: 13501917     EISSN: None     Source Type: Journal    
DOI: 10.1046/j.1365-2575.1997.d01-19.x     Document Type: Review

References (59)

1. Avison, D.E. & Fitzgerald, G. (1995) Information Systems Development: Methodologies, Techniques and Tools, 2nd edn. McGraw-Hill, London.
2. Avison, D.E. & Wood-Harper, AT. (1990) Multiview: An Exploration in Information Systems Development. McGraw-Hill, Maidenhead.
3. Benbasat, I., Goldstein, D.K. & Mead, M. (1987) The case research strategy in studies of information systems. MIS Quarterly, 11, 369-386.
4. Boehm, B. (1981) Software Engineering Economics. Prentice-Hall, Englewood Cliffs.
5. Bostrom, R.P. (1989) Successful application of communication techniques to improve the systems development process. Information and Management, 16, 279-295.
6. Boynton, A.C. & Zmud, R.W. (1984) An assessment of critical success factors. Sloan Management Review, 25, 17-27.
7. Burgess, G.M., Clark, T.D., Hauser, R.D. & Zmud, R.W. (1992) The application of causal maps to develop a collective understanding of complex organisational contexts in requirements analysis. Accounting, Management & Information Technology, 2, 143-164.
8. Byrd, T.A., Cossick, K.L. & Zmud, R.W. (1992) A synthesis of research on requirements analysis and knowledge acquisition techniques. MIS Quarterly, 16, 117-138.
9. Checkland, P. (1981) Systems Thinking, Systems Practice. John Wiley & Sons, Chichester.
10. Checkland, P. & Scholes, J. (1990) Soft Systems Methodology in Action. John Wiley & Sons, Chichester.
11. Colter, M.A. (1984) A comparative examination of systems analysis techniques. MIS Quarterly, 8, 51-65.
12. Curtis, B., Krasner, H. & Iscoe, N. (1988) Afield study of the software design process for large systems. Communications of the ACM, 31, 1268-1287.
13. Darke, P. & Shanks, G. (1995a) Viewpoint development for requirements definition: towards a conceptual framework. Proceedings of the 6th Australasian Conference on Information Systems, Curtin University of Technology, Perth.
14. Darke, P. & Shanks, G. (1995b) Defining system requirements: a critical assessment of the NIAM conceptual schema design procedure. Australian Journal of Information Systems, 2, 50-62.
15. Darke, P. & Shanks, G. (1996) Stakeholder viewpoints in requirements definition: a framework for understanding viewpoint development approaches. Requirements Engineering, i, 88-105.
16. Davis, G.B. (1982) Strategies for information requirements determination. IBM Systems Journal, 21, 4-30.
17. Easterbrook, S. (1991) Handling conflict between domain descriptions with computer-supported negotiation. Knowledge Acquisition, 3, 255-289
18. Easterbrook, S. (1993) Domain modelling with hierarchies of alternative viewpoints. Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Press, Los Alamitos.
19. Easterbrook, S. & Nuseibeh, B. (1996) Using viewpoints for inconsistency management. Software Engineering Journal, 11, 31-43.
20. Feather, M.S. (1993) Requirements engineering - getting right from wrong. Proceedings of the 3rd European Software Engineering Conference, Springer-Verlag, London.
21. Finkelstein, A., Kramer, J., Nuseibeh, B., Finkelstein, L. & Goedicke, M. (1992) Viewpoints: a framework for integrating multiple perspectives in system development. International Journal of Software and Knowledge Engineering, 2, 31-57.
22. Flynn, D.J. & Warhurst, R. (1994) An empirical study of the validation process within requirements determination. Information Systems Journal, 4, 185-212.
23. Goguen, J.A. & Linde, C. (1993) Techniques for requirements elicitation. Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Press, Los Alamitos.
24. Greenspan, S., Mylopoulos, J. & Borgida, A. (1994) On formal requirements modeling languages: RML revisited. Proceedings of the 16th International Conference on Software Engineering, IEEE Press, Los Alamitos.
25. Gutierrez, O. (1987) Some aspects of information requirements analysis using a repertory grid technique. In: Information Analysis: Selected Readings, Galliers, R.D. (ed), pp. 347-362. Addison-Wesley, Reading.
26. Gutierrez, O. (1989) Experimental techniques for information requirements analysis. Information & Management, 16, 31-43.
27. Jarke, M., Bubenko, J., Rolland, C., Sutcliffe, A. & Vassiliou, Y. (1993) Theories underlying requirements engineering: an overview of NATURE at Genesis. Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Press, Los Alamitos.
28. King. W.R. (1978) Strategic planning for management information systems. MIS Quarterly, 2, 27-37.
29. Land, F. (1982) Adapting to changing user requirements. Information & Management, 5, 59-75.
30. Leifer, R., Lee, S. & Durgee, J. (1994) Deep structures: real information requirements determination. Information & Management, 27, 275-285.
31. Leite, J. & Freeman, P.A. (1991) Requirements validation through viewpoint resolution. IEEE Transactions on Software Engineering, 17, 1253-1269.
32. Liou, Y.I. & Chen, M. (1994) Using group support systems and joint application development for requirements specification. Journal of Management Information Systems, 10, 25-41.
33. Lyytinen, K. & Hirschheim, R. (1987) Information systems failures - a survey and classification of the empirical literature. Oxford Surveys in Information Technology, 4, 257-309.
34. Macaulay, L. (1993) Requirements capture as a cooperative activity. In: Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Press, Los Alamitos.
35. Mittermeir, Hsia, P. & Yeh, R.T. (1987) Alternatives to overcome the communication problem of formal requirements analysis. In: Information Analysis: Selected Readings, Galliers, R.D. (ed), pp. 153-165. Addison-Wesley, Reading.
36. Montazemi, A.R. & Conrath, D.W. (1986) The use of cognitive mapping for information requirements analysis. MIS Quarterly, 10, 45-56.
37. Moreno, M. & Souveyet, C. (1993) The evolutionary object model. In: Information System Development Process, Prakash, N., Rolland, C. & Pernici, B. (eds), pp. 41-57. Elsevier Science, Amsterdam.
38. Mumford, E. (1983) Designing Human Systems. Manchester Business School, Manchester.
39. Mumford, E. (1985) Defining system requirements to meet business needs: a case study example. The Computer Journal, 28, 97-104.
40. Necco, C.R., Gordon, C.L. & Tsai, N. (1987) Systems analysis and design: current practices. MIS Quarterly, 11, 461-475.
41. Newman, M. & Robey, D. (1992) A social process model of user-analyst relationships. MIS Quarterly, 16, 249-266.
42. Nuseibeh, B., Kramer, J. & Finkelstein, A. (1994) A framework for expressing the relationships between multiple views in requirements specification. IEEE Transactions on Software Engineering, 20, 760-771.
43. Oliver, I. & Langford, H. (1987) Myths of demons and users: evidence and analysis of negative perceptions of users. In: Information Analysis: Selected Readings, Galliers, R.D. (ed), pp. 113-123. Addison-Wesley, Reading.
44. Olle, T.W., Hagelstein, J., MacDonald, I.G., Sol, H.G., Van Assche, F.J.M. & Verrijn-Stuart, A.A. (eds) (1991) Information Systems Methodologies: A Framework for Understanding, 2nd edn. Addison-Wesley, Wokingham.
45. Patton, M.Q. (1990) Qualitative Evaluation and Research Methods, 2nd edn. Sage, Newbury Park.
46. Pohl, K. (1994) The three dimensions of requirements engineering: A framework and its applications. Information Systems, 19, 243-258.
47. Potts, C., Takashashi, K. & Anton, A. (1994) Inquiry-based requirements analysis. IEEE Software, 21-32 (March).
48. Ramesh, B. & Dhar, V. (1992) Supporting systems development using knowledge captured during requirements engineering. IEEE Transactions on Software Engineering, 18, 498-510.
49. Ramesh, B. & Edwards, M. (1993) Issues in the development of a requirements traceability model. Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Press, Los Alamitos.
50. Ramesh, B. & Luqi (1993) Process knowledge based rapid prototyping for requirements engineering. Proceedings of the IEEE International Symposium on Requirements Engineering, IEEE Press, Los Alamitos.
51. Rockart, J.F. (1979) Chief executives define their own data needs. Harvard Business Review, 57, 81-91.
52. Roman, G.C. (1985) A taxonomy of current issues in requirements engineering. IEEE Computer, 14-22 (April).
53. Tan, M. (1993) Using communication theory for systems design: a model for eliciting information requirements. In: Human, Organizational, and Social Dimensions of Information Systems Development, Avison, D., Kendall, J.E. & DeGross, J.I. (eds), pp. 241-262. Elsevier, Amsterdam.
54. Teng, J.C. & Sethi, V. (1990) A comparison of information requirements analysis methods: An experimental study. Data Base, 20, 27-39.
55. Valusek, J.R. & Fryback, D.G. (1987) Information requirements determination: obstacles within, among and between participants. In: Information Analysis: Selected Readings, Galliers, R.D. (ed), pp. 139-151. Addison-Wesley, Reading.
56. Vitalari, NP. (1992) Structuring the requirements analysis process for information systems: a proposition viewpoint. In: Challenges and Strategies for Research in Systems Development, Cotterman, W.W. and Senn, J.A. (eds), pp. 163-179. John Wiley & Sons, Chichester.
57. Yourdon, E. (1989) Modern Structured Analysis. Prentice-Hall, Englewood Cliffs.
58. Yin, R.K. (1994) Case Study Research: Design and Methods, 2nd edn. Sage, Thousand Oaks.
59. Zmud, R.W., Anthony, W.P. & Stair, R. (1992) The use of mental imagery as a requirements analysis technique. In: Challenges and Strategies for Research in Systems Development, Cotterman, W.W. & Senn, J.A. (eds), pp. 337-350. John Wiley & Sons, Chichester.