Page 251 -

222 PART TWO MANAGING SOFTWARE PROJECTS

8.9. A formal technical review is effective only if everyone has prepared in advance.
How do you recognize a review participant who has not prepared? What do you do
if you're the review leader?

8.10. Some people argue that an FTR should assess programming style as well as
correctness. Is this a good idea? Why?

8.11. Review Table 8.1 and select four vital few causes of serious and moderate
errors. Suggest corrective actions using information presented in other chapters.

8.12. An organization uses a five-step software engineering process in which errors
are found according to the following percentage distribution:
Step Percentage of errors found
1 20%
2 15%
3 15%
4 40%
5 10%
Using Table 8.1 information and this percentage distribution, compute the overall
defect index for the organization. Assume PS = 100,000.
8.13. Research the literature on software reliability and write a paper that describes
one software reliability model. Be sure to provide an example.
8.14. The MTBF concept for software is open to criticism. Can you think of a few
reasons why?
8.15. Consider two safety critical systems that are controlled by computer. List at
least three hazards for each that can be directly linked to software failures.

8.16. Using Web and print resources, develop a 20 minute tutorial on poka-yoke and
present it to your class.

8.17. Suggest a few poka-yoke devices that might be used to detect and/or prevent
errors that are commonly encountered prior to “sending” an e-mail message.

8.18. Acquire a copy of ISO 9001 and ISO 9000-3. Prepare a presentation that dis-
cusses three ISO 9001 requirements and how they apply in a software context.

FURTHER READINGS AND INFORMATION SOURCES

Books by Moriguchi (Software Excellence: A Total Quality Management Guide, Produc-
tivity Press, 1997) and Horch (Practical Guide to Software Quality Management, Artech
Publishing, 1996) are excellent management-level presentations on the benefits of
formal quality assurance programs for computer software. Books by Deming [DEM86]
and Crosby [CRO79] do not focus on software, but both books are must reading for