On the modeling and generation of service-oriented tool chains

Biehl, Matthias; El‐khoury, Jad; Loiret, Frédéric; Törngren, Martin

doi:10.1007/s10270-012-0275-7

Cited by 19 publications

(17 citation statements)

References 25 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The integration of web-based development tools and desktop tools (challenge 3) is not specifically addressed. Thus there are gaps in the state of the art addressing all challenges (1), (2) and (3). In Section III we describe two approaches, which focus on presentation integration (challenge 1) and the efficient engineering of tool chains (challenge 2).…”

Section: Related Workmentioning

confidence: 96%

“…Here we can only give a short overview of TIL, for an elaborated description of concrete graphical syntax, abstract syntax and semantics we refer to [2]. TIL has two basic types: Components and Channels, where Components are connected by Channels.…”

Section: A Til: Integration Of Desktop Toolsmentioning

confidence: 99%

“…The implementation of a tool chain can be partly synthesized from a TIL model, given that metamodels and model transformations are provided. As a consequence, the development of tool chains is faster and requires less resources [2].…”

Section: A Til: Integration Of Desktop Toolsmentioning

confidence: 99%

“…The Tool Integration Language (TIL) [2] is a backend solution for integrating desktop tools and CORSET [6] follows a frontend presentation integration approach leveraging the user interface of web-based development tools. The combination of TIL and CORSET allows us to efficiently develop a tool chain (2) that integrates desktop tools and web-based tools (3) through presentation integration (1).…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Efficient Construction of Presentation Integration for Web-Based and Desktop Development Tools

Biehl

Sosa

Törngren

et al. 2013

2013 IEEE 37th Annual Computer Software and Applications Conference Workshops

Self Cite

View full text Add to dashboard Cite

The engineering of software-intensive systems is supported by a variety of development tools. While development tools are traditionally desktop tools, they are more and more complemented and replaced by web-based development tools. The resulting blend of desktop and web-based tools is difficult to integrate into a seamless tool chain, which supports product development by data, control and presentation integration. Moreover, the construction of such tool chains is a significant engineering challenge. We propose an approach for the efficient, automated construction of tool chains, which integrate both web-based and desktop development tools; and provide a proof of concept of the approach in a case study. Our approach suggests that companies can selectively take advantage of hosted web-based development tools, while maintaining a seamless flow of integration with legacy desktop tools.

show abstract

Section: Related Workmentioning

confidence: 96%

Section: A Til: Integration Of Desktop Toolsmentioning

confidence: 99%

Section: A Til: Integration Of Desktop Toolsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Efficient Construction of Presentation Integration for Web-Based and Desktop Development Tools

Biehl

Sosa

Törngren

et al. 2013

2013 IEEE 37th Annual Computer Software and Applications Conference Workshops

Self Cite

View full text Add to dashboard Cite

show abstract

“…SENSORIA was neither focused on software evolution, nor was tool interoperability its central concern, though. The work by Biehl et al [12] is similar to SENSEI in several regards, e.g. it is based on services and their orchestration, and model-driven techniques to derive executable toolchains.…”

Section: Related Workmentioning

confidence: 99%

SENSEI: Software evolution service integration

Jelschen

2014

2014 Software Evolution Week - IEEE Conference on Software Maintenance, Reengineering, and Reverse Engineering (CSMR-WCRE)

View full text Add to dashboard Cite

Abstract-Software evolution tools mostly implement a single technique to assist in achieving a specific objective. Overhauling, renovating, or migrating large and complex legacy software systems require the proper combination of several different techniques appropriate for each subtask. Since few tools are built for interoperability, the setup of a toolchain supporting a given software evolution process is an elaborate, time-consuming, errorprone, and redundant endeavor, which yields brittle and inflexible toolchains with little to no reusability. This paper presents SENSEI, an approach to enable the implementation of an integration framework for software evolution tools using component-based, service-oriented, and model-driven methods, to ease toolchain creation and enable agile execution of software evolution projects. It will be evaluated by implementing and using it to build the toolchains supporting two software evolution projects, and having practitioners assess its usefulness.

show abstract

Using tool integration for improving traceability management testing processes: An automotive industrial experience

Amalfitano

Simone

Maietta

et al. 2019

J Software Evolu Process

View full text Add to dashboard Cite

Despite the high relevance of traceability in software processes, the activities of traceability creation and management are not always adequately supported in practice. The lack of integration between the tools adopted in the development processes is one of the main causes of such an ineffective management, where traceability relationships are still manually generated and maintained. In this paper we present an industrial experience we performed for improving the traceability management in a testing process performed in the Fiat Chrysler Automobiles company. In this context, we carried out a process for analyzing and identifying the main issues due to the ineffective traceability management and proposed a solution for addressing them.We designed and implemented a software architecture for integrating the existing application lifecycle management platform with the tools used in the process with the aim of automating the process execution and the traceability links management. The new architecture was validated by a case study that showed how the integration solution produced beneficial effects on quality attributes of the testing process. KEYWORDS automotive, industrial case study, software process improvement, tool integration, traceability management 1 INTRODUCTION Requirement traceability was defined by Gotel et al, 1 as the ability to describe and follow the life of a requirement, in both forward and backward directions.It is realized in practice by establishing relationships, usually defined trace links, between the requirements and one or more artifacts of the system. 2 Since then, this definition was extended, and nowadays, we talk more in general about software traceability for indicating the creation and the use of links (or connections) between different kinds of software artifacts such as requirements, models, source code, test cases, or test results. These connections are called trace links and connect in a bidirectional way a source artifact to a target artifact. The research community is devoting great efforts for addressing the topic of the traceability management that is the planning, the organization, and the coordination of all the activities related to traceability, including the creation, maintenance, and use of trace links. 3 Moreover, both software development standards and process assessment frameworks, such as ISO/IEC 15504, automotive SPICE, capability maturity model integration (CMMI), ISO 26262, and IEC 61508, suggest the companies to adopt traceability management solutions to guarantee Abbreviations: ALM, application lifecycle management; API, application programming interface; DSML, domain-specific modeling language; ECU, electronic control unit; FCA, Fiat Chrysler Automobiles; GUI, graphical user interface; ITL, incorrect traceability links; ITLRP, incorrect traceability links reduction percentage; MIL, model in the loop; MTL, missing traceability links; MTLRP, missing traceability links reduction percentage; RQ, research question; SP, speedup percentage; SPEM, software and system pr...

show abstract

On the modeling and generation of service-oriented tool chains

Cited by 19 publications

References 25 publications

Efficient Construction of Presentation Integration for Web-Based and Desktop Development Tools

Efficient Construction of Presentation Integration for Web-Based and Desktop Development Tools

SENSEI: Software evolution service integration

Using tool integration for improving traceability management testing processes: An automotive industrial experience

Contact Info

Product

Resources

About