CS 117: Introduction to Computer Science
Syllabus
Instructor Information
- Instructor: Dave Musicant (email: dmusican)
- Office: CMC 326
- Office phone: (507)646-4369
- Office hours: Mondays, 4-5, Tuesdays, 9-11, Wednesdays, 4-5
- Prefector: Rachel Kirby (email: kirbyr)
- Grader: Hilde Schmitt (email: schmitth)
Textbook
- An Introduction to Object-Oriented Programming with Java, 2nd
edition, by C. Thomas Wu. Published by McGraw Hill, 2001.
Important Dates
- Exam 1: Wednesday, 4/30
- Exam 2: Wednesday, 5/28
- Final project due: Monday, 6/9
Websites
Your Grade
- Assignments: 45%
- Exam 1: 20%
- Exam 2: 20%
- Final Project: 15%
Working from Home
- We will be programming in Java, using the BlueJ programming environment,
under the Linux operating system. This will be set up for use in the Computer
Science labs. You may install Java, BlueJ, and other tools that we use on
your own machine. PCs running Windows or Linux, and Macs should all work.
I'm glad to informally provide whatever advice I can to help you get the software
running on your own machine, but home use is technically "unsupported."
Homework Policy
- Each assignment will have a specific time for which it will be due.
An assignment turned in late within one day of the due time will be
docked 25%. A program turned in later than one day of the due date but
within two days will be docked 50%. A programming assignment turned
in any time after this until the last day of classes will be docked
75%. Non-programming assignments can not be turned in any later than
two days following the due date since we may be discussing answers in
class.
Getting Help
- If you need help with a project, you can consult with other students,
talk to the prefector, ask a lab assistant, or come to me. I am happy to answer
your questions either in person or via email. If you come to my office for
help with a program, please bring a printout of what you have so far.
Collaboration, Plagiarism, and the Difference Between the Two
There are two different kinds of working together: collaborating and plagiarism.
Collaborating
- Collaborating is good.
- You are encouraged to collaborate on ideas and program design.
- Programming is often a social effort, and there is much you can learn
by talking out the ideas in this class with each other.
- You can by all means talk to each other, look at each others' programs
to help fix problems, and share ideas.
Plagiarism
- Plagiarism is bad. DON'T DO IT!
- Any programs that you turn in should be your work.
- Even if you work with someone else and share ideas, you must still
write your own program.
- If a piece of your program utilizes someone else's idea, you must
make sure to give that person credit in program comments.
The following are examples of plagiarism.
- Taking someone else's program, changing the variables and comments
around, putting your name at the top, and turning it in.
- Finding a similar program on the internet, changing the variables
and comments around, putting your name at the top, and turning it in.
- Finding a similar program in a book, changing the variables and comments
around, putting your name at the top, and turning it in.
I will be using software to discover plagiarism if it occurs, and will
not hesitate to notify the College if it does.