RU ITEC421 - Software Dependability
Across
- 3. The ability of a software system to recover quickly and effectively from failures or disruptions.
- 4. The event in which a software system deviates from its expected behavior, resulting in incorrect or unexpected outcomes.
- 6. _____ Assessment The process of evaluating potential risks and their impact on the dependability of a software system.
- 8. The extent to which a software system is operational and accessible when needed for use.
- 9. The process of ensuring that a software system meets its specified requirements and behaves as expected.
- 10. _____ Failure A severe and widespread failure of a software system that leads to significant disruption or loss of functionality.
- 12. The ease with which a software system can be modified, repaired, or enhanced over its lifecycle.
- 15. The gradual deterioration in the performance or reliability of a software system over time.
- 17. The ability of a software system to consistently perform its intended functions correctly under specified conditions.
- 18. The overall property of a software system that encompasses its reliability, availability, safety, and security.
- 20. The property of a software system that ensures it does not cause harm to users, other software systems, or the environment.
Down
- 1. _____ Detection The process of identifying and flagging errors or anomalies in a software system's behavior or output.
- 2. The inclusion of additional components or resources in a software system to provide backup or failover capabilities.
- 5. The process of implementing measures to reduce the likelihood or severity of risks to a software system's dependability.
- 7. Any potential source of harm or danger associated with the use of a software system.
- 11. The property of a software system that ensures sensitive information is not disclosed to unauthorized individuals or entities.
- 13. The property of a software system that ensures data remains unchanged and is protected against unauthorized modification.
- 14. The process of confirming that a software system satisfies the needs and expectations of its users and stakeholders.
- 16. _____ Tolerance The ability of a software system to continue operating despite the presence of hardware or software faults.
- 19. _____ Correction The process of identifying and rectifying errors or anomalies in a software system's behavior or output.