Promoting requirement identification quality: Enhancing the human interaction dimension

Journal of Enterprise Information Management

Volumn 18, Issue 2, 2005, Pages 256-267

  Al Karaghouli, W ^a   Alshawi, S ^b   Fitzgerald, G ^b  

^a UNIVERSITY OF WESTMINSTER   (United Kingdom)

^b BRUNEL UNIVERSITY   (United Kingdom)

Author keywords

Knowledge management; Research methods; Resource allocation; Retail trade; Sociotechnical change

Indexed keywords

EID: 18844437218     PISSN: 17410398     EISSN: None     Source Type: Journal    
DOI: 10.1108/17410390510579945     Document Type: Article

References (37)

1. Anderson, D.R., Sweeney, D.J. and Williams, T.A. (1995), Quantitative Methods for Business, 6th ed., West Publishing Company, New York, NY.
2. Avison, D.E. and Fitzgerald, G. (1995), Information Systems Development: Methodologies, Techniques and Tools, McGraw Hill, New York, NY.
3. Bikson, T. and Eveland, J. (1996) "Groupware implementation, reinvention in the socio-technical frame", ACM Conference on Computer Supported Cooperative, ACM, New York, NY, pp. 428-37.
4. BS6719 (1986) British Standard Guide to Specifying User Requirements for Computer Based Systems.
5. Cavell, S. (1999), "Salespeople buck the system: survey finds software fails to take account of culture", Computing, 25 February, p. 16.
6. Checkland, P. (1978), "The origins and nature of 'hard' systems thinking", Journal of Applied Systems Analysis, Vol. 5 No. 2, pp. 99-110.
7. Checkland, P. and Holwell, S. (1998), Information, Systems and Information Systems - Making Sense of the Field, Wiley & Sons, Chichester.
8. Checkland, P. and Scholes, J. (1997), Software Systems Methodology in Action, Wiley & Sons.
9. Computing UK (1989), "Stock exchange kills projects to focus on Taurus", Computing UK, 2 November, p. 1.
10. Computing UK (1998), "Swanwick Air Traffic Centre set for delays", Computing UK, 22 Ocober, p. 23.
11. Computing UK (2001), "Case study: Tesco - how it can go wrong", Computing UK, 18 October, p. 42.
12. Crosby, P. (1989), Let's Talk Quality, McGraw-Hill, New York, NY.
13. Flood, G. (2000), "Are users satisfiable?", Computing UK, 10 February, p. 11.
14. Glass, R. (1998), Software Runaways: Lessons Learned from Massive Software Project Failures, Prentice-Hall, Englewood Cliffs, NJ.
15. Glass, R. (2001), ComputingFailure.Com: War Stories from the Electronic Revolution, Prentice-Hall, Englewood Cliffs, NJ.
16. Gubbins, M. (2001), "We can still learn lessons from Leo", Computing UK, 18 October, p. 24.
17. Harrington, A. (2001), "Sweet content", Cover Story, Knowledge Management Magazine, June, pp. 14-16.
18. Hatton, L. (1999), "Swanwick bug fixes not good enough", Computer Weekly UK, 7 January, p. 11.
19. Ishikawa, K. (1985), What is Total Quality Control? The Japanese Way, translated by D.J. Lu, Prentice-Hall, New York, NY.
20. Juran, J.M. (1989), Juran on Leadership for Quality: An Executive Handbook, 4th ed., McGraw-Hill, New York, NY.
21. Kelly, L. (1999), "Developers bark up wrong tree", Computing UK, 4 March, p. 14.
22. Kelly, L. (2000), "Let projects fail, says think tank: the Government needs to learn from its mistakes", Computing Public Sector Digest, January, p. 4.
23. Land, F. (1982), "Adapting to changing user requirements", Information and Management, Vol. 5, pp. 59-75.
24. Macaulay, L.A. (1996), Requirements Engineering, Springer-Verlag, London.
25. Myers, M.D. (1994), "A disaster for everyone to see: an interpretive analysis of a failed IS project", Accounting, Management and Information Technology, Vol. 4 No. 4, pp. 185-201.
26. OASIG Survey (1996), "The performance of information technology and the role of human and organisational factors", Professor C. Clegg, Institute of Work Psychology, University of Sheffield, Sheffield.
27. O'Callaghan, A. (2002), "I think, Argo I am", Application Development Advisor, SIGS, Vol. 6 No. 1, pp. 68-71.
28. Parker, A. (2000), "Commons Committee calls for action on IT fiascos", Financial Times, 5 January, p. 2.
29. Pressman, R.S. (1992), Software Engineering: A Practitioner's Approach, 3rd ed., McGraw-Hill, New York, NY.
30. Price Waterhouse (1991, 1992), "The culture gap", Information Technology Review, pp. 16-19.
31. Ranger, S. (2001), "State IT failures squander £1bn: our survey counts the cost of Pathway, NIRS2 and the rest", Computing, 5 July, p. 1.
32. Reddy, M., Pratt, W., Dourish, P. and Shabat, M. (2003), "Socio-technical requirements analysis for clinical systems", Methods Inf. Med., Vol. 42, pp. 437-44.
33. Regnell, B., Kimbler, K. and Wesslen, A. (1995), "Improving the use case driven approach to requirements engineering", Proc. 2nd IEEE Int. Symp. on Requirements Eng. (RE'95), York, April, pp. 40-7.
34. Sieloff, C.G. (1999), "If only HP knows what HP knows: the roots of knowledge management at Hewlett-Packard", Journal of Knowledge Management, Vol. 3 No. 1, pp. 47-53.
35. Sommerville, I. and Sawyer, P. (1999), Requirements Engineering: A Good Practice Guide, John Wiley, Chichester.
36. Sturt, T. (2000), "These craz-e days: can the right ejargon turn you into a guru?", Computing, 10 February, p. 80.
37. Tenkasi, R. and Boland, R. Jr (1996), "Exploring knowledge diversity in knowledge-intensive firms: a new role for information systems", Journal of Organizational Change Management, Vol. 9 No. 1, pp. 79-91.