I have been assigned to gather requirements for a UI, document them, and provide it to the developers to build using those requirements. I am totally lost and literally have no guidance at my current job. I work for a marketing company, which sells products for ATT, Dish Network, Verizon and more. It is a call center. I've side-jacked with the agents and learned the programs they are using. I understand the program and the functionalities they need. But I am totally lost how to document requirements for a UI! My development team is waiting for me to provide them with requirements which they will use to build the application. Help-> what are some examples of requirements for a UI. How are they worded? Has anyone ever document requirements for a UI which they can share, will be much appreciated (email: [email protected]). Any guidance will be much much appreciated!!!
Thanks a million.
Hi Mohammed,
I presume, by UI requirements, your developers are asking you to spec the screens they need to build? First thing to find out then is what are the business requirements that are realised by the need to build screens? Have you gathered these yet?
My advice is to go your business users and ask them what they want. It could be that you need screens. Perhaps it isn't that at all. Maybe they need a change in their processes. Who knows. Just don't start your requirements journey by looking at the solution until you know what the problem is.
Good luck,
Kimbo
Looks like Nick answered your question in another post.
To define a screen do this:
1. Define the screen layout - checkout Balsamiq. Good tool for this.
2. Define each field and the source for the field
3. If you have grids on the screen, define the default selection and sorting and any filters on the grid.
4. Define defaults for each field
5. Define validation rules for each field and generally
6. Define each action that can be taken on the screen and the result of the action
Back in the day I used to say there were 8 things to do but I forget the other two. Anyway that's a good start.
"Looks like Nick answered your question in another post"
I might be too technical ...
brought to you by enabling practitioners & organizations to achieve their goals using: