Abstract
This work aims to propose a qualitative “starter model” for a new software defect prevention for better Software Quality. Software defect prevention methods and models have made substantial progress in recent years. But this still falls short of the needs of today and the future. One contribution is a qualitative model that takes into account key determinants and their interlinked effects. The model is based on System Dynamics and the elements involved in the software development process, e.g. the human being, management, members of staff, work psychology, quality, methods, organizations, customer, culture etc. Current research status comprises 15 identified important key determinants, their respective strength, interrelationships and dynamics. The model is operationalized with a software tool capable of modelling all the key determinants defined, their effect directions and other data of the comprehensive matrix they make up. With the research results made, the new defect prevention model shows promise. The research is due to continue further in order to contribute to improved defect prevention in the software development process. The number of key determinants, their respective strength etc. be will be 140 in the final research work.
Keywords: Systemic, software, software development, Software-quality, defects, defect prevention, Determinants, System Dynamics, qualitative model, the human being, process, methods, technology, organization.
Table of Contents
1. Starting Position and Problem Definition
2. Desk Research and Theoretical Background
2.1 Software Development Process
2.2 Software Defects
3. Software Defect Prevention
3.1 Outline of the four classes of defect prevention actions
3.2 Software Process Improvement Models for Defect Prevention
3.3 Costs and Benefits of Practical Defect Prevention
3.4 Summary of Desk Research and Theoretical Background
4. Method
4.1 Concept Design
4.2 Systemic Thinking / Cross-linked Thinking
5. The Model Concept
5.1 Model Structure
5.2 Identifying the Determinants
5.3 Examination of Applicable Determinants Based on
5.4 Comments on Target Variable and Determinants
5.5 Causal interdependencies, their effect directions and effect intensities
6. Results
6.1 Visualizations an Analyses
6.2 Explanation of Elements in the Result Matrix
6.3 Analysis of determinants in the result matrix
7. Discussion and Conclusion
7.1 Discussion
7.2 Conclusion
Objectives and Research Focus
This work aims to propose a qualitative "starter model" for systemic software defect prevention to improve software quality. The research focuses on identifying key determinants and their interlinked causal effects within the software development process, particularly in the initial phases of requirements analysis, specification, and design.
- Application of System Dynamics to software development
- Identification of 15 key determinants influencing defect prevention
- Analysis of causal interdependencies and effect intensities
- Integration of human factors and organizational culture
- Operationalization through a systemic modeling tool
Excerpt from the Book
4.2 Systemic Thinking /Cross-linked Thinking
Systemic thinking amounts to identifying mutual interdependencies and the rules behind causal interactions (Hamilton 2007, p. 110). Fig. 3 shows an example systemic software development process. Hints and ideas for solving the problem of "comprehensive interlinked defect prevention in the software development process" have been supplied among others by the following authors who spearheaded research into systemic thinking:
(Dörner, 2008); (Gomez/Probst, 1987); (Gomez/Probst, 1997); (Senge, 1996); (Veester, 2007).
Systemic thinking relies on six steps:
(1) Defining objectives and modelling the problem situation
(2) Analyzing causal chains
(3) Exploring and interpreting possible trends in the future
(4) Exploring control options
(5) Planning strategies and actions
(6) Implementing the problem solution
Summary of Chapters
1. Starting Position and Problem Definition: Outlines the rising complexity in software development and justifies the need for a systemic approach to defect prevention, focusing on the early development phases.
2. Desk Research and Theoretical Background: Reviews existing methods, process models, and the nature of software defects, establishing the foundation for the proposed systemic model.
3. Software Defect Prevention: Categorizes prevention actions into analytical, constructive, organizational, and psychological classes and discusses the cost-saving benefits of early detection.
4. Method: Describes the theoretical and empirical research approach, selecting the "Thinking in Networks" model and the "Consideo Modeler" tool for operationalization.
5. The Model Concept: Details the model structure, identifying key determinants (such as human factors and process maturity) and explaining how causal interdependencies are quantified.
6. Results: Presents the findings through network matrices and visualizations, analyzing the short- and long-term effects of the identified determinants on successful defect prevention.
7. Discussion and Conclusion: Evaluates the model output, identifies key levers for improvement, and proposes future research directions including model expansion.
Key Keywords
Systemic, software development, software quality, defects, defect prevention, determinants, System Dynamics, qualitative model, human factor, process, methods, technology, organization, causal interdependencies, feedback loops.
Frequently Asked Questions
What is the core focus of this research?
The work focuses on improving software quality by developing a qualitative, systemic model for defect prevention that specifically addresses the first three phases of the development process: requirements analysis, specification, and design.
Which methodology is used to model defect prevention?
The research employs System Dynamics and "Systemic Thinking" (specifically the "Thinking in Networks" model) to map and analyze the complex causal interdependencies between various factors influencing software defects.
What are the primary themes covered?
Key themes include software development processes, human factors (work psychology, motivation), organizational culture, process maturity models, and the identification of 15 essential determinants that affect defect prevention.
What is the goal of the proposed model?
The goal is to provide a "starter model" that complements existing procedures by visualizing causal chains and identifying the most effective levers for reducing defects systematically.
What does the main body of the work cover?
The main body details the theoretical background, the selected methodology, the construction of the determinant model, and the analysis of results using result matrices to determine short- and long-term effects.
Which keywords characterize this work?
Central keywords include Systemic, software development, defect prevention, System Dynamics, and human factor.
Why is the "human factor" significant in this model?
The author argues that because software is prevalently compiled by humans, the human factor—including leadership, motivation, and quality culture—is the most critical determinant for success in defect prevention.
What is the role of the "Consideo Modeler" tool?
It is used to operationalize the systemic model, allowing for the simulation and visualization of the network of determinants, their effect directions, and their intensities.
How are short-term and long-term effects distinguished?
The research uses result matrices to categorize determinants into four quadrants (progressively/degressively promotive or inhibitive) based on their impact over time, helping to identify which interventions are most effective in the short vs. long run.
- Citar trabajo
- Alfons Unmüßig (Autor), 2012, Software Defect Prevention for better Software Quality, Múnich, GRIN Verlag, https://www.grin.com/document/195119
