Using Architecturally Significant Requirements for Guiding System Evolution

Özkaya, Ipek; Diaz-Pace, Andres; Gurfinkel, Arie; Chaki, Sagar

doi:10.1109/csmr.2010.22

Cited by 10 publications

(4 citation statements)

References 17 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Vidal et al [12] propose an approach to prioritize critical code smells for refactoring, by taking into account aspects that can compromise the architecture of a system, as related modifiability scenarios [14], past component modification and the relevance of the smell for the developer. Macia et al [11] and Arcoverde et al [15] start addressing the problem that a code smell is important if it compromises the architecture of the system.…”

Section: Related Workmentioning

confidence: 99%

Towards Assessing Software Architecture Quality by Exploiting Code Smell Relations

Fontana¹,

Ferme²,

Zanoni³

2015

2015 IEEE/ACM 2nd International Workshop on Software Architecture and Metrics

View full text Add to dashboard Cite

We can evaluate software architecture quality using a plethora of metrics proposed in the literature, but interpreting and exploiting in the right way these metrics is not always a simple task. This is true for both fixing the right metric threshold values and determining the actions to be taken to improve the quality of the system. Instead of metrics, we can detect code or architectural anomalies that give us useful hints on the possible architecture degradation. In this paper, we focus our attention on the detection of code smells and in particular on their relations and co-occurrences, with the aim to evaluate tecnical debt in an architectural context. We start from the assumption that certain patterns of code anomalies tend to be better indicators of architectural degradation than simple metrics evaluation.

show abstract

Section: Related Workmentioning

confidence: 99%

Towards Assessing Software Architecture Quality by Exploiting Code Smell Relations

Fontana¹,

Ferme²,

Zanoni³

2015

2015 IEEE/ACM 2nd International Workshop on Software Architecture and Metrics

View full text Add to dashboard Cite

show abstract

“…This is for example the case in [11], where the authors explicitly discuss evolution scenarios. This is related to this work as the formal model we develop provides a foundation for such an approach.…”

Section: Decision Making On Technical Debtmentioning

confidence: 97%

A formal approach to technical debt decision making

Schmid

2013

Proceedings of the 9th International ACM Sigsoft Conference on Quality of Software Architectures

View full text Add to dashboard Cite

The notion of technical debt attracts significant attention, especially in the context of reconciling architecture and agile development. However, most work on technical debt is still largely informal and if it provides a formalization it is often ad-hoc. In this paper, we provide a detailed, formal analysis of decision making on technical debt in development.Using this formalization, we show that optimal decision making is not effectively computable in real-world situations and provide several well-defined approximations that allow to handle the problem nevertheless in practical situations. Combining these approximations in a single method leads to a light-weight approach that can be effectively applied in iterative software development, including agile approaches.

show abstract

“…BizCo is an online provider of information about travel destinations, designed to be an online one-stop travel agent. This application operates in an inherently distributed environment [35] . BizCo stands on a SOA, since it needs to ensure modifiability and availability, but without sacrificing performance.…”

Section: Case-study #3mentioning

confidence: 99%