Meta-component architecture for software interoperability

Sauer, Ly; Clay, Robert L.; Armstrong, Rob

doi:10.1109/swmt.2000.890423

Cited by 3 publications

(2 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The notion of Component Mill architecture [13] furnishes an infrastructure for component In so doing, the ultimate goal of the IDE as being truly interoperable is defeated.…”

Section: Proposed Approachmentioning

confidence: 99%

Complexity Measure of Software Composition Framework

Sophatsathit¹

2017

JSEA

View full text Add to dashboard Cite

This article proposes a pragmatic approach to software composition based on matching criteria by mimicking integrated hardware counterpart. The tangible value of consumer goods as described by Cox instills this logical derivation of the proposed approach. As software gradually matures in component form, various software compositions can be systematically assembled from related existing software. Two application software are composed based on their functionality matching. Their composition complexities are measured by function point. The total effort unveils a noteworthy finding that high complexity software demands larger effort to deploy. Thus, the proposed software composition framework not only offers the freedom of development mandates to the development team, but also broadens the horizon of cost and project evaluations by arriving at the proper mix of constituent components in the software product.

show abstract

“…The notion of Component Mill architecture [13] furnishes an infrastructure for component In so doing, the ultimate goal of the IDE as being truly interoperable is defeated.…”

Section: Proposed Approachmentioning

confidence: 99%

Complexity Measure of Software Composition Framework

Sophatsathit¹

2017

JSEA

View full text Add to dashboard Cite

show abstract

“…Guo [8] and Wileden & Kaplan [19] give good overviews of the technological solutions. Bao & Horowitz [4] and Saur et al [17] show two typical approaches to integrating largely incompatible products. Yakimovich et al [20] made a classification of the integration technologies and their compatibility, and applied it to typical COTS products.…”

Section: Research In the Areamentioning

confidence: 99%

COTS tenders and integration requirements

Lauesen¹

Proceedings. 12th IEEE International Requirements Engineering Conference, 2004.

View full text Add to dashboard Cite

When buying COTS-based software, the customer has to choose between what is available. The supplier may add some minor parts, but not everything the customer wants. This means that the customer cannot write down his requirements and expect that they can all be met. A scoring system is necessary rather than traditional mandatory requirements. Requirements for integrating the new COTS system with other systems are particularly hard because suppliers may integrate in different ways and with different other systems. A related problem is that once the new COTS system is purchased, the COTS supplier may have a de-facto monopoly. Only he can expand the system or integrate it with other systems. Experience shows that customers fail to deal with these issues adequately. As an example they may believe that asking for open interfaces is sufficient to guard them against monopoly. In this paper we analyze the problems and show ways to deal with them. We illustrate the problems and solutions with real-life examples from Electronic Patient Recording systems (EPR).

show abstract

COTS tenders and integration requirements

Lauesen

2005

Requirements Eng

View full text Add to dashboard Cite

Meta-component architecture for software interoperability

Abstract: Most existing software is one-of-a-kind, monolithic, non-interoperable, and consequently, non-reusable. In addition, this

Cited by 3 publications

References 2 publications

Complexity Measure of Software Composition Framework

Complexity Measure of Software Composition Framework

COTS tenders and integration requirements

COTS tenders and integration requirements

Contact Info

Product

Resources

About