Sebastian Höhnel from Linnaeus University presented a new method for measuring and improving the quality of software processes in his computer science thesis. The method aims to understand how software is developed and the changes that occur over time. Digital data from the development process can be combined with expert analysis and data analytics to predict problems and make decisions about potential improvements.
One of the new tools developed by Sebastian Haenel is a metric called “source code density”. This metric shows the actual amount of code present in a software application relative to its total size. This helps determine whether the code is compact and efficient or messy and contains redundant code.
“Source code density is a valuable tool for identifying redundant code. We have also developed a robust classifier based on it to understand the nature of software changes. It uses a new method to use this and other development data to more easily identify complex problems in the development process,” says Sebastian Höhnel.
New expectations in software development
The research could change the way we think about software development. By focusing on the development process and using tools such as source code density, you can create better, more reliable and more efficient software.
Traditionally, software developers have focused on evaluating the quality of software. But Sebastian Haenel’s research shows that it is equally important to look at how the software is developed.
“To optimize software, we first need to improve the development process, fine-tune it and learn from past experiences. Previously, development efforts were measured by the amount of change, but there was no reliable method. We now propose to use data from the development process together with quantitative analysis to understand the extent of change,” says Sebastian Höhnel.
Identify problems by analyzing code
When managing several computer projects simultaneously, it is inevitable to encounter both successes and problems. There are times when everything goes perfectly, but there are also times when complications arise. This could be because the software doesn’t run fast enough, doesn’t have the features you need, is over budget, or the project wasn’t completed on time.
After completing a project, it’s natural to want to think about and understand the moments when things didn’t go as planned. The challenge may be determining whether problems arise from individual decisions or overall team dynamics.
“We have developed tools that can quickly scan your projects and identify where underlying problems may exist. They may not be able to give you all the details, but they will help you quickly determine which projects need more attention. We can find these problems just by looking at the application code. We believe that this tool can help identify many different types of problems,” says Sebastian Höhnel.
The study marks a step forward in the quest to understand and improve the quality of software. These new tools and techniques can simplify and streamline the work of developers, thus creating better and more reliable software. Source