C# MVC 4 \'My Account\' page for API

*OVERVIEW* I require a C# MVC 4 website that is a single page with multiple sections. See the attached pdf. The page should be made with twitter bootstrap using a fluid layout. Also, use highcharts for the line chart at the bottom. This webpage should be fully functioning with a set of dummy data that I will detail below. I want to be able to change from ‘current month’ to a few other past months to verify that functionality. You can hard code this backend data any way you like. No database connection is necessary but the data models should be in place. DO NOT worry about actual authentication, membership providers, or anything like that. Just hard code a single user’s information. *’GENERAL’ SECTION* Under ‘Secret Key’: Clicking [click to display] will cause the secret key to be shown along with a link [click to hide]. The secret key should already be available to the javascript somehow. Don’t make an ajax request for the secret key. Under ‘Access Permissions’ Those are NOT functioning checkboxes, but a stylized list. Clicking those checkboxes does nothing. They are only there to illustrate which APIs the user has access to and which are under development. They don’t even need to be form elements, you could use icons or graphics of some kind. *ACCOUNT ACTIVITY SECTION* Changing the drop down from ‘Current Month’ to another month will update everything shown in this section only. Don’t reload the entire page. The chart should be implemented with highcharts. It should be free to download [login to view URL] *DATA MODELS* The data structures behind the scenes I imagine to look like this. Note: on the fly calculations DO NOT need to happen. Just hard code all the information. class UserApiInfo - user name - secret key - List - Dictionary class ApiAccessPermissions - api name - (bool) has access - determines if box is checked - (bool) is available - determines if grayed out class MonthlyUserApiUsage - date - ServiceLevelDetails - ApiUsageDetails - ApiUsageTimeline class ServiceLevelDetails - name (Pro Api from example) - monthly cost ($500.00) - discount ($53.29) - balance (also $500.00) class ApiUsageDetails - total cost ($53.29 in example) - total requests (2,259) - SortedList - int determines order on page class ApiUsageDetailsByMethod - api name (‘Url API’ in example) - will need to group by this - method name (‘organic_kws’ or ‘paid_kws’) - request count - rate - cost class ApiUsageTimeline (the line chart in the example) a collection of - api name and method (each one is a different series on the chart) - day - request count You have a little wiggle room with all of this. Let me know if you have questions and we can work out details. My point is that I want a respectable attempt at some data structures. *EXPECTATIONS* I try not to get hung up on every detail when writing a spec. I’d rather rely on your best judgement. That being the case, once I get your work back I will almost certainly ask for something to be changed or added outside of my original spec. So plan on ~10-15% scope creep as I start to use and try out the code. Anything beyond that and he can add additional milestones or whatever works to make sure you are fairly compensated.