Second International Workshop on Incorporating COTS Software Into Software Systems: Tools and Techniques (IWICSS '07) 2007
DOI: 10.1109/iwicss.2007.1
|View full text |Cite
|
Sign up to set email alerts
|

A Framework for Identification and Resolution of Interoperability Mismatches in COTS-Based Systems

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(4 citation statements)
references
References 12 publications
(13 reference statements)
0
4
0
Order By: Relevance
“…The authors in [90] propose an attribute-based framework for performing an automated assessment of the interoperability between at least two Commercial-Of-The-Shelf (COTS) products. In other words, it deals with the Compatibility assessment Non-Human Resources.…”
Section: Approach A8: a Framework For Identification And Resolution Omentioning
confidence: 99%
“…The authors in [90] propose an attribute-based framework for performing an automated assessment of the interoperability between at least two Commercial-Of-The-Shelf (COTS) products. In other words, it deals with the Compatibility assessment Non-Human Resources.…”
Section: Approach A8: a Framework For Identification And Resolution Omentioning
confidence: 99%
“…Each COTS product requires additional components and characteristics to function as desired in the system. These requirements are defined as COTS dependency attributes [36] and include such items as the need for a specific version of another COTS product or the definition of an environment variable in the system where the product is installed. Behavioral dependencies -the interaction between the two components that may only be certified for specific versions of the two products [14] -are included in COTS dependency attributes.…”
Section: Identifying Dependenciesmentioning
confidence: 99%
“…There have been numerous efforts in the categorization and formal definition of data mismatches. Cámara et al [5] defined the term "data mismatch" while in [3] Bhuta and Boehm defined "signature mismatch"; both mismatches highlight the differences that occur among two service components' interfaces with respect to the type and format of their input and output parameters. Similarly, Grenchanik et al [19] defined "message data model mismatch" to describe differences in the format of the messages to be interchanged among components.…”
Section: Background and Related Workmentioning
confidence: 99%