Home > Research > Publications & Outputs > Detecting architecture instabilities with conce...
View graph of relations

Detecting architecture instabilities with concern traces: An exploratory study

Research output: Contribution in Book/Report/Proceedings - With ISBN/ISSNConference contribution/Paperpeer-review

Published
  • Eduardo Figueiredo
  • Ismenia Galvao
  • Safoora Shakil-Khan
  • Alessandro Garcia
  • Claudio Sant'Anna
  • Afonso Pimentel
  • Ana Luisa Medeiros
  • Lyrene Fernandes daSilva
  • Thais Vasconcelos Batista
  • Rita Almeida Ribeiro
  • Pim van denBroek
  • Mehmet Aksit
  • Steffen Zschaler
  • Ana Moreira
Close
Publication date2009
Host publicationJoint Working IEEE/IFIP Conference on Software Architecture, 2009 & European Conference on Software Architecture. WICSA/ECSA 2009.
PublisherIEEE
Pages261-264
Number of pages4
ISBN (print)978-1-4244-4984-2
<mark>Original language</mark>English
Event8th Joint Working IEEE/IFIP Conf. on Software Architecture and European Conf. on Software Architecture (WICSA/ECSA 2009) -
Duration: 1/01/1900 → …

Conference

Conference8th Joint Working IEEE/IFIP Conf. on Software Architecture and European Conf. on Software Architecture (WICSA/ECSA 2009)
Period1/01/00 → …

Conference

Conference8th Joint Working IEEE/IFIP Conf. on Software Architecture and European Conf. on Software Architecture (WICSA/ECSA 2009)
Period1/01/00 → …

Abstract

Sustaining architecture stability in incremental software development is an important aim for software engineers. Traceability mechanisms can be used to assess and predict architecture stability based on recorded information of early software artefacts. However, there is little empirical knowledge on whether traceability of stakeholders' concerns can assist the identification of architecture instabilities. This paper reports on a first exploratory study that analyses the effectiveness of concern traces for architecture stability assessment. We investigate to what extent properties of concern traces, such as their shapes, are correlated with architectural instabilities. Our analysis is based on eight releases implementing two versions of a software product line for handling mobile media.