CMPSCI 121
"Introduction to Problem Solving with Computers" using Java

Course Introduction Handout

CMPSCI 121 provides an introduction in problem solving and computer programming using the programming language Java. It teaches how real-world problems can be solved computationally using the programming constructs and data abstractions of a modern programming language. Concepts and techniques covered include data types, expressions, objects, methods, top-down program design, program testing and debugging, state representation, interactive programs, data abstraction, iteration, interfaces, inheritance, lists and arrays. No previous programming experience required.

Resources

Textbook

Introduction to Programming and Object-Oriented Design Using Java, 2nd Edition (Java 5.0) Jaime Nino, Frederick A. Hosch ISBN: 0-471-71227-2 Book homepage Amazon link UMass Textbook Annex, 413-545-3570

Help with CMPSCI 121

• Last semester CMPSCI 121 students benefitted greatly from the Learning Support Services on the 10th floor of the main library. The CMPSCI 121 support hours are listed at http://www.umass.edu/lss/tutorschedule1.htm
• Form a study group of other students in CMPSCI 121. Get to know other students in the lecture and your discussion section.
• The CMPSCI121 bulletin board: ask questions and get answers online.
• TA office hours are listed on the weekly schedule.

Grading

In addition, to pass the class, you must pass the Final Exam.

The lowest two of the twelve programming assignment grades and two lowest of the twelve problem exercise grades and the lowest three of the twelve quiz grades will be dropped from their respective averages.
(This policy is intended to provide some allowance for sick days or other unavoidable events, not to allow you to skip an assignment you had trouble with. Completion of all 12 assignments will count toward "extra credit," which will be used to adjust letter grades at the end of the semester. The exact effect of extra credit will depend on the final grade distribution.)

As you can see the weekly homework assignments make up the largest single portion of your grade. You learn best by doing, not just listening and reading. Stay on top of the homework, and don't get behind! They come fast--right on top of one another. Keep up with the homework and starting the assignments early. Then: (a) you will have more fun when you aren't under time pressure, and you'll learn more; (b) you will then also understand the lectures better, (c) you will finish the assignment more easily because you will have the context and the support of your peers and TAs, (d) you'll be well on your way to a good grade. It's hard for your instructor, TAs and peers to be sympathetic and helpful to someone who didn't put in the effort to get started before the last minute.

Quizzes are short (less than 10 minutes) tests. Most weeks one quiz wil be given, but some weeks there may be no quiz, followed by two quizzes in a later week. Quizzes will be given unpredictably either during lecture or during lab. In most cases they will occur during the first minutes of the class--so please arrive on time. If you arrive to class or lab late, you will not be allowed to extend your time for finishing the quiz.

You should definitely read the textbook chapters assigned. We have a lot of material to cover--so it is hard to fit it all into 13 lectures. Some material will not be covered in lectures, and you'll be expected to learn it by reading (and asking questions on the bulletin board or in office hours if you are having difficulty.) The quizzes and exams may test material covered in the reading, but not in the lectures or labs. The week's assigned reading should thus be done before the week's lecture, in order to prepare yourself for the quiz.

Late Homework Policy

Homework is assigned during the Lab (aka "Discussion Section") meetings Thursdays at 11:15am, and is due electronically in the OWL system at 9am on Tuesdays. Homework submitted after it is due but 2pm the following day will be accepted, and all problems will be graded with a 30% penalty. Homework submitted after this time will not be accepted (and given a grade of zero), because, in some cases, solution sets will be posted then. As mentioned above, the lowest of the 12 homework assignment grades will be dropped. I encourage you not to "waste" this allowance--it is intended to cover a time when you are sick in the hospital, have a funeral to attend, etc.

Regrading Policy

If you feel that a homework assignment or exam has been misgraded, you should bring this to the attention of a TA or the instructor. Assignments will be open for regrading for two weeks after their due date, up until the day of the final exam.

Honesty Policy for Homework

• You must type in and edit your own code and exercise answers.
• Copying someone else's file or answers is not allowed.
• Allowing someone else to copy from you, either explicitly or implicitly by leaving your code unprotected, is not allowed.
• Editing each other's code or answers is not allowed.

Regarding the ethics of what you may or may not discuss with other students:

• "High level" discussions are fine.
  For example, discussions about the problem statement.
• "Low level" discussions are fine.
  For example, discussions about Java syntax, understanding compiler error messages, understanding the mechanics of the Java language.
• "Mid level" discussions require discretion.
  In some CMPSCI courses, discussions at this level are not allowed. In this course, unless explicitly stated otherwise, you may collaborate with classmates at this level, provided that you cite at the top of the submitted homework the names of the classmates that you worked with and those who helped you. For example:
  /**
  * Chris Brown
  * Homework 2
  * 5/6/2007
  * I worked with Dana Ballard and Randal Nelson.
  * I received help from Claire Cardie.
  */

There may be some "no collaboration" homeworks, or ones in which collaboration with only with a few specific people is allowed.

If the homework writeup states that collaboration is NOT allowed, then:

• You can ask and answer high level questions as described above.
• You can ask and answer low level questions as described above. However,
  A student who needs help with debugging a program may show another student his/her code.
  A student who is helping someone else may not show his/her code.
• Use your best judgement to protect both yourself and your friends. In UMass CMPSCI, typically if a professor suspects unwarranted collaboration, all participating parties are penalized (both helpers and helpees).
• Use your best judgement about asking or answering questions of other students. For example, if you are supposed to implement Algorithm X that is described in the book, and you don't understand Algorithm X, then you can ask another student to explain it to you. However, if you are supposed to come up with your own algorithm to solve a problem, then you can not ask another student to tell you their algorithm.

When in doubt about whether it is ethical to ask or answer a question of another student, ask a TA or the instructor.

Academic Honesty

Any acts of cheating, plagiarism or breaking the above rules will be reported to the University Academic Honesty Board. You are responsible for knowing, and will be held to, the University Academic Honesty Policy. This policy is available online at http://www.umass.edu/dean_students/rights/acad_honest.htm

If you have questions about these policies please talk with the instructor.