Answer to Question 1
When developing safety-critical systems, a key assumption must be that safety will not automatically result from following an organizations standard development methodology. Safety-critical software must go through a much more rigorous and time-consuming development process than other kinds of software. All tasksincluding requirement definition, systems analysis, design, coding, fault analysis, testing, implementation, and change controlrequire additional steps, more thorough documentation, and vigilant checking and rechecking. As a result, safety-critical software takes much longer to complete and is much more expensive to develop.
Answer to Question 2
Reliability and safety are two different system characteristics. Reliability has to do with the capability of the system to continue to perform; safety has to do with the ability of the system to perform in a safe manner. Thus, a system could be reliable but not safe. For example, an antiaircraft missile control system may continue to operate under a wide range of operating conditions so that it is considerably reliable. If, however, the control system directs the missile to change direction and to fly back into its launching device, it is certainly unsafe.
Team of geologists collecting samples for paleomagnetic analysis at Sangiran, Java.
Display piece, Yoruba culture.
Example of a patient’s ledger in practice management software.
Cradle the head briefly in both hands to end this section.
Cradle the head briefly in both hands to end this section. Hold for a few seconds until you can feel ...
Java Software Solutions: Foundations of Program Design