The document discusses software maintenance and modifications to meet changed requirements. It describes identifying reasons for changes, locating sections of code to alter, determining necessary changes, implementing and testing solutions. Key aspects of maintenance include communication between users and developers, understanding original code documentation, analyzing impacts of changes, and thoroughly testing modifications.

1. Maintenance Of Software Solutions Modification of the code to meet changed requirements

2. Syllabus Modification of the code to meet the changed requirements. Identification of the reasons for change in code, macros and scripts. Location of section to be altered. Determining changes to be made. Implementing and testing solutions.

3. Maintenance of Software Maintenance of involves two major components: Maintenance of Software Solutions Modification of Code Documentation of Changes

4. What is Maintenance? Maintenance is an ongoing process of correction and refinement. Maintenance is required if products are to continue to meet user expectations over their lifetime. Maintenance include: Correction of errors (bugs) Upgrades to meet new or changes in requirements.

5. What is Maintenance? THREE different types of software maintenance are: Corrective Maintenance – This relates to the occurrence of a bug or error. Normally, require a patch to fix and are relatively inexpensive.

6. What is Maintenance? Adaptive Maintenance – Involves changing the program to meet some change such as new hardware or OS. Identify an actual example of adaptive maintenance. GST Wireless

7. What is Maintenance? Improvement Maintenance – Adds new functions or requirements to meet new user needs.

8. What is Maintenance? Maintenance requires a cyclical approach. Developer Users Communication Identifying Modifying Documenting

9. What is a Patch? Used to correct a problem in a software solution. A patch is an actual piece of executable code that is inserted into (Patched into) an existing program.

10. Modifications to meet changed requirements Software solutions are continually evolving. Changes made to subsequent releases of applications are often the result of user requests. Remember, fulfilling the needs of end-users is the primary function of all software products.

11. Modifications to meet changed requirements Basically modifications can involve the following: Patches Macros Scripts Replacement modules Overhaul of code.

12. Identification of the reasons for change in code, macros and scripts Because custom software is written to solve a particular problem, minor changes often necessitate alterations to source code. This may cause marco and script commands to change resulting in unexpected errors. Other applications that are linked to a product may require an upgrade as well. Called the Domino Effect.

13. Identification of the reasons for change in code, macros and scripts If upgrades or modifications are undertaken this may have an effect on other modules.

14. Identification of the reasons for change in code, macros and scripts Reasons for change include: Bug Fixes New hardware New software Changed user requirements Organisation restructuring

15. Identification of the reasons for change in code, macros and scripts What is a Macro? A symbol, name, or key of commands that activates a series of commands that have been recorded. What is a Script? A list of commands that are executed with out user interaction. Loaded automatically

16. Discussion Video Studio Pro uses Microsoft’s Media Player to play video sequences. Microsoft has just released a new version of Media Player that is more graphically rich in regards to the interface. Video Studio Pro does not contain sufficient space for the use of the new Media Player. Many end-users have contacted the company in regards to upgrading this problem.

17. Response Questions 1.) Identify what the company could do to solve this problem. 2.) How could this problem be avoided in the future.

18. Response Answers 1.) Creation of a patch that will enable changes in software and hardware requirements. For example freeing up space to process the new interface. 2.) This problem could be avoided by creating their own media player then they dictate the upgrades.

19. Identification of section to be altered Once a decision has been made, the location of the section to be altered needs to be determined. Structure diagrams and data flow diagrams will assist in locating module requiring modification. Once the module has been identified the programmer can analyse the IPO charts, algorithms and source code to gain a understanding.

20. Identification of section to be altered Two approaches that will help in deciding what exactly has to be changed, include: Communication between users and the modification team. Thorough understanding of the original code through study of the original documentation.

21. Identification of section to be altered Identify FOUR examples of communication methods that would be used to promote communication between the users and the modification team.

22. Identification of section to be altered Answers: Interviews Observations Questionnaires Research

23. Identification of section to be altered Outline what documentation a modification team may analyse in order to gain an understanding of a software solution.

24. Identification of section to be altered Answers: Objectives Data Flow Diagram System Flowcharts Algorithms Source Code Code Comments

25. Determining Changes to be made Once the module and code have been located it is now time make the appropriate changes. Depending on the nature of the modification, changes may be required to data structures, files and the user interface. Consequences of modifications must be investigated thoroughly.

26. Determining Changes to be made It may be important to analyse modifications regarding the following criteria: Priority – (Are they urgent) Extent – (Number of changes to be made) Personnel – (Who will do the changes) Expertise – (Are their enough skills evident to make the changes) Downtime

27. Implementing and testing the solution Once the changes have been completed they need to be implemented and tested. Changes to modules that alter parameters will require modifications to each higher-level calling module.

28. Activity 1 Identify THREE factors that could help make a program easier to maintain.

29. Activity 1 Answer Module Independence – The ability to change one component of the program without affecting other modules. Internal Documentation – Good structure and use of intrinsic documentation. Program Testing – The better the testing , the fewer errors that will eventuate.

30. Activity 2 A software company produces a product that automates recorded keeping in doctors surgeries. As part of the contract the company provides an annual update of the program. The company has maintained a database of support calls to identify the modifications needed for each upgrade.

31. Activity 2 The table below lists the top 10 issues: 15 Loss of network connection is not notified until save operation is initiated. 38 Scheduling of doctors does not take into account multiple surgery locations within one practice. 17 Program crashes once two referrals are printed for one patient. 39 Unable to import drug references from a new health department database. 18 Individual patient records can only be viewed one terminal at a time. 56 Standard HP printer driver not accessible. 24 Need to minimise application so other programs can be used. 59 No report available to list frequency of drug prescription by a doctor. 29 Cancelled appointments are not made available immediately. 65 Need to link members of the same family. Frequency Issue Frequency Issue

32. Activity 2 Categorise each of the ten issues as either bugs in the application, hardware issues or changes to program requirements.