Page 268 -
P. 268

CHAPTER 9  SOFTWARE CONFIGURATION MANAGEMENT                       239

                                The configuration audit is an SQA activity that helps to ensure that quality is main-
                              tained as changes are made. Status reporting provides information about each change
                              to those with a need to know.


                              REFERENCES
                              [BAB86] Babich, W.A., Software Configuration Management, Addison-Wesley, 1986.
                              [BAC98] Bach, J., “The Highs and Lows of Change Control,” Computer, vol. 31, no. 8,
                              August 1998, pp. 113–115.
                              [BER80]  Bersoff, E.H., V.D. Henderson, and S.G. Siegel, Software Configuration Man-
                              agement, Prentice-Hall, 1980.
                              [CHO89] Choi, S.C. and W. Scacchi, "Assuring the Correctness of a Configured Soft-
                              ware Description," Proc. 2nd Intl. Workshop on Software Configuration Management,
                              ACM, Princeton, NJ, October 1989, pp. 66–75.
                              [CLE89] Clemm, G.M., "Replacing Version Control with Job Control," Proc. 2nd Intl.
                              Workshop on Software Configuration Management, ACM, Princeton, NJ, October 1989,
                              pp. 162–169.
                              [GUS89] Gustavsson, A., "Maintaining the Evoluation of Software Objects in an Inte-
                              grated Environment," Proc. 2nd Intl. Workshop on Software Configuration Manage-
                              ment, ACM, Princeton, NJ, October 1989, pp. 114–117.
                              [HAR89] Harter, R., "Configuration Management," HP Professional, vol. 3, no. 6, June
                              1989.
                              [IEE94]  Software Engineering Standards, 1994 edition, IEEE Computer Society, 1994.
                              [LIE89]  Lie, A. et al., "Change Oriented Versioning in a Software Engineering Data-
                              base," Proc. 2nd Intl. Workshop on Software Configuration Management, ACM, Prince-
                              ton, NJ, October, 1989, pp. 56–65.
                              [NAR87] Narayanaswamy, K. and W. Scacchi, "Maintaining Configurations of Evolv-
                              ing Software Systems," IEEE Trans. Software Engineering, vol. SE-13, no. 3, March
                              1987, pp. 324–334.
                              [REI89]  Reichenberger, C., "Orthogonal Version Management," Proc. 2nd Intl. Work-
                              shop on Software Configuration Management, ACM, Princeton, NJ, October 1989, pp.
                              137–140.
                              [TAY85]   Taylor, B., "A Database Approach to Configuration Management for Large
                              Projects," Proc. Conf. Software Maintenance—1985, IEEE, November 1985, pp. 15–23.
                              [TIC82]   Tichy, W.F., "Design, Implementation and Evaluation of a Revision Control Sys-
                              tem," Proc. 6th Intl. Conf. Software Engineering, IEEE, Tokyo, September 1982, pp. 58–67.


                              PROBLEMS AND POINTS TO PONDER
                              9.1. Why is the First Law of System Engineering true? How does it affect our per-
                              ception of software engineering paradigms.
                              9.2. Discuss the reasons for baselines in your own words.
                              9.3. Assume that you're the manager of a small project. What baselines would you
                              define for the project and how would you control them?
   263   264   265   266   267   268   269   270   271   272   273