Definitions of tool integration for environments

Thomas, Ian; Nejmeh, Brian A.

doi:10.1109/52.120599

Cited by 171 publications

(72 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In fact, one important barrier in current software engineering environments is the difficulty of integrating tools that address different aspects of the development process. As mentioned in [8], integration is not a property of a single tool, but of its relationships with other elements in the environment. The key notion is the relationships between tools but also the properties of these relationships.…”

Section: A Tool Integrationmentioning

confidence: 99%

Megamodel-based Management of Dynamic Tool Integration in Complex Software Systems

Toure

Fall

Bah

et al. 2016

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-The development of complex software systems is more and more based on the composition and integration of autonomous component systems. This can be done either statically (proactive approach) at development-time or dynamically through a reactive approach in which a new composite system can possibly be created on-demand and/or at run-time from existing systems. With the aim of constructing and managing such complex and reactive software systems, we propose a megamodelbased environment supporting dynamic tool integration. Such an environment must therefore be consistent at any time (i.e. before, during and after an integration) and should also have to exhibit some self-* properties (such self management, selfhealing and self-configuration). In order to meet these challenges we propose the use of Hoare's Axiomatic Semantics and some inference rules to maintain the integrity of the megamodel and its components. For that we have defined a formal-safe execution as well as an execution semantic for each operation likely to modify the megamodel contents.

show abstract

Section: A Tool Integrationmentioning

confidence: 99%

Megamodel-based Management of Dynamic Tool Integration in Complex Software Systems

Toure

Fall

Bah

et al. 2016

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

show abstract

“…Tools might differ on the data format, user-interface conventions, use of common functions, the process flow, etc [3]. Tool integration can be achieved on three different levels: the data source level, the business logic level, and the user interface (UI) level [4].…”

Section: Introductionmentioning

confidence: 99%

Web-Based Tool Integration: A Web Augmentation Approach

Díaz

Sosa

Arellano

et al. 2012

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Desktop tools are steadily being turned into web applications. Tool integration then becomes a question of website integration. This work uses Web Augmentation techniques for this purpose. An integration layer is deployed on top of the existing Web-based tools that augments the rendering of those tools for the integration experience. Layers are specified through a statechart-like DSL and transformed into JavaScript.

show abstract

“…Interoperability is the ability of two (or several) tools to exchange information and thus to use the exchanged information [11] [22]. Interoperability is required in several scenarios: forward engineering, reverse and round-trip engineering, tool and language evolution (to address backward compatibility with previous versions) and, for instance, collaborative development, where several subteams may work on separate views of the system using different tools (e.g., modeling tools) that must be later merged.…”

Section: Introductionmentioning

confidence: 99%

Towards Model Driven Tool Interoperability: Bridging Eclipse and Microsoft Modeling Tools

Brunelière

Cabot

Clasen

et al. 2010

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Successful application of model-driven engineering approaches requires interchanging a lot of relevant data among the tool ecosystem employed by an engineering team (e.g., requirements elicitation tools, several kinds of modeling tools, reverse engineering tools, development platforms and so on). Unfortunately, this is not a trivial task. Poor tool interoperability makes data interchange a challenge even among tools with a similar scope. This paper presents a model-based solution to overcome such interoperability issues. With our approach, the internal schema/s (i.e., metamodel/s) of each tool are explicited and used as basis for solving syntactic and semantic differences between the tools. Once the corresponding metamodels are aligned, model-to-model transformations are (semi)automatically derived and executed to perform the actual data interchange. We illustrate our approach by bridging the Eclipse and Microsoft (DSL Tools and SQL Server Modeling) modeling tools.

show abstract

Definitions of tool integration for environments

Cited by 171 publications

References 4 publications

Megamodel-based Management of Dynamic Tool Integration in Complex Software Systems

Megamodel-based Management of Dynamic Tool Integration in Complex Software Systems

Web-Based Tool Integration: A Web Augmentation Approach

Towards Model Driven Tool Interoperability: Bridging Eclipse and Microsoft Modeling Tools

Contact Info

Product

Resources

About