RU ITEC421 - Software dependability
Across
- 1. mathematical approach to software specification and verification (includes a "-")
- 3. detailed description of a system’s behavior and constraints
- 4. activity that systematically explores model states
- 5. process of turning abstract specs into executable code
- 6. a necessary process for personnel to properly use rigorous methods
- 7. goal of ensuring software behaves as intended
- 9. confirms you're building the system *right*
- 10. the specific trait of software where one small defect can cause failure
- 12. symbolic languages used for software artifacts (gives more info)
- 16. automatic generation of code from formal models
- 17. fault-finding method performed during program execution (includes a "-")
- 18. confirms you're building the *right* system
- 19. all phases from software concept through retirement (one word)
Down
- 2. incorrect belief about how dependability techniques work
- 5. kind of analysis to identify underlying fault sources (includes a "-")
- 8. removing faults that have already been introduced into the software
- 11. strategy aiming to prevent software faults from being introduced
- 13. software that supports engineers in developing dependable systems
- 14. development strategy using abstract representations of system behavior (includes a "-")
- 15. fault-finding method that does not require program execution (includes a "-")