IEEE 1028-1998

Definition of the performance requirements for the methods to be used during the evaluation of software products of the software development life-cycle. The review process ensures that: 1) Progress according to plan is assessed, based on an evaluation of product development status. 2) Recommendations are provided for changing project direction or to identify the need for alternative planning. 3) Recommendations are provided for maintaining global control of the project through adequate allocation of resources. 4) Evidence of compliance of products and processes to standards, guidelines, specifications, and procedures is provided. 5) Evidence is provided that specific software elements conform to its specifications. 6) Evidence is provided that development (or maintenance) of the software elements is being done according to plans, standards, and guidelines applicable for the project. 7) Evidence is provided that changes to the software elements are properly implemented, and affect only those systems areas identified by the change specification. 8) Results of reviews are communicated to developers, managers, and responsible personnel in order to provide a history and provide information for work. The revision of 1028 will specify for the software review processes: the scope, the goals, the measures for determining how well the process goals were achieved, any roles unique to the process, the products to which the process is applied, the conditions(s) that must be satisfied before the process can begin, the standard steps to be followed in performing the process, the condition(s) that must be satisfied before the process is considered complete, the minimum set of results resulting from process completion, the measurement procedure, the associated metrics, and the measurement data to be collected, and the evidence needed to determine at a later date that the process was followed.