The conceptual structure of existing software systems is often implicit or non-existing in the source code. We propose the lightweight abstraction of intentional source-code views as a means of making these conceptual structures more explicit. Based on the experience gained with two case studies, we illustrate how intentional source-code views can simplify and improve software understanding, maintenance and evolution in various ways. We present the results as a catalog of usage scenarios in a pattern-like format
Many program evolution tasks involve source code that is not modularized as a single unit. Furthermo...
Many maintenance tasks address concerns, or features, that are not well modularized in the source co...
As size and complexity of software systems increase, preserving the design and specification of thei...
Maintaining the source code of large software systems is hard. One underlying cause is that existing...
Software maintenance is the lifecycle activity that consumes the greatest amount of resources. Maint...
Understanding software artefacts is a crucial task for people who want to participate in any softwar...
In this study, we collected evidence from empirical studies published over two decades-from 1995 to ...
Maintaining and evolving large software systems is hard. One of the main underlying causes is that e...
peer-reviewedThis paper investigates the use and type of source code employed during program summar...
As size and complexity of software systems increase, preserving the design and specification of thei...
Comprehending source code is an essential activity for software developers. It is not only required ...
Abstract: In this paper we address the inevitable problem of aligning a software model with its resp...
Current software systems contain increasingly more elements that have not usually been considered in...
Rework occurs commonly in software development. This paper describes a simple rework example, namely...
As size and complexity of software systems increase, pre-serving the design and specification of the...
Many program evolution tasks involve source code that is not modularized as a single unit. Furthermo...
Many maintenance tasks address concerns, or features, that are not well modularized in the source co...
As size and complexity of software systems increase, preserving the design and specification of thei...
Maintaining the source code of large software systems is hard. One underlying cause is that existing...
Software maintenance is the lifecycle activity that consumes the greatest amount of resources. Maint...
Understanding software artefacts is a crucial task for people who want to participate in any softwar...
In this study, we collected evidence from empirical studies published over two decades-from 1995 to ...
Maintaining and evolving large software systems is hard. One of the main underlying causes is that e...
peer-reviewedThis paper investigates the use and type of source code employed during program summar...
As size and complexity of software systems increase, preserving the design and specification of thei...
Comprehending source code is an essential activity for software developers. It is not only required ...
Abstract: In this paper we address the inevitable problem of aligning a software model with its resp...
Current software systems contain increasingly more elements that have not usually been considered in...
Rework occurs commonly in software development. This paper describes a simple rework example, namely...
As size and complexity of software systems increase, pre-serving the design and specification of the...
Many program evolution tasks involve source code that is not modularized as a single unit. Furthermo...
Many maintenance tasks address concerns, or features, that are not well modularized in the source co...
As size and complexity of software systems increase, preserving the design and specification of thei...