Article Idea:
how to use functional requirements
suggested by robert coyle on 2007/10/28
Hi there,
I want to propose an article relating to web design. Id like to elaborate on an intermediate stage in the design process for people who still might not get it.. like me for a long while. Take a look at these two stages in a design process.
1 – gather functional requirements (user and business)
2 – use these to create a) navigation and b) wireframes for front page and sub page etc
Now for me the task of converting a list of fucntional requirement into navigation and a well layed out front page takes a bit of work. Its not just hey presto. Theres a limit to what you can put on your front page(or main page). And navigation has…. “certain rules and conventions”. Also from my experience of creating sites for small to medium businesses the brunt of wireframe work goes into the front page and generic subpage. This reality needs to be treated. And lets not forget about other types of website (portfolio, forum).
Let me know if you think this is a subject worth treating and i can expand on my process… which starts with how I go about gathering requirements… and ends with medium detailed wireframes.
Your student. Robert
Want to see this idea turned into a story?
11 people said yes. | 0 people said no.
ed.j. bowers
4 Reputation points
Posted 2007/10/30 @ 13:29PM with
I’d like to see this. We are moving to a more rigidly requirements based development model and of course often sacrifice detailed requirements for speed of delivery. So, lead on McDuff…
Ben Tremblay
0 Reputation points
Posted 2007/11/07 @ 19:48PM with
Yup. A good start on this could lead to a couple more developing some aspects and setting things out in more detail.
FWIW, I came across this in a comment to Why Enterprise Software Sucks (The other comments would interest you too.: