build

mvc_ii.docx

Home >Computer Science homework help >build

MVC

The program should send and receive requests. Between a student an advisor. Studying interact with the advisor through this app. For example

I can send a request to my advisor saying I want to change my major he can accept the request and typing a comment (Good luck in your new major) or he can reject the request I have sent with a comment (e.x- sorry you can’t change your major). You can login as student or as advisor and you can see the requests as a student or as advisor. The data have to be stored in Mongolab with my username and password ( username: wa2el… password : GAzza982655). For the buttons doesn’t really matter to me but make it reasonable

This is the grading rubric --------

Your system should leverage requirements and implement functionality needed for your final Semester project deliverable. The technologies that must be used in this assignment are available in Visual Studio 2013 or open source projects and include Code First, Entity Framework 5.0 , SQL Server (or MongoDb), MVC 5.0 and Azure cloud computing. You are encouraged to deliver your client interface leveraging JQuery and Bootstrap. The design and functionality of the system is up to you.

The technical requirements for this project are:

· Creation of a Model Layer that takes advantage of a SQL Server Database with at least new two tables conforming to the Entity Framework or a NoSQL solution using MongoDb.

· Creation of a ViewModel layer that supports your Views and and a repository layer to interact with your data persistence layer

· Application of the repository pattern with LINQ to create Queries to retrieve, and populate Model layers from database entities.

· Deployment of the database and the MVC Application to an Azure Cloud Account

Your group must turn-in all code documents and participate in a presentation of the iteration to the class. Project Grading will be based on:

Functionality (50%)

· Does it work (20%)?

· Does it meet the technical requirements listed above (15%)?

· Does it clearly achieve an important functional requirement (15%)?

Design & Usability (40%)

· Does it clearly demonstrate standard design patterns (10%)?

· Is it easy to use? Is the code well designed (20%)?

· Is the Interface well designed, responsive and functional (10%)

Class Presentation (10%)

· Was there a Professional presentation and clear explanation of its functionality (5%)?

· Did the all members of the group participate in answering questions (5%)?