Integrate existing Software Configuration Management System

Integrate existing Software Configuration Management System

  1. Software Configuration Management StatusMost large outsourcing companies operate on projects, and SCM is also distributed across nodes in each project.

 

SCM node information is only known to the project personnel. Different SCM types: CVs, clearcase, VSS, and perforce. After the project is completed, the whereabouts of SCM are unknown. 2. Various proposals for Unified Software Configuration Management2.1 completely unified the use of an SCM system in the entire company or group, and assign the SCM and permissions to each project on the system. Advantages of this proposal: 1. A department, such as IT, manages and distributes data in a unified manner. 2. more complete permission control; 3. unified backup mechanism for more effective asset protection; 4. all employees in the company understand SCM information, which is more conducive to asset reuse. However, full unification has many drawbacks. 1. The customer specifies the SCM type. Project customers may specify the SCM type, which is difficult to unify. 2. A robust and large SCM system, such as clearcase, is required for unification. However, the popularization of clearcase takes a long time and cost. 3. The company requires additional personnel management and maintenance, and clearcase experts are required for training, resulting in high costs. 4. Any failure may affect the processes of all projects. 2.2 local unification reduces the scope of unification. Depending on the nature of the project, for example, projects that require the use of clearcase, projects that require the use of VSS, and projects that require the use of CVs, you can apply for different SCM systems for each project. SCM systems can be installed on different nodes. Set up an SCM management organization. administrators of each node are managed by this Organization. administrators can work part-time. However, the information of each node must be made public. Advantages of this proposal: 1. organized and centrally managed by SCM; 2. more complete permission control; 3. all employees in the company understand SCM information, which is more conducive to asset reuse; 4. no additional personnel cost required; 5. reduces the impact of SCM system faults. 6. the SCM type can be flexibly selected by the project team. However, local unification also has drawbacks. 1. failure of the SCM system will still affect the normal operation of some projects; 2. the workload of the SCM management organization cannot be estimated; for example, configuration of new projects, permission management, data backup, and hardware maintenance. 2.3 integrate existing SCM this proposal does not need to change the existing SCM, but includes all SCM nodes in a unified directory system. The SCM directory system is public and accessible to anyone. The SCM organization is still needed, but the organization no longer maintains the actual SCM. Their job is to include SCM Information in the SCM directory system. Advantages of this proposal: 1. no additional software and hardware fees; 2. all employees in the company understand SCM information. 3. the failure of SCM in a project does not affect other projects; 4. the SCM type can be flexibly selected by the project team; 5. reduce the workload of SCM organizations; 6. more in line with customer security requirements. The premise of this proposal is that each SCM node of the project can be accessed through the network in the enterprise. The proposal has the following problems: 1. after the project is completed, the process of the SCM node is unknown; 2. cost of directory system construction; 3. scattered SCM cannot be managed in a unified manner, causing data loss risks and abuse of permissions. 3. SummaryCompare the three proposals and the results are as follows:

	Completely unified	Local unification	Integrate current SCM
Unified management and distribution	√	√	X
Complete permission Control	√	√	X
Information Disclosure of SCM	√	√	√
Optional SCM type	X	√	√
Unified backup mechanism	√	√	X
Low management and maintenance costs	X	X	√
SCM system faults have low impact	X	X	√
No additional hardware and software costs	X	X	√
Valid asset storage	√	√	X

  4. SuggestionsFor outsourcing companies that focus on low-cost operations, we recommend that you use the "integrate existing SCM" solution to edit directories for existing SCM nodes and publish directories. In order to effectively save the assets managed by SCM, establishes a unified SCM backup mechanism within the company. project members regularly back up the data in the SCM to the unified backup node of the company. It is recommended that the independent SCM in the company be used to keep the resources of the terminated project.