Dependable Computing 2

2. necessary assurance that an issue will be solved.
4. a single defective line of_ is more than enough to cause a catastrophic failure.
5. implementation created from mechanical specification.
7. software built by creating multiple variations of transformations from abstract specifications.
8. _methods target processing efficiency.
11. active examination of a system to locate faults.
13. thorough evaluation of a systems specifications and faults.
14. due to human error, humans are_
15. expressed as bits in memory and patterns in hardware
16. methods that are not derived from a technical structure or background.
17. real-time software that runs itself.
18. fault caused by the time of use/overuse that causes degradation
20. routine procedures that upkeep and upgrade systems and machinery.

1. begins with requirements then specifications and lastly, implementation
3. one representation of software is the executable, correct refinement of another.
6. anything done without precision.
9. formal verification that displays an implied specification implementation.
10. always include an_else clause in a case statement.
12. hypothesized cause of error.
19. no single definition of any natural language.