Knowing what problem to solve is sometimes easier said than done. Since we create software to help people, we must understand the people whose lives will be affected by the software we make to understand the problem thoroughly. The better we empathize with their needs, the better we’ll see and understand the real problems that need to be solved.
We call people with an interest or concern in our software stakeholders. It’s the architect’s job to identify stakeholders and understand their needs. Our stakeholders’ expectations for the system will directly or indirectly influence how we design it.
Empathy is the engine that drives design. When you empathize with the people affected by your software, then you’ll make better software. In this chapter, you’ll learn how to decide who to talk to about the problem you’re solving and what you need to learn from them to start designing the architecture.
18.217.222.205