Software release management for component‐based software

@article{Hoek2003SoftwareRM,
  title={Software release management for component‐based software},
  author={Andr{\'e} van der Hoek and Alexander L. Wolf},
  journal={Software: Practice and Experience},
  year={2003},
  volume={33}
}
  • A. Hoek, A. Wolf
  • Published 1 January 2003
  • Engineering, Computer Science
  • Software: Practice and Experience
Software release management is the process through which software is made available to and obtained by its users. Until now, this process has been relatively straightforward. However, the emergence of component‐based software is complicating software release management. Increasingly, software is constructed via the assembly of pre‐existing, independently produced, and independently released components. Both developers and users of such software are affected by these complications. Developers… 
The Release Matrix for Component-Based Software
The challenge of managing the development and evolution of complex, component-based software is increasingly being recognized as the development of such systems becomes more common. This paper
The Release Matrix for Component-Based Software Systems
TLDR
A simple meta-model is used to illustrate the impact that architectural complexity and reusable components have on management patterns and provides a rationale for the Release Matrix, a generalization of a software release plan previously proposed as a technique for managing software product lines.
Package-Based Software Development
TLDR
Techniques that promote fine-grained software reuse across system, group, and institute boundaries, as well as integrated development of component compositions are proposed.
Software Configuration Management
  • T. Nguyen
  • Engineering, Computer Science
    Wiley Encyclopedia of Computer Science and Engineering
  • 2008
TLDR
The state of the art in both research and practice, as well as the well-established and advanced technologies in the area of SCM are summarized.
Component-Based Software Engineering
  • A. Kaur, K. Mann
  • Computer Science
    Lecture Notes in Computer Science
  • 2004
TLDR
The key difference between CBSE and traditional software engineering is that CBSE views a software system as a set of off-the-shelf components integrated within appropriate software architecture, which introduces fundamental changes in software development and maintenance.
Managing Dependencies Between Software Products
TLDR
A formal model of dependencies is developed, and it is shown how the model can be applied during the deployment process to verify the correct assembly of a system.
Continuous release and upgrade of component-based software
TLDR
It is shown how under certain assumptions, the release and delivery of software updates can be automated in the context of component-based systems and user feedback is more accurate, thus enabling quicker response to defects encountered in the field.
Component-based software version management based on a Component-Interface Dependency Matrix
TLDR
This paper separately version the components and interfaces based on a Component-Interface Dependency Matrix (CIDM), and analyze impacts according to their dependency relationship, showing that CIDM is capable of managing large numbers of components without impedance mismatch.
Customer requirements oriented component based software development life cycle model
TLDR
In this research, a system development life cycle model is proposed which has incorporated most importantly customer participation, customer support, customer feedback analysis and new component development phases by providing fully complete customer requirement oriented framework.
Software release management challenges in industry: An exploratory study
Release management has an essential role in the success of large software projects and there is no doubt that correct and efficient management of producing a new release can help the quality of the
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 58 REFERENCES
Software release management
Software release management begins with receipt of a release candidate comprising a software build for a particular target software release. It ends with the step of handing off that software build
Software release management
TLDR
The problems of software release management (SRM) are discussed and a prototype tool — the software release inventory manager (SRIM) — is outlined that addresses these problems.
Integrating Configuration Management and Software Deployment
TLDR
This position paper presents a set of requirements for an integrated system that intimately combines configuration management and software deployment functionality to support the evolution of component-based software in a unified manner.
A cooperative approach to support software deployment using the Software Dock
  • R. Hall, D. Heimbigner, A. Wolf
  • Computer Science
    Proceedings of the 1999 International Conference on Software Engineering (IEEE Cat. No.99CB37002)
  • 1999
TLDR
The Software Dock framework creates a distributed, agent based deployment framework to support the ongoing cooperation and negotiation among software producers themselves and amongSoftware producers and software consumers.
Source Tree Composition
TLDR
This paper's subject is to increase software reuse by decreasing coupling of source code components by automized assembly of software systems from reusable source code component and involves integration of source trees, build processes, and configuration processes.
Component software - beyond object-oriented programming
TLDR
Anyone responsible for developing software strategy, evaluating new technologies, buying or building software will find Clemens Szyperski's objective and market-aware perspective of this new area invaluable.
Version models for software configuration management
TLDR
This article provides an overview and classification of different versioning paradigms and defines and relates fundamental concepts such as revisions, variants, configurations, and changes and focuses on intensional versioning.
Software Configuration Management: ICSE SCM-4 and SCM-5 Workshops. Selected Papers
TLDR
An overview of the CAPITL software development environment and experiences with a script-based software configuration management system.
CVS II: Parallelizing Software Dev elopment
The program described in this paper fills a need in the UNIX community for a freely available tool to manage software revision and release control in a multi-developer, multi-directory, multi-group
An architecture for post-development configuration management in a wide-area network
TLDR
The Software Dock is described and the use of a prototype in deploying a complex system is discussed, designed as a system of loosely-coupled, cooperating, distributed components that are bound together by a wide-area messaging and event system.
...
1
2
3
4
5
...