Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Adry Ferwerda

dblp:177/5009 · DBLP profile ↗
← Back
1ranked-venue papers
0as first author
0since 2021 · last 2016
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Requirements engineering and software design · 61% Software maintenance and evolution · 39%

Topics — the 3 heaviest of 4, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › model-driven engineering
domain-specific modeling
0.212016
Impact of Introducing Domain-Specific Modelling in Software Maintenance: An Industrial Case Study · IEEE Trans. Software Eng. 2016
Requirements engineering and software design
model-driven engineering
0.212016
Impact of Introducing Domain-Specific Modelling in Software Maintenance: An Industrial Case Study · IEEE Trans. Software Eng. 2016
Software maintenance and evolution › software quality assurance
defect analysis
0.112016
Impact of Introducing Domain-Specific Modelling in Software Maintenance: An Industrial Case Study · IEEE Trans. Software Eng. 2016

Methods — techniques the papers use, named apart from their topics

statistical analysis · 0.2case study · 0.2
YearPublicationVenuePosition
2016 Impact of Introducing Domain-Specific Modelling in Software Maintenance: An Industrial Case Study
abstract
Domain-specific modelling (DSM) is a modern software development technology that aims at enhancing productivity. One of the claimed advantages of DSM is increased maintainability of software. However, current empirical evidence supporting this claim is lacking. In this paper, we contribute evidence from a case study conducted at a software development company. We study how the introduction of DSM affected the maintenance of a legacy system. We collected data about the maintenance phase of a system that was initially developed using manual programming, but which was gradually replaced by DSM development. We performed statistical analyses of the relation between the use of DSM and the time needed to resolve defects, the defect density, and the phase in which defects were detected. The results show that after introducing DSM the defect density is lower, that defects are found earlier, but resolving defects takes longer. Other observed benefits are that the number of developers and the number of person-hours needed for maintaining the system decreased, and the portability to new platforms increased. Our findings are useful for organizations that consider introducing DSM and would like to know which benefits can be realized in software maintenance.
Niklas Mellegård, Adry Ferwerda, Kenneth Lind, Rogardt Heldal, Michel R. V. Chaudron
IEEE Trans. Software Eng.2