How do you write a Website Requirement Document?
Just trying to see examples or if there is even a such thing as a standard in website requirement documentation. This is the document handed to the development company that plays the role of a guideline for development and design needs, rules and requirements.
Most often teh development company does their own analysis and creates their own documentation.
If you want to create a document for them, keep in mind they may only use it as a reference to ask you more questions - but it’s a good idea.
You want to briefly give an overview of what the website is.
You want to state what you are hoping the website will gain for you (the objetives)
You’ll want to discuss the elements of the site in specific. IE:
you want a registration form; that submits an email to you as well as the registrant, saves data in a database that can be used for reporting.
Task out what you must absolutely have for the website to work, then state what you would really want to have, but may not get until a future release.
If the website will replace a business process, then document the process as to how it works right now so the developer knows how to automate it.
For Example: Receptionist gives Sales department the gold copy, and the Accounting deparment the green copy, the white copy is left with the customer and the blue copy is filed.
(This could translate into an application that stores dat in a database and emails the sales,accounting and can be referenced via reporting tools. - and prints out the page so the receptionist can give the customer a copy; maybe the customer will also get an email…)
Keep in mind of features that would be handy… for example your reporting page may list all the registrants - but it’d be nice if you can sort by first name, last name, postal code, or date registered.
And all options should sub-sort by last name, except last name which should subvsort by first name…
Well hopefully you get the idea.
Realistically the developing company should ask you the questions about how the website should perform the tasks you want and create their own document.
October 29th, 2009 at 3:27 am
Most often teh development company does their own analysis and creates their own documentation.
If you want to create a document for them, keep in mind they may only use it as a reference to ask you more questions - but it’s a good idea.
You want to briefly give an overview of what the website is.
You want to state what you are hoping the website will gain for you (the objetives)
You’ll want to discuss the elements of the site in specific. IE:
you want a registration form; that submits an email to you as well as the registrant, saves data in a database that can be used for reporting.
Task out what you must absolutely have for the website to work, then state what you would really want to have, but may not get until a future release.
If the website will replace a business process, then document the process as to how it works right now so the developer knows how to automate it.
For Example: Receptionist gives Sales department the gold copy, and the Accounting deparment the green copy, the white copy is left with the customer and the blue copy is filed.
(This could translate into an application that stores dat in a database and emails the sales,accounting and can be referenced via reporting tools. - and prints out the page so the receptionist can give the customer a copy; maybe the customer will also get an email…)
Keep in mind of features that would be handy… for example your reporting page may list all the registrants - but it’d be nice if you can sort by first name, last name, postal code, or date registered.
And all options should sub-sort by last name, except last name which should subvsort by first name…
Well hopefully you get the idea.
Realistically the developing company should ask you the questions about how the website should perform the tasks you want and create their own document.
References :