What are the limitations of financial analyses as control mechanisms in a DFTS process? Give some examples of nonfinancial control mechanisms. What can go wrong when such analyses lose sight of customer requirements and focus only on the software developer's internal objectives?
2.
Discuss the need for visibility and control in a software development process. Specify with examples the challenges of providing visibility and control. What are their implications?
3.
Discuss the limitations of the CoSQ approach given the difficulties of knowing and estimating even the most important costs. How much can you depend on quantitative analysis for taking quality initiatives? What else should you consider?
4.
Explain the need to incorporate ABC into the software development process. When is it most recommended? When is it not?
5.
Explain the limitations of financial metrics in evaluating a quality initiative. How can they be addressed?
6.
Interview the appropriate managers in a software development company to determine if and how they measure the cost of quality. If they do, find out how useful their experience has been. If they don't, ask why not.
7.
Explain the difference between the "specification-based" approach to quality loss and Taguchi's concept of Quality Loss Function. Illustrate with specific examples in a software development context.
8.
What does Taguchi mean by "loss to society"? Is it possible to measure all these losses? What does Taguchi propose in this context?
