CS 111 - Introduction to Computer Science I
Course Information

Course Overview

On the surface it appears that Computer Science is a very dynamic discipline. However, there are certain principles that are basic to Computer Science. These are the fundamentals that enable us to solve problems within the context of a hardware environment. For that reason this course has a heavy emphasis on the methodology of problem solving with the use of computing equipment, algorithms, and the implementation of those algorithms in a specific programming language.  Because of the importance of the Internet and the World Wide Web, this course will be taught using the Java programming language.  Exercises will introduce the student to basic computing concepts, data types, classes and methods, decisions, iteration, testing and debugging, arrays and vectors, and other selected topics.  The goal of these exercises is to illustrate good programming principles, an understanding of object oriented programming, programming and elementary data structures, as well as some basic software engineering principles. Students will have weekly homework exercises throughout the term that will provide a solid foundation of experience for future problem-solving.

Learning Objectives

Text


Introduction to Java Programming, Comprehensive Version (10th Edition)
by Y. Daniel Liang

Text Home Page (author), (Pearson)
ISBN-13: 978-0133813463
ISBN-10: 0133813460 
2014
 

Instructor

Section A - Glatfelter 112 M,W,F 11:00-11:50AM:
Section B - Glatfelter 112 M,W,F 12:00-12:50PM:
Todd Neller
Office: Glatfelter 209
Office Hours: Mo-Fr 2-4PM or by appointment. Note: Generally, feel free to drop in if my office door is open (i.e., most of the time beyond class).
Phone: 337-6643
E-mail: 

Student Assistants

In-class Assistants:
    Section A: Thy Do (TA office hours Thursday, 7:30-9:30PM, Glatfelter 207)
    Section B: Alexi Doak (TA office hours Tuesday, 7-9PM, Glatfelter 207)

Grading Assistants: Will Czubakowski (TA office hours Monday, 7-9PM, Glatfelter 207) and Kevin Maldonado (TA office hours Wednesday, 7-9PM, Glatfelter 207)

Grading

60% Assignments
20% MyProgrammingLab Activities (4th Hour Requirement)
10% Quizzes / Exams
5% Colloquium Attendance
5% Class Attendance / Participation

You are responsible to know the material from each lecture and reading assignment before the start of the next class.  Homework is due at the beginning of lecture on the due date.  Late homework will not necessarily be accepted.  Source code that does not compile may not receive partial credit.  You are required to attend 2 colloquia or approved departmental events over the course of the semester.

Attendance

Class attendance and participation is required.  If you attend all classes and are willing to participate, you'll get 100% for this part of your grade.  Even if you know enough to give a particular lecture, please consider the value of helping your peers during in-class exercises.

Woody Allen is quoted as saying "80% of success is just showing up."   While our class attendance/participation grade is not 80% of the final grade, it is critical that late arrivals and unexcused absences are not excessive.  Missing more than half of class unexcused is considered being absent.  An unexcused late arrival is counted as a half absence.  If the total number of absences counted this way exceeds 20% of class meetings, i.e. 8.5 absences or more, the student will have failed the course.

Work Expectations

You are expected to work an average of 9 hours per week beyond class time Gettysburg College policy, in accordance with federal and state standards, equates 1 credit unit with an average of 12 hours of work per week with 50 minute classes counting as 1 full hour of work.  During these remaining 9 hours beyond class, a student is expected to learn from assigned readings, complete exercises related to such readings, attend required colloquia, and complete assignments.

Think of your college studies as a more-than-full-time job, and engage in it with passion.  After all, you get out of it what you put into it, and it is my hope that you'll gain much from your investment in this course.  If you'd like to learn more about how to better track tasks and manage time as a student, consider watching my short tutorial on getting things done.

Honor Code

Honesty, Integrity, Honor.  These are more important than anything we will teach in this class.  Students can and are encouraged to help each other understand course concepts, but all graded work must be done independently unless otherwise specified (e.g. group work).  Submitted work should be created by those submitting it.  Submission of plagiarized code or design work is a violation of the Honor Code, which I strictly enforce.  For detailed information about the Honor Code, see http://www.gettysburg.edu/about/offices/provost/advising/honor_code/index.dot.

What is permitted:

What is not permitted:

Put simply, students may discuss assignments at an abstract level (e.g. specifications, algorithm pseudocode), but must actually implement solutions independently or in permitted groups.  Credit should be given where credit is due.  Let your conscience be your guide.  Do not merely focus on the result; learn from the process.