User Manuals as Project Management Tools: Part I—Theoretical Background

IEEE Transactions on Professional Communication

Volumn 37, Issue 2, 1994, Pages 75-80

  Shand, Rod McIntosh ^a  

^a NONE

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER SOFTWARE; INDUSTRIAL RESEARCH; INFORMATION RETRIEVAL SYSTEMS; MATHEMATICAL MODELS;

INFORMATION SYSTEM (IS); PROJECT FAILURE; USER MANUALS;

PROJECT MANAGEMENT;

EID: 0028446355     PISSN: 03611434     EISSN: 15581500     Source Type: Journal    
DOI: 10.1109/47.291572     Document Type: Article

References (23)

1. R. McIntosh Shand, “User manuals as project management tools: Part II—Practical applications,” IEEE Trans. Prof Commun., vol. 37, no. 3, 1994. In press.
2. A. A. Verrijn-Stuart and K. Anzenhofer, “Information systems user-designer designer communications problems,” Inform. and Manage., vol. 14, pp. 133–142, 1988.
3. K. Lyytinen, “Expectation failure concept and systems analysts’ view of information system failures: Results of an exploratory study,” Inform. and Manage., vol. 14, pp. 45–56, 1988.
4. K. Lyytinen and R. Hirschheim, “Information systems failures: A survey and classification of empirical literature,” Oxford Surveys in Inform. Technol., vol. 4, pp. 257–309, 1987.
5. B. W. Boehm, “Software risk management: Principles and practices,” IEEE Software, vol. 8, no. 1, pp. 32–41, 1991.
6. W. J. Doll and M. U. Ahmed, “Managing user expectations,” J. Syst. Manage., vol. 34, no. 6, pp. 6–11, 1983.
7. B. W. Boehm and R. Ross, “Theory-W software project management principles and examples,” IEEE Trans. Software Eng., vol. 15, no. 7, pp. 902–916, 1989.
8. P. N. Johnson-Laird, Mental Models. Cambridge, MA: Harvard University Press, 1983.
9. D. Gentner and A. L. Stevens (Eds), Mental Models. Hillsdale, NJ: Lawrence Erlbaum, 1983.
10. N. Staggers and A. F. Norcio, “Mental models: Concepts for human-computer computer interaction research,” Int. J. Man-Machine Studies, vol. 38, no. 4, pp. 587–605, 1993.
11. G. Fischer, “The importance of models in making complex systems comprehensible,” In Mental Models and Human-Computer Interaction 2, M. J. Tauber and D. Ackermann (Eds). Amsterdam: Elsevier North Holland, 1991.
12. D. A. Norman, “Some observations on mental models,” In Mental Models, D. Gentner and A. L. Stevens (Eds), Hillsdale, NJ: Lawrence Erlbaum, 1983.
13. G. B. Davis, A. S. Lee, K. R. Nickles, S. Chatterjee, R. Hartung, and Y. Wu, “Diagnosis of an information system failure,” Inform. and Manage., vol. 23, pp. 293–318, 1992.
14. D. A. Norman, “The trouble with Unix,” Datamation, vol 27, no. 12, pp. 139–150, 1981.
15. K. Holtzblatt and H. Beyer H, “Making customer-centred design work for teams,” Commun. of ACM, vol. 36, no. 10, pp. 93–103, 1993.
16. T. Moynihan and N. O’Connor, “A method to help end-users validate the functional specification for a computer system,” J. Inform. Syst. (U.K. Journal), vol. 1, no. 3, pp. 191–206, 1991.
17. G. M. Schneider, J. Martin and W. T. Tsai, “An experimental study of fault detection in user requirements documents,” ACM Trans. Software Eng. Method., vol. 1, no. 2, pp. 188–204, 1992.
18. M. E. Fagan, “Design and code inspections to reduce errors in program development,” IBM Syst. J., vol. 15, no. 3, pp. 182–211, 1976.
19. M. E. Fagan, “Advances in software inspections,” IEEE Trans. Software Eng., vol. 12, no. 7, pp. 744–751, 1986.
20. K. Auguston, “How to get the system you want. and stay out of court,” Modern Materials Handling, vol 46, no. 5, pp. 62–65, 1991.
21. J. Rothfeder, “It's Late, Costly, Incompetent—But Try Firing a Computer System,” Business Week, no. 3078 (November 7), pp. 164–165, 1988.
22. H. Glover, H. J. Watson, and R. K. Rainer, “Twenty ways to waste an EIS investment,” Inform. Strategy: Executive's J., vol. 8, no. 2, pp. 11–17, 1992.
23. F. P. Brooks, “No silver bullet: Essence and accidence of software engineering,” IEEE Comput., vol. 20, no 4, pp. 10–19, 1987.