Automated Architecture Consistency Checking for Model Driven Software Development
2009 (English)In: ARCHITECTURES FOR ADAPTIVE SOFTWARE SYSTEMS, 2009, 36-51 p.Conference paper (Refereed)
When software projects evolve their actual implementation and their intended architecture may drift apart resulting in problems for further maintenance. As a countermeasure it is good software engineering practice to check the implementation against the architectural description for consistency. In this work we check software developed by a Model Driven Software Development (MDSD) process. This allows us to completely automate consistency checking by deducing information from implementation, design documents, and model transformations. We have applied our approach on a Java project and found several inconsistencies hinting at design problems. With our approach we can find inconsistencies early, keep the artifacts of an MDSD process consistent, and, thus, improve the maintainability and understandability of the software.
Place, publisher, year, edition, pages
2009. 36-51 p.
, Lecture Notes in Computer Science, ISSN 0302-9743 ; 5581
consistency, mdsd, transformation
IdentifiersURN: urn:nbn:se:kth:diva-49584DOI: 10.1007/978-3-642-02351-4\_3ISI: 000270318900003ScopusID: 2-s2.0-70350629533OAI: oai:DiVA.org:kth-49584DiVA: diva2:459846
5th International Conference on the Quality of Software Architectures. E Stroudsburg, PA. JUN 24-26, 2009
QC 201111302011-11-282011-11-282011-11-30Bibliographically approved