grading.html

Grading Policy (READ!!!)

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

All assignments 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. Submit a document using SVN.	April 10th
Milestone 1	5%	User can leave a message for him or herself at a specific location. When a message is left, an icon (like a pushpin) will appear at that location in the Android maps view. User can leave messages at different locations. No alerts or sharing of messages is required. All messages will be stored locally, using the phone's memory. No server interaction needed, except for google maps. Please ensure that the code to implement this functionality has been checked into SVN by this April 15, noon, and meet with TA within 2 days (until April 17 th) to show him that your team has implemented this functionality on your laptop	April 15th
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: place-it notes, both timed and untimed; friend laerts, geotagged pictures, groups, group place-its (time-constrainted and not) and friend alert groups. Complete list of uses will be posted shortly. Upload a complete project with XML files to SVN by deadline; if hand-drawing, scan it, and upload pdf (if this is a problem, talk to me). Also there will be a UML design review. Create a uml diagram with argouml, and upload the zargo or other UML file. You can also hand-draw it; in this case, upload a scanned copy (ask if this is a problem).	April 29th
Milestone 2	5%	Person-person place-its work: both time-constained and time-unconstrained. Message can be left, and received. Message length of 150 characters is enforced. Todos will also work. POssible to create geo-tagged pictures, which can be read by the receipient. Possible to create groups, and invite contacts to join.	May 6th
Final Project	20%	All features functioning; non-working features and bugs (largely) documented. NO EXTENSIONS POSSIBLE!!	June 3

Assignments:

All assignments are due at noon on the day indicated, and should be submitted online, one per team, using SVN.
If your submission has many files, please bundle using "tar".
For written assignments/documentation, the only acceptable forms are HTML, postscript, PDF and raw text. 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 20% 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..

Milestones: The two mid-project Milestones carry the credit as indicated.

What's a milestone? It's an industry-standard practice for customers to ensure that software projects are making reasonable progress
Milestones do not require any submissions.
To meet the milestone, you must make an appointment and meet with the TA anytime BEFORE the due date of the milestone to crank up your system and demonstrate that you have met the milestone.
The final project grade will be affected by your meeting the milestones as follows.

We will run a certain number t of tests, (TBD), probably around 15-20, when we grade the final project. This testing will carry 70% of the final project grade, and 14 points out of a total of 100 for the course. Let's suppose your system fails f of these tests. These 14 points will be calculated as
n = the total score on the milestones (between 0-10).
f = The number of failed tests.
t = The total number of tests.
Your final score = 14* (1 -(f/t)*(15-n)/10) Look through that formula, and make sure you understand it. You get penalized for defects we find, but your penalty is reduced depending on the level at which you meet milestones. In particular, if you meet all the milestones, and actually fail every single test, you will still walk away with 7 points!! So milestones can really be of benefit in your final grade. This is also realistic: if you are dealing with the customer, and you are meeting the milestones, the customer will be less unhappy with the final project when they find defects.

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 quiz, 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