9.2.5 Maintaining Flashcards
What does maintaining code refer to?
- Correcting bugs
- Improving code efficiency (eg speed, reduced memory usage etc)
- Adding features
List reasons for maintaining software.
- Bug fixes
- Support for new hardware or software
- Support for new operating systems
- Legal or regulatory changes
- Additional features
How does intrinsic documentation contribute to the maintenance of code?
Good intrinsic documentation makes it easier to modify in newer versions as the purpose of different elements of code can be easily understood not just by the original developer.
What is a patch and how is it used in the maintenance of software.
Users need a way to update their software when changes are made.
A patch is an executable file that modifies the existing code in an installation to make these changes.
The alternative would be to have users completely reinstall the updated program.
When maintaining code, how would developers locate the section of code to be altered?
- Use of systems models to identify modules that require changes (eg structure charts, data flow diagrams).
- Once located, developers would use documentation like IPO diagrams, data dictionaries and other internal documentation to understand the code they need to modify.
What are some examples of changes that developers might make to the source code?
- Changing modules or subroutines for additional functionality
- Changing the number or type of parameters and return values
- Changing data types or data structures.
- Making modifications to the user interface.
Discuss the importance of testing when maintaining source code.
- A modular approach will enable any changes made to be tested at the module level, using existing or additional test data.
- However, if there have been changes to data types, parameters and return values, then higher level modules/subroutines that use these would need to be updated.
