Two weeks for the site and a year for the partridge in a pear tree :) Seriously, the biggest problem I see is that the "types" are not consistant and that he wants to generate / edit / delete fields dynamically. That is not going to work well within the nature of an ordinary db such as SQL server unless you run the "types" as a vertical record where each field is a record. In that type of envionment, you can specify additional values for each field such as access group level for the field, last time modified, by who, data field was created, etc. If this is your plan, this type of structure does usually require considerable more time to work with than horizontal records. There are a few points I am not sure I understand such as "integrated into his solely html based website", but for the parts I do understand it would be something like:
Resource Description
Hours
20-40 DB design, data layer (C#) business objects and test
(would include limited fixed searching abilities)
8-16 Add, edit, delete Types, includes editing permissions on each field
16-32 User permissions and account adimination module
(includes add/edit/delete user permission roles/groups -
Internal and External users/clients)
8-16 Integration with HTML site and provide basic account registration and
comformation.
4- 8 Notification automation for posting of new matching types
(assign them to categories so that he can notify them of
new listings - includes automated emailing of notifications and
a review page )
XX-XX 3 different report views, 9 summary pages
1YR partridge in a pear tree
So that is 56-112 single resource hours not including the last two items. Not enough information to begin accounting for those items. This is raw hours. I personally double my calculations to take in account of cross browser problems, unknown bugs in platform and client approvals. If it were me, i would say 4-6 weeks for one developer. Rocky <>< www.GotTheAnswerToSpam.com