Delegating configuration management responsibilities within the software development process
TL;DRAbstract
A software project produces a number of items during its execution, including various documents, programs, data, and test artifacts. Configuration management (CM) is the aspect of project management that is concerned with identifying distinct variants of these items, and systematically controlling how they change. Configuration management is often conceived and conducted as a process distinctly separate from and in service of software development. This separation is reflected in a division of work where software developers build software components while a configuration manager combines the components in various configurations. We relate our experiences within a project named MPTE where CM was coordinated and monitored by a configuration manager, but the responsibility for performing CM activities was shared among the software developers.
Chat with Paper
AI Agents for this Paper
A software project produces a number of items during its execution, including various documents, programs, data, and test artifacts. Configuration management (CM) is the aspect of project management that is concerned with identifying distinct variants of these items, and systematically controlling how they change. Configuration management is often conceived and conducted as a process distinctly separate from and in service of software development. This separation is reflected in a division of work where software developers build software components while a configuration manager combines the components in various configurations. We relate our experiences within a project named MPTE where CM was coordinated and monitored by a configuration manager, but the responsibility for performing CM activities was shared among the software developers.
Keywords
Chat
Click to start Chat