Chapter 3 · Practice 3 of 3
Name the users and stakeholders and what each needs
Why it matters
Even a short proposal should say who the system is for. List each type of user or stakeholder with one line about what they need:
- Pharmacist: record stock quickly during busy hours.
- Pharmacy owner: see losses and expiring stock at a glance.
- Supplier (optional): receive return requests for near-expiry stock.
The FAST handbook's development report format, for instance, includes a stakeholder summary and the "key high level goals and problems of stakeholders" as part of the project vision. Getting this right early makes requirements, testing and the final demo far easier, because you know whose task you are demonstrating.
Do
- List each user type with its main need
- Mark which users you will actually test with
Avoid
- Writing "general public" as the only user