Monday, February 11, 2008

Guide to Software Engineering Part 2

Software Configuration Management (SCM) is the discipline of identifying, organizing, and controlling changes to the software to maintain the integrity of its configuration.

The Need to Manage Change
- Overwriting
- Bug fixes

To perform SCM, you need:
- A nomenclature(naming) to identify work products in the process
o Baseline
o Configuration Item
- Processes
o CM policies and procedures (CM Plan)
o Change request process
o Version control and naming
o CM audit and status accounting
- Roles and responsibilities
o Configuration Manger
o Change Control Board
o Auditor
- Tools
o Configuration Repository
o Version Control

Configuration Item (CI) is a work product that is place under configuration control (Baseline).E.g. Minutes of Meeting, requirement specification project proposal, codes, test plan, user documentation.

Baseline is a specification or product that has been formally reviewed and approved which can only be changed through forma approvals.

Roles and Responsibilities
- Configuration Manager
- Change Control Board (CCB)
- Software Engineers
- Project Manager

Configuration Audit is the activity performed independently to evaluate the conformance of CM policies and procedures.

Status Accounting is the recording, monitoring and reporting of configuration management information and the purpose of it is to maintain continuous record of changes and actions for all baseline CIs.

Posted by Zack at 7:14 PM