About SCM
Global Transfer Process (GTP bv) can help you with all problems and questions concerning Software Configuration Management (SCM).
What is Software Configuration Management?
Software (or source) control is a method that allows control in a set of files in a repository and tracks revisions of those files. When changes are made to files in the repository, the method can identify conflicts from other changes and either automatically merge them or notify the conflict. This permits multiple developers to modify the same set of files. An SCM tool also provides accountability in tracking who made which changes. Finally, an SCM allows you to logically group files together into sets that are related, such as source files that make up a software image or executable.
The use of SCM tools has become more and more widespread. Understandable, when you realise that SCM tools provide high quality software.
How does SCM achieve this goal?
High quality through: Debugging
SCM tools characterise products as a collection of known inputs. This:
- helps to set control parameters when debugging.
- tells you, with certainty, which products are affected by a discovered bug.
High quality through: Documenting
Track and identify products by version numbers and release labels. Sometimes a bug is found in a source file of software that is already in production. With the help of release notes you will immediately know which executable is affected.
High quality through: Developers working together
Work on a set of files without concern for the work of other developers by maintaining multiple environments for reading and editing files. SCM synchronises all changes and prompts the user for manual intervention when conflicts arise.
Change is required
The most important change after implementing an SCM tool is in the mindset of those working with the tool. Engineers need to let go of old habits in developing files in their own directories. In order to wreak full benefits of an SCM tool, all developing should be done within the provided workspace. An important part of the implementation is therefore consists of support and sometimes organisational structure assistance.
Effective SCM consists of the following components
 |
Identification of input components |
|
|
Control over changes to the input components |
|
|
Record vital statistics about products |
|
|
Verify the product by audit and review. |
|
|
Build from input components |
|
|
Process management, the policy is designed and followed. |
|
|
Team work, managing interactions among multiple developers. |
How can we help?
|
|
Analysis of current situation, demands and wishes. |
|
|
Independent recommendation of products needed and/or organisational changes. |
|
|
Support of technical as well as organisational changes. |
|
|
When needed we provide courses on the new SCM tool, made to measure on your company’s situation. |
|
|
We continue to be available for your questions! |
Analysis
We can make an accurate analysis of your organisation, including all tools in use, employees, project teams, efficiencies and inefficiencies. We use the Configuration Management (CM) Model to build a framework of wishes and demands.
Configuration Management Model Please find more information on these divisions in our vocabulary.
Organisational changes based on legislation
With current legislative demands on corporate integrity, every company should know what goes on in their company since they are personally responsible. SCM is now a vital part of IT Governance.
Multiple tools have been developed to centralise information and make it traceable. Such as: ITIL, CMMI, ASL etc. Every organisation is unique and therefore need a tailor-made solution. Again, it is essential to provide a long-term solution and not a project based temporary one.
Most important is a centralised repository that connects different parts of the organisation, and thus provides centralised, traceable and accessible information.
ITIL model
The benefits of a centralised repository
In organisations now, most often the departments work with their own tools, files and processes. This however creates high inefficiency and chaotic processes.
When working with a centralised repository however development is more efficient, visible and controllable.
To conclude it is of the utmost importance to regard SCM as a continuing and dynamic process that develops in the same way your organisation does.
(C) 2005 - All rights reserved