Under CopyrightDenger, C.C.Denger2022-03-0710.07.20032003https://publica.fraunhofer.de/handle/publica/29177910.24406/publica-fhg-291779Since their invention by Fagan in 1976, inspections proved to be an essential quality assurance technique in software engineering. Traditionally, inspections were used to detect defects in code documents, and later in requirements documents. However, not much is known how to apply inspections to design document. Statecharts are an important technique to describe the dynamic behavior of a software system. Thus, it is essential to define techniques for detecting defects in statechart models. In this report, checklists and reading scenarios are presented to support an inspector during defect detection for statecharts.1 Introduction S.1 2 Brief introduction to Inspections S.2-6 - 2.1 The Inspection process S.2-4 - 2.2 Reading Techniques S.4-6 - 2.2.1 Checklist based reading S.4-5 - 2.2.2 Scenario and Perspective based reading S.5-6 3 Inspections of large scaled documents S.7-9 4 State of the art in Statechart-Inspections S.10-18 - 4.1.1 Correct S.10 - 4.1 Defect Taxonomy for Statecharts S.10-14 - 4.1.2 Complete S.11 - 4.1.3 Consistent S.11 - 4.1.4 Unambiguous S.11 - 4.1.5 Testable S.12 - 4.1.6 Traceable S.12-13 - 4.1.7 Feasibility S.13 - 4.1.8 Understandable S.13-14 - 4.2 Statechart Inspection with Traceability based Reading S.14-15 - 4.3 Statechart Inspections with Checklists S.15-16 - 4.4 The QUASAR-Inspection Approach S.16-18 5 Checklist-based Inspections of Statecharts S.19-21 6 Scenario-based Inspections of Statecharts S.22-31 - 6.1.1 Perspective: Tester of the High Level Statecharts (System Specification Document) S.24-26 - 6.1.2 Perspective: Low Level Statechart Designer (System Specification Document) S.26-28 - 6.1.3 Perspective: Maintainer of the statecharts (system specification document) S.29-31 7 Conclusion and Further Research S.32 References S.33-37ensoftware inspectionsoftware reviewperspective-based readingstatechartstatechart inspectionQUASAR004005006report