Configuration management refers to a discipline for evaluating, coordinating, approving or disapproving, and implementing changes in artifacts that are used to construct and maintain software systems.
According to the
Technopedia SCM helps in i
dentifying individual elements and configurations, tracking changes, and version selection, control, and baselining. One of the most widely used SCM is
Git, created by Linus Tovalds in 2005.
• Identify and store artifacts in a secure repository.
• Control and audit changes to artifacts.
• Organize versioned artifacts into versioned components.
• Organize versioned components and subsystems into versioned subsystems.
• Create baselines at project milestones.
• Record and track requests for change.
• Organize and integrate consistent sets of versions using activities.
• Maintain stable and consistent workspaces.
• Support concurrent changes to artifacts and components.
• Integrated early and often.
• Ensure reproducibility of software builds
Why is SCM important?
In Software Engineering is almost impossible to work alone. In this discipline, to make a good product, team work is necessary. In small teams it could be easy to track changes that co-workers make, but what about big organizations? When haven’t even met the people you’re working with. Well, that’s why we need SCM. In big projects, every person is working in something different that, at the end, will make great software. To accomplish goals, it’s important to manage the Development and Testing departments.