Member-only story
Hows of documenting UX design
Is building a design document, difficult? Well, the answer lies what method you use to structure it. Learn about how to start doing design documentation.
What are use cases?
The use cases are the description that explains how the user should be able to use the product for the completion of the task. A Use case depends on ‘User’s action’ and the ‘system responses’ to the user’s action.
It is a document of actions that a user performs to achieve the certain goals and the responses received from the system to the user’s action.
It is a user-centric approach: One has to specify ‘what actions will be done by the user?’ and ‘what he will see in the system?’
It is not a system-centric approach: One does not have to specify ‘what are the inputs given to system?’ and ‘what are its output?’
Difference between use cases written by Product managers, User Experience Designer and Developers?
Product managers define the order of the task to be performed to achieve the end goal of the product.
Eg: User should be able to access the cabs nearby.
Product designers demonstrate the UI flow of the task to fulfill the goal of the product.
Eg: User should be able to view for cabs in his locality, User should be able to get visual clues about the number of cabs that are in his locality.
Developer writes as the input they require from the user and the responses that the system will show to the users.
Eg: User should be able to enter the destination location, User should be able to view the cabs within 5 KM of their vicinity
Note The exeptional case: where the situation appears when the final goal seems to be unachievable then that is called as exceptional cases.
What are the objectives of writing use cases?
•Illustrate the actions required to achieve a particular goal.
