Integration of Heterogenous Software Architectures — An Experience Report

Gruhn, Volker; Wellen, Ursula

doi:10.1007/978-0-387-35563-4_25

Cited by 5 publications

(4 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…1,2 The integration is usually accomplished using a three-phase approach, which includes data integration, control integration, and interface integration. This is the approach that the STCL architecture committee selected, and it led to a more detailed set of integration requirements:…”

Section: The Requirementsmentioning

confidence: 99%

The STCL test tools architecture

Williams¹,

Sluiman²,

Pitcher³

et al. 2002

IBM Syst. J.

View full text Add to dashboard Cite

The Software Test Community Leaders (STCL) group is an IBM-wide initiative focused on improving software test and quality practices within the corporation. In 1999, we began working to develop an architecture to integrate both new and existing test tools into solutions for use in the testing organizations across IBM. This paper discusses the requirements for the architecture, as well as the issues associated with developing a solution architecture for a large base of tools that span a variety of platforms and domains. The architecture is being designed and developed to address three concerns for integrating testing tools: integration of the data across tools and repositories, integration of the control across tools, and integration to provide a single graphical user interface into the tool set. Because of the heterogeneous nature of the platforms and domains the architecture must support, extensibility is essential. We address each of these three integration concerns using an opensource framework that operates on a set of standardized but extensible entities.

show abstract

Section: The Requirementsmentioning

confidence: 99%

The STCL test tools architecture

Williams¹,

Sluiman²,

Pitcher³

et al. 2002

IBM Syst. J.

View full text Add to dashboard Cite

show abstract

“…Architecture properties form the basis for a software migration of telecommunication components (Gruhn & Wellen, 1999). Therefore, this published application study makes the values of architecture properties more explicit.…”

Section: A Software Migration In Telecommunicationsmentioning

confidence: 99%

The impact of component architectures on interoperability

Davis

Gamble

Payton

2002

Journal of Systems and Software

View full text Add to dashboard Cite

“…The context viewpoint: an overview of the system and the systems in its environment with which it communicates. This communication can take the form of file transfer, a shared database or 'call/return' (see [5]). In the analysis this view is used to assess which systems have to be adapted to implement a change scenario.…”

Section: Macro Architecture Levelmentioning

confidence: 99%

Viewpoints on Modifiability

Lassing

Rijsenbrij

Vliet

2001

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

Software architecture is generally regarded as an important tool to achieve systems of higher quality. It is claimed that the foundation for a system's quality is laid by the decisions made in the software architecture. A question that is occupying both researchers and practitioners is in which areas should decisions be made in the software architecture? We believe architectural view models play an important role in the answer to this question. View models consist of a coherent set of architectural views. These view models have both a prescriptive and a descriptive role in the development process. Their prescriptive role is that they call for a number of aspects to be considered when defining a software architecture and their descriptive role is that they provide a framework to document a software architecture. Currently, a number of view models exist, the most important of which are the 4+1 View Model of Kruchten and the four views by Soni et al. In our experience with modifiability analysis for business information systems we found that the views in current view models do not include all information required. In this paper we discuss the views we found useful for architecture level impact analysis of business information systems. They are illustrated using a case study we performed for the Dutch Tax and Customs Administration. We claim that when these views are required for architecture level impact analysis, the decisions they capture should also be considered during architecture development.

show abstract

Integration of Heterogenous Software Architectures — An Experience Report

Cited by 5 publications

References 8 publications

The STCL test tools architecture

The STCL test tools architecture

The impact of component architectures on interoperability

Viewpoints on Modifiability

Contact Info

Product

Resources

About