Please use this identifier to cite or link to this item: http://buratest.brunel.ac.uk/handle/2438/7052
Full metadata record
DC FieldValueLanguage
dc.contributor.authorWermelinger, M-
dc.contributor.authorYu, Y-
dc.contributor.authorLozano, A-
dc.contributor.authorCapiluppi, A-
dc.date.accessioned2012-12-10T10:25:48Z-
dc.date.available2012-12-10T10:25:48Z-
dc.date.issued2011-
dc.identifier.citationEmpirical Software Engineering, 16(5): 623 - 666, Oct 2011en_US
dc.identifier.issn1382-3256-
dc.identifier.urihttp://link.springer.com/article/10.1007%2Fs10664-011-9164-xen
dc.identifier.urihttp://bura.brunel.ac.uk/handle/2438/7052-
dc.descriptionThis is the post-print version of the Article. The official published can be accessed from the link below - Copyright @ 2011 Springeren_US
dc.description.abstractThis paper proposes to use a historical perspective on generic laws, principles, and guidelines, like Lehman’s software evolution laws and Martin’s design principles, in order to achieve a multi-faceted process and structural assessment of a system’s architectural evolution. We present a simple structural model with associated historical metrics and visualizations that could form part of an architect’s dashboard. We perform such an assessment for the Eclipse SDK, as a case study of a large, complex, and long-lived system for which sustained effective architectural evolution is paramount. The twofold aim of checking generic principles on a well-know system is, on the one hand, to see whether there are certain lessons that could be learned for best practice of architectural evolution, and on the other hand to get more insights about the applicability of such principles. We find that while the Eclipse SDK does follow several of the laws and principles, there are some deviations, and we discuss areas of architectural improvement and limitations of the assessment approach.en_US
dc.language.isoenen_US
dc.publisherSpringeren_US
dc.subjectSoftware architectureen_US
dc.subjectSoftware evolutionen_US
dc.subjectDesign principlesen_US
dc.subjectStructured designen_US
dc.subjectMetricsen_US
dc.subjectEclipseen_US
dc.titleAssessing architectural evolution: A case studyen_US
dc.typeArticleen_US
dc.identifier.doihttp://dx.doi.org/10.1007/s10664-011-9164-x-
pubs.organisational-data/Brunel-
pubs.organisational-data/Brunel/Brunel Active Staff-
pubs.organisational-data/Brunel/Brunel Active Staff/School of Info. Systems, Comp & Maths-
pubs.organisational-data/Brunel/University Research Centres and Groups-
pubs.organisational-data/Brunel/University Research Centres and Groups/School of Information Systems, Computing and Mathematics - URCs and Groups-
pubs.organisational-data/Brunel/University Research Centres and Groups/School of Information Systems, Computing and Mathematics - URCs and Groups/Centre for Information and Knowledge Management-
Appears in Collections:Publications
Computer Science
Dept of Computer Science Research Papers

Files in This Item:
File Description SizeFormat 
Fulltext.pdf798.62 kBAdobe PDFView/Open


Items in BURA are protected by copyright, with all rights reserved, unless otherwise indicated.