Reducing Code Complexity through Code Refactoring and Model-Based Rejuvenation

Mooij, Arjan J.; Ketema, Jeroen; Klusener, Steven; Schuts, Mathijs

doi:10.1109/saner48275.2020.9054823

Cited by 3 publications

(3 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Mooij et al use small iterative code refactoring steps before extracting models. 4 The rationale is that the intermediate refactoring steps increasingly reduce noise in the code, making model extraction easier. They also used the Eclipse CDT parser like we did in the current article.…”

Section: Related Workmentioning

confidence: 99%

“…Although a successful product family such as described above will live for a long time, its components may live shorter lives. Components may become obsolete (unused), or their maintainability has deteriorated over the years (accumulated technical debt) such that replacement or rejuvenation 3,4 is required, or a newer, better component has arrived which can replace the "legacy" component. From the perspective of the entire product family, replacing the old component with the new component is called a "refactoring."…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Large‐scale semi‐automated migration of legacy C/C++ test code

et al. 2022

View full text Add to dashboard Cite

This is an industrial experience report on a large semi-automated migration of legacy test code in C and C++. The particular migration was enabled by automating most of the maintenance steps. Without automation this particular large-scale migration would not have been conducted, due to the risks involved in manual maintenance (risk of introducing errors, risk of unexpected rework, and loss of productivity). We describe and evaluate the method of automation we used on this real-world case. The benefits were that by automating analysis, we could make sure that we understand all the relevant details for the envisioned maintenance, without having to manually read and check our theories. Furthermore, by automating transformations we could reiterate and improve over complex and large scale source code updates, until they were "just right."The drawbacks were that, first, we have had to learn new metaprogramming skills. Second, our automation scripts are not readily reusable for other contexts; they were necessarily developed for this ad-hoc maintenance task. Our analysis shows that automated software maintenance as compared to the (hypothetical) manual alternative method seems to be better both in terms of avoiding mistakes and avoiding rework because of such mistakes. It seems that necessary and beneficial source code maintenance need not to be avoided, if software engineers are enabled to create bespoke (and ad-hoc) analysis and transformation tools to support it.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Large‐scale semi‐automated migration of legacy C/C++ test code

et al. 2022

View full text Add to dashboard Cite

show abstract

“…Software legacy and rejuvenation: methods and tools to support the developers of industrial software in understanding their codebases and in (semi-)automatically improving them and reducing the accidental complexity. Legacy code can be scrutinized and rejuvenated using static analysis (Mooij 2020) and dynamic code analysis (Aslam 2020). The vision is to establish continuous computer-aided software maintenance, so code never gets old.…”

Section: Expertise Teams and Roadmapsmentioning

confidence: 99%

TNO‐ESI – Systems Engineering Methodologies for Managing Complexity in the High‐Tech Equipment Industry: Our Roadmap

Leibbrandt¹,

Wesselius²,

Beenker³

2022

INSIGHT

View full text Add to dashboard Cite

The high-tech equipment industry brings complex industrial products to the market with high speed, enhanced functionality, a better cost-performance ratio, and greater integration into customer workflows. Driven by digitalization, the complexity of these systems continues to grow steeply. To manage this complexity, continuous innovation in systems engineering methodologies is needed. TNO-ESI targets to 1) create impactful and industrially applicable systems engineering methodologies and 2) provide innovation support to the industry to get these applied in an industrial context. The ESI research program is defined through a roadmapping process that follows two tracks: a roadmap that maps industry needs and related research and development requirements and a roadmap that describes the developments in the expertise areas necessary for addressing these industry needs. In this paper, we describe the ESI mission, our way of working and activities, and explain the roadmapping process and the roadmaps.

show abstract