The goals of SCM
Configuration identification - Identifying configurations, configuration items and baselines.
Configuration control - Implementing a controlled change process. This is usually achieved by setting upa changecontrol board whose primary function is to approve or reject all change requests that are sentagainst any baseline.
Configuration status accounting - Recording and reporting all the necessary information on the status of thedevelopment process.
Configuration auditing - Ensuring that configurations contain all their intended parts and are sound withrespect totheir specifying documents, including requirements, architectural specifications and usermanuals.
Build management - Managing the process and tools used for builds.
Process management - Ensuring adherence to the organization's development process.
Environment management - Managing the software and hardware that host the system.
Teamwork - Facilitate team interactions related to the process.
Defect tracking - Making sure every defect has traceability back to the source.
i. Software doesn’t Wear
Out. ii. Software is engineered & not manufactured.
Software doesn‟t Wear Out.
The hardware can wear out whereas software can't. In case of hardware we have a "bathtub “like curve, which is a curve
that lies in between failure-rate and time. In this curve, in the starting time there is relatively high failure rate. But, after some period of time, defects get corrected and failure-rate drops to a steady-state for some time period. But, the failure-rateagain rises due to the effects of rain, dust, temperature extreme and many other environment effects. The hardware beginsto wear out.But, the software is not responsible to the failure rate of hardware. The failure rate of software can be understood by the "idealized curve". In this type of curve the failure rate in the initial state is very high. But, the errors in the softwareget corrected and the curve flattens. However, the implication is clear that the software can "deteriorate" it does not "wear
out”. This can be explained by the ac
tual curve. As soon as that error gets corrected the curveencounters another spike thatmeans another error in the software. After some time the steady state of the software don't remains steady and the failurerate begins to rise. If hardware getsfailed then it can be replaced but there is no replacement in case of software.Software is engineered & not manufactured.The roadmap to building high quality software products is software process.
Software processes are adapted to meet the needs of software engineers and managers as they undertake thedevelopment of a software product.
A software process provides a framework for managing activities that can very easily get out of control.
Different projects require different software processes.
The software engineer's work products (programs, documentation, data) are produced as consequences of theactivities defined by the software process.
The best indicators of how well a software process has worked are the quality,timeliness, and long-term viability of the resulting software product.
Q5.Explain the Different types of Software Measurement Techniques.
Most estimating methodologies are predicated on analogous software programs. Expert opinion is based on experiencefrom similar programs; parametric models stratify internal data based to simulate environments from many analogous programs;engineering builds reference similar experience at the unit level; and cost estimating relationships like parametricmodels regress algorithms from several analogousprograms. Deciding which of these methodologies or combination or methodlogies is the most appropriate for your program usually depends on availability of data. Which is inturn depends onwhere you are in the life cycle or your scope definition.Analogies. Cost and schedule are determined based on data from competed similar efforts. When applying thismethod, it is often difficult to find analogous efforts at the total system level. It may be possible, however, to findanalogous efforts at the subsystem or lower level computer software configuration item/computer softwarecomponent/computer software unit (CSCI/CSC/CSU). Furthermore, You may be able to find completed efforts that are