2015
DOI: 10.1007/978-3-319-26138-6_46
|View full text |Cite
|
Sign up to set email alerts
|

Semantic Matching of Components at Run-Time in Distributed Environments

Abstract: Abstract. Software factories are a key element in Component-Based Software Engineering due to the common space provided for software reuse through repositories of components. These repositories can be developed by third parties in order to be inspected and used by different organizations, and they can also be distributed in different locations. Therefore, there is a need for a trading service that manages all available components. In this paper, we describe a matching process based on syntactic and semantic in… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2016
2016
2018
2018

Publication Types

Select...
1
1

Relationship

2
0

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 14 publications
0
2
0
Order By: Relevance
“…This step requires three inputs: the set of alternative software architectures (generated by the default model transformation process), a set of metrics to measure QAs and constraints, and the specification of the components to feed the metrics at run-time (stored in the component and architecture models [37,2]). It is noteworthy to clarify that all the required information to calculate the set of metrics must be allocated in these models.…”
Section: Step 2: Measuring Qas and Constraints At Run-timementioning
confidence: 99%
“…This step requires three inputs: the set of alternative software architectures (generated by the default model transformation process), a set of metrics to measure QAs and constraints, and the specification of the components to feed the metrics at run-time (stored in the component and architecture models [37,2]). It is noteworthy to clarify that all the required information to calculate the set of metrics must be allocated in these models.…”
Section: Step 2: Measuring Qas and Constraints At Run-timementioning
confidence: 99%
“…The metrics presented here are focused on our particular domain of component-based systems, but they can be adapted according to the needs. This step requires three inputs: the set of alternative software architectures (generated by the default model transformation process), a set of metrics to measure QAs and constraints (see Table 1 for QAs and Table 2 for constraints), and the specification of the components to feed the metrics at run-time (stored in the metamodel [8,10]). It is important to emphasize that Tables 1 and 2 show metrics elicited and validated by an expert in the domain architecture of component-based systems, but they may be adapted to the needs of other domains.…”
Section: Step 2: Measuring Qas and Constraints At Run-timementioning
confidence: 99%