CONFIGURATION
MANAGEMENT TOOLS
Abhishek Dangol
Niroj Maharjan
Pratik Maharjan
TABLE OF CONTENTS
• Introduction
• Characteristics
• Principle
• Process
• Strength and Weakness of techniques or tools
• Sample of documentation/diagrams
INTRODUCTION
• Also called version control tools although configuration
management is more than just a version control
• maintain a record of file version and changes form one
version to the next
• record all the versions of software and tools that are
required to produce a repeatable software build
CHARACTERISTICS
• Concurrency Management:
When two or more tasks are happening at same time it is
known as concurrent operation. If we talk concurrency in
context to SCM it means that the same file being edited by
multiple persons at the same time. If concurrency is not
managed properly with SCM tools then it may lead to very
severe problems.
CHARACTERISTICS
• Version Control
The second important feature provided by SCM tools
is version control. SCM tool uses archiving method or
saves every change made to file so that it is possible
for use to roll back to previous version in case of any
problems.
CHARACTERISTICS
• Synchronization
This is another feature provided by SCM tools where the user
is allowed to checkout more than one files or entire copy of
repository. The user then works on the required files and
checks in the changes back to repository, also they can update
there local copy of periodically to stay updated with the
changes made by other team members. This is known as
synchronization.
Besides these features SCM tools provide lot more
functionality like build management, auditing, reporting
system, defect tracking etc.
PRINCIPLES
The fundamental purpose of Configuration Management (CM)
is to establish and maintain the integrity and control of system
components and elements throughout a project's life cycle
• controls over the change and integrity of the components
of the system in their widest possible definition.
• provide means to identify, track, and control system
components from the inception of the concept for the
system until it is replaced or retired.
• It can then provide analysis of project control change
indicators such as requirements change per month, number
of errors, changed locations, upgrades.
PROCESS
• Planning and Management
This guides the design of the product, who has what
responsibilities, and includes which tools and procedures to
use. It identifies third-party requirements and the audit and
review process.
• Identification
Allows for setting baselines and identifying the configuration
of assets and/or software.
PROCESS
• Control
Maintain control of configurations, change requests, and
execution of changes to a system and its documentation.
Status Accounting
• The process of recording and reporting configuration item
descriptions and changes from the baseline over the item’s
life-cycle. If a problem arises, this allows for a quick
determination of the baseline configuration and changes
that have taken place over time.
STRENGTH AND WEAKNESS OF CASE
TOOLS:
Strength:
• Reduced redundant work.
• Effective management of simultaneous updates.
• Avoids configuration-related problems.
• Facilitates team coordination.
• Helps in building management; managing tools used in
builds.
• Defect tracking: It ensures that every defect has traceability
back to its source.
STRENGTH AND WEAKNESS OF CASE
TOOLS:
Weakness:
• tends to be more time consuming
• may not be feasible when either time and personnel are
limited
• may be inaccurate because the necessary information may
not be available in the early phase
• may overlook many of the system-level costs (integration,
configuration management, quality assurance, etc.)
associated with software development
SAMPLE OF DOCUMENTATION/
DIAGRAMS:
EXTRA
• ensures that the current design and build state of the
system is known, good & trusted
• help in accessing accurate historical record of system, which
is very useful for project management and audit purposes.
• it helps to identify what could possibly be causing a fault.
THE END
