Head First Software Architecture

Table of Contents (the real thing)

• How to use this Book: Intro

  Because software architecture is hard, your brain will trick you into thinking you can’t learn it. Your brain’s thinking, ”Better to focus on more important things, like what to eat for lunch and whether pigs have wings.” The good news is that you CAN trick your brain into thinking software architecture is an important skill to learn, and in this chapter we’re going to show you just how to do that.

  • “Who is this book for?”

  • “We know what you’re thinking”

  • “We know what your brain is thinking”

  • “Metacognition: Thinking about thinking”

  • “Here’s what WE did”

  • “Here’s what YOU can do to bend your brain into submission”

  • “Read me”

  • “Do it yourself chapters”

  • “The technical review team”

  • “Joint acknowledgments”

  • “Individual acknowledgments”

• Chapter 1

  Software architecture is fundamental to the success of your system. This chapter demystifies software architecture. You’ll gain an understanding of architectural dimensions and the differences between architecture and design. Why is this important? Because understanding and applying architectural practices helps you build more effective and correct software systems—systems that not only function better, but also meet the needs and concerns of the business and continue to operate as your business and technical environments undergo constant change. So, without further delay, let’s get started.

  • “Building your understanding of software architecture”

  • “Building plans and software architecture” ...