rocknbil - 5:44 pm on Apr 29, 2010 (gmt 0)
This could be fun, unless,
I have until tomorrow ;)
It's due tomorrow. If so, you're hosed.
If not, fill in the blanks:
Public controls: list what the person filling out the survey will see. Be as detailed as possible, is it anonymous, will they see branding for the sponsor (configurable by administrator,) the number and nature of the questions. Obviously each question will be stored in a database, are there other functions, such as emailing the participant iif they opted to neter an email address?
How do sponsors opt in, via request from the site or only added by administrators?
- Levels of access (Super admin, sponsor, and . . . ?)
- Sponsor data management by super admins, and to what extent? Search obviously, what data fields are required (company, name, email . . . ?)
- Nature and function of the controls, obviously create surveys, others?
- Nature of the controls over the questions, obvious (multiple choice/radio buttons with defaults, multiple response checkboxes, etc.)
- Controls over the look of the survey (templates, layouts, logos, etc.)
- Nature of the display of the results: spreadsheet/data, graphing, controls over selection and organization
- Supplemental controls: settings that affect overall survey function, email sponsors functions, help files and their addition/modification.
These are off the top of my head, a lot falls under "survey."
As a programmer I've learned (the hard way) not to re-invent the wheel, is it even remotely possible you can take one of the thousands of open source apps already out there and modify it to your needs?