March 8, 2009
In the Software Configuration Management Process: Configuration is controlled by a systematic approach named as Configuration Control.
Configuration Control Enforces a rigorous change control mechanism.
Configuration Control requires formal procedure to
February 27, 2009
Version
Defined set of functional capabilities for a software Configuration Item (CI) is called the version or Software Configuration Item version.
Revisions
Changes to a version to correct only errors in design logic but doesn’t affect documented functional capabilities since none of the requirements have changed.
Variants
Variation of a version developed to run on different types of Hardware
OR
Provide slightly different facilities for different users.
Merging
Two diverging versions may be merged to create a single new version combining both set of change requests.
Note: Merge operations are typically done interactively with tool assistance.
CI Promotion
A configuration Item may be promoted from one developmental baseline to another to signify a change in a CI’s internal developmental state.
Release
A release is used to designate certain promotions of CIs that are distributed outside the development organization.
February 26, 2009
Process to Identify what the different baselines consists of is known is Configuration Identification.
Set labeling and identification conventions for the CI’s.
Every CI has it’s identity that is used to keep change records and it shows that some particular CI belongs to some particular baseline . Particular CI has following attributes and it is identified through these attributes.
Basic Configuration Item Information
1) Item Identity
2) Baseline to which it belongs
3) Relationship to other Items
4) Version
5) Variant
February 23, 2009
Methodology to control change in SDLC is as follows.
Change Request ( CR ) Submission
Technical and business evaluation and Impact Analysis
Change Control Board ( CCB ) approval
Engineering Change Order (ECO) generation stating
Changest to be made in CI
Criteria for reviewing the changed CI
CI’s Check Out
Change made and reviewed
CI’s Check In
February 19, 2009
Phase Baseline
1) Feasibility Study, Requirements Definition 1) Functional Baseline
2) SRS, Interface Specification 2) Allocated Baseline
3) Detailed Design 3) Design Baseline
4) Source and object code,User Manual,Test documents 4) Product Baseline
5) Installation 5) Operational Baseline
February 18, 2009
Milestone
Milestone is the end of a stage or phase of a project of at which one or more deliverables are actually delivered to the client.
Example:
Example of a milestone is the milestone on the road that shows that you have travelled a particular distance ( traveled distance ), mean to say that it is the symbol of completion.
Similarly , in the SDLC Milestone shows the completion job/ completed deliverables. When milestone reaches then it shows that it’s time to deploy/ handle deliverables to the client.
Baseline
In the Configuration Management process, Baseline is the logical label for some items/deliverable that indicates on it’s completion milestone in the development process has been reached.
Note: Baseline is the identifier to the Milestone that acts an alert about Milestone.
February 17, 2009
Software Configuration Management (SCM) has two major types regarding items
1) Development Item
2) Configuration Item
Items that are not approved yet are known as Development Item.
Development Items can be changed without any formal approval.
Configuration Item
Approved and accepted deliverable is known as Configuration Item.
Changes are made through formal change control procedure.
Typical Software Configuration Items
List of CI’s involved in the Software Configuration Mangement process is as follows.
February 16, 2009
Software Configuration Management has following four tasks.
1) Configuration Identification
Configuration Identification identifies the items that might have change and there is need to control the change for it.
The items that are identified against this activity are called Configuration Itmes ( CI )
2) Configuration Control
Identifies the items that need to be identify, change and control the change is called configuration Contorl.
Configuration Control applies for evolutionary and revolutionary changes.
3) Status Accounting
Status Accounting cheks for the status of the change that is going to be made whether this change is possible, if being done then what’s its status whether approved, rejected etc.
4) Configuration Audit
Configuration Audits are applied over the entire process of configuration Management to verify whether Configuration Management process is going to be followed or not?
Two major types of Configuration Audits are
1) Physical Configuration Audits (PCA)
2) Functional Configuration Audits (FCA)
February 15, 2009
There are following eight functions of Software Configuration Management (SCM).
1) Identification of software items and products
2) Definition of Baselines
3) Access controls
4) Progressing defect Reports
5) Progressing change requests
6) Recording Item Status
7) Controlling Release (Versions and Variants)
8)Reporting
February 13, 2009
TQM stands for Total Quality Management (TQM)
Following are the Eight Quality Management Principles of TQM.
1) Customer Focus.
2) Leadership.
3) Involvement of People.
4) Process Approach.
5) System Approach to Management.
6) Continual Improvement.
7) Factual Approach to Decision Making.
8)Mutually Beneficial Supplier Relationship.
