Early Software Product Improvement with Sequential Inspection Sessions: An Empirical Investigation of Inspector Capability and Learning Effects (D. Winkler, B. Thurnher, S. Biffl)
Early defect detection and remove of defects helps increase the software quality and decrease rework effort and cost. Software inspection – a static verification and validation approach – spots on defect detection in early development phases (e.g., in requirements documents and design specifications). Furthermore, inspection promises to be a vehicle to support learning, even for less-qualified inspectors. Main findings, which were reported in the paper, are (a) the inspection technique UBR (usage-based reading) better supported the performance inspectors with lower experience in sequential inspection cycles (learning effect) and (b) when inspecting objects of similar complexity significant improvements of defect detection performance could be measured.
Nowadays, open source software (OSS) solutions provide mission-critical services to industry and government organizations. Nevertheless, empirical studies on OSS development practices raise concerns on risky practices such as unclear requirements elicitation, ad hoc development processes, little attention to quality assurance (QA) and documentation and poor project management. This paper introduces a QA framework for open source projects and presents some preliminary results on two cases studies from OSS projects regarding a couple of variables, e.g., defect detection frequency, defect collection effectiveness, defect closure time, and ratio of verified solutions.
The third paper introduces a based concept for balancing existing quality assurance approaches for software process and product improvement along the process life cycle. The selection of a suitable set of methods depends strongly on the project context and is based on measurable quality attributes. Decision makers need to assess and compare the overall effects of QA method combination and the tradeoffs between involved QA strategies and to identify tradeoffs of individual methods. The proposed QATAM assessment method of different strategies is originally based on the Architecture Trade-Off Analysis Method (ATAM).
Dietmar Winkler (edited by Alexander Schatten)