ASP.Net MVC application for Creating and editing forms

I am in need an ASP.Net MVC application for creating and editing forms that is similar to Google's <[login to view URL]> The browser client is to use pure HTML (as it will NOT have javascript) so post backs between each question is OK. You will also need to create the database and structure to hold the blank forms and the answers that get returned. You must also create a page with links to the list of forms so that a user can select a form and fill it in ... and you save the data. A wish list item would be to also have the forms completed by email, but this is not yet required. ## Deliverables * * *This broadcast message was sent to all bidders on Sunday May 22, 2011 5:09:29 PM: Sorry for delay. To respond to all questions from all bidders, below is the process as I see your development will go: 1) In Visual Studio 2010, start a new MVC3 application with tests 2) Using the included [login to view URL], creates any tables that you need (I prefer to prefix all tables with “V2_Forms_??, so a table that holds the blank form might be called “V2_Forms_Templates?? 3) Create\Edit forms: When Admin logs in, that user sees a list of current forms in the Template table and an option to edit them or create a new one. When the template is selected, he can either add or delete questions in the list. This functionality should closely mimic how Google describes this at [login to view URL] 4) Viewing Responses: The Admin user can also see a list of completed forms with the answers. Similar functionality to [login to view URL] 5) When anyone other than an Admin user logs in, they are given a choice to select what form to fill in. After the user selects the form, then he is taken to a screen that list all questions and then a submit buttons will validate the answers and either display validation errors or it will save the form id, question and answer to a database table with the users login id and date when it was completed. 6) Ignore the wish w\list request for email form filling, 7) Do NOT use AJAX or javascript. Everything must be pure HTML. The admin user will obviously have a post back between each question that is added or deleted, but the user will typically only have to submit the button one time unless there are multiple pages. 8) Keep database update methods in a model class (do not put database calls in the controller class). I prefer a simple CRUD model class that does (Create, select, updates and deletes) with those 4 methods and then the controller can just call the model. Please reply with your confirmation that this is acceptable to you and revise your bid if desired. Thanks and regards, Gary