Chapter 4. The Architectural Perspective

FAQ 4.01 What is the purpose of this chapter?

FAQ 4.02 Why is software architecture important?

FAQ 4.03 What should the architecture be based on, the problem being solved or the problem domain?

FAQ 4.04 Should the software architecture be based on the policy of the problem?

FAQ 4.05 Do customers ever change their requirements?

FAQ 4.06 Are stable requirements desirable?

FAQ 4.07 What is the key to planning for change?

FAQ 4.08 What is a framework?

FAQ 4.09 What is the "inversion of control" exhibited by frameworks?

FAQ 4.10 What is an extensible, domain-specific framework?

FAQ 4.11 What characteristics make a framework extensible yet domain-specific?

FAQ 4.12 What happens if the domain analysis is incorrect?

FAQ 4.13 How much effort should be expended to support change that is, how much is extensibility worth?

FAQ 4.14 How does an architect make the software architecture flexible?

FAQ 4.15 What is the secret to achieving reuse?