Grading

15%	In class participation and keeping up with recorded materials
10%	Completion and submission of class exercises
30%	Programming Assignments (~5)
45%	Final Project

Final Project

The final project will consist of the programming of -- ** drum roll ** -- an Android application. You do not have to start working on the application right at the beginning of classes, but you should start thinking about what the application should be. You will be working on the project in teams of 4 or 5. During the time that you will be working on the project, each team member will be asked to submit short reports on their own contribution to the project, and a quick evaluation of the work of your teammates. The grade of the project will be distributed as follows:

• timely submission of all the reports: 5%
• your ability to work on a team: 5%
• your innovation and leadership: 5%
• your contribution to the final application: 15%
• team grade on the final application: 10%
• team grade on the presentation of the application: 5%

Class Participation

Your participation grade consists of:

• Required attendance to lecture
• Active participation in lecture
• Active engagement in the class discussion group (Piazza)
• Watching the recorded materials in a timely manner

Programming Assignment Policy

Programming assignments are submitted electronically using onCourse, and are typically due by 11:59 PM. You may submit your assignment multiple times, but only the final submission will be graded.

You are allowed to work on programming assignments with a partner to allow you to work on larger projects and to gain important experience working in groups to build software. Both team members should submit the assignment, but the name of both partners should be indicated on the submitted files. Both team members should participate in writing the program so that both partners will gain code-writing experience.

Late Policy: Programming assignments will typically be assigned during lab and will be due at 11:59PM on the day indicated on the assignment. You are strongly encouraged to start early and to attend the tutoring sessions for extra practice. You must submit your assignments electronically by submitting to your files on onCourse. You may submit your assignment multiple times, only the final submission will be graded.

To help with cases of minor illnesses, athletic conflicts, or other short-term time limitations, all students start the course with two late assignment days to be used at your discretion, with no questions asked. To use your extra time, you must email your professor after you have completed the lab and attach your programming assignment to the email. You do not need to inform anyone ahead of time. When you use late time, you should still expect to work on the newly-released lab during the following lab section meeting. The professor and tutors will always prioritize answering questions related to the current lab assignment.

Your late days will be counted at the granularity of full days and will be tracked on a per-student (NOT per-partnership) basis. That is, if you turn in an assignment five minutes after the deadline, it counts as using one day. For partnered labs, using a late day counts towards the late days for each partner. In the rare cases in which only one partner has unused late days, that partner's late days may be used, barring a consistent pattern of abuse.

If you feel that you need an extension on an assignment or that you are unable to attend class for two or more meetings due to a medical condition (e.g., extended illness, concussion, hospitalization) or other emergency, you must contact the dean's office and your instructors. Faculty will coordinate with the deans to determine and provide the appropriate accommodations. Note that for illnesses, the College's medical excuse policy, states that you must be seen and diagnosed by the Student Health Center and get a note justifying your absence or inability to complete your work in time.

Academic Integrity

Academic honesty is required in all your work. Under no circumstances may you hand in work done with (or by) someone else under your own name. Your code should never be shared with anyone; you may not examine or use code belonging to someone else, nor may you let anyone else look at or make a copy of your code. This includes, but is not limited to, obtaining solutions from students who previously took the course or code that can be found online. You may not share solutions after the due date of the assignment.

Discussing ideas and approaches to problems with others on a general level is fine (in fact, we encourage you to discuss general strategies with each other), but you should never read anyone else's code or let anyone else read your code. All code you submit must be your own with the following permissible exceptions: code distributed in class, code found in the course text book, and code worked on with an assigned partner. In these cases, you should always include detailed comments that indicates on which parts of the assignment you received help, and what your sources were.

Failure to abide by these rules constitutes a violation of the Wheaton Honor Code and will be referred to the Dean of Students Office for disciplinary action. In extreme cases involving copyrighted materials, prosecution under State and Federal laws may also apply.

I will routinely run plagiarism detection software on your lab assignment submissions.

The spirit of this policy applies to all course work, including code, homework solutions (e.g., proofs, analysis, written reports), and exams. Please contact me if you have any questions about what is permissible in this course.