SCM homepage Computer Science LTH

Software Configuration Management - Wednesday lecture:

Traditional SCM

Literature

  • Daniels, chapters 2, 3, 4 & 5.
    Read these four chapters. Make sure that you fully understand:
    • In chapter 2, pay special attention to the change process and be sure that you completely understand the role and working of the CCB.
    • In chapter 3, it is important that you understand how Daniels selects and structures CIs - you may want to compare that with Kelly's definitions from yesterday. Notice also his way of defining and using the concept "baseline".
    • the goals of status accounting
    • what reports can be generated from status accounting
    • why and how audits are conducted
  • Bohner and Arnold: An Introduction to Software Change Impact Analysis.
    Read this paper and make sure that you:
    • understand the concepts and principles of impact analysis
    • the place of impact analysis in the change process (and relation to CCB)
    • methods and techniques for handling impact analysis
  • Compton, chapter 3.
    Read this chapter to get a feel for the different roles and responsibilities connected with CM.
  • Leon, chapter 11.
    Read this chapter as background material for the exercises next week, where you have to produce parts of a CM-plan. Section 2.2 in Daniels also gave information about CM-plans.
  • Brad Appleton et al.:Streamed Lines - Branching Patterns for Parallel Software Development.
    Read the introduction part of this paper to get the context.
    • Read the following patterns so you are ready to discuss them at the lecture:
      • P5, P7, P8, C2, C3, C4, S2, S5 and S6.
    • Browse very quickly through the rest of the patterns.

Lecture summary:

  • configuration identification, control, status accounting and audit
  • configuration items and structures
  • the change process, impact analysis, traceability analysis
  • SCM plans and SCM roles

Quote of the day

CM-managers version of the beer song:
99 little bugs in the code,
99 little bugs in the code,
remove one bug - recompile and run
101 little bugs in the code....


Updated May 5, 2004