Think about user actions in a way of HOW he will de it, not WHAT he will do(this is already described in documentation)
how he inputs the data(all the filters, text boxes, comboboxes, checkboxes etc)
how the requested data will be shown to him(i.e. there's a bunch of places, which satisfies his request - where and how to show them?)
how is he supposed to view details of specific institution(where to click, where to show the details)
how will he authenticate via other system(again where to click, how is he notificated about successfull authentication etc)
how should he vote for place?
how should he mark the place as his favorite?
how should he review his own places, places he voted for, places of other users(hint - where does these questions best fit beying other question?)
how should he add a new place(how big will be the data-input form, what data shoudl user put into, where to place this form etc)
how should he grant\deny to let others to view his places
how should he write a comment about the place?
how to show errors to user?
So the task for you is to design these scenarios - every single detail from point of view of user.
The best option would be to write about these scenarios in details and to have visual representation of them - it doesn't matter if it's made in html, paint, photoshop, paint on paper or anything else - just so that others can see it
if you come up with other scenarios - you're welcome to design them too
Think about user actions in a way of HOW he will de it, not WHAT he will do(this is already described in documentation)
So the task for you is to design these scenarios - every single detail from point of view of user. The best option would be to write about these scenarios in details and to have visual representation of them - it doesn't matter if it's made in html, paint, photoshop, paint on paper or anything else - just so that others can see it
if you come up with other scenarios - you're welcome to design them too