Open Specifications
Posted: Mon May 17, 2010 5:41 am
I've got an idea about writing some open specifications for the bits of websites that are always having to be integrated into every site we write - things like News, Event calendars, User registration (and login, forgotten passwords, etc), Contact Forms... essentially it'd be a list of things that you could pick bits from and produce a full spec very quickly. For example, if you chose to have a Contact Form in the site it'd include something like:
You could then go in to the text and modify it as per your needs.
I have a couple of questions though;
1. How would you feel, as a developer, receiving that sort of list from your client? What could be done to make you happier to get it?
2. Would you or your clients pay for a service that produced a full spec very easily? If so, how much do you think would be a fair amount?
Code: Select all
Contact Form
The website shall provide a contact form for users to send comments and enquiries to the site owner.
The website contact form shall allow the user to enter their name, email address, subject and a message.
The website contact form shall use an anti-spam (eg Re-captcha) to stop automated messaging.I have a couple of questions though;
1. How would you feel, as a developer, receiving that sort of list from your client? What could be done to make you happier to get it?
2. Would you or your clients pay for a service that produced a full spec very easily? If so, how much do you think would be a fair amount?