Integration of Existing Software Artifacts into a View- and Change-Driven Development Approach

Transcription

1 Integration of Existing Software Artifacts into a View- and Change-Driven Development Approach Sven Leonhardt, Johannes Hoor, Benjamin Hettwer, Michael Langhammer SOFTWARE DESIGN AND QUALITY GROUP INSTITUTE FOR PROGRAM STRUCTURES AND DATA ORGANIZATION, FACULTY OF INFORMATICS KIT University of the State of Baden-Wuerttemberg and National Research Center of the Helmholtz Association

2 Agenda Background and Goal Why is integration necessary? Integration strategies Applicability 2/

3 Background: Change-Driven Consistency Change-driven software development approach Model-driven framework Changes on models are recorded Change serves as a basis for the update of related models and their elements (Change Propagation) Semantic overlap expressed as correspondences Software system described by multiple models Related elements in different meta-models are set explicitly How to obtain changes from legacy models? 3/

4 Background: Change-Driven Consistency Based on [VITRUVIUS, Kramer et al., 2014] 4/

5 Why is Integration Necessary? Java Java Classes Class 1 Java Java Class 2 Interfaces Java Java Interface DTOs????????? [JaMoPP, Heidenreich et al., 2010] [Palladio Component Model, Becker et al., 2009] How can we use already existing models? Need to determine correspondences 5/

6 STRATEGIES Integration of models by a Reconstructive Integration Strategy 6/

7 Reconstructive Integration Strategy Abstracted process: 7/

8 Example: Syntactic Conflict PCM Java main component transforms to class main componentimpl { }... Solution: Detection of invalid elements (e.g. via OCL-Expressions) and changing them accordingly before executing any incremental transformation Here: Insertion of _ Conflict introduced by the metamodel 8/

9 Example: Semantic Conflict PCM Java <<interface>> IFileStore + store(e: Object) <<interface>> IMetaFiles + store(e: Object) class MediaStoreImpl implements IFileStore, IMetaFiles { <<provides>> MediaStore transforms to } void store(object e) { } Solution: Renaming the duplicate methods Conflict introduced by the mapping 9/

10 Integration by Model Traversal Traversal: Gradually adding elements to the system Traversal order depending on: Metamodel structure and metamodel invariants Structural Dependencies Can be added later Needs to be available for traversing a CollectionDataType 10/

11 Integration by Model Traversal Dependencies through invariants Constraint: ProvidedRolesMustBeBound [...] ensures that all outer provided roles of a system have a provided delegation connector that binds them to something. [PCM2011] 11/

12 Integration by Model Traversal Dependencies through Invariants 12/

13 STRATEGIES Integration of code by a Linking Integration Strategy 13/

14 Linking Integration Strategy Abstracted process: 14/

15 Correspondence Model Correspondences describe on instance level Mappings describe on meta level Mappings are given by the methodologist, e.g. Java Code Component Model 15/

16 Generating Correspondences Creating a mapping between classes and components is a typical use case in reverse engineering Reverse-/Forward-Engineering-Tool as basis Component Model Linking Information Java Code Strong correlation between linking information and needed mapping recommended 16/

17 Generating Correspondences What if not all necessary information can be gathered through RE? Gather information in RE input (e.g. code) and output (e.g. generated component model) Component Model Linking Information Correspondences Code Model Transformation 17/

18 Challenges Linking information usually do not conform to the defined mappings It needs to respect the structure the developer defined Workflow 18/

19 Applicability Use the reconstructive strategy, when: Injective mapping between In/Out-artifacts Compact meta model Detectable traversal strategy Small number of structural invariants Benefit Correspondence model independent of integration strategy and created by change-driven approach 19/

20 Applicability Use the Linking Strategy, when: Suitable reverse-/forward engineering tool available Tool provides trace/linking information Trace/linking information corresponds to the defined mapping Missing information gatherable in other artifacts More variability in the output artifact required Complex meta model (deep hierarchies, lots of cross references, etc.) 20/

21 Validation Reconstructive Integration Strategy Usage of medium sized architectural models ~200 elements per model Test if models remain the same after integration Linking Integration Strategy Usage of small Java projects ~10 classes Use the created correspondence model to test if changes are propagated correctly 21/

22 Related Work / Future Work Related Work Kramer et al. by providing the VITRUVIUS framework Lukman et al. on generating model traversal sequences Xiong et al. on model synchronization via bidirectional transformations Future Work Focus on larger code examples and optimization of integration steps Integration of complete software projects, that consist of a variety of different models and metamodels 22/

23 Conclusion Reconstructive Integration Strategy Suited for integration of models Linking Integration Strategy Relies on secondary tool Suited for integration of source code More research needed for integrating complete software projects 23/

24 Literatur [Kramer2014] M. E. Kramer et al. A View-Centric Approach to Automated Consistency Preservation in Software Engineering, 2014 [Jamopp2009] F. Heidenreich et al. Closing the Gap between Modelling and Java., In Proc. of 2nd International Conference on Software Language Engineering (SLE 09), LNCS. Springer, [Palladio2009] S. Becker, H. Koziolek, and R. Reussner, The Palladio component model for model-driven performance prediction, Journal of Systems and Software, vol. 82, pp. 3-22, [Xiong2007] Xiong, Yingfei and Liu, Dongxi and Hu, Zhenjiang and Zhao, Haiyan and Takeichi, Masato and Mei, Hong. Towards Automatic Model Synchronizationfrom Model Transformations, 2007 [Lukman2010] T. Lukman et al. Automatic Generation of Model Traversals from Metamodel Definitions. In: Proceedings of the 48th Annual Southeast Regional Conference. ACM SE 10. ACM, /