2009 · 13 citations · 9 references
Software MaintenanceEngineeringArchitectural InstabilitiesArchitectural EngineeringVerificationSoftware EngineeringArchitecture InstabilitiesArchitecture SpecificationSoftware AnalysisFormal VerificationSoftware ArchitectureSocial SciencesReliability EngineeringSystems EngineeringReliabilitySoftware Architecture ModelingDesignComputer ScienceSoftware DesignArchitectural DesignArchitecture StabilityArchitecture AnalysisProgram AnalysisSoftware TestingSoftware Architecture RecoverySystem Software
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.
9
An analysis of the requirements traceability problem
O. Gotel, Clive Finkelstein · 2002 · 1.2K citations
Evolving software product lines with aspects
Eduardo Figueiredo, Nélio Cacho · 2008 · 335 citations
Software Maintenance, Engineering, Cross-cutting Concern +18
Do Crosscutting Concerns Cause Defects?
Marc Eaddy, Thomas Zimmermann, Kaitlin Duck Sherwood et al. · IEEE Transactions on Software Engineering · 2008 · 235 citations