A software developer might have a different “mental image” of the software than the users which may be different than the stakeholders. However, since the user is the one who will be using it, shouldn’t they be the one who has the most consideration for the interface?
This doesn’t necessarily mean talking them about what they would want. They can get easily side tracked about color (I knew one person who always wanted it more blue – no matter what was being discussed), size, or position on their screen – not thinking about the many other users who would need to use it.
When thinking about the user, it’s helpful to ask certain questions:
- Are they technical? If so, how technical?
- How much education do they have?
- What’s their age?
- Will their age, or physical limitations, limit what can be done? (think eye sight)
- Will this be used all the time, or only occasionally?
- Will people with multiple (primary) languages being using it?
There are many more questions that can be asked, some are listed in the book.
When you think about a task the user must preform, it is helpful to make sure everything they need to do it is easily accessible.
- What work will the user perform in specific circumstances?
- What tasks and subtasks will be performed as the user does the work?
- What specific problem domain objects will the user manipulate as work is performed?
- What is the sequence of work tasks—the workflow?
- What is the hierarchy of tasks?
You use cases should help you identify what the tasks and sub-tasks will be.
Interface Analysis was originally found on Access 2 Learn
