Configuration Management

A software configuration version is an approved set of the SCI versions that constitute a documented software system at a given point of time.

Software configuration management items and software configuration - Software configuration item (SCI) or configuration item(CI) An approved unit of software code, a document or piece of hardware that is designed for configuration management and trated as a distinct entity in the software configuration management process - SCI version The approved state of an SCI at any given point of time during the development or maintenance process. - Software configuration version An approved selected set of document SCI versions that constitute a software system or document at a given point of time, where the activiries to be performed are controlled by software configuration management procedure. The software configuration version are released according to the cited procedures.

Common types of software configuration items Design document Software development plan(SDP) System requirements documents Software requirements documents(SRD) Interface design specifications Preliminary design documents (PDD) Critical design document Database description Software test plan(STPR) Software test report (STR) Software user manuals Software maintenance manuals Software installation plan (SIP) Software maintenance request (including reports) Software change request (SCRs) and software change orders(SCOs) Version description document(VDD)

Software code Source code Object code Prototype software

Data files Test cases and test scripts Parameters, codes, etc. Software development tools (the version applied in the development and maintenance stages) Compilers and debuggers Application generators Case tools

Software configuration management An SQA component responsible for applying (computerized and noncoputerized technical tools and administrative procedures that enable completion of the task required to maintain SCIs and software configuration version.

Software configuration management- task and organization

the tasks of software configuration management the task of software configuration management may be classified into four groups: Control software change Released of SCI and software configuration versions Provision of SCM information services Verification of compliance to SCM procedures.

The software configuration authority It is practically self-evident that an authority to oversee implementation of the aove tasks is vital in softwaredeveloping and/or maintaining organizations. SCM procedures specify who is responsible for SCM issues. This responsibility is usually assigned to a senior professional or a committee dedicated to SCM issues. In may organization, software change control is

Software change control Software change management controls the process of introducing changes mainly by doing the following: Examining change request and approving implementation of appropriate requests.
Assuring the quality of each new version of software configuration before it becomes operational.

Approval to carry out proposed changes

Once the baseline version of the software system becomes operational, its just a matter of time before proposals for changes begin to flow. These initiatives may relate to one or several SCIs. In order to coordinate the efforts invested and guarantee that the changes follow the project customer priorities, an authorized body must analyze the request s and make the necessary decisions.

The factors affecting the decision whether to implement a proposed change include:
Expected contribution of the proposed change Urgency of the change Effect of the proposed change on project timetables, level of service, etc. Effort required in making the change operational Required software quality assurance efforts Estimated required professional resources and cost of performing the change.

Software change request (SCR) document-a template Change principles The initiator The date SCR was presented The character of the change The goals The expected contribution of the project/system The urgency of performance Change details Description of the proposed change A list of the SCIs to be changed Expected effect on other SCIs Expected effect on interfaces with other software systems and hardware firmware Expected delays in development completion schedules and expected disturbances to services to customer Change timetable and resources estimates Timetable for completion Estimated required professional resources Other resources required Estimated total cost of the requested change

Quality assurance of software changes While change efforts are directed to one or several SCIs, the user experiences the changes indirectly, through application of the revised version of the software system.

Quality assurance efforts are required at two levels Quality assurance of the entire new software system version (that includes changes SCIs).

Released of software configuration versions The need to release a new software configuration version usually stems from one or more of the following conditions: Defective SCIs Special features demanded by new customers The teams initiatives to introduce SCI improvements. Discussions of the following issues, all of which are part of the process of software configuration version release, occupy the remainder of this section: Types of software configuration releases Software configuration management plans (SCMPs) Software configuration evolution models Documentation of software configuration versions.

Types of configuration releases Baseline versions Intermediate versions Revisions Numeration convention of identification of SCI and software versions

Software configuration management plans (SCMPs) The main objective of a software configuration management plan (SCMP) is to plan ahead the schedule of baseline version releases and the required resources to carry out all the activities required for the software configuration releases. Accordingly, an SCMP usually includes: An overview of the software development project or existing software system. A list of schedule baseline version releases. A list of SCIs (document, code, etc.) to be included in each version. A table identifying the relationship of software development project plans and maintenance plans to scheduled releases of new SCIs or SCI versions. A list of assumption