Proceedings. 30th Euromicro Conference, 2004. 2004
DOI: 10.1109/eurmic.2004.1333356
|View full text |Cite
|
Sign up to set email alerts
|

Evaluation of component technologies with respect to industrial requirements

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
5

Citation Types

0
10
0

Year Published

2006
2006
2023
2023

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 15 publications
(10 citation statements)
references
References 9 publications
0
10
0
Order By: Relevance
“…or "what happens if I change this component?" [10] Components that share some common property are of particular interest in system analysis, e.g. "all highreliability components", "all components using over 1 MB of memory", "all components introduced in the system version 2.3", or "all components in the same thread" [15].…”
Section: Introductionmentioning
confidence: 99%
“…or "what happens if I change this component?" [10] Components that share some common property are of particular interest in system analysis, e.g. "all highreliability components", "all components using over 1 MB of memory", "all components introduced in the system version 2.3", or "all components in the same thread" [15].…”
Section: Introductionmentioning
confidence: 99%
“…or "what happens if I change this component?" [Möller et al 2004] Software elements that share a common property are of particular interest in system analysis, e.g. "all high-reliability components", "all components using over 1 MB of memory", "all components introduced in the system version 2.3", or "all components in the same thread" [Voinea and Telea 2004].…”
Section: Introductionmentioning
confidence: 99%
“…However, as the number of component models increases, a new challenge arises: how to discriminate among models that satisfy the same set of requirements such that the best suited one is selected as development base for a given system. Using the evaluation methodology proposed in [4], one can easily reach the conclusion that for example the Koala [6], and PECOS [9] component models offer similar benefits from the point of view of testability, resource utilization, and availability of a computational model. When these are the only important nonfunctional requirements for the component model, the selection of the best suited model can be further refined on two directions.…”
Section: Introductionmentioning
confidence: 99%
“…While it has proven to be successful in many application domains such as office and distributed internet-based applications, the component-based approach toward development is still to be validated in the area of dependable systems, which have special requirements on the quality attributes. Möller et al [4] have elaborated a set of such requirements, and classified a number of existing component models according to their conformance to the set. However, as the number of component models increases, a new challenge arises: how to discriminate among models that satisfy the same set of requirements such that the best suited one is selected as development base for a given system.…”
Section: Introductionmentioning
confidence: 99%