Lab exercises and project assignments will be posted here weekly each Monday. The usual deadline is the following Monday night at midnight. But there are some exceptions. Notice this means that you will be beginning lab i+1 and project i+1 in the lab on Monday afternoon and then finishing lab i and handing in project i on Monday night.
|Section||A, B, C|
|Date Time, Location||
Section A: M 1:00 - 2:20 pm, Davis 102
Section B: M 2:30 - 3:50 pm, Davis 102
Section C: T 1:00 - 2:20 pm, Davis 102
The learning goals for the lecture and lab are the same -- both are
meant to work together to accomplish the goals for the course as a
whole. They are
|Labs and Projects||
The work in lab will lead into and be part of the week's project. Labs will also count significantly towards participation.
During each lab, the instructor will not be able to answer questions about any projects until you have completed the exercises for that lab.
Programming projects involve completing more significant programs as well as a writeup describing the work completed in the project.
The grading policy for projects is designed to support three aspects of software production that are important for any computer scientist to have: high quality code, effective communication to the software's user or future programmer, and coding creativity and initiative. Each project has 30 points associated with it:
|Submission, Late Policy||
You are expected to finish your write-up on Wiki and submit your source codes to filer before the deadline of each project.
Every student is allowed a free 4-day extension to one project. Let us know when you are taking your "freebie". Other late projects will be given reduced grades. Programming projects are graded on a 30 point scale. For each day late (up to four days), your grade will be reduced by 3 points. Projects more than four days late will not be accepted. Also, the freebie will not be accepted if it is submitted more than 4 days after the due date.
In the lab, we are have installed Java 1.8 (also referred to as Java Platform Standard Edition 8). You may have an older version on your computer (which is fine, as long as it is version 1.5 or later). Here are the links to the APIs for the most recent versions:
When you write a class, always include a main function for the class that tests out its capabilities. The main function should try creating a class object and calling the methods of that class. Ideally, a test function should try out all of the class methods and access all of the class variables. Having a proper test function for each class will be part of the grade for each assignment.
Important: Write complete tests for each class before you try to use the class somewhere else. For example, before you try to use the class A in class B, you should be sure the class A functions properly on its own. Get in this habit early; it will help you avoid a lot of frustration that comes when integrating even moderately complex systems.
|Collaboration, Academic honesty||
Computer science, both academically and professionally, is a collaborative discipline. In any collaboration, however, all parties are expected to make their own contributions and to generously credit the contributions of others. In our class, therefore, collaboration on homework and programming assignments is encouraged, but you as an individual are responsible for understanding all the material in the assignment and doing your own work. Always strive to do your best, give generous credit to others, start early, and seek help early from both your professors and classmates.
The following rules are intended to help you get the most out of your education and to clarify the line between honest and dishonest work. We reserve the right to ask you to verbally explain the reasoning behind any answer or code that you turn in and to modify your project grade based on your answers. It is vitally important that you turn in work that is your own. We do use automated plagiarism detection software, so please be sure to abide by these, rather minimal, rules. Reports of academic dishonesty are handled by an academic review board and a finding of academic dishonesty may result in significant sanctions. For more details on Colby's Academic Integrity policies and procedures, see colby.edu/academicintegrity.
|The Colby Affirmation||
Colby College is a community dedicated to learning and committed to the growth and well-being of all its members.
As a community devoted to intellectual growth, we value academic integrity. We agree to take ownership of our academic work, to submit only work that is our own, to fully acknowledge the research and ideas of others in our work, and to abide by the instructions and regulations governing academic work established by the faculty.
As a community built on respect for ourselves, each other, and our physical environment, we recognize the diversity of people who have gathered here and that genuine inclusivity requires active, honest, and compassionate engagement with one another. We agree to respect each other, to honor community expectations, and to comply with College policies.
As a member of this community, I pledge to hold myself and others accountable to these values. More ...
|Title IX Statement||
Colby College prohibits and will not tolerate sexual misconduct or gender-based discrimination of any kind. Colby is legally obligated to investigate sexual misconduct (including, but not limited to sexual assault and sexual harassment).
If you wish to speak confidentially about an incident of sexual misconduct, please contact Colby Counseling Services (207-859-4490) or the Director of the Gender and Sexual Diversity Program, Emily Schusterbauer (207-859-4093).
Students should be aware that faculty members are considered responsible employees; as such, if you disclose an incident of sexual misconduct to a faculty member, they have an obligation to report it to Colby's Title IX Coordinator. "Disclosure" may include communication in-person, via email/phone/text, or through class assignments.
To learn more about sexual misconduct or report an incident, visit http://www.colby.edu/sexualviolence/.
© 2017 Caitrin Eaton .