RU ITEC421 Dealing with Faults
Across
- 3. Process of returning a computer system, network, or service to its normal or functional state after a disruption, fault, or outage.
- 4. The ability of a system to continue operating properly in the event of the failure of some of its components.
- 6. The proactive process of identifying and removing faults or defects within a system before it is deployed or put into operation.
- 7. The strategy of proactively preventing or mitigating potential issues, errors, or faults before they occur or manifest.
- 9. The process of creating copies of data or files to prevent data loss in case of accidental deletion, corruption, or hardware failure.
- 10. The ability of a system to deliver services that can justifiably be trusted.
- 13. The process of identifying and removing faults, errors, or defects from a system or software application.
- 14. A process or phenomenon that involves randomness or probability.
- 16. A software tool that translates source code written in a high-level programming language into machine code or bytecode that can be executed by a computer.
- 19. The act of closely inspecting or scrutinizing something in order to assess its condition, identify any issues or faults, and gather information.
Down
- 1. The process of assigning an initial value to a variable or data structure at the beginning of its usage within a program.
- 2. The process of making a system or software application available and accessible for use in a live environment.
- 5. The proactive analysis and prediction of potential faults or failures in a computer system before they occur.
- 7. The extent to which a particular method, technique, or solution is suitable or appropriate for addressing a specific problem or fulfilling a particular requirement within the context of computing systems.
- 8. Faults that arise due to gradual deterioration or weakening of system components over time.
- 11. Type of fault in a distributed computing system where components exhibit arbitrary and inconsistent behavior, potentially including malicious actions such as lying or sending conflicting information to different parts of the system.
- 12. Measurable quantities or parameters used to assess various aspects of a system, process, or performance.
- 15. The process of evaluating the extent of harm or disruption caused by a fault, error, or malicious attack within a computer system or network.
- 17. To defects or flaws in the fundamental design of a system or software that can lead to errors or malfunctions.
- 18. An abnormal condition or defect in a system, software, or hardware component that may lead to malfunctions or errors in its operation.