A detailed discussion of these questions can be found in the "Appendix A" section on page 519.
How does project size affect your software design and the work involved in creating it?
Is a well-documented bad design better than an undocumented good one?
How can you measure the design quality of a piece of code? How can you quantify its simplicity, elegance, modularity, and so on?
Is design a team activity? How important are teamworking skills in creating a good design?
Are different methodologies more suitable to different projects?
In what ways can you determine whether a design is highly cohesive or weakly coupled?
If you've solved a similar design problem in the past, how good an indicator is it of how difficult this problem ...