Software Maintenance? Didn’t they teach you that in school?
You just graduated from school last week in Computer Science to be a developer, and it is you second week on your new “high paying” [ah!] entry level job. You boss just ask you to go and fix this bug that the customer just found, thinking it would be a good idea to get introduced to the software system that was written before you were born. Oh, and he want to know how long it will take to fix it. You tell him that you don’t know to fix other peoples code nor how long it would take. He ask, “Why not, didn’t they teach you that in school?”
Purpose
The purpose of this blog is to identify tools, techniques, and methodologies to improve the peon programmer, like myself, ability to solve software maintenance problems.
Overview of Software Maintenance
Since the invention of “HelloWorld” there has been software maintenance. It has gone by different names, from debugging, operations and maintenance, operations & support, new features, etc. But purpose has stay the same, fix problems with existing code and/or add new features with out adding new problems.
E.B. Swanson[1] initially identified three categories of maintenance: corrective, adaptive, and perfective. These have since been updated and ISO/IEC 14764 presents:
• Corrective maintenance: Reactive modification of a software product performed after delivery to correct discovered problems.
• Adaptive maintenance: Modification of a software product performed after delivery to keep a software product usable in a changed or changing environment.
• Perfective maintenance: Modification of a software product after delivery to improve performance or maintainability.
• Preventive maintenance: Modification of a software product after delivery to detect and correct latent faults in the software product before they become effective faults.
Why should I learn to do software maintenance?
Have you ever had to read you own code from six month ago? Have you ever had to review someone else’s code? Have you had to read documentation about you favorite software, and discovered it is not up to date? Have you had to use freeware, and make modification? If so, you have done software maintenance.
Reference
1. http://en.wikipedia.org/wiki/Software_maintenance
October 3, 2007
WorkingEffectivelyWithLegacyCode
Working Effectively with Legacy Code (Robert C. Martin Series) (Paperback)
From the Back Cover
Get more out of your legacy systems: more performance, functionality, reliability, and manageability
Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts.
In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his renowned Object Mentor seminars: techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control.
The topics covered include
* Understanding the mechanics of software change: adding features, fixing bugs, improving design, optimizing performance
* Getting legacy code into a test harness
* Writing tests that protect you against introducing new problems
* Techniques that can be used with any language or platform—with examples in Java, C++, C, and C#
* Accurately identifying where code changes need to be made
* Coping with legacy systems that aren't object-oriented
* Handling applications that don't seem to have any structure
This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.
Product Details
* Paperback: 456 pages
* Publisher: Prentice Hall PTR (September 22, 2004)
* Language: English
* ISBN-10: 0131177052
* ISBN-13: 978-0131177055
http://www.amazon.com/exec/obidos/ASIN/0131177052/codinghorror-20
http://www.objectmentor.com/resources/articles/WorkingEffectivelyWithLegacyCode.pdf
From the Back Cover
Get more out of your legacy systems: more performance, functionality, reliability, and manageability
Is your code easy to change? Can you get nearly instantaneous feedback when you do change it? Do you understand it? If the answer to any of these questions is no, you have legacy code, and it is draining time and money away from your development efforts.
In this book, Michael Feathers offers start-to-finish strategies for working more effectively with large, untested legacy code bases. This book draws on material Michael created for his renowned Object Mentor seminars: techniques Michael has used in mentoring to help hundreds of developers, technical managers, and testers bring their legacy systems under control.
The topics covered include
* Understanding the mechanics of software change: adding features, fixing bugs, improving design, optimizing performance
* Getting legacy code into a test harness
* Writing tests that protect you against introducing new problems
* Techniques that can be used with any language or platform—with examples in Java, C++, C, and C#
* Accurately identifying where code changes need to be made
* Coping with legacy systems that aren't object-oriented
* Handling applications that don't seem to have any structure
This book also includes a catalog of twenty-four dependency-breaking techniques that help you work with program elements in isolation and make safer changes.
Product Details
* Paperback: 456 pages
* Publisher: Prentice Hall PTR (September 22, 2004)
* Language: English
* ISBN-10: 0131177052
* ISBN-13: 978-0131177055
http://www.amazon.com/exec/obidos/ASIN/0131177052/codinghorror-20
http://www.objectmentor.com/resources/articles/WorkingEffectivelyWithLegacyCode.pdf
Subscribe to:
Posts (Atom)
Posts
