Software Configuration Management (CSE2552)

Software Configuration Management (CSE2552)

• Software Configuration Management (SCM) encompasses naming, labeling, and version control

1. Identification of Configuration Items

• Configuration item identification includes naming, labeling, and version control functions
• Naming and Labeling
  • Identification determines how product parts and built-from-parts baselines are identified
  • Each software configuration item requires unique labeling
  • The labeling scheme reflects product structure
  • Criteria for identifying and labeling software configuration items and tests/test data must be established
  • Support tools used to build baselines (compilers, linkers, assemblers, make files, etc.) should be included in identification criteria
  • Special attention needed for third-party or purchased software integration for copyright/royalty reasons, reusability from other products or prototypes
• Version Control
  • Enables parallel development through branching and merging
  • Parallel development is important to
    • Allow different projects to use the same source files simultaneously
    • Isolate work not yet ready for sharing
    • Isolate work that should never be shared (e.g., fixing a bug in an older release)
    • Enable development on a branch while a development track is frozen (e.g., during validation testing)
  • SCM tools require branching, file comparison, and merging functions

1.1 Naming and Labeling (continued)

• Diagram (Figure 8.3) shows a software parts list (SRS, SDDs, source code, library routines, executable code, etc.)
• Diagram (Figure 8.4) depicts a software exploded parts diagram
• Criteria for identifying and labeling support tools for building baselines are essential
• Ensuring ability to recreate exact information from tools after changes/updates/replacements is crucial
• Software that will be reused or is a prototype requires special attention

1.2 Version Control (continued)

• Branching is a SCM function where a configuration item (usually code) develops simultaneously on multiple branches. New versions are independently added to each branch.
• File comparison is the ability to compare files with the same name in different branches or baselines to identify differences.
• Merging processes the selective application of changes made to source files in branches or baselines to corresponding source files in the main branch.
• Diagrams (Figure 8.5) illustrate branching and merging processes

1.2 Version Control (continued) - Procedure

• Version control procedures facilitate controlled change management using a known baseline, requiring some level of review for changes to baselines
• Procedure impact (to cost, schedule, development, and manufacturing) must be assessed
• Approval from appropriate bodies (CCB, key managers, project team) may be needed
• Implementation of approved changes is necessary and all affected parties are notified after approval

1.3 Software Configuration Items

• Table lists examples of software configuration items (Product concept specification, Software project plans, Software requirements specification, Software design descriptions, Source code, Database descriptions, SCM procedures, Software release process, Software test documents, User documentation, Maintenance documentation) and their corresponding information