Abstract
Software project mistakes represent a loss of millions of dollars to thousands of companies all around the world. These software projects that somehow ran off course share a common problem: Risks became unmanageable. There are certain number of conjectures we can draw from the high failure rate: Bad management procedures, an inept manager was in charge, managers are not assessing risks, poor or inadequate methodologies where used, etc. Some of them might apply to some cases, or all, or none, is almost impossible to think in absolute terms when a software project is an ad hoc solution to a given problem. Nevertheless, there is an ongoing effort in the knowledge engineering (KE) community to isolate risk factors, and provide remedies for runaway projects, unfortunately, we are not there yet. This work aims to express some general conclusions for risk assessment of software projects, particularly, but not limited to, those involving knowledge acquisition (KA).
This project has been partially funded by CONACyT as project number D.A.J-J002-222-98-16-II-98 (REDII), and Asociación Mexicana de Cultura, A.C.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Boehm, B.: A spiral model of software development and enhancement. IEEE Computers, 61–62 (1988)
Boehm, B., Ross, R.: Theory-w software project management: principles and examples. IEEE Trans. Softw. Eng. 15(7), 902–916 (1989)
Cairó, O.: The kamet methodology: Content, usage, and knowledge modeling. In: Gaines, B., Mussen, M. (eds.) Proceedings of the 11th Banff Knowledge Acquisition for Knowledge-Based Systems Workshop, Department of Computer Science, University of Calgary, pp. 1–20. SRGD Publications (1998)
Cairó, O., Barreiro, J., Solsona, F.: Software methodologies at risk. In: Fensel, D., Studer, R. (eds.) EKAW 1999. LNCS (LNAI), vol. 1621, pp. 319–324. Springer, Heidelberg (1999)
Cole, A.: Runaway projects -cause and effects. Software World 26(3) (1995)
Glass, R.L.: Short-term and long-term remedies for runaway projects. Communications of the ACM 41(7), 13–15 (1998)
Keil, M., Cule, P.E., Lyytinen, K., Schmidt, R.C.: A framework for identifying software project risks. Communications of the ACM 41(11), 76–83 (1998)
Lanubile, F., Visaggio, G.: Evaluating predictive quality models derived from software measures: Lessons learned. Technical report, University of Maryland, Computer Science Department, College Park, Maryland 20742 (1996)
Lemos, R.: d., Saeed, A., and Anderson, T, On the integration of requirements analysis and safety analysis for safety-critical software. Technical report, University of Newcastle upon Tyne, Department of Computer Science (1996)
Nonaka, I., Takeuchi, H.: The Knowledge Creating Company. Oxford Univ Press, New York (1995)
Zadeh, L.A.: Editorial uc-berkeley computer science commen cement address. IEEE Transactions on Systems, Man, and Cybernetics - Part C: Applications and reviews 28(1) (1998)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2000 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Cairó, O., Barreiro, J., Solsona, F. (2000). Risks Inside-Out. In: Cairó, O., Sucar, L.E., Cantu, F.J. (eds) MICAI 2000: Advances in Artificial Intelligence. MICAI 2000. Lecture Notes in Computer Science(), vol 1793. Springer, Berlin, Heidelberg. https://doi.org/10.1007/10720076_39
Download citation
DOI: https://doi.org/10.1007/10720076_39
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-67354-5
Online ISBN: 978-3-540-45562-2
eBook Packages: Springer Book Archive