Demo Data from EDBT 2026 / reviewers in the wild / expert
Michael Mortensen
dblp:77/3550
· DBLP profile ↗
3ranked-venue papers
3as first author
0since 2021 · last 2012
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 3 · 3 first-author
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 |
Software maintenance and evolution · 91% Empirical software engineering · 9% |
Topics — the 4 heaviest of 4, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution › refactoring
aspect-oriented refactoring |
0.1 | 1 | 2012 | Aspect-Oriented Refactoring of Legacy Applications: An Evaluation · IEEE Trans. Software Eng. 2012 |
Software maintenance and evolution › software modularization
crosscutting concern modularization |
0.1 | 1 | 2012 | Aspect-Oriented Refactoring of Legacy Applications: An Evaluation · IEEE Trans. Software Eng. 2012 |
Software maintenance and evolution
refactoring |
0.1 | 1 | 2012 | Aspect-Oriented Refactoring of Legacy Applications: An Evaluation · IEEE Trans. Software Eng. 2012 |
Empirical software engineering › software engineering research methodology
industrial case study |
0.0 | 1 | 2012 | Aspect-Oriented Refactoring of Legacy Applications: An Evaluation · IEEE Trans. Software Eng. 2012 |
Methods — techniques the papers use, named apart from their topics
aspect-oriented programming · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2012 | Aspect-Oriented Refactoring of Legacy Applications: An EvaluationabstractThe primary claimed benefits of aspect-oriented programming (AOP) are that it improves the understandability and maintainability of software applications by modularizing crosscutting concerns. Before there is widespread adoption of AOP, developers need further evidence of the actual benefits as well as costs. Applying AOP techniques to refactor legacy applications is one way to evaluate costs and benefits. We replace crosscutting concerns with aspects in three industrial applications to examine the effects on qualities that affect the maintainability of the applications. We study several revisions of each application, identifying crosscutting concerns in the initial revision and also crosscutting concerns that are added in later revisions. Aspect-oriented refactoring reduced code size and improved both change locality and concern diffusion. Costs include the effort required for application refactoring and aspect creation, as well as a decrease in performance. Michael Mortensen, Sudipto Ghosh 0001, James M. Bieman |
IEEE Trans. Software Eng. | 1 |
| 2008 | A test driven approach for aspectualizing legacy software using mock systems
Michael Mortensen, Sudipto Ghosh 0001, James M. Bieman |
Inf. Softw. Technol. | 1 |
| 2006 | Testing During Refactoring: Adding Aspects to Legacy SystemsabstractMoving program code that implements cross-cutting concerns into aspects can improve the maintainability of legacy systems. This kind of refactoring, called aspectualization, can also introduce faults into a system. A test driven approach can identify these faults during the refactoring process so that they can be removed. We perform systematic testing as we aspectualize commercial VLSI CAD applications. The process of refactoring these applications revealed the kinds of faults that can arise during aspectualization, and helped us to develop techniques to reduce their occurrences Michael Mortensen, Sudipto Ghosh 0001, James M. Bieman |
ISSRE | 1 |