Maintenance Classifications

Corrective Maintenance

  • diagnose and fix logic errors
  • replace defective network cabling
  • restore proper configuration settings
  • debug program code
  • update drivers
  • install software patch

Adaptive Maintenance

Perfective Maintenance

Preventive Maintenance

  • add online capability
  • create new reports
  • add new data entry field to input screen
  • install links to website
  • create employee portal
  • install additional memory
  • write macros to handle repetitive tasks
  • compress system files
  • optimize user desktop settings
  • develop library for code reuse
  • install more powerful network server
  • install new antivirus software
  • develop standard backup schedule
  • implement regular defragmentation process
  • analyze problem report for patterns
  • tighten all cable connections

Configuration Management

  • Most maintenance projects require documentation changes
  • As enterprise-wide information systems grow more complex, configuration management becomes critical
  • Makes your systems such as servers, networks, operating systems, data centers, configuration files, IT assets and all other configuration items work
  • A systems engineering process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life

Release Methodology

  • A numbering pattern distinguishes the different releases

Pros:


  • Reduces the documentation burden


  • Entire things are tested prior to the maintenance work which helps in reducing the cost

  • Service packs
  • The entire noncritical changes are gathered and implemented at the same time

Cons:


  • New features or upgrades are available less often


  • Gathering of the requirement initially require interaction of the user this is the main disadvantages of the release methodology

Definition Terms

Response Time

Turnaround time

Throughput

Bandwidth

  • measured as the overall time from the request of any activity related to the system to the delivery of that request to the user.
  • explained as the amount of the information or data handle by a system in the given period of the time.
  • expresses the transfer rate of the data which is used for measuring the performance of the system in the given circumstances.
  • basically applied for the operations of centralized batch processing type. It is the time from the submission of the request to the fulfillment of the request and displays the output to the user.

How are the terms related?

  • The IT department often measures response time, bandwidth, throughput, and turnaround time to evaluate system performance both before and after changes to the system or business information requirements.
  • Management uses current performance and workload data as input for the capacity planning process.