Please enable JavaScript.
Coggle requires JavaScript to display documents.
SYSTEM OPERATION AND SUPPORT - Coggle Diagram
SYSTEM OPERATION AND SUPPORT
Maintenance Classifications
Corrective maintenance
Diagnoses and corrects errors in an operational
system
Example: Resolving a software bug that is causing system crashes.
Adaptive Maintenance
Adds enhancements to an operational system and
makes the system easier to use.
Example: Adding new features to a software application to meet changing user needs.
Perfective Maintenance
Involves changing an operational system to make it
more efficient, reliable or maintainable. Can improve system reliability
Two techniques = 1) reverse engineering. 2) reengineering
Example: Making changes to a system to improve its scalability.
Preventive Maintenance
Reverse engineering includes changes to an operational system that reduce the possibility of future problems
Example: Backing up data regularly. This is one of the most important preventive maintenance tasks that can be performed. By backing up data regularly, you can ensure that it is safe and secure in case of a system crash or other disaster.
Configuration Management
Configuration management (CM) is a process for tracking and managing the configuration of a system. This includes tracking the hardware, software, and documentation that make up the system, as well as the changes that are made to these components over time.
CM is important for system operation and support because it helps to ensure that the system is always in a known good state. This means that the system is working as expected and that it is not vulnerable to security risks. CM also helps to make it easier to troubleshoot problems and to recover from outages.
Release Methodology
a process for planning, scheduling, testing, deploying, and controlling software releases. It ensures that release teams efficiently deliver the applications and upgrades required by the business while maintaining the integrity of the existing production environment.
Pros
can help to improve communication between the different teams involved in the release process.
can help to reduce the risk of errors and problems during the release process.
can help to improve compliance with regulations.
can help to increase visibility into the release process.
improve the efficiency of the release process.
Cons
can be complex to implement and manage. This can be a challenge for organizations that do not have a lot of experience with release management.
Resistance to change: Some teams may be resistant to change and may not want to adopt a new release methodology.
Cost: Release methodologies can be expensive to implement and maintain. This can be a challenge for organizations that have limited resources.
Performance and Workload Measurement
Turnaround time: The total amount of time it takes for a process to complete. This includes the time it takes to submit the request, the time it takes the system to process the request, and the time it takes to return the results.
Throughput: The amount of data that is successfully transferred over a network connection in a given amount of time.
Bandwidth: The maximum amount of data that can be transferred over a network connection in a given amount of time.
Response time: The time it takes for a system to respond to a request.
Response time, bandwidth, throughput, and turnaround time are all terms used to measure the performance of computer systems and networks. They are all related, but they measure different aspects of performance.