James Madison University, Spring 2017 Semester
Interactive demo in class on April 14th.
Your app should be at least 90% complete by the deadline. All group members should be present during grading to explain their contribution to the project design and implementation.
[Repository1] Make sure you have only one copy of your project on GitHub. It must be located under the webapp directory. In addition, you must complete the two files in the present directory. Please do not rename these files, and follow their instructions carefully.
[Repository2] Is everything related to your project in GitHub? Each team member should run git status – do any files have a question mark? If you're using external data sources (e.g., Google Fusion Tables), do you have a copy of the original data in git?
[Appearance] How does your website look on different devices? Is the layout reasonable on a desktop, a tablet, and a phone? What does it look like when you print the results on paper? Do your screenshot and short description represent your project well?
[Performance] Do all queries run in less than a second on the database server? Is the user able to submit queries without having to wait a long time? Are there unnecessary queries that can be combined into a single query?
[Code Quality] Would an experienced developer be able to read and understand your code? Does it represent your best work? Would you be confident or ashamed to submit this code as part of a job application?
You should expect to make changes during the last two weeks of class based on the feedback you receive from the instructor and your external client.
Appearance (10 pts)
|_____ / 5 pts||Design, Layout, CSS|
|_____ / 5 pts||Description, Screenshot|
Performance (10 pts)
|_____ / 5 pts||Server-side Indexing|
|_____ / 5 pts||Client-side Scripting|
Functionality (20 pts)
|_____ / 10 pts||Main Feature #1:|
|_____ / 10 pts||Main Feature #2:|
Code Quality (10 pts)
|_____ / 3 pts||Formatting (consistent indentation, helpful whitespace, uncomplicated syntax)|
|_____ / 3 pts||Code Style (organized well, insightful documentation, descriptive variable names)|
|_____ / 4 pts||Elegance (efficient algorithms, easy-to-follow control flow, clear dependencies)|