This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Software Reliability Allocation Based on Structure, Utility, Price, and Cost
April 1991 (vol. 17 no. 4)
pp. 345-356

A software reliability allocation model is developed. This model determines how reliable software modules and programs must be in order to maximize the user's utility, while taking into account the financial and technical constraints of the system. The model is shown to provide a unified approach in which the user's requirements and preferences are formally integrated with the technical structure of the software and its module and program reliabilities. The model determines reliability goals at the planning and design stages of the software project, making reliability a singular measure for performance evaluation and project control. An example for the application of the model is provided.

[1] T. Anderson, P. A. Barret, D. N. Halliwell, and M. R. Moulding, "Software fault tolerance: An evaluation,"IEEE Trans. Software Eng., vol. SE-11, no. 12, pp. 1502-1510, 1985.
[2] E. E. Anderson, "A heuristic for software evaluation and selection,"Software--Practice and Experience, vol. 19, no. 8, pp. 707-717, Aug. 1989.
[3] N. Ashrafi, "Decomposition models for predicting software reliability," Ph.D. dissertation, Dep. Management Sci. Inform. Syst., Univ. Texas, Arlington, 1989.
[4] N. Ashrafi, R. C. Baker, and J. P. Kuilboer, "Proposed structure for decomposition software reliability prediction model,"Software Inform. Technol., vol. 35, no. 7, pp. 1-7, 1990.
[5] B. W. Boehm, "Software engineering economics,"IEEE Trans. Software Eng., vol. SE-10, pp. 4-21, 1984.
[6] B. W. Boehm and R. W. Wolverton, "Software cost modeling: Some lessons learned,"J. Syst. Software, vol. 1, no. 3, pp. 195-201, 1980.
[7] A. Brooke, D. Kendrick, and A. Meeraus,GAMS: A User Guide. Redwood City, CA: Scientific Press, 1988.
[8] D. B. Brown, S. Maghsoodloo, and W. H. Deason, "A cost model for determining the optimal number of software test cases,"IEEE Trans. Software Eng., vol. 15, no. 2, pp. 218-225, 1989.
[9] J. R. Brown and M. Lipow, "Testing for software reliability," inProc. Int. Conf. Reliable Software, Los Angeles, CA, Apr. 1975, pp. 518-527.
[10] J. P. Buzen, P. P. Chen, and R. P. Goldberg, "Virtual machine techniques fur improving system reliability," inRec. 1973 IEEE Symp. Computer Software Reliability, New York, NY, Apr. 30-May 2, 1973, pp. 12-17.
[11] R. C. Cheung, "A user-oriented reliability model,"IEEE Trans. Software Eng., vol. SE-6, no. 2, pp. 118-125, 1980.
[12] A. I. Concepcion and B. P. Zeigler, "DEVS formalism: A framework for hierarchical model development,"IEEE Trans. Software Eng., vol. 14, no. 2, pp. 228-241, Feb. 1988.
[13] Expert Choice Inc.,Expert Choice; Based on the Analytic Hierarchy Process, Pittsburgh, PA, 1983, 1990.
[14] A. L. Goel and K. Okumoto, "Time dependent error detection rate model for software reliability and other performance measures,"IEEE Trans. Rel., vol. R-28, no. 3, pp. 206-211, 1979.
[15] L. L. Gremillion, "Determinants of program repair maintenance requirements,"Commun. ACM, vol. 27, no. 8, pp. 826-832, Aug. 1984.
[16] P. T. Harker, "Alternative modes of questioning in the analytic hierarchy process,"Math. Modelling, vol. 9, pp. 353-360, 1987.
[17] P. T. Harker, "The art and science of decision making: The analytic hierarchy process," inThe Analytic Hierarchy Process: Applications and Studies, B. L. Golden, E. A. Wasil, and P. T. Harker, Eds. Berlin: Springer-Verlag, 1989, pp. 2-36.
[18] H. Hecht and M. Hecht, "Software reliability in system context,"IEEE Trans. Software Eng., vol. SE-12, no. 1, pp. 51-58, 1986.
[19] F. S. Hillier and G. J. Lieberman,Operations Research, 3rd ed. San Francisco, CA: Holden-Day, 1980.
[20] Z. Jelinski and P. B. Moranda, "Software reliability research," inStatistical Computer Performance, W. Freiberger, Ed. New York: Academic, 1972, pp. 465-484.
[21] P. Kubat, "Assessing reliability of modular software,"Oper. Res. Lett., vol. 8, pp. 35-41, 1989.
[22] M. Lipow, "On software reliability,"IEEE Trans. Rel., vol. R-28, no. 3, pp. 178-180, Aug. 1979.
[23] B. H. Liskov, "A design methodology for reliable software," inProc. Fall Joint Conf. AFIPS, vol. 41, part 1, 1972, pp. 191-199.
[24] B. Littlewood, "How to measure software reliability and how not to,"IEEE Trans. Rel., vol. R-28, no. 2, pp. 103-110, 1979.
[25] B. Littlewood, "Software reliability model for modular program structure,"IEEE Trans. Rel., vol. R-28, no. 3, pp. 241-246, 1979.
[26] B. Littlewood and J. Verral, "Likelihood function of a debugging model for computer software reliability,"IEEE Trans. Rel., vol. R-30, no. 2, pp. 145-148, 1980.
[27] B. Meyers,Object Oriented Software Construction. Englewood Cliffs, NJ: Prentice-Hall, 1988.
[28] H. D. Mills, "On the development of large reliable software," inRec. 1973 IEEE Symp. Computer Software Reliability, New York, April 30-May 2, 1973, pp. 155-159.
[29] K. B. Misra, "A method of solving redundancy optimization problems,"IEEE Trans. Rel., vol. R-20, no. 3, pp. 117-120, 1972.
[30] K. B. Misra, "Reliability optimization of a series-parallel system,"IEEE Trans. Rel., vol. R-21, no. 4, pp. 230-237, 1972.
[31] J. Musa, "Software quality and reliability basics," inProc. 1987 Fall Joint Conf. IEEE Exploring Technology Today and Tomorrow, Oct. 25-29, 1987, Dallas, TX, 1987, pp. 114-115.
[32] J. D. Musaet al., Software Reliability Measurement, Prediction, Application. New York: McGraw-Hill International, 1987.
[33] E. C. Nelson, "Estimating software reliability from test data,"Microelectron. Rel., vol. 17, no. 1, pp. 67-74, 1974.
[34] E. C. Nelson, "Software reliability," TRW Software Series, TRW-SS-75- 05, Redono Beach, CA, Nov. 1975.
[35] T. J. Ostran and M. J. Balcer, "The category-partition method for specifying and generating functional tests,"Commun. ACM, vol. 31, no. 6, pp. 676-686, 1988.
[36] D. L. Parnas, "The influence of software structure on reliability," inProc. IEEE Int. Conf. Reliable Software, Los Angeles, CA, Apr. 21-23, 1975, pp. 358-362.
[37] Ramamoorthy, C.V. et al. 1984. "Software Engineering: Problems and Perspectives."IEEE Computer, October, pp. 191-209.
[38] C. V. Ramamoorthy, A. Prakash, V. Garg, T. Yamaura, and A. Bhide, "Issues in he development of large, distributed, and reliable software," inAdvances in Computer, M. G. Yovits, Ed. New York: Academic, 1987, pp. 393-443.
[39] T. L. Saaty, "A scaling method for priorities in hierarchical structure,"J. Math. Psychol., vol. 15, pp. 234-281, 1977.
[40] G. J. Schick and R. W. Wolverton, "An analysis of competing software reliability models,"IEEE Trans. Software Eng., vol. SE-4, no. 2, pp. 104-120, 1978.
[41] N. Schneidewind, "Application of program graphs and copplexity analysis to software development and testing,"IEEE Trans. Rel., vol. R-28, no. 3, pp. 192-211, 1979.
[42] J. Sharma and K. V. Venkateswaran, "A direct method for maximizing the system reliability,"IEEE Trans. Rel., vol. R-28, no. 4, pp. 256-259, 1971.
[43] S. A. Sherer, "Measuring the risk of software failure: a financial application," inProc. Tenth Int. Conf. Information Systems, Boston, MA, Dec. 1989, pp. 237-245.
[44] S. A. Sherer and E. K. Clemons, "Software risk assessment," inAFIPS Conf. Proc., vol. 56, Chicago, IL, June 1987, pp. 701-707.
[45] M. L. Shooman,Software Engineering. New York: McGraw-Hill, 1983.
[46] M. L. Shooman, "Probabilistic models for software reliability prediction," inStatistical Computer Performance Evaluation, W. Freidberger, Ed. New York: Academic, 1972, pp. 485-502.
[47] B. Shriver and P. Wegner, Eds.,Research Directions in Object Oriented Programming. Cambridge, MA: MIT Press, 1987.
[48] M. Stefik and D. G. Babrow, "Object-oriented programming: Themes and variations,"AI Mag., vol. 6, no. 4, pp. 40-62, Dec. 1985.
[49] F. L. Tillman, C. Hwang, and W. Kuo, "Optimization techniques for system reliability with redundancy--A review,"IEEE Trans. Reliability, vol. R-28, no. 3, pp. 148-155, 1977.
[50] F. A. Tillman, C. Hwang, and W. Kuo, "Determination of component reliability and redundancy for optimum systems reliability," inOptimization of Systems Reliability, W. Meier, Ed. New York: Dekker, 1980, pp. 273-284.
[51] S. N. Weiss and E. J. Weyuker, "An extended domain-based model for software reliability,"IEEE Trans. Software Eng., vol. 14, no. 10, pp. 1512-1524, 1988.
[52] F. Zahedi, "A method for the quantitative evaluation of expert systems,"European J. Oper. Res., 1990, to be published.
[53] F. Zahedi, "Quantitative evaluation of micro vs. larger database products,"Comput. Oper. Res., vol. 16, no. 6, pp. 513-532, 1989.
[54] F. Zahedi, "A utility approach to the analytic hierarchy process,"Math. Modelling, vol. 9, no. 3-5, pp. 387-395, 1987.
[55] F. Zahedi, "Qualitative programming for selection decisions,"Comput. Oper. Res., vol. 14, no. 5, pp. 395-407, 1987.
[56] F. Zahedi, "Reliability of information systems based on critical success factors--Formulation,"MIS Quarterly, vol. 11, no. 2, pp. 187-203, 1987.
[57] F. Zahedi, "The analytic hierarchy process--A survey of the method and its applications,"Interfaces>, vol. 16, no. 4, pp. 96-108, 1986.
[58] F. Zahedi, "A simulation study of estimation methods in the analytic hierarchy process,"Socio-Economic Planning Sci., vol. 20, no. 6, pp. 347-354, 1986.
[59] F. Zahedi, "Group consensus function estimation when preferences are uncertain,"Oper. Res., vol. 34, no. 6, pp. 883-894, 1986.
[60] F. Zahedi, "DBMS evaluations and selection decision,"Decision Sci., vol. 16, no. 1, pp. 91-116, 1985.

Index Terms:
structure; utility; price; cost; software reliability allocation; reliability goals; performance evaluation; project control; reliability theory; software reliability
Citation:
F. Zahedi, N. Ashrafi, "Software Reliability Allocation Based on Structure, Utility, Price, and Cost," IEEE Transactions on Software Engineering, vol. 17, no. 4, pp. 345-356, April 1991, doi:10.1109/32.90434
Usage of this product signifies your acceptance of the Terms of Use.