Course work includes exams, homework assignments, and a Term Project. The distribution is at the bottom of this page.
Assignments
The homework assignments are available via the assignments link on the navigation bar at the upper left or by clicking here. They are based on the lectures and readings and are designed to help you with the reading and to develop your skills as a web designers and programmers. They range from straightforward to challenging.
The assignments' due dates are posted on the syllabus. We may tinker with them a little, adding clarifications and such, but they will be largely unchanged. When planning your schedule, keep in mind that computers and printers take a special joy in breaking down when you are most desperate. Try to leave time to deal with last-minute emergencies, and remember that outside of laboratory hours, you may have to compete with other students for a machine.
Work will NOT be accepted after the time at which it is due. If you have not completed an assignment, you should still turn in whatever you have for partial credit. In extenuating circumstances (e.g., sickness, personal crisis, family problems, religious holidays), you may request an extension. The instructors in the course will decide as a group whether to grant extensions. Furthermore, the “no late assignments” policy means that once you have turned something in, you should not modify it after the deadline has passed, so that when we grade it, it's still exactly what you turned in.
Projects
Computer Science 110 has a Term Project. Class members form teams of two students. Each team will find a client or other resource person to help design, develop, and demonstrate a web presence. The project will be related to an area in which you (and your partner and client) have some special interest.
The projects proceed in several phases, and the due dates for each phase may be found in the syllabus . You will receive detailed instructions for each phase of the project. All project deadlines are firm. Teams will lose points for missed deadlines.
More information about the Term Project is available via the project link in the navigation bar at the upper left or by clicking here.
Grading Policy
The final grade in the class will be computed as a weighted average of each of the course requirements above. The relative weight of the each component is outlined below:
Homework 20% Project 40% Midterm Exam 15% Final Exam 25%
There will be one midterm examination during class period. There will be no makeup examinations without prior arrangement with your instructor. The final exam will be self-scheduled during exam period.
Honor Code
The Honor Code applies to this course. You are encouraged to discuss assignments with other students, and with your instructors. However, you must solve, write up, debug, test and document the assignment on your own. In other words, it is acceptable to talk with other students using natural languages, but not acceptable to use any formal language and especially not HTML, CSS or Javascript. You should not be looking at other people's code or showing them yours. If you worked with others or you have obtained help from any source, you must acknowledge their contribution in writing.
Homework assignments must be your own work. You may not look at solutions from other students, either from the current offering of CS110 or from past offerings.
Exams are open-book and open-notes, but only your own books and notes. You may also bring in any review materials we distribute to all students. You may not consult any materials from past offerings of CS110.
Your project work will comprise both the content of
the site and the coding of the site. Content consists
of things like text, pictures, PDF. For example, if your
project is the website of a student organization, it might
include the organization's constitution, descriptions and
pictures of their activities, and so forth. The constitution
will, of course, not be your work. Some of the pictures may
have been taken by members of the organization. It would make
no sense to forbid you from using that content.
However, all the coding of the site should be your
work: the HTML coding, the CSS coding, the JavaScript coding
must all be the work of your team. If you find some coding
from a website other than the cs110 website and you would like
to borrow it, you must clear this with your team
advisor. You must carefully document what code is to be
borrowed or modified, giving proper credit both in the
coding files themselves using comments, and in
your P3_changes.html document. You must document
where you got the code from and how you adapted it for your
project. Human memory is fallible, so it is not acceptable to
get your advisor's verbal agreement: You must get prior,
written authorization, and then carefully document that, so
that there is no question of proper authorship.
Furthermore, because project work is done by a team, you must make clear who did each part of the project. If one partner did all the work of a particular page, her name can be put at the top stating that. If work on a page was divided, that must also be carefully documented with comments in the code. For co-authored documents, namely the requirements, design and testing documents, both students must contribute to the document. Both names being on the document means that both teammates contributed to it, so it is a violation of the honor code to have your name on the document if you did no work and it is a violation to put your teammate's name on it if she did no work.
You will be assigned a course account on the CS file server that includes a password to access the account. It is a violation of the honor code to share this password with anyone.
© Computer Science 110 Staff
This work is licensed under a Creative Commons License
Date Modified:
Friday, 25-Jan-2008 17:24:43 EST
