Verification of Architectural Refactorings: Rule Extraction and Tool Support
With the recent success of the component-based and service-oriented paradigm, the complexity of software also increased. To tackle complexity, architectural models aid the developers. However, a software in constant use, must continually evolve, otherwise it becomes progressively less satisfactory . During the adaptation to changed requirements and improvement of internal structure, changes may be required to preserve the observable behaviour of the systems. In OO programming, such behaviour-preserving transformations are called refactorings .
KeywordsActivity Diagram Observable Behaviour Rule Extraction Communicate Sequential Process Eclipse Modeling Framework
Unable to display preview. Download preview PDF.
- 1.Lehman, M.M.: Laws of software evolution revisited. In: European Workshop on Software Process Technology, pp. 108–124 (1996)Google Scholar
- 2.Fowler, M., Beck, K., Brant, J., Opdyke, W., Roberts, D.: Refactoring: Improving the Design of Existing Code, 1st edn. Addison-Wesley Professional, Reading (1999)Google Scholar
- 5.Ehrig, H., Ehrig, K., Prange, U., Taentzer, G.: Fundamentals of Algebraic Graph Transformation (Monographs in Theoretical Computer Science). An EATCS Series. Springer, New York (2006)Google Scholar
- 6.Tiger Developer Team: Tiger EMF Transformer (2007), http://www.tfs.cs.tu-berlin.de/emftrans
- 7.Bisztray, D.: Verification of architectural refactoring rules. Technical Report CS-08-001, Department of Computer Science, University of Leicester (2008), http://www.cs.le.ac.uk/people/dab24/refactoring-techrep.pdf
- 8.Formal Systems Europe Ltd: FDR2 User Manual (2005), http://www.fsel.com/documentation/fdr2/html/index.html