Tag Archives: Control

Definition of Configuration Management

Software CM is a discipline for controlling the evolution of software systems. Classic discussions about CM are given in texts such as [6] and [8]. A standard definition taken from IEEE standard 729-1983 [42] highlights the following operational aspects of CM: Identification: an identification scheme reflects the structure of the product, identifies components and their… Read More »

Interview Questions and Answer for Perforce Version Control Tool

Some of the perforce commands which is not commonly used but useful. p4 annotate – Print file lines along with their revisions. e.g p4 annotate file.c How to ignore files/folder in perforce workspace/client? Assuming you have a client named “CLIENT”, a directory named “foo” (located at your project root), and you wish to ignore all… Read More »

How to Select the Right Software version Control Product?

Original link: http://www.cmcrossroads.com/cm-articles/275-articles/14286-selecting-the-right-software-version-control-product Selecting the Right Software Version Control Product Written by Mike Feighner For many years, I worked loyally for the same company where my expertise was restricted to one single software version control tool—the one that was already in place. I was not involved with determining whether the selected tool was appropriate for… Read More »

Power Point PPT: Version Control With CVS – Complete Guide

Power Point PPT: Version Control With CVS Version Control With CVS from Rajesh Kumar  

The symptoms of our software development malaise

Software development has traditionally suffered from producing end products with a definite lack of inherent quality. The symptoms of this quality lack are listed here:

  • Software development projects are often delivered late and over budget.
  • Often the delivered product does not meet customer requirements and is never used.
  • Software products simply do not work right.

As we look into the symptoms of our software development malaise, five principal issues related to software development arise.

Lack of Visibility
Software is conceptual in nature. Unlike a bridge, a building, or another physical structure, it is not easy to look at software and assess how close it is to completion. Without strong project management, “software is 90% complete 90% of the time.” Through the adoption of SCM policy and the definition of the configuration management model of the software under development, all CIs, components, and subcomponents are immediately visible for versions, releases, and product families.