TFL Vsebine / Revija SIR*IUS

Evaluating the quality of information solutions with the concept of technical debt

Metrike programske opreme nam ponujajo možnost, da neki projekt ocenimo glede na kakovost njegove izdelave, tj. ocenimo kakovost njegove programske kode. Da bi neko programsko rešitev lahko ocenili, moramo določiti in pregledati njene metrike, ki nam prikažejo številčne podatke o stanju programske kode, njeno zanesljivost, dokumentiranost, podvrženost napakam ipd. S pomočjo metrik programske opreme je možno oceniti, ali se neka programska rešitev drži predpisanih standardov, ki jih izbrana metrika ponazarja oz. meri. Metrike programske opreme nam omogočajo tudi izračun t. i. tehničnega dolga, ki nam s svojo vrednostjo pove, koliko ur programerskega dela bi bilo potrebno za njegovo odpravo. Spremljanje tehničnega dolga med samim razvojem projekta pa omogoča nadzor nad kakovostjo izvorne programske kode skozi njen razvoj, s tem pa pripomore tudi k zmanjšanju stroškov.

Software metrics offer us the possibility to evaluate a software project on the basis of its design quality, which means to assess the quality of its program code. To evaluate a software solution, we must determine and review its metrics. Metrics gives us numerical data on the state of the software code, its reliability, the state of its documentation, and error proneness. Software metrics information makes it possible to evaluate whether a software solution follows the standards indicated or measured by the selected metrics. The use of software metrics also allows us to calculate the technical debt, whose value tells us how many hours of software design a software engineer would need to fix the produced debt. Monitoring the technical debt during the development of a software project allows us to control the quality of the source code and contributes to reducing the costs.