document.write() This function is used to write arbitrary HTML and content into page. If we use this function after an…Read more »
The following outlines the basic steps to adopt the continuous inspection pattern: 1. Tool selection. Evaluate and select one or…Read more »
Basic Work Cycle in Subversion (SVN) Subversion has numerous features, options, bells, and whistles, but on a day-to-day basis, odds…Read more »
Command Description p4 add Open file(s) in a client workspace for addition to the depot. p4 admin Perform administrative operations…Read more »
Identification, control, audit, and status accounting are the four basic requirements for a software configuration management system. These requirements must be satisfied regardless of the amount of automation within the SCM process. All four may be satisfied by an SCM tool, a tool set, or a combination of automated and manual procedures.
- Identification—Each software part is labeled so that it can be identified. Furthermore, there will be different versions of the software parts as they evolve over time, so a version or revision number will be associated with the part. The key is to be able to identify any and all artifacts that compose a released configuration item. Think of this as a bill of materials for all the components in your automobile. When the manufacturer realizes that there has been a problem with parking brakes purchased from a subcontractor, it needs to know all the automobile models using that version of the parking brake. It is the same with software. If we are building a multimedia system that has audio MPEG3 drivers for Windows 98, Windows 2000, Windows CE, Linux, and FreeBSD operating systems, how do we find out which releases are impacted when we find an error in the Linux product? You must go back to your SCM system to identify all the common components in all operating system releases that are impacted.
Read more »