The Correlation between Software Difficulty and Care Charges
Article Sidebar
-
Software, Software Maintenance, Software Evolution, Maintenance Costs
Abstract
As software becomes more and more difficult due to an increased number of module sizes, process sizes, and dividing difficulties, software care prices are often on the increase. Consider software such as the Windows 8 operating system with 80 million source lines of code (SLOC) and with 3000 designers [1]; there is no disbelief that such a large and complex software will require a large amount of money and common and environmental factors to keep it. It has been estimated that over 70% of the total costs of the software development process are spent on maintenance after the software has been distributed. This paper studies the relationship between software complexity and maintenance cost, the reasons responsible for software difficulty, and why maintenance costs increase with software complexity. The results show that there is a strong correlation between software complexity and maintenance costs. That is, as lines of code increase, the software becomes more complex, and more bugs may be presented, and therefore the cost of keeping software rises.
Full text article
References
[1] M. Glinz, (2003), "Estimating Software Maintenance," Requirements Engineering Research Group, University of Zurich.
[2]-Lyu, M.R. (1996) Handbook on Software Reliability Engineering. McGraw-Hill, USA, and IEEE Computer Society Press, Los Alamitos, California, USA.
[3]-Ogheneovo, E.E. (2013) Software Maintenance and Evolution: The Implication for Software Development. West African Journal of Industrial and Academic Research, 7, 34-42.
[4] Banker, R.D., Datar, S.M., Kemerer, C.F., and Zweig, D. (1993) Software Complexity and Maintenance Costs. Communications of the ACM, 36, 81-94.
[5] Grubb, P. and Takang, A.A. (2003) Software Maintenance: Concepts and Practice. 2nd Edition, World Scientific Publishing Company, Singapore. 3
[6]-Guth, R.A. (2005) Code Red: Battling Google, Microsoft Changes How It Builds Software. The Wall Journal, A1. Factiva, MIT Libraries, Cambridge.
[7] Shihab, E., Bird, C., and Zimmermann, T. (2012). The Effects of Branching Strategies on Software Quality. Proceedings of ESEM '72, Lund, 17-22 September 2012, 301-310.
[8]-Appleton, B., Berazuk, S., Cabrera, R., and Orenstein, R. (1998) Streamed Links: Branching Patterns for Parallel Software Development, 2002.
[9] Mall, R. (2009) Fundamentals of Software Engineering. 3rd Edition, PHI Learning Private Ltd., New Delhi, 404-411.
[10] Dvorak, D.L., Ed. (2016) NASA Study on Flight Complexity Final Report, Systems and Software Division, Jet Propulsion Laboratory, California Institute of Technology. 3
[11]-R. Spiewak, K. McRitchie. (2014) "Using Software Quality Methods to Reduce Cost and Prevent Defects," 23-27.
Authors
This work is licensed under a Creative Commons Attribution 4.0 International License.
In a brief statement, the rights relate to the publication and distribution of research published in the journal of the University of Sebha where authors who have published their articles in the journal of the university of Sebha should how they can use or distribute their articles. They reserve all their rights to the published works, such as (but not limited to) the following rights:
- Copyright and other property rights related to the article, such as patent rights.
- Research published in the journal of the University of Sebha and used in its future works, including lectures and books, the right to reproduce articles for their own purposes, and the right to self-archive their articles.
- The right to enter a separate article, or for a non-exclusive distribution of their article with an acknowledgment of its initial publication in the journal of Sebha University.
Privacy Statement The names and e-mail addresses entered on the Sabha University Journal site will be used for the aforementioned purposes only and for which they were used.