Sep 2026· Journal of Advanced Computational Intelligence and Intelligent Informatics· 0 citations· 33 references
Software Engineering Research
Abstract
In the software engineering field, the size of projects is used as explanatory variable for predicting the effort, duration, defects, costs, or risks of a project. Thus, the software project size has been considered the most influential factor. A systematic mapping study on the use of categorical data in software prediction concludes that the use of categorical data as explanatory variable in prediction models is an important issue because in the first phases of the software development process, the information is expressed in a categorical manner rather than numerical; however, at date, software size has mostly been used in its quantitative form rather than in its categorical representation. Because the software enhancement maintenance has the highest impact on business, our purpose is to classify software enhancement projects from their size by applying a new model termed simplified minimalist machine learning (S-MML) algorithm, which belongs to the minimalist machine learning (MML) paradigm. S-MML reduces five attributes commonly used for sizing a software project to only one. The performance of the S-MML is compared to those obtained from three classifiers. Seven public datasets of projects obtained from an international public repository of software projects were used to train and test the classifiers. Results showed that the S-MML had a better
f
-measure than the other three classifiers for all of the datasets at 95% confidence. We can conclude that the S-MML can be applied to classify the size of software enhancement projects.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.