Understanding Concerns in Software: Insights Gained from Two Case Studies

Revelle, Meghan; Broadbent, T.; Coppit, David

doi:10.1109/wpc.2005.43

Cited by 26 publications

(28 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Alternatively, an assignment to a container component automatically propagates to its contained components. (This is similar to the rules in [18].) CAG3.…”

Section: Concern Identification Guidelinessupporting

confidence: 84%

“…Previous assignment guidelines (for example, see [9] and [18]) attempt to establish a contribution relationship, i.e., a component contributes to the implementation of a concern. In our experience, contribution is hard to decide even when the assignor knows the program well, because it forces the assignor to consider any possible change to a component that could potentially affect the concern directly or indirectly.…”

Section: Concern Assignment Guidelinesmentioning

confidence: 99%

“…Alas, manually locating the source code related to a concern is a notoriously hard problem even when the concerns are well defined [2,15,18,22]. Unfortunately, concerns are rarely well defined, partly because the term -concern‖ is so abstract [20], leading to inconsistent interpretations [6,15,18].…”

Section: Introduction and Related Workmentioning

confidence: 99%

“…Unfortunately, concerns are rarely well defined, partly because the term -concern‖ is so abstract [20], leading to inconsistent interpretations [6,15,18]. Another level of inconsistency is introduced when concerns are assigned to code because existing guidelines [11,18] are ambiguous. These inconsistencies ensure that experimental results are not repeatable and lead to misguided assessments of the nature and extent of crosscutting in the program.…”

Section: Introduction and Related Workmentioning

confidence: 99%

See 3 more Smart Citations

Identifying, Assigning, and Quantifying Crosscutting Concerns

Eaddy

Aho

Murphy

2007

First International Workshop on Assessment of Contemporary Modularization Techniques (ACoM '07)

View full text Add to dashboard Cite

Crosscutting concerns degrade software quality. Before we can modularize the crosscutting concerns in our programs to increase software quality, we must first be able to find them. Unfortunately, accurately locating the code related to a concern is difficult, and without proper metrics, determining how much the concern is crosscutting is impossible. We propose a systematic methodology for identifying which code is related to which concern, and a suite of metrics for quantifying the amount of crosscutting code. Our concern identification and assignment guidelines resolve some of the ambiguity issues encountered by other researchers. We applied this approach to systematically identify all the requirement concerns in a 13,531 line program. We found that 95% of the concerns were crosscutting-indicating a significant potential for improving modularity-and that our metrics were better able to determine which concerns would benefit the most from reengineering.

show abstract

“…Alternatively, an assignment to a container component automatically propagates to its contained components. (This is similar to the rules in [18].) CAG3.…”

Section: Concern Identification Guidelinessupporting

confidence: 84%

Section: Concern Assignment Guidelinesmentioning

confidence: 99%

Section: Introduction and Related Workmentioning

confidence: 99%

Section: Introduction and Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Identifying, Assigning, and Quantifying Crosscutting Concerns

Eaddy

Aho

Murphy

2007

First International Workshop on Assessment of Contemporary Modularization Techniques (ACoM '07)

View full text Add to dashboard Cite

show abstract

“…Revelle et al [23] also studied concern overlapping. However, their study included only two concern sets (compared to our 7).…”

Section: Mental Model Overlappingmentioning

confidence: 99%

Sharing Developers' Mental Models through Source Code Annotations

Sulír

Nosal

2015

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-Context: Developers possess mental models containing information far beyond what is explicitly captured in the source code. Objectives: We investigate the possibility to use source code annotations to capture parts of the developers' mental models and later reuse them by other programmers during program comprehension and maintenance. Method: We performed two studies and a controlled experiment. Results: Developers' mental models overlap and thus can be shared. Possible use cases of shared annotations are hypotheses confirmation, feature location, obtaining new knowledge, finding relationships and maintenance notes. In the experiment, the presence of annotations reduced program comprehension and maintenance time by 34%. Conclusion: Annotations are a viable way to share programmers' thoughts.

show abstract

Mining static and dynamic crosscutting concerns: a role‐based approach

Bernardi

Cimitile

Lucca

2016

J Software Evolu Process

View full text Add to dashboard Cite

The implementation of crosscutting concerns in object-oriented (OO) systems entails scattering and tangling of code across several components increasing code duplication and making the system harder to comprehend, maintain, evolve and reuse. Therefore, identification of crosscutting concerns drives the reengineering or refactoring tasks in order to improve modularization of an existing system and increasing its overall internal quality. This paper proposes an approach to identify and analyse the components implementing the static and dynamic crosscutting in OO systems. The approach defines a meta-model representing the structure of an OO system in terms of its components. A static analysis of an OO software system is performed to create an instance of this meta-model. Such meta-model is finally analysed to find static and dynamic crosscutting among concerns. The effectiveness and efficiency of the proposed approach have been validated in an empirical assessment where it was applied to some OO java systems. The obtained results show a good level of effectiveness for the crosscutting analysis.

show abstract

Understanding Concerns in Software: Insights Gained from Two Case Studies

Cited by 26 publications

References 10 publications

Identifying, Assigning, and Quantifying Crosscutting Concerns

Identifying, Assigning, and Quantifying Crosscutting Concerns

Sharing Developers' Mental Models through Source Code Annotations

Mining static and dynamic crosscutting concerns: a role‐based approach

Contact Info

Product

Resources

About