Across
- 4. a system state that can lead to catastrophic consequences (i.e. death, pollution, explosions and etc.)
- 6. a defect within the system that can cause the system to enter an erroneous state.
- 7. the system of interest is the ... system
- 10. a type of fault in the system that will cause an error if encountered
- 12. an event that could happen if a system is an erroneous state and something happens to trigger the event
- 15. a loss event that occurs when a system is in a hazardous state for too long and another event triggers this. Note, this event is not guaranteed to occur if a system is in a hazardous state
- 16. a type of fault in the system that will remain present regardless of efforts
- 18. a type of fault in the system that does not cause an error if encountered
- 19. these serve as the detailed understanding of the abstract requirements. These will be implemented to the system
Down
- 1. a type of fault where the effects of the fault are observed differently by it's observer
- 2. a device that is connected to a computer which completes external tasks (i.e. printing, storing and etc.)
- 3. the overall system as a whole. Including all subsystems and peripherals
- 5. these serve as the requirements overview. They are notoriously ambiguous and are generally compiled by conducting meetings with stakeholders
- 7. the physical form to which a system is in at any particular time
- 8. A state that could lead to service failure
- 9. a type of fault that insinuates that something has broken down
- 11. this can be excessive sometimes, but it can also be the driving factor for not identifying one or more faults
- 13. the potential cause for an error to occur
- 14. a type of fault that is identified to be in response to the system design
- 17. a type of fault in the system that comes and goes and can be very unpredictable as well as hard to identify/prevent if encountered