System dynamics model for simulation of the software inspection process

Abstract

Repairing a defect in the late phases of software development can be a hundred times more expensive than finding and fixing it during the requirements and design phase. Software inspection is a technique that may be used to aid in the identification of defects during early stages of the process and avoid propagation of such defects to later phases. The cost-benefit of inspections may be significant if they are efficiently performed. Since this process is affected by several quality factors, the analysis of the overall context of inspection may become complex. Project managers are reluctant to introduce inspection due to uncertainty regarding its real benefits. This paper presents a system dynamics model, which is a descriptive technique for systems modeling and simulation and involves several variables that strongly influence inspection efficiency. The influence levels of model variables are quantified based on real or empirical experiments reported in the literature, in order to approximate model results to values that would be obtained in the real world. The model allows the reproduction of scenarios without paying the costs and facing the risks of a real project implementation. Therefore, it enables the analysis of inspection effects on the software development process.

Using system dynamics to teach about dependencies, correlation and systemic thinking on the software process workflows

“…In 2013, De Sousa et al. [18] presented a system dynamics (SD) model to analyse 5 techniques (ad hoc, checklist, perspective, scenario, N‐fold) that can be applied to analyse the inspection phase in software projects. The model allows the estimation of the total number of defects from the early stages of software development as well as the effectiveness and cost of inspection activity.…”

Software Process Simulation Modeling: Systematic literature review

“…(1) Regarding «software quality» area, SPSM proposals are focused on quality of simulation models [37,50], quality of software projects [38,43,56], security software [71] and error reduction [40,49,67].…”

“…[39] Reduction of the risk of software projects with the identification of defects in SDP using, or not, software tests. [40,43,49,64,71] Agile techniques to meet the requirements of stakeholders during the execution of software requirements engineering process [69] Application of simulation models as support for software construction [70] Distributed software development processes by the project and team size, number of artifacts, and project duration.…”

“…Finally, error reduction is another relevant topic in «software quality» area. On the one hand, De Sousa Coelho et al [40] proposes a simulation model to evaluate scenarios in the inspection of software projects in terms of 10 input variables (such as technique, number of inspectors, parallel equipment, etc.). However, the simulation model establishes very little relationships between variables, so it is convenient to improve this aspect to obtain a more robust and complete model.…”