Skip to main content

Software Product Maintenance: A Case Study

  • Conference paper
  • First Online:
Computer Information Systems and Industrial Management (CISIM 2022)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 13293))

  • The original version of this chapter was revised: the affiliation of Sanjay Misra was presented incorrectly. This has been corrected. The correction to this chapter is available at https://doi.org/10.1007/978-3-031-10539-5_29

Abstract

Maintenance is the most important part of software product development. It is a major component of all software development life cycle models (SDLC). Several variables are being used as intermediaries for software systems’ maintainability throughout software development. The goal of this study is to see whether these variables are consistent between themselves and how well they anticipate maintenance efforts at the system stage. The maintenance of software products includes error checking, proper functionality of the system, improving performance, making the system adaptive, and follow up the change request that come from the client side. To perform all these types of actions to enhance the product quality 4 types of maintenance are normally followed Corrective, Preventive, Adaptive, and Perfective maintenance. The maintenance activity is the most time taking activity when change requests come from the client. This paper is explaining the concept of maintenance with an iterative model and its 4 types. Case studies are also discussed in the paper to explain the maintenance activities performed in software organizations and their impact on the product. The performance measures are not aligned with one another. Only the size of the system and its lack of consistency are found to be highly linked to greater maintenance effort. Maintainability measurements, aside from size, may well not accurately indicate additional maintenance effort. Parts of the project must be assessed in the situations where they will be deployed. Conventional factors are being used to indicate problematic places in the code, but improving the worst parts may mistakenly cause further problems throughout the system. Our findings show that local changes must be supported by a system-wide examination.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 79.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 99.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Change history

  • 16 November 2022

    In an older version of this chapter, the affiliation of Sanjay Misra was presented incorrectly. This has been corrected.

References

  1. Jangra, P., Das, S., Khurana, S.K.: Remote software maintenance system for telecom network. In: 2017 International Conference on Advances in Computing, Communications, and Informatics (ICACCI), pp. 1356–1359. IEEE (2019)

    Google Scholar 

  2. Rashid, M.A., Lo, B.: W: A task-oriented software maintenance model. Malays. J. Comput. Sci. 9(2), 36–42 (1996)

    Google Scholar 

  3. Ahmad, M.O., Kuvaja, P., Oivo, M., Markkula, J.: Transition of software maintenance teams from Scrum to Kanban. In: 2016 49th Hawaii International Conference on System Sciences (HICSS), pp. 5427–5436. IEEE (2016)

    Google Scholar 

  4. Sirisomboonsuk, P., Gu, V.C., Cao, R.Q., Burns, J.R.: Relationships between project governance and information technology governance and their impact on project performance. Int. J. Project Manag. 36(2), 287–300 (2018)

    Article  Google Scholar 

  5. Acar, Y., et al.: Comparing the usability of cryptographic APIs. In: IEEE Symposium on Security and Privacy (2017)

    Google Scholar 

  6. Acar, Y., Backes, M., Fahl, S., Kim, D., Mazurek, M.L., Stransky, C.: You get where you’re looking for: the impact of information sources on code security. In: IEEE Symposium on Security and Privacy. https://doi.org/10.1109/SP.2016.25

  7. Acar, Y., Backes, M., Fahl, S., Kim, D., Mazurek, M.L., Stransky, C.: How internet resources might be helping you develop faster but less securely. IEEE Secur. Priv. 15(2), 50–60 (2017)

    Google Scholar 

  8. Acar, Y., Fahl, S., Mazurek, M.L.: You are not your developer, either: a research agenda for usable security and privacy research beyond end users. In IEEE Cybersecurity Development. https://doi.org/10.1109/SecDev.2016.013

  9. Acar, Y., Stransky, C., Wermke, D., Weir, C., Mazurek, M.L., Fahl, S.: Developers need support, too: a survey of security advice for software developers. In: Cybersecurity Development (SecDev) (2017)

    Google Scholar 

  10. Assal, H., Chiasson, S.: Motivations and amotivations for software security. In SOUPS Workshop on Security Information Workers (WSIW). USENIX Association (2018)

    Google Scholar 

  11. Butt, S.A., Misra, S., Piñeres-Espitia, G., Ariza-Colpas, P., Sharma, M.M.: A cost estimating method for agile software development. In: Gervasi, O., et al. (eds.) ICCSA 2021. LNCS, vol. 12955, pp. 231–245. Springer, Cham (2021). https://doi.org/10.1007/978-3-030-87007-2_17

    Chapter  Google Scholar 

  12. Assal, H., Chiasson, S.: Security in the software development lifecycle. In Symposium on Usable Privacy and Security. USENIX (2018)

    Google Scholar 

  13. Ayewah, N., Hovemeyer, D., Morgenthaler, J.D., Penix, J., Pugh, W.: Using static analysis to find bugs. IEEE Softw. 25, 5 (2008). https://doi.org/10.1109/MS.2008.130

    Article  Google Scholar 

  14. Butt, S.A.: Study of agile methodology with the cloud. Pac. Sci. Rev. B: Humanit. Soc. Sci. 2(1), 22–28 (2016)

    Google Scholar 

  15. Baca, D., Boldt, M., Carlsson, B., Jacobsson, A.: A novel security-enhanced agile software development process applied in an industrial setting. In: International Conference on Availability, Reliability and Security (2015)

    Google Scholar 

  16. Baca, D., Petersen, K., Carlsson, B., Lundberg, L.: Static code analysis to detect software security vulnerabilities - does experience matter? In: International Conference on Availability, Reliability and Security (2009)

    Google Scholar 

  17. Przybyłek, A.: Systems evolution and software reuse in object-oriented programming and aspect-oriented programming. In: Bishop, J., Vallecillo, A. (eds.) International Conference on Modelling Techniques and Tools for Computer Performance Evaluation, TOOLS 2011. LNCS, vol. 6705, pp. 163–178. Springer, Heidelberg (2011). https://doi.org/10.1007/978-3-642-21952-8_13

  18. Bartsch, S.: Practitioners’ perspectives on security in agile development. In: International Conference on Availability, Reliability and Security. https://doi.org/10.1109/ARES.2011.82

  19. Butt, S.A., Jamal, T.: Frequent change request from user to handle cost on project in agile model. Proc. Asia Pac. J. Multidiscip. Res. 5(2), 26–42 (2017)

    Google Scholar 

  20. Berisha, G., Pula, J.S.: Defining small and medium enterprises: a critical review. Acad. J. Bus. Adm. Law Soc. Sci. 1 (2015)

    Google Scholar 

  21. Aziz Butt, S., Piñeres-Espitia, G., Ariza-Colpas, P., Tariq, M.I.: Project management issues while using agile methodology. In: Przybyłek, A., Jarzębowicz, A., Luković, I., Ng, Y.Y. (eds.) LASD 2022. LNBIP, vol. 438, pp. 201–214. Springer, Cham (2022). https://doi.org/10.1007/978-3-030-94238-0_12

    Chapter  Google Scholar 

  22. Przybyłek, A.: An empirical study on the impact of AspectJ on software evolvability. Empir. Softw. Eng. 23(4), 2018–2050 (2017). https://doi.org/10.1007/s10664-017-9580-7

    Article  Google Scholar 

  23. Boone, H.N., Boone, D.A.: Analyzing likert data. J. Ext. 50(2), 1–5 (2012)

    Google Scholar 

  24. Chess, B., McGraw, G.: Static analysis for security. IEEE Secur. Priv. 2, 6 (2004). https://doi.org/10.1109/MSP.2004.111

    Article  Google Scholar 

  25. Dillman, D.A.: Mail and Internet Surveys: The Tailored Design Method. Wiley, Hoboken (2000)

    Google Scholar 

  26. Fischer, F., et al.: Stack overflow considered harmful? the impact of copy paste on android application security. In: IEEE Symposium on Security and Privacy. https://doi.org/10.1109/SP.2017.31

  27. Garfinkel, S., Lipford, H.R.: Usable Security: History, Themes, and Challenges. Synthesis Lectures on Information Security, Privacy, and Trust, vol. 5, no. 2 (2014)

    Google Scholar 

  28. Tariq, M.I., Diaz-Martinez, J., Butt, S.A., Adeel, M., De-la-Hoz-Franco, E., Dicu, A.M: A learners experience with the games education in software engineering. In: Balas, V., Jain, L., Balas, M., Shahbazova, S. (eds.) Soft Computing Applications, SOFA 2018. Advances in Intelligent Systems and Computing, vol. 1222, pp. 379–395. Springer, Cham (2018). https://doi.org/10.1007/978-3-030-52190-5_27

  29. Gorski, P.L.: Developers deserve security warnings, too: on the effect of integrated security advice on cryptographic API misuse. In: Fourteenth Symposium on Usable Privacy and Security (SOUPS 2018), pp. 265–281. USENIX Association, Baltimore (2018). https://www.usenix.org/conference/soups2018/presentation/Gorski

  30. Butt, S.A., Gochhait, S., Andleeb, S., Adeel, M.: Games features for health disciplines for patient learning as entertainment. In: Das, S., Gochhait, S. (eds.) Digital Entertainment, pp. 65–86. Palgrave Macmillan, Singapore (2021). https://doi.org/10.1007/978-981-15-9724-4_4

  31. Green, M., Smith, M.: Developers are not the enemy!: the need for usable security APIs. IEEE Secur. Priv. 14(5), 40–46 (2016). https://doi.org/10.1109/MSP.2016.111

  32. Grieco, G., Grinblat, G.L., Uzal, L., Rawat, S., Feist, J., Mounier, L.: Toward large-scale vulnerability discovery using machine learning. In: ACM Conference on Data and Application Security and Privacy 12 (2016). https://doi.org/10.1145/2857705.2857720

  33. Butt, S.A., Misra, S., Luis, D.M.J., De la Emiro, H.F: Efficient approaches to agile cost estimation in software industries: a project-based case study. In: Misra, S., Muhammad-Bello, B. (eds.) Information and Communication Technology and Applications, ICTA 2020. Communications in Computer and Information Science, vol, 1350, pp. 645–659. Springer, Cham (2020). https://doi.org/10.1007/978-3-030-69143-1_49

  34. Butt, S.A., Tariq, M.I., Jamal, T., Ali, A., Martinez, J.L.D., De-La-Hoz-Franco, E.: Predictive variables for agile development merging cloud computing services. IEEE Access 7, 99273–99282 (2019)

    Google Scholar 

  35. Tian, F., Wang, T., Liang, P., Wang, C., Khan, A.A., Babar, M.A.: The impact of traceability on software maintenance and evolution: a mapping study. J. Softw.: Evol. Process 33(10), e2374 (2021)

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Shariq Aziz Butt .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2022 The Author(s), under exclusive license to Springer Nature Switzerland AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Butt, S.A., Melisa, AC., Misra, S. (2022). Software Product Maintenance: A Case Study. In: Saeed, K., Dvorský, J. (eds) Computer Information Systems and Industrial Management. CISIM 2022. Lecture Notes in Computer Science, vol 13293. Springer, Cham. https://doi.org/10.1007/978-3-031-10539-5_6

Download citation

  • DOI: https://doi.org/10.1007/978-3-031-10539-5_6

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-031-10538-8

  • Online ISBN: 978-3-031-10539-5

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics