Knowledge-based systems application to reduce risk in software requirements
The development of complex large scale software systems begins with the elicitation and explication of requirements definitions between users and software systems engineers. Errors at this phase may account for 35 to 75 percent of the errors that will occur in software development. The development of requirements is probably flawed through failure in the processes of critical thinking on the part of the user and the design team. This leads to volatility in requirements in the form of imprecision, multiplicity, and conflict in quality goals. There exists a substantial need to provide a means for verification and validation (V&V) of requirements, particularly those factors that relate system characteristics to functionality factors. Risk related to these factors must be resolved if the error rate is to be reduced. Functionality goals have been classified and relationships established, a conflict matrix has been prepared, and a rule-set to apply the inference model has been constructed. The results of this work, on development of a knowledge-based system to resolve questions of risk in software requirements, show that substantial improvement in risk reduction is feasible by application of a rule-based system to reduce requirements volatility.
KeywordsCritical Thinking Inference Model Software Requirement Quality Goal Quality Framework
Unable to display preview. Download preview PDF.
- Balzer, R., "A 15 Year Perspective on Automatic Programming," IEEE Transactions on Software Engineering, Vol.11, No.11, November 1987.Google Scholar
- Beam, W.R., Palmer, J.D., and Sage, A.P., "Systems Engineering for Software Productivity," IEEE Transactions on Systems, Man, and Cybernetics, Vol 17, No.2, March/April 1987.Google Scholar
- Charette, R.N., Software Engineering Environments: Concepts and Technology, McGraw Hill Book Co., 1986.Google Scholar
- Cohen, P.R., Heuristic Reasoning About Uncertainty: An Artificial Intelligence Approach, Pitman, 1985.Google Scholar
- Cooke, N.M., and McDonald, J.E., "A Formal Methodology for Acquiring and Representing Expert Knowledge," Proceedings of the IEEE, October 1986.Google Scholar
- Dressel, P and Mayhew, L.B. General Education: Exploration in Evaluation, Final Report of the Cooperative Study of Evaluation of General Education, American Council on Education, Washington, D.C., 1954Google Scholar
- Kandel, Abraham, Fuzzy Mathematical Techniques with Applications, Addison-Wesley Publishing Co., 1985.Google Scholar
- Palmer, J.D., "Uncertainty and Probabilistic Inference in Software Requirements Definitions," to appear in Large Scale Systems, 1988.Google Scholar
- Pressman, R.S., Software Engineering: A Practioner's Approach, McGraw Hill Book Co., 1982.Google Scholar
- Stephanou, H., and Sage, A.P., "Perspectives on Imperfect Information Processing," IEEE Transactions on Systems, Man, and Cybernetics, Vol.17, No.5, September 1987.Google Scholar
- Watson, G. and Glasser, E.M., Critical Thinking Appraisal Manual, Harcourt, Brace, and World, New York, 1964.Google Scholar