Identifying capabilities and features
In Chapter 1, The Requirements Domain, we identified two of the main entities in the requirements domain: stakeholders and goals. In the previous section about impact mapping, we saw how these entities slot perfectly into an impact map. It's time now to look at the other two main entities that constitute the requirements domain and how they are all represented within an impact map.
In the Introduction to impact mapping section earlier in this chapter, we saw how the third and fourth levels of an impact map correspond to the business and system impacts of a stakeholder's effort to accomplish their goal, respectively. We shall define the business impact as a capability. A capability is a stakeholder's required ability to do something with our system in order to reach their goal. We shall define the system impact as a feature. A feature is a system functionality or behavior required in order to support a capability. Let's now...
