Compatible Component Upgrades Through Smart Component Swapping

Stuckenholz, Alexander; Zwintzscher, Olaf

doi:10.1007/11786160_12

Cited by 4 publications

(2 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To respect component evolution and the requirements of different versions the version reachability graph was introduced in [22]. The version reachability graph is an extended dependency graph containing all available versions of the components together with their dependencies.…”

Section: Examplementioning

confidence: 99%

Safe component updates

Stuckenholz

Osterloh

2006

Proceedings of the 5th International Conference on Generative Programming and Component Engineering

Self Cite

View full text Add to dashboard Cite

Component updates always imply the risk of negatively influencing the operability of software systems. Because of wrong combinations of component versions, dependencies might break, methods which do no longer exist, might be called or methods might not be compatible to provided interfaces, objects, or classes. In this paper we model the problem of finding a well-configured system consisting of multiple component versions as a Boolean Optimization Problem. We introduce objective functions and constraints, which use Branch-and-Bound for restricting the search space and yield most recent, minimal systems.

show abstract

Section: Examplementioning

confidence: 99%

Safe component updates

Stuckenholz

Osterloh

2006

Proceedings of the 5th International Conference on Generative Programming and Component Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…We will address this problem, firstly, by devising a framework that automates most of the testing process, and secondly, reduces the number of test cases by adequately selecting and prioritizing them, therefore minimizing the cost of testing after each modification by testing only the altered parts of the SoS, and by finding the most defects with the lower number of tests. Moreover, a model-based approach could be used to detect incompatibilities between components without resorting to testing [2,10,13]. This makes the verification of a modification as little disruptive as possible for the running configuration and reduces the latency between the moment a reconfiguration is requested and the moment it is deployed.…”

Section: Integration and Reconfigurationmentioning

confidence: 99%