Selecting a Model Interchange Format: The SPOOL Case Study

Authors:
Guy St-Denis;Reinhard Schauer;Rudolf K. Keller
Affiliations:
-;-;-
Venue:
HICSS '00 Proceedings of the 33rd Hawaii International Conference on System Sciences-Volume 8 - Volume 8
Year:
2000

Citing 0
Cited 8

Pattern-based design recovery with SPOOL

Advances in software engineering
Datrix™ source code model and its interchange format: lessons learned and considerations for future work

ACM SIGSOFT Software Engineering Notes
Generic XMI-Based UML Model Transformations

OOIS '02 Proceedings of the 8th International Conference on Object-Oriented. Information Systems
Design and Implementation of a UML-Based Design Repository

CAiSE '01 Proceedings of the 13th International Conference on Advanced Information Systems Engineering
Dimensions of reengineering environment infrastructures

Journal of Software Maintenance: Research and Practice
Controversy Corner: A new research agenda for tool integration

Journal of Systems and Software
An exchange format for representing dynamic information generated from High Performance Computing applications

Future Generation Computer Systems
A metamodel for the compact but lossless exchange of execution traces

Software and Systems Modeling (SoSyM)

Quantified Score

Hi-index	0.00

Visualization

Abstract

The aim of this paper is to provide tool developers with effective strategies to minimize the risks, costs, effort and time involved in handling model interchange issues. Specifically, we establish a requirements list for model interchange formats and highlight the advantages and disadvantages of representative solutions RSF, TA, RDF, XIF and XMI. As a case study, we introduce SPOOL, our prototype environment for design recovery and composition, and discuss the particular project requirements that led us to envision an XMI-based model interchange engine. We then discuss implementation details and relate the lessons learned in pursuing the described path.