Patching: A Techniques for Fixing Errors

Sashi Tarun*, R. Bhardwaj**, Uma Bhardwaj***
*-*** Arni University, Kathgarh, Himachal Pradesh, India.
Periodicity:April - June'2011
DOI : https://doi.org/10.26634/jse.5.4.1441

Abstract

When the software is delivered or installed and is operational at customer’s site, different problems exist in the form of errors or bugs (design errors, logic errors and coding errors). Maintenance of software life cycle is said to be very time-consuming and expensive process incurring 30%-70% cost during the software development cycle phase because it affects the other product modules also. It is the step towards more enhancements to increase the capabilities of the software by eliminating obsolete capabilities and make the product error free. It shows a team effort of different members of the development team to handle any of the tasks, when any issue or requirement arises from regular users for fulfilling their requirements. In this paper, the focus is placed on various truths, needs, issues and how patching- an adhoc emergency small program, fixes the problems using available software maintenance tools and slicing technique. The problem arises in the form of ripple effects, in front of whole development team engaged in life cycle model. The Ripple Effects change the whole picture of the product.

Keywords

Maintenance, Errors, Enhancements, Obsolete, Ripple Effects.

How to Cite this Article?

Sashi Tarun, R. Bhardwaj and Uma Bhardwaj (2011). Patching: A Techniques For Fixing Errors. i-manager’s Journal on Software Engineering, 5(4),1-5. https://doi.org/10.26634/jse.5.4.1441

References

[1]. Ashish Arora, Ramayya Krishnan. (2006). “An Empirical Analysis of Software Vendor's Patching Behavior: Impact of Vulnerability Disclosure”, ICIS 2006 Proceedings. Paper 22.
[2]. James R. Lyle, and Dolores R. Wallace, Using the Unravel Program Slicing Tool to Evaluate High Integrity Software, Technology administration, National Institute of Standards and Technology Information Technology Laboratory Gaithersburg, MD 20899.
[3]. James R. Lyle, Dolores R. Wallace, James R. Graham, Keith B. Gallagher, Joseph P. Poole, and David W. Binkley. (1987). Unravel: A CASE Tool to Assist Evaluation of High Integrity Software Volume 1: Requirements and Design, U.S. Department of Commerce Technology Administration, National Institute of Standards and Technology, Computer Systems Laboratory Gaithersburg, MD 20899
[4]. S.R. Vallabhaneni, “Auditing the Maintenance of Software”, Prentice-Hall, Inc. Publishing.
[5]. G. Parikh. (1982). “Some Tips, Techniques and Guidelines for Program and System Maintenance”, Winthrup Publishers, Cambridge, Mass. pp.65-70.
[6]. Khaled Md. Khan, BmceW. N. Lo, Torbjom Skramstad. (2001). “Tasks and Methods of Software Maintenance: A Process Oriented Framework”.
[7]. S. Black. (2001). “Computation of ripple effect measures for software”, Ph.D. thesis, SCISM, South Bank University, London, UK, 123 pp.
[8]. www.cs.ucl.ac.uk/staff/mharman /exe1.html.
If you have access to this article please login to view the article or kindly login to purchase the article

Purchase Instant Access

Single Article

North Americas,UK,
Middle East,Europe
India Rest of world
USD EUR INR USD-ROW
Online 15 15

Options for accessing this content:
  • If you would like institutional access to this content, please recommend the title to your librarian.
    Library Recommendation Form
  • If you already have i-manager's user account: Login above and proceed to purchase the article.
  • New Users: Please register, then proceed to purchase the article.