Grading

5%	In class participation and keeping up with recorded materials
40%	Programming Assignments (~4)
55%	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 individual reports reports: 5%
• your ability to work on a team: 5%
• your innovation and leadership: 5%
• your contribution to the final application: 10%
• team grade on the final application: 15%
• team grade on the pitch presentation: 5%
• team grade on the final presentation: 10%

Pitch Presentation

Around week 10, each team will present their plan for their project. The presentation should last 10 to 15 minutes and should cover the following points:

• What is the problem your app is trying to solve, and how will the app help
• What will the app look like? Present a few sketches of key screens.
• How will you achieve your objectives and will you need specific outside resources?
• What could you add if you achieve all your main objectives early? What could you remove if you are short on time?
• Is there any specific feedback you would like from the other teams?

After watching each presentation, other teams will brainstorm on your behalf, provide constructive criticism and give you the feedback you requested if applicable.

Final Presentation

At the end of the semester, you will give a final presentation in which you will present your finished project. The presentation should last about 30 minutes and should cover the following points:

• Recall from the pitch: what problem was the app trying to solve?
• Demo your entire app and show how it solves the problem
• Explain the various techniques you used to implement your app.
• Did you implement any additional features not mentioned in the pitch, and did you remove any of the initially planned features?
• If you had more time, what would be the next step towards improving the app.

Individual Reports

From the time you give your pitch presentation till the end of the semester, each students will write an individual report on their work on the project every two weeks. The report should should be about a page long and contain the following:

• Your work since the previous report. Did you achieve the objectives from your previous report? If not, explain what happened.
• What you plan to complete before the next report
• A quick evaluation (2 or 3 sentences) of the work of each of your teammates. Describe their performance, what they did well and what you wish they would do better (no magic thinking though, be realistic).

The goal of these reports is to help you plan your work and to make you reflect on how large projects are managed: find ways to best use the skills of your teammates and minimize the impact of their weaknesses, identify the patterns that lead to success and try to anticipate problems before they become unsurmountable.

Class Participation

Your participation grade consists of:

• Required attendance to lecture
• Active participation in lecture
• If relevant, active participation in the discussion group

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.