SOFTWARE QUALITY MANAGEMENT SYSTEM

2022;
: 1-20
https://doi.org/10.23939/ujit2022.01.001
Received: April 08, 2022
Accepted: May 19, 2022

Ци­ту­ван­ня за ДСТУ: Гри­цюк Ю. І. Сис­те­ма уп­рав­лян­ня якіс­тю прог­рам­но­го за­без­пе­чен­ня. Ук­ра­їнсь­кий жур­нал ін­фор­ма­ційних тех­но­ло­гій. 2022, т. 4, № 1. С. 01–20.

Citation APA: Hrytsiuk, Yu. I. (2022). Software quality management system. Ukrainian Journal of Information Technology, 4(1), 01–20. https://doi.org/10.23939/ujit2022.01.001

Authors:
1
Lviv Polytechnic National University, Lviv, Ukraine

The Software quality management system has been developed. The system allows you to determine the state of software quality at each hierarchical level of the management system, taking into account the cost of ensuring the required quality. The system also allows the IT company manager to set the potential costs for the transition of software quality indicators from one state to another. It was found out that software quality is a multifaceted concept that can be adequately expressed by some hierarchical structure of characteristics and attributes, which is called the model of software product quality. To assess the quality of the software, a set of criteria and aggregate indicators were used, which maximally characterise it in terms of functionality and usage options. It is established that the software quality model is the main attribute of the complex system of its assessment. The quality model determines which characteristics of the software product must be taken into account when transiting the control system from one state to another. The level of software quality that meets the stated and indirect needs of various stakeholders and is relevant to them is directly reflected in the quality model of the software product in the form of its properties. The software quality model classifies product properties into characteristics and sub-characteristics.

A method for selecting stressful variants of software quality state according to input criteria or aggregate indicators of its current quality has been developed. The method allows to determine the current state of software quality at each hierarchical level according to the corresponding aggregate indicator, taking into account its development cost. A method for selecting the optimal version of the software quality management system from the set of permissible has been developed. The method takes into account the structure of criteria and aggregated indicators of current software quality at each hierarchical level of the management system. It is established that the task of choosing the optimal version of the software quality management system belongs to the tasks of multicriteria optimization. The task takes into account the following criteria: portability of the product and its ease of maintenance, product safety and compatibility, ease of use of the product and reliability of its work, as well as the functional suitability of the product and its efficiency of use. An example of implementation of the software quality management system in both quantitative and cost ratio is given. The example allows us to understand the essence of the method of choosing the optimal variant for the management system, as well as the features of the method of selection of stressful variants of the system state according to two criteria or aggregate indicators.

[1]     Al­yos­hin, G. V., Panchen­ko, S. V., & Prik­hod­ko, S. I. (2019). Op­ti­mi­za­ti­on of di­gi­tal transmis­si­on systems: textbo­ok. Khar­kiv: Pub­lis­hing hou­se UkrDUZT, 142 p. [In Ukrainian].

[2]     Al­yos­hin, G., Ko­lo­miytsev, O., & Tret­yak, V. (2020). Fe­atu­res of op­ti­mal synthe­sis of rich in­for­ma­ti­on systems. Col­lec­ti­on of sci­en­ti­fic works ΛΌGOΣ, 81–84. https://doi.org/10.36074/24.04.2020.v2.23

[3]     Azar D., Har­ma­na­ni, H., & Korkmaz, R. (2009, Sep­tem­ber). A hybrid heu­ris­tic appro­ach to op­ti­mi­ze ru­le-ba­sed softwa­re qua­lity es­ti­ma­ti­on mo­dels. In­for­ma­ti­on and Softwa­re Techno­logy, 1365–1376. https://doi.org/10.1016/j.infsof.2009.05.003

[4]     Bo­egh. J. (2008, March-Ap­ril). A new Stan­dard for Qua­lity Req­ui­re­ments. IEEE Softwa­re, 25(2), 57–63. https://doi.org/10.1109/MS.2008.30

[5]     Bot­su­la, M. P., & Mor­hun, I. A. (2011). Me­tod otryman­nia kompleksnoi ot­sinky ya­kos­ti veb-ma­te­ri­aliv z vykorystan­ni­am po­li­ar­noi systemy ko­ordynat. Visnyk Vinnytsko­ho po­li­tekhnichno­ho instytu­tu, 1, 84–88. Ret­ri­eved from: https://visnyk.vntu.edu.ua/in­dex.php/visnyk/ar­tic­le/vi­ew/1367/ con­fe­ren­ces.vntu.edu.ua. [In Ukrainian].

[6]     Bot­su­la, M. P., & Mor­hun, I. A. (2014). Nov­yi me­tod ta in­for­mat­si­ina tekhno­lo­hiia ob­rob­len­nia danykh dlia up­rav­lin­nia ya­kis­tiu elektronnykh navchalnykh kur­siv. In­for­mat­si­ini tekhno­lo­hii ta kom­piu­ter­na inzhe­ne­riia: mizhna­rodnyi nau­ko­vo-tekhnichnyi zhur­nal, 3, 25–33. Ret­ri­eved from: https://nbuv.gov.ua/UJRN/It­ki_2014_3_6. [In Ukrainian].

[7]     Bu­da­retskiy, Y., Shcha­vinskiy, Y., Kuz­net­sov, V., & Ni­ko­la­yev, S. (2021). Appli­ca­ti­on of the met­hod of analysis of hi­erarchi­es to as­sess the softwa­re of comple­xes of au­to­ma­ti­on me­ans. Mi­li­tary Techni­cal Col­lec­ti­on, (25), 3–12. https://doi.org/10.33577/2312-4458.25.2021.3-12

[8]     But­ko, M. P. (Ed.), But­ko, I. M., Mashchen­ko, V. P., et al. (2015). De­ci­si­on the­ory: textbo­ok. Kyiv: Pub­lis­hing hou­se "Cen­ter for Edu­ca­ti­onal Li­te­ra­tu­re", 360 p. [In Ukrainian].

[9]     Chal­la, Ja­gat Sesh, Pa­ul, Arin­dam, Da­da, Yo­gesh, Ne­rel­la, Ven­ka­tesh, Sri­vas­ta­va, Pra­ve­en Ran­jan, & Singh, Ajit Pra­tap. (2011). In­teg­ra­ted Softwa­re Qua­lity Eval­ua­ti­on: A Fuzzy Mul­ti-Cri­te­ria Appro­ach. Jo­ur­nal of In­for­ma­ti­on Pro­ces­sing Systems, 7(3), 473–518. https://doi.org/10.3745/JIPS.2011.7.3.473

[10]  Gev­ko, I. B. (2009). Met­hods of ma­king ma­na­ge­ri­al de­ci­si­ons: textbo­ok. Kyiv: Con­dor, 187 p.

[11]  Ghan­ba­ri, H., Var­tiainen, T., & Si­po­nen, M. (2019, March). Omis­si­on of Qua­lity Softwa­re De­ve­lop­ment Prac­ti­ces: A Syste­ma­tic Li­te­ra­tu­re Re­vi­ew. ACM Com­pu­ting Sur­veys, 51(2), 1–27. https://doi.org/10.1145/3177746

[12]  Gna­ti­en­ko, G., & Snytyuk, V. Ye. (2008). Ex­pert de­ci­si­on-ma­king techno­lo­gi­es: mo­nog­raph. Kyiv: McLa­ugh Li­mi­ted Li­abi­lity Com­pany, 444 p. [In Ukrainian].

[13]  Greshchak, M. G. (Ed.), Gre­beshko­va, O. M., & Kotsyu­ba, O. S. (2001). In­ter­nal eco­no­mic mec­ha­nism of the en­terpri­se: Tu­to­ri­al. Kyiv: KNEU Pub­lis­hing Hou­se, 228 p. [In Ukrainian].

[14]  Gül Çalıklı & Ayşe Başar Be­ner. (2013). Influ­en­ce of con­fir­ma­ti­on bi­ases of de­ve­lo­pers on softwa­re qua­lity: an em­pi­ri­cal study. Softwa­re Qua­lity Jo­ur­nal, 21(2), 377–416. https://doi.org/10.1007/s11219-012-9180-0

[15]  Hrytsi­uk, Yu. I. (2022). Compre­hen­si­ve softwa­re qua­lity as­sessment system. Sci­en­ti­fic Bul­le­tin of UN­FU, 32(2), 81–95. https://doi.org/10.36930/40320213

[16]  Hrytsi­uk, Yu. I., & Andrushcha­kevych, O. T. (2018). Me­ans for de­ter­mi­ning softwa­re qua­lity by met­ric analysis met­hods. Sci­en­ti­fic Bul­le­tin of UN­FU, 28(6), 159–171. https://doi.org/10.15421/40280631

[17]  Hrytsi­uk, Yu. I., & Buchkovska, A. Yu. (2018). Vis­ua­li­za­ti­on of the re­sults of ex­pert eval­ua­ti­on of softwa­re qua­lity using po­lar di­ag­rams. Sci­en­ti­fic Bul­le­tin of UN­FU, 27(10), 137–145. https://doi.org/10.15421/40271025

[18]  Hrytsi­uk, Yu. I., & Dal­yavskyy, V. S. (2018). Using Pe­tal Di­ag­ram for Vis­ua­li­zing the Re­sults of Ex­pert Eval­ua­ti­on of Softwa­re Qua­lity. Sci­en­ti­fic Bul­le­tin of UN­FU, 28(9), 97–106. https://doi.org/10.15421/411832

[19]  Hrytsi­uk, Yu. I., & Kuz­men­ko, I. S. (2013). Compre­hen­si­ve eval­ua­ti­on of in­for­ma­ti­on se­cu­rity imple­men­ta­ti­on pro­jects. Bul­le­tin of the Na­ti­onal Uni­ver­sity "Lviv Polytechnic". Se­ri­es: Au­to­ma­ti­on, me­asu­re­ment and control, 743, 118–122. [In Ukrainian].

[20]  Hrytsi­uk, Yu. I., & Ne­mo­va, E. A. (2018). Ma­na­ge­ment Fe­atu­res Pro­cess of De­ve­lo­ping Softwa­re Req­ui­re­ments. Sci­en­ti­fic Bul­le­tin of UN­FU, 28(8), 161–169. https://doi.org/10.15421/40280832

[21]  Hrytsi­uk, Yu. I., & Ne­mo­va, E. A. (2018). Pe­cu­li­ari­ti­es of For­mu­la­ti­on of Req­ui­re­ments to the Softwa­re. Sci­en­ti­fic Bul­le­tin of UN­FU, 28(7), 135–148. https://doi.org/10.15421/40280727

[22]  Hrytsi­uk, Yu. I., & Zhabych, M. R. (2018). Risk Ma­na­ge­ment of Imple­men­ta­ti­on of Prog­ram Pro­jects. Sci­en­ti­fic Bul­le­tin of UN­FU, 28(1), 150–162. https://doi.org/10.15421/40280130

[23]  Hrytsi­uk, Yu., Grytsyuk, P., Dyak, T., & Hrynyk, H. (2019). Softwa­re De­ve­lop­ment Risk Mo­de­ling. IEEE 2019 14th In­ter­na­ti­onal Sci­en­ti­fic and Techni­cal Con­fe­ren­ce on Com­pu­ter Sci­en­ces and In­for­ma­ti­on Techno­lo­gi­es (CSIT 2019), (Vol. 2, 134–137), 17–20 Sep­tem­ber, Lviv, Uk­ra­ine. Lviv: Lviv Polytechnic Na­ti­onal Uni­ver­sity, 206 p. https://doi.org/10.1109/stc-csit.2019.8929778

[24]  ISO 9001:2015 Qua­lity Ma­na­ge­ment System – Req­ui­re­ments. Ret­ri­eved from: https://www.iso.org/stan­dard/62085.html

[25]  ISO/IEC 25010. (2017). ISO/IEC 25000. Softwa­re and Da­ta Qua­lity. Ret­ri­eved from: https://iso25000.com/in­dex.php/en/ iso-25000-stan­dards/iso-25010?li­mit=3

[26]  ISO/IEC 9126. (1991). In­for­ma­ti­on techno­logy – Softwa­re pro­duct eval­ua­ti­on – Qua­lity cha­rac­te­ris­tics and gui­de­li­nes for the­ir use. Ge­ne­va: In­ter­na­ti­onal Or­ga­ni­za­ti­on for Stan­dar­di­za­ti­on, In­ter­na­ti­onal Electro­techni­cal Com­mis­si­on, 136 p. (In­ter­na­ti­onal Stan­dard)

[27]  ISO/IEC 9126-1:2001. (2022). Softwa­re En­gi­ne­ering – Pro­duct Qua­lity. Part 1: Qua­lity mo­del. Ret­ri­eved from: https://www.iso.org/stan­dard/22749.html

[28]  ISO/IEC CD 25010.2. (2022). Systems and softwa­re en­gi­ne­ering – Systems and softwa­re Qua­lity Req­ui­re­ments and Eval­ua­ti­on (SQua­RE) – Pro­duct qua­lity mo­del. Ret­ri­eved from: https://www.iso.org/ru/stan­dard/78176.html

[29]  ISO/IEC TR 9126-2:2003 Softwa­re En­gi­ne­ering – Pro­duct Qua­lity – Part 2: Ex­ter­nal met­rics. Ret­ri­eved from: https://www.iso.org/stan­dard/22750.html

[30]  ISO/IEC TR 9126-3:2003 Softwa­re En­gi­ne­ering – Pro­duct Qua­lity – Part 3: In­ter­nal met­rics. Ret­ri­eved from: https://www.iso.org/stan­dard/22891.html

[31]  ISO/IEC TR 9126-4:2004 Softwa­re En­gi­ne­ering – Pro­duct Qua­lity – Part 4: Qua­lity in use met­ric. Ret­ri­eved from: https://www.iso.org/stan­dard/39752.html

[32]  Kar­minska­ya-Be­lob­ro­va, M. V. (2012). Or­ga­ni­za­ti­onal struc­tu­res of en­terpri­se ma­na­ge­ment. Bu­si­nes­sIn­form, 12, 192–195. [In Ukrainian].

[33]  Kat­ren­ko, A. V., & Pa­sichnyk, V. V. (2009). De­ci­si­on the­ory: textbo­ok stam­ped by the Mi­nistry of Edu­ca­ti­on and Sci­en­ce. Kyiv: BHV Pub­lis­hing Gro­up, 448 p. Ret­ri­eved from: https://vlp. com.ua/no­de/7110. [In Ukrainian].

[34]  Kat­ren­ko, A. V., & Pa­sichnyk, V. V. (2020). De­ci­si­on ma­king: the­ory and prac­ti­ce: textbo­ok. Lviv: Pub­lis­hing hou­se "New World – 2000", 447 p. Ret­ri­eved from: https://ns2000.com.ua/wp-con­tent/up­lo­ads/2019/07/ Pryyni­at­tia_ris­hen-.pdf. [In Ukrainian].

[35]  Maz­za, R. (2009). Intro­duc­ti­on to In­for­ma­ti­on Vis­ua­li­za­ti­on, Uni­ver­sity of Lu­ga­no Swit­zer­land. Sprin­ger-Ver­lag Lon­don Li­mi­ted 2009. 139 p. https://doi.org/10.1007/978-1-84800-219-7

[36]  Na­ze­mi, K. (2014). Adap­ti­ve Se­man­tics Vis­ua­li­za­ti­on. Dis­ser­ta­ti­on zur Er­lan­gung des aka­de­mischen Gra­des eines Dok­tor-In­ge­ni­eurs. Eu­rog­rap­hics As­so­ci­ati­on for Com­pu­ter Grap­hics. 360 p. Ret­ri­eved from: https://dig­lib.eg.org/handle/ 10.2312/12076

[37]  Ples­kach, V. L., Za­to­natska, T. H. (2011). In­for­ma­ti­on systems and techno­lo­gi­es in en­terpri­ses. Kyiv: Znan­nia. 718 p. Ret­ri­eved from: https://pid­ruchni­ki.com/1194121347734/ in­for­ma­ti­ka/ana­liz_ya­kos­ti_prog­ram­no­go_za­bez­pec­hennya#42. [In Ukrainian].

[38]  Po­mo­ro­va, O. V., & Ho­vo­rushchen­ko, T. O. (2013a). Mo­dern prob­lems of softwa­re qua­lity as­sessment. Ra­dio electro­nic and com­pu­ter systems, 5, 319–327. Khar­kiv: NAU "KhAI". Ret­ri­eved from: https://elar.khnu.km.ua/jspui/handle/1234567 89/1497. [In Uk­ra­ini­an].

[39]  Po­mo­ro­va, O., & Ho­vo­rushchen­ko, T. (2013b). In­tel­li­gent As­sessment and Pre­dic­ti­on of Softwa­re Cha­rac­te­ris­tics at the De­sign Sta­ge. Ame­ri­can Jo­ur­nal of Softwa­re En­gi­ne­ering and Appli­ca­ti­ons (AJ­SEA), 2(2), 25–31. Ret­ri­eved from: https://ar­tic­le.sci­en­ce­pub­lis­hinggro­up.com/pdf/10.11648.j.aj­sea.20130202.11.pdf.

[40]  Po­no­ma­ren­ko, V. S., Pav­len­ko, L. A., Be­se­dovsky, O. M., et al. (2012). Met­hods and systems of de­ci­si­on sup­port in the ma­na­ge­ment of en­vi­ron­men­tal and eco­no­mic pro­ces­ses of en­terpri­ses: Tu­to­ri­al. Khar­kiv: Pub­lis­hing hou­se KhNEU, 272 p. [In Ukrainian].

[41]  Pryymak, V. M. (2008). Ma­na­ge­ment De­ci­si­on Ma­king: Tu­to­ri­al. Kyiv: At­ti­ca Pub­lis­hing Hou­se, 240 p. [In Ukrainian].

[42]  Step­hen R. Til­ler. (2012, Jan­uary). Or­ga­ni­za­ti­onal Struc­tu­re and Ma­na­ge­ment Systems. Le­adership and Ma­na­ge­ment in En­gi­ne­ering, 12(1), 20–23. https://doi.org/10.1061/(AS­CE)LM.1943-5630.0000160

[43]  Sytnyk, W. F. (2004). De­ci­si­on Sup­port Systems: Tu­to­ri­al. Kyiv: Pub­lis­hing hou­se KNEU, 614 p. [In Ukrainian].

[44]  Tho­mas L. Sa­aty. (1990, Sep­tem­ber). How to ma­ke a de­ci­si­on: The analytic hi­erarchy pro­cess. Eu­ro­pe­an Jo­ur­nal of Ope­ra­ti­onal Re­se­arch, 48(1), 9–26. https://doi.org/10.1016/0377-2217(90)90057-I

[45]  Vo­los­hin, O. F., & Mashchen­ko, S. O. (2010). Mo­dels and met­hods of de­ci­si­on ma­king: Tu­to­ri­al for stu­dents. Uni­ver­sity. 2nd ed., Re­vi­sed. and add. Kyiv: Kyiv Uni­ver­sity Pub­lis­hing and Prin­ting Cen­ter, 336 p. [In Ukrainian].

[46]  Volska­ya, K. O. (2019). The pro­ce­du­re of eval­ua­ting the qua­lity of ac­co­un­ting softwa­re. Prob­lems of The­ory and Met­ho­do­logy of Ac­co­un­ting. Control and Analysis, 2(43), 22–28. https://doi.org/10.26642/pbo-2019-2(43)-22-28

[47]  Vo­ro­nin, A. N., Zi­at­di­nov, Yu. K., & Ku­linsky, M. V. (2011). Mul­tic­ri­te­ria tasks: mo­dels and met­hods: mo­nog­raph. Kyiv: NAU Pub­lis­hing Hou­se. 348 p. [In Russian].