9. Can a system ever be completely "decoupled"? That is, can the degree of coupling be reduced so much that there is no coupling between components? Why or why not?
10. Are there some systems that cannot be made completely functionally cohesive? Why or why not?
11. For each of the quality attributes in the quality models of Chapter 1, explain how the characteristics of good design contribute to the product quality. For example, how do coupling, cohesion, and molecularity affect reliability and tractability?
12.A recursive component is one that calls itself or in some way refers to itself. Given the design guidelines presented in this chapter, is a recursive component a good or a bad idea? Why?
13. For a complex module that you have already developed for another project, specify the module at varying degrees of abstraction (according to the descriptions in Sidebar 6.3). How might each abstraction be distinctly useful?
16. Consider a module that takes two arrays of integers, and creates and returns a new array of integers whose elements are the sums of the respective elements of the input arrays. How might this module fail? If this module were responsible for recovering from these failures, how might it do so?
Other samples, services and questions:
When you use PaperHelp, you save one valuable — TIME
You can spend it for more important things than paper writing.