Computer software maintenance is a critical responsibility for ICT technicians in Kenya, ensuring that software systems remain efficient, secure, and aligned with user requirements. This chapter explores the systematic approach to maintaining computer software, focusing on how to plan, schedule, and execute maintenance activities. In dynamic environments such as county government offices or banking institutions, timely software maintenance mitigates risks of downtime and data breaches, supporting seamless service delivery. Understanding software maintenance schedules and updates equips ICT technicians with the tools to enhance system reliability and user satisfaction.

3.1 Development of Software Maintenance Schedule

Developing a software maintenance schedule is foundational for effective management of the software lifecycle in professional ICT settings. It involves planning maintenance activities to anticipate and resolve software issues proactively. For example, in a university's IT department, a well-structured maintenance schedule minimises disruptions during critical academic periods such as examinations and registration. This section covers the nature of software maintenance, how to prepare a maintenance schedule, the types of maintenance, and the role of updates in sustaining software health.

3.1.1 Introduction to computer software maintenance

Software maintenance refers to the modifications and updates applied to software after its initial deployment to correct faults, improve performance, or adapt it to a changed environment. This activity is essential because software systems evolve due to changing user needs, operating environments, or emerging security threats. In a public hospital, for instance, software maintenance ensures that the patient management system remains compliant with new health reporting requirements and compatible with updated medical devices. The process extends the useful life of software and protects investments in IT infrastructure.

3.1.1.1 Importance of software maintenance

Software that is not maintained gradually becomes slow, insecure and incompatible with the equipment around it. Regular maintenance keeps systems reliable, protects data and lets an organisation get full value from the software it has paid for. For example, a SACCO that maintains its member records system regularly avoids sudden failures on days when members queue to make deposits.

The main reasons software maintenance is important are:

• Correcting defects: Software inevitably contains bugs that emerge during use. Maintenance addresses these defects to prevent system failures.
• Enhancing performance: Updates can optimise software routines to improve speed and resource usage.
• Adapting to environment changes: Changes in hardware or operating systems require software adjustments to maintain compatibility.
• Adding new features: Users' evolving needs call for feature enhancements that increase software usefulness.
• Ensuring security: Maintenance patches vulnerabilities to protect against cyber threats, which is critical for financial institutions such as SACCOs that handle sensitive data.

Impact on organisational efficiency: effective software maintenance reduces system downtime, improves user satisfaction and safeguards data integrity. For example, a retail business using point-of-sale software benefits from maintenance that prevents transaction errors and supports new payment methods, maintaining customer trust and the flow of work.

3.1.2 Prepare software maintenance schedule

Preparing a software maintenance schedule involves planning maintenance tasks on a structured timeline so that interventions happen on time without disrupting critical operations. The schedule guides ICT technicians in managing workloads and allocating resources. In a county government office, where several applications support service delivery, a maintenance schedule coordinates updates so that two activities do not clash or take down the same service at once.

Steps to prepare a software maintenance schedule

1. Identify software assets: List all software applications in use, including their versions, licence status and how critical each one is to the organisation.
2. Assess maintenance needs: Determine the type and frequency of maintenance each application requires, based on usage patterns and vendor recommendations.
3. Define maintenance activities: Specify the tasks to be done, such as bug fixes, updates, backups and performance tuning.
4. Allocate resources: Assign personnel, tools and budget to each maintenance activity so that every task has an owner.
5. Develop the timeline: Schedule activities around peak operational periods, for example placing major work in school holidays or at weekends, to minimise impact.
6. Communicate the schedule: Inform stakeholders and end-users about maintenance windows and expected downtime so that they can plan their work.
7. Review and update the schedule: Record completed tasks, note problems and adjust the schedule regularly as software, users and vendor advice change.

Sample maintenance schedule

The table below is an illustration of how entries in a schedule can be laid out for a small organisation. Real frequencies depend on the criticality of each system and the vendor's advice.

Factors influencing the schedule

• Criticality of software: Mission-critical systems require more frequent maintenance and more careful timing.
• Vendor support policies: Some software vendors mandate periodic updates and stop supporting old versions.
• User feedback: Input from users helps prioritise maintenance tasks.
• Compliance requirements: Regulatory frameworks may impose update schedules.
• Organisational capacity: The availability of skilled technicians and budget constraints affect what can be scheduled.

Tools for scheduling maintenance

Challenges in software maintenance

Software maintenance does not always run smoothly, and technicians must plan for the obstacles that can delay or reduce the quality of the work. Understanding these challenges helps in preparing realistic schedules and in justifying maintenance budgets to management.

• Resource allocation: Limited budgets in public institutions may restrict how often maintenance can be done.
• Complexity of legacy systems: Older software may lack documentation, which complicates updates.
• User resistance: Users may be reluctant to adopt changes, which affects maintenance success.
• Downtime management: Scheduling updates without disrupting operations requires careful planning.
• Keeping pace with technology: Rapid technological change demands continuous learning and adaptation by ICT technicians.

3.1.3 Types of software maintenance

Software maintenance encompasses various activities that address different aspects of software evolution and support. Recognising these types helps ICT technicians apply the appropriate intervention efficiently and plan the right amount of time and budget for it. ICT teams in universities, hospitals or banks encounter all of these types in their routine responsibilities.

3.1.3.1 Adaptive

Adaptive maintenance involves modifying software so that it remains compatible with a changing environment, such as new hardware, a new operating system version or changed business rules. The software's function stays the same, but the way it connects with its surroundings is adjusted. Example: a cooperative society updating its client management software so that it runs correctly on the latest version of its operating system is carrying out adaptive maintenance.

3.1.3.2 Perfective

Perfective maintenance enhances existing software by improving performance, usability or adding minor features, without altering its core functionality. It responds to user requests and to opportunities for improvement rather than to faults. Example: a retail company optimising its inventory software so that stock queries return faster, or adding a new report layout, demonstrates perfective maintenance.

3.1.3.3 Preventive

Preventive maintenance anticipates potential problems by making changes that reduce the chance of future faults. It includes restructuring code to make it easier to maintain, updating security settings, cleaning up databases and checking backups. Example: a hotel's booking system undergoing a security review and a database clean-up before the busy tourist season, so that it is protected against cyber-attacks and slow performance, reflects preventive maintenance.

3.1.3.4 Corrective

Corrective maintenance focuses on fixing identified faults or bugs so that the software returns to its intended working state. It is carried out after a fault has been reported or detected. Example: a hospital's patient record system may require corrective maintenance to resolve data entry errors caused by a software glitch.

Emergency maintenance is a form of corrective work that addresses critical issues causing system failures or security breaches and needing immediate attention, outside the normal schedule. An example is a SACCO's online banking platform receiving an urgent patch after a vulnerability is found to be exploited by hackers.

3.1.4 Computer software updates

Software updates are essential components of maintenance. They involve installing new versions or patches to improve software functionality, security or compatibility. Updates range from small bug fixes that correct errors and feature updates that add capabilities, to large service packs and version upgrades. For ICT technicians in financial institutions or educational facilities, managing updates is a routine task that supports operational stability.

3.1.4.1 Service packs

A service pack is a comprehensive collection of fixes, security patches and minor improvements released together by the vendor as a single installable package. It saves technicians from installing dozens of separate patches one by one and brings a computer to a known, consistent level. Example: when setting up a new computer in a college laboratory, a technician can install the latest service pack for the operating system so that all earlier fixes are applied in one step.

3.1.4.2 Version upgrades

A version upgrade replaces the installed software with a newer major release that usually brings a changed interface, new features and improved performance. Unlike a small patch, it may need a new licence, more powerful hardware and conversion of existing data to the new format. Example: an office moving from an older release of its word processing and spreadsheet suite to the next release should first check that the computers meet the hardware requirements and that existing files will open correctly.

3.1.4.3 Security upgrades

Security upgrades are patches and releases that close vulnerabilities which attackers could use to steal data, damage files or take control of a system. They are released when a weakness is discovered, so delay leaves computers exposed. Example: an accounts office that applies operating system security patches promptly reduces the risk of ransomware reaching the files that hold payroll and supplier records.

3.1.4.4 Device drivers

A device driver is a small program that allows the operating system to communicate with a hardware component such as a printer, graphics card, network adapter or scanner. Updated drivers fix hardware faults, improve performance and allow devices to work with a newer operating system. Example: if a school's new printers fail to print after an operating system upgrade, a technician downloads the latest driver from the manufacturer and installs it to restore printing.

3.1.4.5 Utility program updates

Utility programs such as antivirus software, disk clean-up and defragmentation tools, backup software and file compression tools support the running of a computer. They need to be updated so that they remain effective, for example antivirus programs must receive new virus definitions regularly to recognise recent threats. Example: a technician in a cyber café sets the antivirus to update its definitions every day and updates the backup tool so that it can read the newer file formats being used.

Methods of delivering software updates

Updates reach computers in different ways, and the method chosen depends on how critical the system is, how many computers are involved and the quality of the internet connection. Choosing the right method reduces risk and saves technician time.

• Manual updates: Technicians download and install updates individually, which is suitable for critical systems that need controlled deployment.
• Automatic updates: Software is configured to download and install updates without user intervention, which is common in antivirus software.
• Scheduled updates: Updates are deployed during off-peak hours to minimise disruption, and are often used in public sector ICT departments.
• Centralised deployment: An update server downloads updates once and distributes them to computers on the network, which saves bandwidth and allows the technician to control which updates are installed.
• Offline updates: The installer is downloaded once and copied to the computers from a flash disk or shared folder, which is useful where internet bandwidth is limited or expensive.

Best practices for managing software updates

Updates can occasionally cause new problems, such as incompatibility with other programs or failed installations. Following good practice protects users and data, and gives the technician a way back if something goes wrong.

• Testing before deployment: Validate updates in a controlled environment, such as one test computer, to prevent introducing new issues.
• Backup before update: Ensure data and system backups exist so that the system can be rolled back if the update fails.
• User communication: Inform users about update schedules and expected impacts.
• Compliance monitoring: Verify that updates meet regulatory and organisational standards.
• Documentation: Record update details, such as date, version and the technician responsible, for audit trails and future reference.

Chapter Summary

This chapter explored the development of a software maintenance schedule, emphasizing the importance of regular maintenance to ensure software reliability and performance. It outlined the preparation of such schedules and detailed the various types of software maintenance, including adaptive, perfective, preventive, and corrective. The chapter also examined different computer software updates, such as service packs, version upgrades, security updates, device driver updates, and utility program updates. Monitoring software functionality was discussed with a focus on tools and the use of operating system event logs, alongside the types of event logs commonly used. The process and significance of conducting software upgrades and updates were covered, highlighting their role in maintaining software effectiveness and security. Finally, the chapter addressed safety procedures during software maintenance activities, detailing the use of personal protective equipment and proper handling of tools and equipment to safeguard users.