grading.html

Grading Policy (READ!!!)

You will be assessed on the basis of three assignments (and one milestone) constituting a term project plus one quiz and one final, which will be weighted as follows to compute your final grade:

All assignments (except for assignment 0 which is an individual app) which will be submitted as team efforts.

The following are the assignments for your term project, including their due dates and their weighting as a percentage of your final grade:

Term Project Assignment
*All Dates are tentative and subject to change*
Assignment	Weight	Description	Due Date
Assginment 1	5%	Test Scripts/Use Case. Submit the document in BitBucket, and also by email to the TA. Create an initial design of your system, including UML class diagram of major classes (UML will be covered in class shortly). A few projects will be selected at random for design review meetings in the discussion section. Presentation is not optional for selected teams.	April 19
Assignment 2	10%	Mockup all the layouts and views for your application. You can make this all up using XML and show me just using the layout preview within Eclipse. Create layout.xml mockups, or hand-drawn GUI storyboards, for all use cases. Complete list of uses required will accompany your graded fist assignment. Upload a complete project with XML files to version control by deadline. Also prepare a full test plan, consisting of a set of test cases, based on your solution to assignment 1. . Submit code, (layout.xml) or image of storyboards in bit bucket.	May 3rd
Scheduled Milestone	5%	The following features will function: user can create account. User can make a ride offer. User can display list of available rides between specificied locations.	May 20
DEMO WEEK	5%	Each Team will prepare to meet with Prem, and give a polished demonstration of the current state of the project. Depending on time available, some teams will present in person (chosen at random) and others will submit video (narrated screen presenation)	June 6 and 7th
Final Project	20%	All features functioning; non-working features and bugs (largely) documented. NO EXTENSIONS POSSIBLE!!	June 1

Assignments:

All assignments are due at noon on the day indicated, and should be submitted online, one per team, using version control.
For (english language) written assignments/documentation, the only acceptable forms are HTML, or raw text or PDF Submissions in other formats will not be accepted; we are not responsible for notifying you that you have submitted in the wrong format. If you resubmit in the right format you run the risk of being late.
Lateness penalty is 25% of the full credit per day (or portion thereof) past the due time . No exceptions can be granted.
The dates posted above may change due to unforeseen circumstances. This page will always be kept up to date; make sure to check this page in case of doubt..

Grading is done based only on mastery of the material as exhibited in the exams and the project. If everyone masters the material very well, then everyone will get an A. In case your final scores fall on a borderline, performance on the midterm, exam, and classroom participation will count for more in making the determination which side you fall.

Regrading Policy.

In general, papers or submissions to be considered for regrades must be turned in no later than one week after the graded submissions/papers were made available, not from when the student picked up her or his submission. See the TAs or reader for regrades of assignments; see the instructor for regrades of exams. Similarly, any misrecorded grades must be reported within a week of their posting, except if announced differently at the end of the quarter.

These above rules are necessary to meet the challenge of providing timely, fair grading with the large enrollments we have for ECS 160.

Term Project Assignment

Weight

Description