What does aspect-oriented programming mean to Cobol?
Proceedings of the 4th international conference on Aspect-oriented software development
Toward an engineering discipline for grammarware
ACM Transactions on Software Engineering and Methodology (TOSEM)
An infrastructure to support interoperability in reverse engineering
Information and Software Technology
Controversy Corner: A new research agenda for tool integration
Journal of Systems and Software
Factbase Filtering Issues in an Ontology-Based Reverse Engineering Tool Integration System
Electronic Notes in Theoretical Computer Science (ENTCS)
Towards model driven tool interoperability: bridging eclipse and microsoft modeling tools
ECMFA'10 Proceedings of the 6th European conference on Modelling Foundations and Applications
| Hi-index | 0.00 |
Data interchange in the form of a standard exchange format (SEF) is only a first step towards tool interoperability. Inter-tool communication using files is slow and cumbersome; a better approach would be an application program interface, or API, that allowed tools to communicate with each other directly. This paper argues such an AP is a logical next step that builds on the current drive towards an SEF. It presents high-level descriptions of three approaches to tool-to-tool APIs and illustrates how requirements for the SEF also apply to the API.