1 / 28

Software Configuration Management (SCM)

Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner ’ s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi, C. et al., Fundamentals of Software Engineering 2 nd . Ed. New Jersery: Prentice Hall, 2003;

gwyneth-young
Download Presentation

Software Configuration Management (SCM)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Configuration Management (SCM) Source: Pressman, R., Software Engineering: A Practitioner’s Approach. Boston: McGraw Hill, Inc., 2005; Ghezzi, C. et al., Fundamentals of Software Engineering 2nd. Ed. New Jersery: Prentice Hall, 2003; Bersoff, H. E., Elements of Software Configuration Management. IEEE Transactions on Software Engineering, Vol. SE-10, No. 1, Jan 1984

  2. First Law of System Engineering • No matter where you are in the system life cycle, the system will change, and the desire to change it will persist throughout the lifecycle.

  3. Configuration Management Definition: The set of activities that have been developed to manage change throughout the software life cycle. Purpose: Systematically control changes to the configuration and maintain the integrity and traceability of the configuration throughout the system’s life cycle.

  4. Baseline • Definition: Specification or product that • has been formally reviewed and agreed upon, • serves as the basis for further development, and • can be changed only through formal change control procedures. • Signals a point of departure from one activity to the start of another activity. • Helps control change without impeding justifiable change.

  5. Project Baseline • Central repository of reviewed and approved artifacts that represent a given stable point in overall system development. • Shared DB for project and kept in consistent state. • Policies allow the team to achieve consistent state and manage the project.

  6. Software Configuration Item (SCI) • Definition: Information that is created as part of the software engineering process. • Examples: • Software Project Plan • Software Requirements Specification • Models, Prototypes, Requirements • Design document • Protocols, Hierarchy Graphs • Source code • Modules • Test suite • Software tools (e.g., compilers)

  7. Elements of SCM There are four elements of SCM: • Software Configuration Identification • Software Configuration Control • Software Configuration Auditing • Software Configuration Status Accounting

  8. Software Configuration Identification • Provides labels for the baselines and their updates. • Evolution graph: depicts versions/variants. • An object may be represented by variant, versions, and components. 1.4 1.3 1.0 1.1 1.2 2.0 1.1.1 1.1.2

  9. Family of Products A family of products using a component database

  10. Software Configuration Control Three basic ingredients to SCC • Documentation for formally precipitating and defining a proposed change to a software system. • An organizational body (Configuration Control Board) for formally evaluating and approving or disapproving a proposed change to a software system. • Procedures for controlling changes to a software system.

  11. Software Configuration Control • Why needed? • Not all possible changes are beneficial. • Need a mechanism to control access to different items of the configuration (who can access what).

  12. Access and Synchronization Control Configuration Object (Modified Version) Check-In Configuration Object (Baseline Version) Audit Info Unlock Software Engineer Project Database Ownership Info Access Control Lock Configuration Object (Baseline Version) Configuration Object Request Check-Out

  13. Access and Synchronization Control Configuration Object (Modified Version) Check-In Configuration Object (Baseline Version) Audit Info Unlock Software Engineer Project Database Ownership Info Access Control Lock Configuration Object (Baseline Version) Configuration Object (Extracted Version) Check-Out

  14. Access and Synchronization Control Configuration Object (Modified Version) Check-In Configuration Object (Baseline Version) Audit Info Unlock Software Engineer Project Database Ownership Info Access Control Lock Configuration Object (Baseline Version) Configuration Object (Extracted Version) Check-Out

  15. Access and Synchronization Control Configuration Object (Modified Version) Check-In Configuration Object (Baseline Version) Audit Info Unlock Software Engineer Project Database Ownership Info Access Control Lock Configuration Object (Baseline Version) Configuration Object (Extracted Version) Check-Out

  16. Customer Project Manager Dev Team Configuration Manager* Configuration Management Cycle Customer approves changes Customer generates a change request Manager assigns change request to software engineer SE checks in modified configuration objects and notifies CM Software engineer checks out necessary configuration objects SE completes necessary changes CM prepares new system release for operation if necessary CM creates new system baseline *In charge of administering project database and providing access control to engineers

  17. Software Configuration Auditing • Provides mechanism for determining the degree to which the current configuration of the software system mirrors the software system pictured in the baseline and the requirements documentation.

  18. Software Configuration Auditing • Asks the following questions: • Has the specified change been made? • Has a formal technical review been conducted to assess technical correctness? • Has the software process been followed and standards been applied? • Have the SCM procedures for noting the change, recording it, and reporting it been followed? • Have all related SCIs been properly updated?

  19. Software Configuration Auditing Why needed?

  20. Software Configuration Status Accounting • Provides a mechanism for maintaining a record of where the system is at any point with respect to what appears in published baseline documentation. • When a change proposal is approved it may take some time before the change is initiated or completed.

  21. Software Configuration Status Accounting • Why needed? • Ensure that there is progress within the development of the project. • Track updates to baselines.

  22. Requirements for CM • Repository: shared DB for artifacts with controlled access to prevent overwrites. • Version management: Maintain history of changes made to each artifact; provide ability to see how version was created. • Work-space control: Private work space with ability to check out from repository and check in with new version number. • Product modeling and building: Procedure to build the product from artifacts in repository.

  23. CM Tools • Concurrent Version System (CVS) • Subversion • Visual Source Safe

  24. Lock-Modify-Unlock System [2] Figure 1.3. The lock-modify-unlock solution

  25. Copy-Modify-Merge System-1 [2]

  26. Copy-Modify-Merge System-2 [3] )

  27. Schedule • Complete the configuration management plan for your team. • Due date: January 27, 2011

  28. References [1] Bersoff, H. E., Elements of Software Configuration Management. IEEE Transactions on Software Engineering, Vol. SE-10, No. 1, Jan 1984. [2] Collins-Sussman. B. et al., “Version Control with Subversion”, http://svnbook.red-bean.com/en/1.0/ch02s02.html. [3] Ghezzi, C. et al., Fundamentals of Software Engineering 2nd. Ed. New Jersery: Prentice Hall, 2003. [4] Pressman, R., Software Engineering: A Practitioner’s Approach. Boston: McGraw Hill, Inc., 2005.

More Related