A Scheme to Analyze the Root Causes of Defects based on Software Development Roles: Case Study on the Health-care Systems

  • 楊 淇祿

Student thesis: Doctoral Thesis


A root cause is a source of software defect the removal of which reduces or eliminates the defect Software engineers inject a root cause of a software defect during the development process One of the main concerns of software team leaders such as the project manager is to determine who injected various root causes of defects into the software and the time these root causes were injected In this paper a cost–benefit scheme (Cause Analysis and Action Priority or CAAP) is presented This scheme allows a software team to determine the weakness in skill and improve team capability The scheme provides effective in-process feedback based on the causal analysis of software defects The proposed CAAP scheme includes orthogonal root cause definitions role-based root cause types and gradational correction actions In the experiment two systems for defect causal analysis are developed The first system is a fuzzy inference system for self-health estimation through blood pressure and body mass index; the system leverages physical vital signs through fuzzy logic technology for daily self-health status estimation The second system is a self-adaptable indoor localization system; the close tracking algorithm-based system is designed by improving the received signal strength indication (RSSI)-based algorithms to locate moving objects in wireless sensor networks Both systems can be further applied in out-of-hospital services in the health-care domain The two healthcare systems are utilized to validate the efficiency of the proposed scheme Results show that the root cause ratios are 33 8% 30 6% 21 9% 10 7% and 3 0% in design implementation analysis business and deployment respectively The defects in the projects mainly occurred during the design and implementation phases Correction activities to enhance the skills of the designers such as exception handling (40 5%) and DB/data schema (25 0%) are the top priorities that the software team must address The findings can help the team leader determine methods to improve these weaknesses in the software team
Date of Award2015 Jan 28
Original languageEnglish
SupervisorYeim-Kuan Chang (Supervisor)

Cite this