Status Reporting

The configuration status reporting sometimes called status accounting is an SCM task which answers the following questions

(1) what happened?  

(2) Who did it?

(3) what happened? When did it happen?

(4) What else will be affected? The flow of information of configuration status reporting.  Each time is SCI is assigned new or updated identification a CSR entry is made. Each time a change is approved through the CCA for example and ECO is issued a CSR entry is established. Every time a change is made. Each time a configuration audit is conducted the results are reported as category of the CSR task. The output from CSR may be placed in an on-line database [TAY85] so which software developers or maintainers can access change information through keyword category. In addition a SCR report is created on a regular basis and is intended to keep practitioners and management appraised of important changes.

Configuration status reporting plays a vital role in the success of a large software project development. When many   people dare involved it is likely that "the left hand not knowing what the right hand is doing" syndrome will happen. 2 developers may attempt to modify the similar SCI with several and conflicting intent. The software engineering team may spend months of effort building software to an obsolete for a proposed change is not aware in which the change is being made. CSR helps to eliminate these problems through improving communication between all people involved.