Get Thinking

A detailed discussion of these questions can be found in the "Appendix A" section on page 522.

Mull It Over

  1. Define where architecture ends and software design begins.

  2. In what ways can a bad architecture affect a system? Are there parts that wouldn’t be affected by architectural flaws?

  3. How easy is it to repair architectural deficiencies once they become apparent?

  4. To what extent does architecture affect the following things?

    1. System configuration

    2. Logging

    3. Error handling

    4. Security

  5. What experience or qualifications are required to be called a software architect?

  6. Should sales strategy influence architecture? If so, how? If not, why?

  7. How would you architect for extensibility? How would you architect for performance? How do these design goals affect the ...

Get Code Craft now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.