Office hours (in the lab): Thursday 3=4:30 and Friday 10:30am-noon
Moodle
This course is being managed using Moodle. There is where you will find all course assignments,
submit your programs, carry on on-line discussions, and complete homework in the form of online quizzes.
Go to http://moodle.soe.ucsc.edu/ and click on the link for CMPS 11.
You will be able create an account for yourself and join the class online.
Class notes on Ubiquitous Presenter
I plan to use Ubiquitous Presenter (UP)
during class. This will provide you with access to
my notes/slides including any annotations I make during class. I also expect to use
UP for in class activities/exercises where you will submit items (typically code fragments)
for display during class.
Please go to up.soe.ucsc.edu
and enroll in cmps011S09. The password will be given out during class and sent via email to enrolled students.
Audio and screen shots from class
I also hope to be posting "movies" with audio of the primary computer
display from class. These will appear in
class recordings.
Lab Information
Lab attendance is optional, but STRONGLY encouraged.
The labs meet Thursday 3-4:30 and Friday 10:30am-noon.
You are guaranteed a seat on your assigned lab day, but are welcome to attend either lab section
on a first come, first serve basis. This is a time to work on your programming assignments with your
partner (see below), get help from the teaching assistant and/or tutors, and get help from other
members of the class. The instructor will also be in lab on occasion.
Text:
- Required - one of:
- Java by Dissection 2nd Edition. Pohl and McDowell
The text is available online at http://www.lulu.com/JavaByDissection
The first three chapters are available for free downloading from that same site. A complete electronic copy is
also available for only $5.
Evaluation:
- Programming assignments (20%).
- Bi-Weekly quizzes (best four out of five) (35%).
- Review questions/homework (10%).
- Final (35%).
- OR
- Programming assignments (20%).
- Bi-Weekly quizzes (best four out of five) (20%).
- Review questions/homework (10%).
- Final (50%).
Whichever gives you the highest score.
A minimum of 50% on all four aspects of the grade is necessary but
not sufficient to pass this class. This means, if you receive less
than 50% on any one of the four parts (programming assignments, quizzes,
review questions, or final), you will
not pass, however, just because you score at least 50% on each part
does not imply that you will necessarily pass. For example, someone
that scored 51% on each of the four parts would almost certainly, NOT pass.
The policy is intended
primariliy to prevent students from "blowing off" the homework or programming assignments because
they only count 10% and 20% of the grade respectively. You cannot pass this class if you do
not do the homework and programmming assignments.
Working Together:
The programming projects are to be done
in two person teams following the
pair programming guidelines.
For the first three programs (really one program done in three steps) you can select your
own partner. There will be opportunites in class and lab to find a partner.
For the remaining projects, you will be assigned a new partner from your same lab section
for each assignment.
New lab partner assignments will be posted the same day that assignments are due.
The normal policy is for all students to be assigned new partners after each
project, however, if you feel strongly that you want to continue with your current
partner, you may petition the instructor as described in the
pair programming guidelines.
You may freely give and receive help with the
computer facilities, editors, debugging techniques, the meaning and
proper use of Java constructs, built-in functions, etc..
You should not discuss your design or implementation of the
programming assignments with students other than your partner
until after they are turned in.
In particular you should not view another person/pair's program, or
allow someone (other than your partner)
to view any part of your program, prior to successfully completing that assignment (see below).
Obviously,
copying any part of another person/pair's program, or allowing your program to
be copied is not permitted. A program,
Moss,
will be in use to detect copying. If you have any questions on this
important point, please see me.
Academic Dishonesty:
Any confirmed academic dishonesty including but not limited to copying
programs or cheating on exams, will constitute a failure of the computer
ethics portion of this class and result in a no-pass or failing grade.
You are encouraged to read the
campus policies regarding academic integrity.
Programming Projects:
BOTH partners in a
pair should submit the program.
This avoids the "I thought my partner was going to
submit it" problem. Each partner should also submit a readme.txt file that
includes a suitably modified version of this
sample pair programming log.
Programs will be submitted through http://moodle.soe.ucsc.edu/.
Programming assignments, grading policy, and due dates can be found in
http://moodle.soe.ucsc.edu/.
Quizzes
There will be a quiz every other week with the first quiz on Tuesday, April 7th
at the start of class.
If you qualify for classroom accommodations because of a
disability, please get an Accommodation Authorization from the
Disability Resource Center (DRC) and submit it to your instructor
(Charlie McDowell) in person outside
of class (e.g., office hours) within the first two weeks of the
quarter. Contact DRC at 459-2089 (voice), 459-4806 (TTY), or
http://drc.ucsc.edu for more information on the requirements and/or
process.
This page maintained by Charlie McDowell.
Email regarding
this site.