Component Deployment IFIP/ACM Working Conference, CD 2002, Berlin, Germany, June 20-21, 2002, Proceedings /

• Συγγραφή απο Οργανισμό/Αρχή: SpringerLink (Online service)
• Άλλοι συγγραφείς: Bishop, Judith (Επιμελητής έκδοσης, http://id.loc.gov/vocabulary/relators/edt)
• Μορφή: Ηλεκτρονική πηγή Ηλ. βιβλίο
• Γλώσσα: English
• Έκδοση: Berlin, Heidelberg : Springer Berlin Heidelberg : Imprint: Springer, 2002.
• Έκδοση: 1st ed. 2002.
• Σειρά: Lecture Notes in Computer Science, 2370
• Θέματα: Software engineering.; Architecture, Computer.; Computer logic.; Programming languages (Electronic computers).; Computer programming.; Software Engineering.; Computer System Implementation.; Software Engineering/Programming and Operating Systems.; Logics and Meanings of Programs.; Programming Languages, Compilers, Interpreters.; Programming Techniques.

 Deployment is the act of taking components and readying them for productive use. There may be steps following deployment, such as installation or m- agement related functions, but all decisions about how to con?gure and c- pose/assemble a component are made at the deployment stage. This is therefore the one opportunity in the software lifecycle to bridge the gap between what the component developer couldn't know about the deployment environment and what the environment's developer couldn't know about the open set of depl- able components. It is not surprising that deployment as a dedicated step gains importance when addressing issues of system-wide qualities, such as coping with constrained resources or preparing for component adaptation and system evolution. Yet, component deployment is still a discipline in its infancy: it became mainstream practice only in the mid 1990s. Much of the best practice impulse originated in products like Microsoft's Transaction Server and its approach to attribute-based programming and later products like Enterprise JavaBeans and now the Corba Component Model. All these address the speci?c needs of enterprise appli- tion servers. However, the potential of the deployment concept goes far beyond this. Deployment can and should touch e?ectively all truly component-based solutions. The proceedings of Component Deployment 2002 represent a good cro- section of the gamut of deployment issues. From customization to address - source constraints to recon?guration of deployed systems and from architecture to design to languages, the avid reader will ?nd some contribution. 

 An Environment for Building Customizable Software Components -- A Contract-Based Approach of Resource-Constrained Software Deployment -- Architecture-Level Support for Software Component Deployment in Resource Constrained Environments -- Evolution of Distributed Java Programs -- Reconfiguration in the Enterprise JavaBean Component Model -- A Component Framework for Dynamic Reconfiguration of Distributed Systems -- Software Deployment Using Mobile Agents -- Packaging Predictable Assembly -- Dynamic Replacement of Active Objects in the Gilgul Programming Language -- Beyond Generic Component Parameters -- CC4J - Code Coverage for Java A Load-Time Adaptation Success Story -- Scenario-Based Connector Optimization An XML Approach -- Adapting Components with Mismatching Behaviours -- A Component Model for Field Devices -- A Translation System for Enabling Flexible and Efficient Deployment of QoS-Aware Applications in Ubiquitous Environments -- An Infrastructure for CORBA Component Replication -- Architectures of Enterprise Systems: Modelling Transactional Contexts -- Software, Component, and Service Deployment in Computational Grids -- Model, Notation, and Tools for Verification of Protocol-Based Components Assembly.