Coping with 'requirements-uncertainty': the theories-of-action of experienced IS/software project managers

Journal of Systems and Software

Volumn 53, Issue 2, 2000, Pages 99-109

  Moynihan, Tony ^a  

^a DUBLIN CITY UNIVERSITY   (Ireland)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTATIONAL COMPLEXITY; INFORMATION TECHNOLOGY; MANAGEMENT INFORMATION SYSTEMS; REQUIREMENTS ENGINEERING; SUPERVISORY PERSONNEL; USER INTERFACES;

INFORMATION SYSTEMS; REQUIREMENTS UNCERTAINTY; USER REQUIREMENTS;

SOFTWARE ENGINEERING;

EID: 0034249299     PISSN: 01641212     EISSN: None     Source Type: Journal    
DOI: 10.1016/S0164-1212(00)00049-2     Document Type: Article

References (16)

1. Bannister, D., Fransella, F., 1989. Inquiring Man: The Psychology of Personal Constructs. third ed. Routledge, London.
2. Baskerville R.L., Stage J. Controlling prototype development through risk analysis. MIS Quarterly. 20:1996;481-504.
3. Burns, R.N., Dennis, A.R., 1985. Selecting the appropriate application development methodology. Data Base 19-23.
4. Davis G.B. Strategies for information requirements determination. IBM Systems Journal. 21(1):1982;3-30.
5. El Louadi M., Galleta D.F., Sampler J.L. An empirical validation of a contingency model for information requirements determination. Data Base. 29(3):1999;16-28.
6. Fazlollahi B., Tanniru M.R. Selecting a requirement determination methodology-contingency approach revisited. Information and Management. 21:1991;291-303.
7. Galleta D.F., El Louadi M. L'effet de L'incertitude et des strategies de determination des besoins de l'utilisateur sur les projets d'informatisation. Canadian Journal of Administrative Systems. 12(1):1995;56-76.
8. Keil M., Cule P., Lyytinen K., Schmidt R. A framework for identifying software project risks. Communications of the ACM. 41(11):1998;76-83.
9. Law K.S., Wong C.-S., Mobley W.H. Towards a taxonomy of multidimensional constructs. Academy of Management Review. 23(4):1998;741-755.
10. Mathiassen, L., Stage, J., 1990. Complexity and uncertainty in software design. In: Proceedings of the 1990 IEEE Conference on Computer Systems and Software Engineering. IEEE Computer Society Press, Silver Spring, MD, pp. 482-489.
11. Moynihan T. An inventory of personal constructs for risk researchers. Journal of Information Technology. 11:1996;359-371.
12. Naumann, J.D., Jenkins, A.M., Wetherbe, J.C., 1983. The information requirements determination contingency model: an empirical Investigation. Working Paper, University of Minneapolis, Minnesota.
13. Nidumolu S.R. Standardization, requirements uncertainty and software project performance. Information and Management. 31:1996;135-150.
14. Redmill F. Software Projects: Evolutionary versus Big-Bang Delivery. 1997;Wiley, Chichester, UK.
15. Saarinen T., Vepsalainen A. Managing the risks of information systems implementation. European Journal of Information Systems. 2(4):1993;283-295.
16. Stork D., Sapienza A.M. Uncertainty and equivocality in projects: managing their implications for the project team. Engineering Management Journal. 7(3):1995;33-38.