8.3.5 Assessment Report (AsProt)
The Assessment Report contains the assessor-originated recordings about the course of the assessment, especially the comparison between expected and actual results. This information will be completed within the scope of analyses with possible reasons for erroneous behavior and proposed measures.
The Assessment Report exists for each object to be assessed and for each assessment.
1. General Information
2. Identification of the Assessment
2.1. Reference to Assessment Plan, Object to be Assessed, Assessment Specification and Assessment Procedure
2.2. Execution Details
4.1. Evaluation and Judgment of Results
4.2. Development Trends with regard to Occurrences of Deficiencies
See schema 1. General Information.
The Assessment Report refers to an actual assessment and thus to a uniquely defined version of an object to be assessed, Assessment Specification and Assessment Procedure.
Information about Assessor, location, date and time, and the result of the assessment (product "accepted" or "b. proc.") will be documented.
The actual results of the assessment will be documented. The final and interim results and also any possible further information will be stored in chronological order.
The expected target results from the product Assessment Specification (structural item 5.1 Test Case Description) will be listed.
The deviations of the results will be documented, and its impacts on the functionality of the System will be evaluated. The possible reasons for errors will be listed.
If required, further measures and recommendations will be stated, in particular solution approaches and correction measures.
Should it become obvious during the assessment that errors are contained in specified test cases (e. g. the expected result is wrong or the requirement cannot be met) then these test cases must be identified, and a separate problem report has to be generated.
If the assessment results point to a certain trend with regard to defects of a certain kind, relevant assumptions must be documented and possible counter-measures ought to be suggested. This information has to be integrated into QA5 - QA Reporting.
Last Updated 01.Jan.2002
Updated by Webmaster
Last Revised 01.Jan.2002
Revised by Webmaster