Problem 2
Explain why it is practically impossible to validate reliability specifications when these are expressed in terms of a very small number of failures over the total lifetime of a system.
Problem 4
Is it ethical for an engineer to agree to deliver a software system with known faults to a customer? Does it make any difference if the customer is told of the existence of these faults in advance? Would it be reasonable to make claims about the reliability of the software in such circumstances?
Problem 5
Explain why ensuring system reliability is not a guarantee of system safety.
Problem 8
Suggest how you would go about validating a password protection system for an application that you have developed. Explain the function of any tools that you think may be useful.
Problem 9
Why is it necessary to include details of system changes in a software safety case?
Problem 10
List four types of systems that would require system software safety cases.
Problem 11
Assume you were part of a team that developed software for a chemical plant, which failed in some way, causing a serious pollution incident. Your boss is interviewed on television and states that the validation process is comprehensive and that there are no faults in the software. She asserts that the problems must be due to poor operational procedures. A newspaper approaches you for your opinion. Discuss how you should handle such an interview.
Problem 12
What are the arguments for and against the licensing of software engineers?
