24-07-2012, 05:10 PM
Software Configuration Management
scm.pdf (Size: 698.44 KB / Downloads: 24)
Symptoms of poor CM
Bugs that have been corrected reappear
Previous releases of software cannot be rebuilt
Previous releases of software cannot be found
Files get lost
Files are “mysteriously” changed
The same or similar code exists multiple times
in different projects
Two developers accidentally change the same
file concurrently
Benefits of an appropriate CM
Systems are built “automatically” and faster
Reintroducing already corrected bugs is avoided
better reputation of company
Concurrent development is simplified
Appropriate CM is a prerequisite for distributed
development
What is SCM?
Software configuration management (SCM)
is responsible to establish and maintain the
integrity of the products of the software project
throughout the software life cycle.
This includes identifying configuration items,
controlling changes and recording and reporting
the change implementation status.
What is a Configuration?
A configuration
is the functional and physical characteristics of
hardware or software as set forth in technical
documentation or achieved in a product.
System Releases
Not just a set of executable programs
May also include
Configuration files
Data files needed for system operation
Installation program or shell script
Electronic and paper documentation
Packaging and associated publicity
Systems are now normally released on DVD,
CD-ROM or as downloadable installation files
from the web