Abstract
Identifying the causes which may potentially generate high financial damage was the goal of our research. To reach this goal, we conducted a case study on a system in the field of education. We studied the software defects of this system over several months and classified them based on two classification concepts: the EVOLIS and their severity. These defects prevent any essential operation or activity to be conducted through the concerned system or other systems connected to it. In fact, the occurrence of these failures causes a double financial cost to organizations: one in fixing them and the other one because of the unavailability of the system or systems. We targeted three types of software defects as sources of these failures. We conducted this study by classifying 665 software defects of a school management system and we found that the top two trigger groups are the technology and the IS architecture groups. This result led us to propose a method to identify the origins of severe software defects.
Publisher
Institute of Certified Specialists
Reference17 articles.
1. R. N. Charette, “Why software fails [software failure],” Ieee Spectr., vol. 42.9, pp. 42–49, 2005.
2. R. Kaur and D. J. Sengupta, “Software Process Models and Analysis on Failure of Software Development Projects,” Int. J. Sci. Eng. Res., vol. 2, no. 2, p. 4.
3. 1044-2009 IEEE Standard Classification for Software Anomalies. 2009.
4. A. Métrailler and T. Estier, “EVOLIS Framework: A Method to Study Information Systems Evolution Records,” in System Sciences (HICSS), 2014 47th Hawaii International Conference on, 2014, pp. 3798–3807.
5. A. A. Alshazly, A. M. Elfatatry, and M. S. Abougabal, “Detecting defects in software requirements specification,” Alex. Eng. J., vol. 53, no. 3, pp. 513–527, Sep. 2014.