<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/"><rdf:Description rdf:about="https://dk.um.si/IzpisGradiva.php?id=83044"><dc:title>Evaluation and comparison of software quality within modern web applications</dc:title><dc:creator>Tomić,	Ilija	(Avtor)
	</dc:creator><dc:creator>Beranič,	Tina	(Mentor)
	</dc:creator><dc:subject>technical</dc:subject><dc:subject>debt</dc:subject><dc:subject>quality</dc:subject><dc:subject>comparison</dc:subject><dc:subject>SonarQube</dc:subject><dc:description>In this thesis, we developed two different full-stack applications using two different approaches. In the first approach, we were focused on the goal to create the application with zero technical debt taking as much time as needed. 
In the second approach, we took a different strategy for app development. The goal was to develop the second application in the shortest time possible to get to a product that is good enough for deployment in the real world. To achieve that, we were willing to take on technical debt, which meant that we would need to repay that debt later. We took some shortcuts, did not write tests, and ignored non-critical and minor bugs.
We were able to analyze both approaches, compare them, and decide which was the most effective approach. To analyze software quality, we used the code quality inspection platform SonarQube. 
If done correctly, the second approach gets results faster than the first. The best plan of action would be to take some shortcuts and start repaying created debt as soon as possible, for example, right after the delivery deadline.</dc:description><dc:publisher>[I. Tomić]</dc:publisher><dc:date>2022</dc:date><dc:date>2022-09-14 10:44:09</dc:date><dc:type>Magistrsko delo/naloga</dc:type><dc:identifier>83044</dc:identifier><dc:language>sl</dc:language></rdf:Description></rdf:RDF>
