1998
DOI: 10.21236/ada452086
|View full text |Cite
|
Sign up to set email alerts
|

A Characterization Framework for Software Deployment Technologies

Abstract: Software applications are no longer stand-alone systems. They are increasingly the result of integrating heterogeneous collections of components, both executable and data, possibly dispersed over a computer network. Different components can be provided by different producers and they can be part of different systems at the same time. Moreover, components can change rapidly and independently, making it difficult to manage the whole system in a consistent way. Under these circumstances, a crucial step of the sof… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
74
0
3

Year Published

2004
2004
2008
2008

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 105 publications
(81 citation statements)
references
References 8 publications
(9 reference statements)
0
74
0
3
Order By: Relevance
“…Software deployment is defined in [2] as being a process composed of several phases as follows: release, installation, activation, deactivation, adaptation, update, uninstall and retire. Let classify the application deployment approaches using the following criteria, (i) the deployment target either distributed or local and (ii) the deployment constraints.…”
Section: State Of the Art: Software Deployment Systemsmentioning
confidence: 99%
“…Software deployment is defined in [2] as being a process composed of several phases as follows: release, installation, activation, deactivation, adaptation, update, uninstall and retire. Let classify the application deployment approaches using the following criteria, (i) the deployment target either distributed or local and (ii) the deployment constraints.…”
Section: State Of the Art: Software Deployment Systemsmentioning
confidence: 99%
“…Of these three component tools, only Nix focusses on variable features provided by different instantiations of components, and only Nix discusses the opportunities for a transparent configuration environment [10]. Software component developers often use their own specific deployment tools or custom build checks to see whether the system on which the component is deployed satisfies all requirements for consistent and correct deployment [11]. The developer therefore must develop its own models and formalisations to ensure a correct component deployment.…”
Section: Component Deployment Issuesmentioning
confidence: 99%
“…The goal is to find a valid deployment f such that the system's availability is maximized. 1 In the most general case, the number of possible deployments is k n . However, some of these deployments may be invalid (i.e., they may not satisfy the required constraints).…”
Section: Problem and Approachmentioning
confidence: 99%
“…Our approach, illustrated in Figure 2, employs runtime redeployment to increase a system's availability by (1) monitoring the system, (2) visualizing, estimating, and analyzing its redeployment architecture, and (3) effecting the selected redeployment architecture. We leverage an architectural middleware, Prism-MW, to support runtime system monitoring.…”
Section: Problem and Approachmentioning
confidence: 99%
See 1 more Smart Citation