'Requirements-uncertainty': Should it be a latent, aggregate or profile construct?

Proceedings of the Australian Software Engineering Conference, ASWEC

Volumn 2000-January, Issue , 2000, Pages 181-188

  Moynihan, T ^a  

^a DUBLIN CITY UNIVERSITY   (Ireland)

Author keywords

Aggregates; Computer applications; Contingency management; Electrical capacitance tomography; Financial management; Project management; Prototypes; Software engineering; System testing; Uncertainty

Indexed keywords

AGGREGATES; APPLICATION PROGRAMS; COMPUTER APPLICATIONS; ELECTRIC IMPEDANCE TOMOGRAPHY; MANAGERS; PROJECT MANAGEMENT; SOFTWARE PROTOTYPING; SOFTWARE TESTING;

CONTINGENCY MANAGEMENT; ELECTRICAL CAPACITANCE TOMOGRAPHY; FINANCIAL MANAGEMENTS; PROTOTYPES; SYSTEM TESTING; UNCERTAINTY;

SOFTWARE ENGINEERING;

EID: 84950161834     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ASWEC.2000.844575     Document Type: Conference Paper

References (14)

1. G. B. Davis, "Strategies for information requirements determination", IBM Systems Journal, 21(1), 1982, pp. 3-30.
2. L. Mathiassen and J. Stage, "Complexity and uncertainty in software design". In Proceedings of the 1990 IEEE Conference on Computer Systems and Software Engineering, IEEE Computer Society Press, 1990, pp. 482-489.
3. B. Fazlollahi and M. R. Tanniru, "Selecting a requirement determination methodology-contingency approach revisited", Information and Management, 21, 1991, pp. 291-303.
4. T. Saarinen and A. Vepsalainen, "Managing the Risks of Information Systems Implementation", European Journal of Information Systems, 2(4), 1993, pp. 283-295.
5. D. F. Galletta and M. El Louadi", 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, pp. 56-76.
6. J. D. Naumann, A. M. Jenkins, and J. C. Wetherbe, "The information requirements determination contingency model: An empirical Investigation", University of Minnesota, Minneapolis, 1983.
7. F. Redmill, Software Projects: Evolutionary versus Big-Bang Delivery, John Wiley and Sons, Chichester, England, 1997.
8. R. L. Baskerville and J. Stage, "Controlling Prototype Development through Risk Analysis", MIS Quarterly, 20(4), 1996, pp. 481-504.
9. K. S. Law, Chi-Sum Wong and W. H. Mobley, "Towards a Taxonomy of Multidimensional Constructs", Academy of Management Review, 23(4), 1998, pp. 741-755.
10. R. N. Burns and A. R. Dennis, "Selecting the Appropriate Application Development Methodology", Data Base, Fall, 1985, pp. 19-23.
11. S. R. Nidumolu, "Standardization, requirements uncertainty and software project performance", Information and Management, 31, 1996, pp. 135-150.
12. D. Stork and A. M. Sapienza, "Uncertainty and Equivocality in projects: Managing their implications for the project team", Engineering Management Journal, 7(3), 1995, pp. 33-38.
13. T. Moynihan, "An Inventory of Personal Constructs for Risk Researchers", Journal of Information Technology, 11, 1996, pp. 359-371.
14. D. Bannister and F. Fransella, Inquiring Man: The Psychology of Personal Constructs (third edition), Routledge, London, 1989.