Martin Blom

Martin Blom

Auto-generated profile, based on publicly available information

Martin Blom

Karlstad University

Research Focus & Metrics

Academic Career Length

24Years (2003-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications
8 March 2018 in Software Quality Journal
Verified
Journal Article
Open access
PDF file
JLJörg Lenhard
Jörg Lenhard
MBMartin Blom
Martin Blom
SHSebastian Herold
Sebastian Herold
Software architecture degradation is a phenomenon that frequently occurs during software evolution. Source code anomalies are one of the several aspects that potentially contribute to software architecture degradation. Many techniques for automating the detection of such anomalies are based on source code metrics. It is, however, unclear how accurate these techniques are in identifying the architecturally relevant anomalies in a system. The objective of this paper is to shed light on the extent to which source code metrics on their own can be used to characterize classes contributing to software architecture degradation. We performed a multi-case study on three open-source systems for each of which we gathered the intended architecture and data for 49 different source code metrics taken from seven different code quality tools. This data was analyzed to explore the links between architectural inconsistencies, as detected by applying reflexion modeling, and metric values indicating potential design problems at the implementation level. The results show that there does not seem to be a direct correlation between metrics and architectural inconsistencies. For many metrics, however, classes more problematic as indicated by their metric value seem significantly more likely to contribute to inconsistencies than less problematic classes. In particular, the fan-in, a classes’ public API, and method counts seem to be suitable indicators. The fan-in metric seems to be a particularly interesting indicator, as class size does not seem to have a confounding effect on this metric. This finding may be useful for focusing code restructuring efforts on architecturally relevant metrics in case the intended architecture is not explicitly specified and to further improve architecture recovery and consistency checking tool support.

1 May 2010 in Procedia Computer Science
Verified
Journal Article
Open access
MBMartin Blom
Martin Blom
This article discusses the question if Scrum and XP is well suited for development of Computational Science and Engineering (CSE) software. The reason for choosing Scrum and XP is based on two facts. Firstly, CSE developers are not used to formal processes for software development and Scrum and XP are informal in nature, hence easier to adopt. Secondly CSE projects are often once-off and aimed at producing scientific results rather than commercial software, so the overhead of a process or methodology needs to be kept at a minimum. Scrum and XP are focused on producing software, thus keeping everything else, i.e. the overhead to a minimum, a fact that benefits CSE development. In this article, the characteristics of Scrum and XP in particular and agile development in general are evaluated against the needs of CSE developers. The results show that almost all the key points in both methodologies are well suited for CSE development and that agile development in general is a good match with CSE

25 June 2003
Verified
Conference Paper
Open access
ENE.J. Nordby
E.J. Nordby
MBM. Blom
M. Blom
Anna BrunstromAnna Brunstrom
Anna Brunstrom
When designing a software module or system, a systems engineer must consider and differentiate between how the system responds to external and internal errors. External errors cannot be eliminated and must be tolerated by the system, while the number of internal errors should be min- imized and the faults they result in should be detected and removed. This paper presents a development strategy based on design contracts and a case study of an industrial project in which the strategy was successfully applied. The goal of the strategy is to minimize the number of internal errors during the development of a software system while accom- modating external errors. A distinction is made between weak and strong contracts. These two types of contracts are applicable to external and internal errors respectively. Ac- cording to the strategy, strong contracts should be applied initially to promote the correctness of the system. Before release, the contracts governing external interfaces should be weakened and error management of external errors en- abled. This transformation of a strong contract to a weak one is harmless to client modules.

28 July 2008 in Lecture Notes in Computer Science
Verified
Book Chapter
Closed access
PDF file
MBMartin Blom
Martin Blom
ENEivind J. Nordby
Eivind J. Nordby
ABAnna Brunstrom
Anna Brunstrom