CMPS 013H - Fall 2003

Index of class resources

Handouts — homework problem sets, homework solutions, other helpful handouts
General Class Information — class and section times, instructor and TA information

Handouts

• Course Syllabus
• Additional Readings
• Edsger Dikstra, How do we tell truths that might hurt?
• Edsger Dijkstra, Go To statement considered harmful
• Ken Thomson, Reflections on Trusting Trust
• Homework
• link homework into SECURE directory

General Class Information

Class Newsgroup:

We use a mailing list instead: cmps013h@cs.ucsc.edu

Lecture times:

MWF, 11:00–12:10, Social Sciences II, rm. 137

Section times: none (see me during office hours)

Associated Laboratory:

M, 17:00–19:00, 105 JBE

Instructor:

Darrell Long (darrell@cs.ucsc.edu)

Phone: 831-459-2616

Office: 247 JBE

Instructor Office Hours:

MW 12:30–13:30, and also easily arranged

Teaching Assistant(s): none (we’re on our own)

Programming Assignments

• Computing π on Gilligan’s Island
• The Knight’s Tour

Schedule

Date	Topic	Reading	Lecture
9/26	Introduction	JBD Ch. 1	JBD Chapter 1
9/29	Basic Java	JBD Ch. 2	JBD Chapter 2
10/1	Class cancelled	JBD Ch. 3
10/3	Basic Java
10/6	Unix and Design	JBD Ch. 4	Unix and Design
10/8	Statements and Control Flow		JBD Chapter 3
10/10	Methods	JBD Ch. 5	JBD Chapter 4
10/13	Recursion
10/15	Arrays	JBD Ch. 6	JBD Chapter 5
10/17	Objects
10/20	Objects		JBD Chapter 6
	Data Structures	W&M Ch. 3	Introduction
	Linked Lists	W&M Ch. 4	Lists
	Stacks	W&M Ch. 6	Stacks
	Queues	W&M Ch. 7	Queues
	Sorting	W&M Ch. 9	Sorting

Academic Integrity

While this really should not be an issue, life in the contemporary university discussing academic dishonesty necessary. The bottom line is that you are expected to conduct yourself as a person of integrity. You are expected to adhere to the highest standards of academic integrity. This means that plagiarism (look it up in the dictionary if necessary) in any form is unacceptable.

As a (soon to be) computing professional, I encourage you to consult the code of ethics appropriate to your discipline. The Association for Computing Machinery, the IEEE and the IEEE Computer Society each have professional codes of conduct. You should take the time to read each of them.

Plagiarism will be assumed, until disproved, on work that is essentially the same as that of other students. This includes identically incorrect, off-the-wall, and highly unusual duplicate answers where the probability of a sheer coincidence is extremely low. Automatic program checkers may be employed to compare programs. All parties to this unacceptable collaboration will receive the same (zero) score. Should you be found to be cheating, at a minimum, you will fail that assignment and a letter will be sent to your Department, the School of Engineering, and to your Provost and academic preceptor. I reserve the right to stronger action should I feel that the situation warrants it.

There are no programming groups in this course. Your work must be your own (web archaeology is prohibited as well). This refers to examinations, written assignments and programming projects.

You may discuss programming projects with your friends, but you are expected to abide by the Gilligan's Island rule. The Gilligan's Island rule states that following a discussion of the project, a break must be taken for at least a half hour before coding. Watching a mind-numbing program like Gilligan's Island on television satisfies this rule. Better yet, read a book unrelated to computer science before beginning to code your program: I recently finished Tuxedo Park, or see my personal web page for other suggestions.

The only thing you may bring to such a discussion is you, and no notes may be taken away from the meeting. The copying of files is strictly forbidden.

A zero score on any of the examinations or on one of the programming assignments is considered grounds for failing the course.

General info · News · Events · Degree Programs · Research · Classes · Admissions · Advising · People · Jobs · Administration

SOE Webmail · SOE SSH · Search · Sitemap · Contact us · Driving directions · Privacy · UCSC
© Baskin School of Engineering, University of California, Santa Cruz
1156 High St., Santa Cruz, CA 95064 · (831) 459-2158 · webmaster@soe.ucsc.edu