Software Deployment

14,000,000 Leading Edge Experts on the ideXlab platform

Scan Science and Technology

Contact Leading Edge Experts & Companies

Scan Science and Technology

Contact Leading Edge Experts & Companies

The Experts below are selected from a list of 68988 Experts worldwide ranked by ideXlab platform

Alexander L. Wolf - One of the best experts on this subject based on the ideXlab platform.

  • a cooperative approach to support Software Deployment using the Software dock
    International Conference on Software Engineering, 1999
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software Deployment is an evolving collection of interrelated processes such as release, install, adapt, reconfigure, update, activate, deactivate, remove, and retire. The connectivity of large networks, such as the Internet, is affecting how Software Deployment is performed. It is necessary to introduce new Software Deployment technologies that leverage this connectivity. The Software Dock framework creates a distributed, agent based Deployment framework to support the ongoing cooperation and negotiation among Software producers themselves and among Software producers and Software consumers. This Deployment framework is enabled by the use of a standardized Deployment schema for describing Software systems, called the Deployable Software Description (DSD) format. The Software Dock also employs agents to traverse between Software producers and consumers in order to perform Software Deployment activities by interpreting the descriptions of Software systems. The Software Dock infrastructure allows Software producers to offer their customers high level Deployment services that were previously not possible.

  • ICSE - A cooperative approach to support Software Deployment using the Software dock
    Proceedings of the 21st international conference on Software engineering - ICSE '99, 1999
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software Deployment is an evolving collection of interrelated processes such as release, install, adapt, reconfigure, update, activate, deactivate, remove, and retire. The connectivity of large networks, such as the Internet, is affecting how Software Deployment is performed. It is necessary to introduce new Software Deployment technologies that leverage this connectivity. The Software Dock framework creates a distributed, agent based Deployment framework to support the ongoing cooperation and negotiation among Software producers themselves and among Software producers and Software consumers. This Deployment framework is enabled by the use of a standardized Deployment schema for describing Software systems, called the Deployable Software Description (DSD) format. The Software Dock also employs agents to traverse between Software producers and consumers in order to perform Software Deployment activities by interpreting the descriptions of Software systems. The Software Dock infrastructure allows Software producers to offer their customers high level Deployment services that were previously not possible.

  • Agent-based Software configuration and Deployment
    1999
    Co-Authors: Richard S. Hall, Alexander L. Wolf
    Abstract:

    Software Deployment is an evolving collection of interrelated processes such as release, install, adapt, reconfigure, update, activate, deactivate, remove, and retire. The connectivity of large networks, such as the Internet, is affecting how Software Deployment is performed. It is necessary to introduce new Software Deployment technologies that leverage this connectivity. The Software Dock framework presented in this thesis creates a distributed, agent-based Deployment framework to support the ongoing cooperation and negotiation among Software producers themselves and among Software producers and Software consumers. This Deployment framework is enabled by the use of a standardized Deployment schema for describing Software systems, called the Deployable Software Description (DSD) format. The Software Dock also employs agents to traverse between Software producers and consumers in order to perform Software Deployment activities by interpreting the Deployment descriptions of the Software systems. The Software Dock infrastructure allows Software producers to offer to their customers high-level Deployment services that were previously not possible.

  • Investigating the Applicability of Architecture Description in Configuration Management and Software Deployment
    1998
    Co-Authors: Andre Van Der Hoek, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Abstract : The discipline of Software architecture has traditionally been concerned with high-level design. In particular, a variety of architecture description languages have been developed that are used to precisely capture a design. Additionally, analysis tools have been constructed that are used to verify particular properties of a design. However, today's trend towards the development of component-based Software seems to suggest a new use of Software architecture. Because an architecture captures components and the connections among them, it could potentially be used as an organizing abstraction for many of the activities in the Software life cycle. In this paper we present an initial investigation into the feasibility of such use. In particular, we closely examine the role system modeling plays in the fields of configuration management and Software Deployment, and relate this role to the system modeling capabilities of architecture description languages. The outcome of this investigation is twofold. First, we conclude that, for the specific cases of configuration management and Software Deployment, the use of Software architecture brings opportunities to significantly extend the provided functionality. Second, we present requirements for a number of extensions to typical architecture description languages that are needed to make our approach viable.

  • ICSM - Evaluating Software Deployment Languages and Schema
    1998
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software distribution is evolving from a physical media approach to one where it is practical and advantageous to leverage the connectivity of networks. Network distribution of Software systems provides timeliness and continuity of evolution not possible with physical media distribution methods. To support network-based Software distribution, companies and organizations such as Microsoft, Marimba, and the Desktop Management Task Force (DMTF) are strengthening their efforts to package Software systems in a way that is conducive to network distribution and management. The result of these efforts has led to the creation of Software description languages and schema such as the Open Software Description format created by Microsoft and Marimba and the Management Information Format created by DMTF. While these efforts are steps in the right direction, they do not address Deployment issues in a complete and systematic fashion. The contribution of this paper is to evaluate these leading Software description technologies.

Richard S. Hall - One of the best experts on this subject based on the ideXlab platform.

  • a cooperative approach to support Software Deployment using the Software dock
    International Conference on Software Engineering, 1999
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software Deployment is an evolving collection of interrelated processes such as release, install, adapt, reconfigure, update, activate, deactivate, remove, and retire. The connectivity of large networks, such as the Internet, is affecting how Software Deployment is performed. It is necessary to introduce new Software Deployment technologies that leverage this connectivity. The Software Dock framework creates a distributed, agent based Deployment framework to support the ongoing cooperation and negotiation among Software producers themselves and among Software producers and Software consumers. This Deployment framework is enabled by the use of a standardized Deployment schema for describing Software systems, called the Deployable Software Description (DSD) format. The Software Dock also employs agents to traverse between Software producers and consumers in order to perform Software Deployment activities by interpreting the descriptions of Software systems. The Software Dock infrastructure allows Software producers to offer their customers high level Deployment services that were previously not possible.

  • ICSE - A cooperative approach to support Software Deployment using the Software dock
    Proceedings of the 21st international conference on Software engineering - ICSE '99, 1999
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software Deployment is an evolving collection of interrelated processes such as release, install, adapt, reconfigure, update, activate, deactivate, remove, and retire. The connectivity of large networks, such as the Internet, is affecting how Software Deployment is performed. It is necessary to introduce new Software Deployment technologies that leverage this connectivity. The Software Dock framework creates a distributed, agent based Deployment framework to support the ongoing cooperation and negotiation among Software producers themselves and among Software producers and Software consumers. This Deployment framework is enabled by the use of a standardized Deployment schema for describing Software systems, called the Deployable Software Description (DSD) format. The Software Dock also employs agents to traverse between Software producers and consumers in order to perform Software Deployment activities by interpreting the descriptions of Software systems. The Software Dock infrastructure allows Software producers to offer their customers high level Deployment services that were previously not possible.

  • Agent-based Software configuration and Deployment
    1999
    Co-Authors: Richard S. Hall, Alexander L. Wolf
    Abstract:

    Software Deployment is an evolving collection of interrelated processes such as release, install, adapt, reconfigure, update, activate, deactivate, remove, and retire. The connectivity of large networks, such as the Internet, is affecting how Software Deployment is performed. It is necessary to introduce new Software Deployment technologies that leverage this connectivity. The Software Dock framework presented in this thesis creates a distributed, agent-based Deployment framework to support the ongoing cooperation and negotiation among Software producers themselves and among Software producers and Software consumers. This Deployment framework is enabled by the use of a standardized Deployment schema for describing Software systems, called the Deployable Software Description (DSD) format. The Software Dock also employs agents to traverse between Software producers and consumers in order to perform Software Deployment activities by interpreting the Deployment descriptions of the Software systems. The Software Dock infrastructure allows Software producers to offer to their customers high-level Deployment services that were previously not possible.

  • ICSM - Evaluating Software Deployment Languages and Schema
    1998
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software distribution is evolving from a physical media approach to one where it is practical and advantageous to leverage the connectivity of networks. Network distribution of Software systems provides timeliness and continuity of evolution not possible with physical media distribution methods. To support network-based Software distribution, companies and organizations such as Microsoft, Marimba, and the Desktop Management Task Force (DMTF) are strengthening their efforts to package Software systems in a way that is conducive to network distribution and management. The result of these efforts has led to the creation of Software description languages and schema such as the Open Software Description format created by Microsoft and Marimba and the Management Information Format created by DMTF. While these efforts are steps in the right direction, they do not address Deployment issues in a complete and systematic fashion. The contribution of this paper is to evaluate these leading Software description technologies.

  • Software Deployment Extending Configuration Management Support into the Field
    1998
    Co-Authors: Andre Van Der Hoek, Dennis Heimbigner, Richard S. Hall, Antonio Carzaniga, Alexander L. Wolf
    Abstract:

    Traditionally, configuration management has only addressed the needs of the Software development process. Once a Software system leaves the development environment and enters the field, however, there still is a signifi- cant role for configuration management. Activities such as release, installation, activation, update, adaptation, deactivation, and de-release constitute the "Deployment lifecycle"; these activities need careful coordination and planning in their own right. This article discusses the dimensions of Software Deployment, argues why current solutions are not sufficient, and presents two research systems that specifically address Software Deployment.

Dennis Heimbigner - One of the best experts on this subject based on the ideXlab platform.

  • a cooperative approach to support Software Deployment using the Software dock
    International Conference on Software Engineering, 1999
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software Deployment is an evolving collection of interrelated processes such as release, install, adapt, reconfigure, update, activate, deactivate, remove, and retire. The connectivity of large networks, such as the Internet, is affecting how Software Deployment is performed. It is necessary to introduce new Software Deployment technologies that leverage this connectivity. The Software Dock framework creates a distributed, agent based Deployment framework to support the ongoing cooperation and negotiation among Software producers themselves and among Software producers and Software consumers. This Deployment framework is enabled by the use of a standardized Deployment schema for describing Software systems, called the Deployable Software Description (DSD) format. The Software Dock also employs agents to traverse between Software producers and consumers in order to perform Software Deployment activities by interpreting the descriptions of Software systems. The Software Dock infrastructure allows Software producers to offer their customers high level Deployment services that were previously not possible.

  • ICSE - A cooperative approach to support Software Deployment using the Software dock
    Proceedings of the 21st international conference on Software engineering - ICSE '99, 1999
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software Deployment is an evolving collection of interrelated processes such as release, install, adapt, reconfigure, update, activate, deactivate, remove, and retire. The connectivity of large networks, such as the Internet, is affecting how Software Deployment is performed. It is necessary to introduce new Software Deployment technologies that leverage this connectivity. The Software Dock framework creates a distributed, agent based Deployment framework to support the ongoing cooperation and negotiation among Software producers themselves and among Software producers and Software consumers. This Deployment framework is enabled by the use of a standardized Deployment schema for describing Software systems, called the Deployable Software Description (DSD) format. The Software Dock also employs agents to traverse between Software producers and consumers in order to perform Software Deployment activities by interpreting the descriptions of Software systems. The Software Dock infrastructure allows Software producers to offer their customers high level Deployment services that were previously not possible.

  • Investigating the Applicability of Architecture Description in Configuration Management and Software Deployment
    1998
    Co-Authors: Andre Van Der Hoek, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Abstract : The discipline of Software architecture has traditionally been concerned with high-level design. In particular, a variety of architecture description languages have been developed that are used to precisely capture a design. Additionally, analysis tools have been constructed that are used to verify particular properties of a design. However, today's trend towards the development of component-based Software seems to suggest a new use of Software architecture. Because an architecture captures components and the connections among them, it could potentially be used as an organizing abstraction for many of the activities in the Software life cycle. In this paper we present an initial investigation into the feasibility of such use. In particular, we closely examine the role system modeling plays in the fields of configuration management and Software Deployment, and relate this role to the system modeling capabilities of architecture description languages. The outcome of this investigation is twofold. First, we conclude that, for the specific cases of configuration management and Software Deployment, the use of Software architecture brings opportunities to significantly extend the provided functionality. Second, we present requirements for a number of extensions to typical architecture description languages that are needed to make our approach viable.

  • ICSM - Evaluating Software Deployment Languages and Schema
    1998
    Co-Authors: Richard S. Hall, Dennis Heimbigner, Alexander L. Wolf
    Abstract:

    Software distribution is evolving from a physical media approach to one where it is practical and advantageous to leverage the connectivity of networks. Network distribution of Software systems provides timeliness and continuity of evolution not possible with physical media distribution methods. To support network-based Software distribution, companies and organizations such as Microsoft, Marimba, and the Desktop Management Task Force (DMTF) are strengthening their efforts to package Software systems in a way that is conducive to network distribution and management. The result of these efforts has led to the creation of Software description languages and schema such as the Open Software Description format created by Microsoft and Marimba and the Management Information Format created by DMTF. While these efforts are steps in the right direction, they do not address Deployment issues in a complete and systematic fashion. The contribution of this paper is to evaluate these leading Software description technologies.

  • Software Deployment Extending Configuration Management Support into the Field
    1998
    Co-Authors: Andre Van Der Hoek, Dennis Heimbigner, Richard S. Hall, Antonio Carzaniga, Alexander L. Wolf
    Abstract:

    Traditionally, configuration management has only addressed the needs of the Software development process. Once a Software system leaves the development environment and enters the field, however, there still is a signifi- cant role for configuration management. Activities such as release, installation, activation, update, adaptation, deactivation, and de-release constitute the "Deployment lifecycle"; these activities need careful coordination and planning in their own right. This article discusses the dimensions of Software Deployment, argues why current solutions are not sufficient, and presents two research systems that specifically address Software Deployment.

Herman Bruyninckx - One of the best experts on this subject based on the ideXlab platform.

  • A model-based approach to Software Deployment in robotics
    2013 IEEE RSJ International Conference on Intelligent Robots and Systems, 2013
    Co-Authors: Nico Hochgeschwender, Azamat Shakhirmardanov, Davide Brugali, Luca Gherardi, Gerhard K. Kraetzschmar, Herman Bruyninckx
    Abstract:

    Deploying a complex robot Software architecture on real robot systems and getting it to run reliably is a challenging task. We argue that Software Deployment decisions should be separated as much as possible from the core development of Software functionalities. This will make the developed Software more independent of a particular hardware architecture (and thus more reusable) and allow it to be deployed more flexibly on a wider variety of robot platforms. This paper presents a domain-specific language (DSL) which supports this idea and demonstrates how the DSL is used in a model-driven engineering-based development process. A practical example of applying the DSL to the development of an application for the KUKA youBot platform is given.

  • IROS - A model-based approach to Software Deployment in robotics
    2013 IEEE RSJ International Conference on Intelligent Robots and Systems, 2013
    Co-Authors: Nico Hochgeschwender, Azamat Shakhirmardanov, Davide Brugali, Luca Gherardi, Gerhard K. Kraetzschmar, Herman Bruyninckx
    Abstract:

    Deploying a complex robot Software architecture on real robot systems and getting it to run reliably is a challenging task. We argue that Software Deployment decisions should be separated as much as possible from the core development of Software functionalities. This will make the developed Software more independent of a particular hardware architecture (and thus more reusable) and allow it to be deployed more flexibly on a wider variety of robot platforms. This paper presents a domain-specific language (DSL) which supports this idea and demonstrates how the DSL is used in a model-driven engineering-based development process. A practical example of applying the DSL to the development of an application for the KUKA youBot platform is given.

Xiaozong Yang - One of the best experts on this subject based on the ideXlab platform.

  • SA based Software Deployment reliability estimation considering component dependence
    Journal of Electronics (China), 2011
    Co-Authors: Hongwei Liu, Xiaozong Yang, Decheng Zuo
    Abstract:

    Reliability is one of the most critical properties of Software system. System Deployment architecture is the allocation of system Software components on host nodes. Software Architecture (SA) based Software Deployment models help to analyze reliability of different Deployments. Though many approaches for architecture-based reliability estimation exist, little work has incorporated the influence of system Deployment and hardware resources into reliability estimation. There are many factors influencing system Deployment. By translating the multi-dimension factors into degree matrix of component dependence, we provide the definition of component dependence and propose a method of calculating system reliability of Deployments. Additionally, the parameters that influence the optimal Deployment may change during system execution. The existing Software Deployment architecture may be ill-suited for the given environment, and the system needs to be redeployed to improve reliability. An approximate algorithm, A*_D, to increase system reliability is presented. When the number of components and host nodes is relative large, experimental results show that this algorithm can obtain better Deployment than stochastic and greedy algorithms.

  • SA Based Software Deployment Reliability Estimation Considering Component Reliability of Exponential Distribution
    Journal of Software, 2011
    Co-Authors: Hongwei Liu, Xiaozong Yang, Decheng Zuo
    Abstract:

    Although many approaches for architecture- based reliability estimation exist, these approaches are typically limited to certain classes or exclusively concentrate on Software reliability, neglecting the influence of hardware resources, component reliability, component replica and Software Deployment. In this paper, a reliability estimation model based on Software architecture (SA) is presented. This model incorporates the influence of Software Deployment, component reliability and component replica. Component lifetimes can be modeled by exponential distribution. The approach of calculating system reliability considering component replica and component reliability is proposed. The influences of different Deployment architectures on component reliabilities and system reliability are investigated. The improvement of system reliability by reDeployment or component replica is discussed.

  • Reliability Analysis Of SA based Software Deployment with Consideration of System Deployment
    Intelligent Automation & Soft Computing, 2011
    Co-Authors: Hongwei Liu, Xiaozong Yang
    Abstract:

    Abstract Software architecture (SA) has been widely advocated as an effective abstraction for modeling, implementing, and evolving complex Software systems such as those in distributed, decentralized, heterogeneous and mobile environments. There are two important facets related to this domain: Software Deployment and reliability. SA based Software Deployment models help to analyze reliability of system Deployments. Though there exist many approaches for architecture-based reliability estimation, little work has been done in incorporating the influence of system Deployment and hardware resources. In this paper, a new approach of estimating system reliability at architectural level is proposed. The approach incorporates the influence of system Deployment and hardware resources. Additionally, there are many factors influencing system Deployment, such as possible restrictions on component location. In order to make fully use of these factors, the multi-dimension factors on system Deployment are translated int...

  • A Comprehensive Approach of SA Based Software Deployment Reliability Estimation in Neural Networks
    2010 First International Conference on Pervasive Computing Signal Processing and Applications, 2010
    Co-Authors: Hongwei Liu, Decheng Zuo, Xiaozong Yang
    Abstract:

    Software architecture (SA) has been widely advocated as an effective abstraction for modeling, implementing, and evolving complex Software systems such as those in distributed, decentralized, heterogeneous and pervasive environments. We intend to investigate two problems related to the domain of those environments: Software Deployment and reliability. Though many approaches for Architecture-based reliability research, little work has been done in incorporating Software Deployment into SA based reliability estimation. This paper presents a new comprehensive approach of reliability estimation considering Software Deployment in neural networks. Additionally, we explain Software component replica and different Software component Deployment architectures in neural networks.

  • SA based Software Deployment reliability estimation: Problem space, challenges and strategies
    2010 International Conference on Educational and Information Technology, 2010
    Co-Authors: Hongwei Liu, Decheng Zuo, Xiaozong Yang
    Abstract:

    Software architecture (SA) has been widely advocated as an effective abstraction for modeling, implementing, and evolving complex Software systems such as those in distributed, decentralized, heterogeneous, mobile, and pervasive environments. We intend to investigate two problems related to the domain of those environments: Software Deployment and reliability. Software Deployment is a post-production activity that is performed for or by the customer of a piece of Software. Though many approaches for Architecture-based reliability research, little work has been done in incorporating Software Deployment into architecture-based reliability estimation. Thus, this paper describes which information constitute SA based Software Deployment reliability model and how to obtain available information for the model. The system reliability estimation at an architectural level includes Software Deployment, architectural style and component replica.