By the same authors

Models from code or code as a model?

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Standard

Models from code or code as a model? / Garcia-Dominguez, Antonio; Kolovos, Dimitrios S.

Proceedings of the 16th International Workshop on OCL and Textual Modelling: CEUR Workshop Proceedings. Vol. 1756 2016. p. 137-148.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Harvard

Garcia-Dominguez, A & Kolovos, DS 2016, Models from code or code as a model? in Proceedings of the 16th International Workshop on OCL and Textual Modelling: CEUR Workshop Proceedings. vol. 1756, pp. 137-148.

APA

Garcia-Dominguez, A., & Kolovos, D. S. (2016). Models from code or code as a model? In Proceedings of the 16th International Workshop on OCL and Textual Modelling: CEUR Workshop Proceedings (Vol. 1756, pp. 137-148)

Vancouver

Garcia-Dominguez A, Kolovos DS. Models from code or code as a model? In Proceedings of the 16th International Workshop on OCL and Textual Modelling: CEUR Workshop Proceedings. Vol. 1756. 2016. p. 137-148

Author

Garcia-Dominguez, Antonio ; Kolovos, Dimitrios S. / Models from code or code as a model?. Proceedings of the 16th International Workshop on OCL and Textual Modelling: CEUR Workshop Proceedings. Vol. 1756 2016. pp. 137-148

Bibtex - Download

@inproceedings{fb65aed0d5864c47adb4f2892950d008,
title = "Models from code or code as a model?",
abstract = "Many model-driven engineering workflows take the existing code of a system as an input. Some of these include validation and verification, software modernisation or knowledge extraction. Current approaches take the code and produce a standalone model, instead of treating the code itself as a model and navigating through it on demand. For very large codebases this can be quite expensive to produce, and the resulting model can be too large to suit the simplest monolithic file-based stores. In this work we propose reusing a model that is already incrementally built for us and supports fast lookups: the internal indices maintained by our integrated development environments for code analysis and refactoring. In particular, we show an Epsilon driver that exposes the Eclipse JDT indices of one or more Java projects as a model, and compare its performance and usability against MoDisco for validating Java code with regards to a partial UML model.",
author = "Antonio Garcia-Dominguez and Kolovos, {Dimitrios S.}",
year = "2016",
month = "10",
day = "2",
language = "English",
volume = "1756",
pages = "137--148",
booktitle = "Proceedings of the 16th International Workshop on OCL and Textual Modelling",

}

RIS (suitable for import to EndNote) - Download

TY - GEN

T1 - Models from code or code as a model?

AU - Garcia-Dominguez, Antonio

AU - Kolovos, Dimitrios S.

PY - 2016/10/2

Y1 - 2016/10/2

N2 - Many model-driven engineering workflows take the existing code of a system as an input. Some of these include validation and verification, software modernisation or knowledge extraction. Current approaches take the code and produce a standalone model, instead of treating the code itself as a model and navigating through it on demand. For very large codebases this can be quite expensive to produce, and the resulting model can be too large to suit the simplest monolithic file-based stores. In this work we propose reusing a model that is already incrementally built for us and supports fast lookups: the internal indices maintained by our integrated development environments for code analysis and refactoring. In particular, we show an Epsilon driver that exposes the Eclipse JDT indices of one or more Java projects as a model, and compare its performance and usability against MoDisco for validating Java code with regards to a partial UML model.

AB - Many model-driven engineering workflows take the existing code of a system as an input. Some of these include validation and verification, software modernisation or knowledge extraction. Current approaches take the code and produce a standalone model, instead of treating the code itself as a model and navigating through it on demand. For very large codebases this can be quite expensive to produce, and the resulting model can be too large to suit the simplest monolithic file-based stores. In this work we propose reusing a model that is already incrementally built for us and supports fast lookups: the internal indices maintained by our integrated development environments for code analysis and refactoring. In particular, we show an Epsilon driver that exposes the Eclipse JDT indices of one or more Java projects as a model, and compare its performance and usability against MoDisco for validating Java code with regards to a partial UML model.

UR - http://www.scopus.com/inward/record.url?scp=85009344012&partnerID=8YFLogxK

M3 - Conference contribution

VL - 1756

SP - 137

EP - 148

BT - Proceedings of the 16th International Workshop on OCL and Textual Modelling

ER -