Web Site Requirements Doc
Web Site Requirements Doc
Author
Discussion

boony

Original Poster:

382 posts

268 months

Thursday 13th August 2009
quotequote all
I am currently beavering away on a requirements document for a web site I need implementing. I plan to outsource to keep costs down (probably via rentacoder) so want to make sure I get everything nailed down.

I've got about 20 pages up to now, and guestimate I'm about a quarter of the way through. Have I gone mad?? Is an 80 page requirement spec likely to result in no bids?

I haven't said anything about how I want the site to look (other than to stipulate no garish colours, consistent, professional look and feel) because I have no artistic flair and want to leave that to them. I have mainly stipulated what functions need to be supported.

Just wondered if anyone has experience of writing or working from such a specification and could offer any advice?

Cheers all

maser_spyder

6,356 posts

213 months

Thursday 13th August 2009
quotequote all
80 pages is great for detail, but they simply won't read it all.

You'll get a better result if you condense it all down.

Saying that, if you have 2 pages of intent, and 78 pages of completely nailed down detail, you should end up with a good result.

Finding a developer to work with may not be so easy, the best ones generally don't (or can't) read!

*Fletch*

290 posts

214 months

Thursday 13th August 2009
quotequote all
Personally I prefer a verbose document because then it leaves no ambuiguity and prevents disappointment if the end product doesn't meet the perceived requirements.

However a summary page would be useful.

Mind sending me the spec through when finished?


Don

28,378 posts

315 months

Thursday 13th August 2009
quotequote all
A detailed specification is brilliant - but as mentioned before having a good summary (four or five pages) at the beginning followed by plenty of detail is just great.

You'll not persuade people to fixed-price a development contract with a lax specification.

Also, as I'm sure you are aware, prices will vary dramatically on what service you are buying.

If you pay a Rent-a-coder to write you a load of source code and hand it over that's one cost.

If you pay a development firm to build you a system and then support it forever after with a 9 to 5.30 helpline and plenty of staff to answer the phone that's another. Since it looks like you are in IT I imagine it's the former you want and you'll support the software in-house after the initial development.

If that's going to be the case remember to specify coding standards you can live with...

boony

Original Poster:

382 posts

268 months

Thursday 13th August 2009
quotequote all
Cheers for the input, I'll crack on then safe in the knowledge I'm not wasting my time.

I already have the summary at the front so got that one covered. I will revisit once I'm done with the detail as I'm sure there will be changes to be made.

My main concern now is that I release the requirements and someone steals the idea! LOL