A new research agenda for tool integration

Wicks, Michael; Dewar, Rick

doi:10.1016/j.jss.2007.03.089

Cited by 34 publications

(24 citation statements)

References 108 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As we mentioned above, there is an established research area on CASE tools [83,207]. Finally, the integration of OSS components is closely related to research on, for instance, ComponentBased Software Engineering (CBSE) [35,122,134,208] and software reuse [137,193].…”

Section: Related Research Fieldsmentioning

confidence: 99%

See 1 more Smart Citation

Adoption of open source software in software-intensive organizations – A systematic literature review

Hauge¹,

Ayala²,

Conradi³

2010

Information and Software Technology

193

113

View full text Add to dashboard Cite

Context: Open source software (OSS) is changing the way organizations develop, acquire, use, and commercialize software. Objective: This paper seeks to identify how organizations adopt OSS, classify the literature according to these ways of adopting OSS, and with a focus on software development evaluate the research on adoption of OSS in organizations. Method: Based on the systematic literature review method we reviewed publications from 24 journals and seven conference and workshop proceedings, published between 1998 and 2008. From a population of 24289 papers, we identified 112 papers which provide empirical evidence on how organizations actually adopt OSS. Results: We show that adopting OSS involves more than simply using OSS products. We moreover provide a classification framework consisting of six distinctly different ways in which organizations adopt OSS. This framework is used to illustrate some of the opportunities and challenges organizations meet when approaching OSS, to show that OSS can be adopted successfully in different ways, and to organize and review existing research. We find that this research does not sufficiently describe the context of the organizations studied. It is furthermore fragmented and fails to benefit fully from related research fields. Finally, we present directions for future research.

show abstract

Section: Related Research Fieldsmentioning

confidence: 99%

“…However, Wicks and Dewar propose a new agenda for research on tool integration, requesting a more business-oriented approach to future research [207]. The use and development of OSS CASE tools and research on such tools could easily fit into this new agenda.…”

Section: Topics For Future Researchmentioning

confidence: 99%

Adoption of open source software in software-intensive organizations – A systematic literature review

Hauge¹,

Ayala²,

Conradi³

2010

Information and Software Technology

193

113

View full text Add to dashboard Cite

show abstract

“…A change in these opens up the possibility to reiterate the earlier steps to identify new opportunities for better tool integration. We have not found any suggestion on a structured approach to this, which is not surprising as for instance the lack of research into economical implications of tool integration have been noted in [3].…”

Section: Reason About Non-functional Requirementsmentioning

confidence: 76%

“…As will be apparent later in this section these principles figure prominently in literature throughout the last two decades, which is, in itself, promising. What made us finally decide was that [1] is being mentioned in literature reviews summarizing the most salient papers [2] and used as a reference to compare with when trying to build new research agendas for tool integration [3].…”

Section: Diverging From Wassermanmentioning

confidence: 99%

Advanced Information Systems Engineering Workshops

Asplund

Biehl

El‐khoury

et al. 2011

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstr act. The typical development environment today consists of many specialized development tools, which are partially integrated, forming a complex tool landscape with partial integration. Traditional approaches for reasoning about tool integration are insufficient to measure the degree of integration and integration optimality in today's complex tool landscape. This paper presents a reference model that introduces dependencies between, and metrics for, integration aspects to overcome this problem. This model is used to conceive a method for reasoning about tool integration and identify improvements in an industrial case study. Based on this we are able to conclude that our reference model does not detract value from the principles that it is based on, instead it highlights improvements that were not well visible earlier. We conclude the paper by discussing open issues for our reference model, namely if it is suitable to use during the creation of new systems, if the used integration aspects can be subdivided further to support the analysis of secondary issues related to integration, difficulties related to the state dependency between the data and process aspects within the context of developing embedded systems and the analysis of non-functional requirements to support tool integration.

show abstract

“…The interoperability problem has been widely addressed in the literature (see [23,19] for existing surveys) but it is still far from being solved. For instance, the OMG has recently created the Architecture Ecosystem Special Interest Group to discuss this same problem.…”

Section: Problem Definitionmentioning

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

A new research agenda for tool integration

Cited by 34 publications

References 108 publications

Adoption of open source software in software-intensive organizations – A systematic literature review

Adoption of open source software in software-intensive organizations – A systematic literature review

Advanced Information Systems Engineering Workshops

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

Contact Info

Product

Resources

About