SUP.8.BP1 Develop a configuration management strategy
(
)
Develop a configuration management strategy, including • responsibilities; • tools and repositories; • criteria for configuration items; • naming conventions; • access rights; • criteria for baselines; • merge and branch strategy; • the revision history approach for configuration items NOTE 1: The configuration management strategy typically supports the handling of product/software variants which may be caused by different sets of application parameters or by other causes. NOTE 2: The branch management strategy specifies in which cases branching is permissible, whether authorization is required, how branches are merged, and which activities are required to verify that all changes have been consistently integrated without damage to other changes or to the original software.