TY - GEN
T1 - A method to diagnose self-weaknesses for software development organizations
AU - Yang, Chi Lu
AU - Chang, Yeim Kuan
AU - Chu, Chih Ping
N1 - Publisher Copyright:
© 2008 by Knowledge Systems Institute Graduate School. All rights reserved.
PY - 2008
Y1 - 2008
N2 - A root cause is a source of a defect such that if it is removed, the defect is subsequently decreased or removed. By analyzing the root causes of defects of our software projects, we will be able to determine the weaknesses of our software development teams. We could thus decide on how much effort to be invested on specific actions to improve the weaknesses of the teams. In this paper, we first described how defects were objectively collected during project development. Second, the root causes were defined and categorized into six groups. Then we focused on analyzing defects to find out their root causes. Based on statistical results, the weaknesses of the project teams were determined. The results showed that the disturbing defects in our projects were mainly injected in the design phase, especially in the detail design phase. Moreover, we should invest considerable effort on enhancing our detail design skills, such as designing components, algorithms and interfaces, and so on. Some corrective actions and prevention proposals would correspondingly be acted upon and planned, respectively. Overall, we believe that our experiences and methods are worthy of sharing.
AB - A root cause is a source of a defect such that if it is removed, the defect is subsequently decreased or removed. By analyzing the root causes of defects of our software projects, we will be able to determine the weaknesses of our software development teams. We could thus decide on how much effort to be invested on specific actions to improve the weaknesses of the teams. In this paper, we first described how defects were objectively collected during project development. Second, the root causes were defined and categorized into six groups. Then we focused on analyzing defects to find out their root causes. Based on statistical results, the weaknesses of the project teams were determined. The results showed that the disturbing defects in our projects were mainly injected in the design phase, especially in the detail design phase. Moreover, we should invest considerable effort on enhancing our detail design skills, such as designing components, algorithms and interfaces, and so on. Some corrective actions and prevention proposals would correspondingly be acted upon and planned, respectively. Overall, we believe that our experiences and methods are worthy of sharing.
UR - http://www.scopus.com/inward/record.url?scp=84923912250&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84923912250&partnerID=8YFLogxK
M3 - Conference contribution
AN - SCOPUS:84923912250
T3 - Proceedings: DMS 2008 - 14th International Conference on Distributed Multimedia Systems
SP - 124
EP - 129
BT - Proceedings
PB - Knowledge Systems Institute Graduate School
T2 - 14th International Conference on Distributed Multimedia Systems, DMS 2008
Y2 - 4 September 2008 through 6 September 2008
ER -