An approach to the software quality management. (English. Russian original) Zbl 1117.68331

Cybern. Syst. Anal. 42, No. 5, 758-768 (2006); translation from Kibern. Sist. Anal. 42, No. 5, 174-185 (2006).
Summary: This article is devoted to an engineering approach to software quality management. The approach is oriented toward the attainment of the software maturity, which is a key software quality characteristic. A model of quality and a conceptual model for making decisions on software quality management are developed. They are based on methods of specification of quality requirements to the maturity of software components, defect prediction, and systematic quantitative reliability control during software development. A graphical defect prediction model (a Bayesian Belief Network) is presented.


68N99 Theory of software
Full Text: DOI


[1] 12207/FPDAM 1.2. Software Engineering: Life Cycle Processes, ISO/IEC JTC1/SC7 N2413, Software & System Engineering Secretariat, Canada (2001).
[2] V. V. Lipaev, Methods of Quality Maintenance of Large-Scale Software Tools [in Russian], SINTEG, Moscow (2003). · Zbl 1124.68346
[3] ISO/IEC 9126-1:2001, Software Engineering – Product Quality. Part 1. Quality Model.
[4] V. V. Lipaev, Quality of Software Tools: Methodical Recommendations [in Russian], A. A. Polyakov (ed.), Yanus-K, Moscow (2002).
[5] DSTU 2844-94 Software Tools of Computers. Quality Maintenance: Terms and Definitions, Derzhstandart Ukrainy, Kyiv (1994).
[6] E. M. Lavrishcheva, ”Integration paradigm in program engineering,” Problemy Programmirovaniya, Nos. 1–2, 351–360 (2000).
[7] V. N. Grishchenko and E. M. Lavrishcheva, ”Methods and tools of component programming,” Cybernetics and Systems Analysis, No. 1, 39–55 (2003). · Zbl 1040.68024
[8] ISO/IEC TR 9126-4:2004. Software Engineering: Product Quality. Part 4. Quality in using metrics.
[9] G. I. Koval and G. B. Moroz, ”Modeling of requirements to the quality of software systems of data processing,” Problemy Programmirovaniya, Nos. 2–3, 237–244 (2006).
[10] F. Zahedi and N. Ashrafi, ”Software reliability allocation based on structure, utility, price, and cost,” IEEE Trans. On Softw. Eng., 17, No. 4, 345–356 (1991). · Zbl 05113649
[11] G. I. Koval, ”An approach to the prediction of the reliability of software support during project management,” in: Proc. Conf. UkrPROG’2002, Kiev (2002), pp. 282–290.
[12] G. B. Moroz and E. M. Lavrishcheva, ”Reliability Growth models of software tools,” in: Prepr. V. M. Glushkov Cybernetics Inst. of AS of Ukraine, No. 92-38, Kiev (1992).
[13] G. B. Moroz, ”Poisson reliability growth models of software tools and their application: An analytical review,” USiM, Nos. 1–2, 69–85 (1996).
[14] J. D. Musa, A. Iannino, and K. Okumoto, Software Reliability Measurement, Prediction, and Application, McGraw-Hill, New York (1987).
[15] G. I. Koval, ”Methods of determination of program sizes,” Problemy Programmirovaniya, No. 1, 63–71 (1999). · Zbl 1025.60013
[16] P. B. Lakey and A. M. Neufelder, System and Software Reliability Assurance Notebook, Rome Lab. Rep., Griffiss Air Force Base, Rome NY (1997).
[17] N. E. Fenton and M. Neil, ”A critique of software defect prediction models,” IEEE Trans. on Soft. Eng., 25, No. 5, 675–689 (1999).
[18] Yu. V. Kapitonova, N. M. Mishchenko, O. D. Felizhanko, and N. N. Shchegoleva, ”Using Bayesian networks for monitoring computer users,” Cybernetics and Systems Analysis, No. 6, 3–14 (2004). · Zbl 1101.68873
[19] G. I. Koval, ”Bayesian networks as a method of estimation and prediction of software quality,” Problemy Programuvannya, No. 2, 15–23 (2005).
[20] Hugin Lite 6.5. Hugin Expert Product, www.hugin.com/products_Services/products/Demo/Download/.
[21] T. M. Korotun and E. M. Lavrishcheva, ”Construction of a process of testing software systems,” Problemy Programmirovaniya, Nos. 1–2, 272–281 (2002).
[22] G. B. Moroz and T. M. Korotun, ”Risk-operational approach to the solution of the problem of optimum release of software systems,” Problemy programmirovaniya, Nos. 2–3, 231–236 (2006).
This reference list is based on information provided by the publisher or from digital mathematics libraries. Its items are heuristically matched to zbMATH identifiers and may contain data conversion errors. It attempts to reflect the references listed in the original paper as accurately as possible without claiming the completeness or perfect precision of the matching.