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, except for the Twitter App (which is individual work) 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 on Smartsite. One submission per team is sufficient.
Jan 30
Weekly Project Reviews
5%
Attend Weekly Project reviews during discussion section, and present project status. Starting week 3, attendance will be taken at project reviews. Everyone graded on participation.






Milestone 1
     2.5%         
Basic functionality: user can create an appointment for himself at a place. Can also create an appointment or task for another user, which will result in a text message being sent. The other user doesn't yet need to process it.

Submit code in BitBucket version control, by due date, and then make appointment with TA to demonstrate it.




Feb 3






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; 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).

Submit code in version control, and then make appointment with TA to demonstrate it.






Feb 14
Milestone 2
    2.5%
 (TENTATIVE, SUBJECT TO MINOR CHANGES)  
Person-person place-its work: both time-constained (todos) and time-unconstrained (notes)

Possible to create geo-tagged pictures, which can be read by the receipient.

Feb 29
Final Project
20%
All features functioning; non-working features and bugs (largely) documented. NO EXTENSIONS POSSIBLE!!  Also must submit results of testing your partner teams' project by June 3.
March 14

Assignments:



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.