Hi There!

I'm Dan Schlegel, an Assistant Professor in the Computer Science Department at SUNY Oswego

CSC212 – Fall 2019

Principles of Programming


Prof. Daniel R. Schlegel, 395 Shineman Center, daniel.schlegel@oswego.edu
Office/Lab hours: Monday: 4-5pm; Tuesday: 9-10am and 12:30-1:30pm; Thursday: 8-9am; and by appointment 
Section 800: MWF 9:10-10:05am, Park 315

Teaching Assistants:

We will have five teaching assistants during the Fall 2019 instance of the course: Adrian Naaktgeboren, Kate Gordon, Phoenix Boisnier, Rinaldo Iorizzo, and Thomas Hanley.

Office Hours / Course Schedule:

8:00Prof. Early's Lab (L52)
Shineman 446
Dan's Office Hours
Shineman 395
Park 315
Dan's Office Hours
Shineman 395
Park 315
Park 315
9:30Prof. Schlegel's Lab (L57)
Shineman 446
10:00A+P Office Hours
Shineman 446
A+P Office Hours
Shineman 446
11:00Prof. Schlegel's Lab (L54)
Shineman 446
12:30Dan's Office Hours
Shineman 395
Prof. Lee's Lab (L55)
Shineman 446
1:30R+T Office Hours
Shineman 446
2:30Prof. Pantaleev's Lab (L53)
Shineman 446
3:00A+K+R Office Hours
Shineman 446
Dan's Office Hours
Shineman 395
Prof. Tenbergen's Lab (L50)
Shineman 446
3:30K+T Office Hours
Shineman 446
4:00R+T Office Hours
Shineman 446
Prof. Lea's Lab (L51)
Shineman 446
A+P Office Hours
Shineman 446
5:00K+P Office Hours
Shineman 446

Coming soon: TA Office Hours!

There is also tutoring available from the Office of Learning Services. Contact them for details.

Course Description:

This course provides an introduction to programming and computation, including the concepts and usage of expressions, variables, control structures, functions, compound types, classes, objects, and I/O in a high-level programming language, along with their roles in implementing programs to solve common problems.

Course Objectives:

Upon completion of this course, students will demonstrate ability to:

  • Write, test, and explain the behavior of programs involving fundamental programming constructs, built-in data structures, standard libraries.
  • Construct, execute and debug programs using development tools; apply and implement structured problem solving; handle abnormal control flow; understand and rely on static type safety to reduce errors
  • Incorporate class design, encapsulation, and inheritance; incorporate data structures for problem solving; describe positive and negative ways in which software impacts society.


Required: Graci, C. and Schlegel, D.R. A First Course in Computer Programming: Laboratory Manual

Useful Resources:

Introduction to Computer Science Using Java
Introduction to Programming Using Java, 8th Edition
Think Java: How to Think like a Computer Scientist
Java Tutorials @ Oracle
Java 8 Standard Libraries @ Oracle
Java on Lynda.com

Important Links:

CS1 Web Site Resources
Student Web Pages

Attendance and Participation:

As per college policy, attendance in all sessions is obligatory. If you cannot attend a class meeting due to religious, athletic, health related circumstance, or circumstance of particular hardship, please notify me in advance via email. Please be ready to present proof, if necessary. It is expected that each person actively engage in each class session.

Classroom Etiquette:

A positive learning environment relies upon creating an atmosphere where all students feel welcome. Classroom discussion is meant to allow us to hear a variety of viewpoints. This can only happen if we respect each other and our differences. Hostility and disrespectful behavior is not acceptable.

Electronic devices may not be used during class by students in this course, including cell phones, laptops, headphones, etc.


If you construct knowledge you make it your own, and in doing so you get better at using it.  For this reason, slides from the course will, in general, not be posted online. Some selected materials, such as handouts, will be posted either on this page or on Blackboard.

“The art of being wise is the art of knowing what to overlook”
    — William James

Grading Summary:

Exam 120%
Exam 220%
Final Exam30%

The default grading for the course will be along the university’s standard grading curve:

A: 93-100C+: 77-79
A-: 90-92C: 73-76
B+: 87-89C-: 70-72
B: 83-86D+: 67-69
B-: 80-82D: 60-66
 E: 0-59

Grades may be adjusted downward as a result of poor attendance or poor engagement in programming assignments. If your participation in these is satisfactory your grade will simply be that as calculated above.


All assignments will be completed alone, but working together without writing or sharing code to come up with general solutions is encouraged. You are expected to post all of your programming assignments to your Web site.

Assignments will be demoed in-person to one of the TAs during their office hours. You will only have one chance to demo each assignment to the TA. They may ask you to modify your program in certain ways, or use specific input during the demo.

Assignments are considered on-time if they are demoed on or before the due date. Assignments may still be demoed up to two weeks after the due date, but with a 5% penalty per weekday past the deadline.

Note that no credit will be given for assignments which do not work, and partial credit will be given if only parts of the assignment are shown to work during the demo. From Assignment 2 onward, only assignments posted on your work site will be graded.

Your programming assignment grade does not figure directly into your course grade, unless your work is unsatisfactory, in which case your course grade (exam/lab grade) will be lowered by 1 letter grade. (Of course, it figures indirectly into your grade, since the learning that accrues as a result of completing the assignments will help you to prepare for the exams.)


You are required to attend the lab in which you are enrolled, and no other. For each lab, you will get a grade based partly on engagement in the lab during your regularly scheduled lab period, and partly on completion of the lab, on your own time, if need be. These grades will be assigned by your lab instructor. TAs cannot grade labs. Completion will be assessed by examining your web site.

The recommended approach for engaging in the laboratory component of the course is to do the following sequence of tasks for each lab:

  1. Prepare for the lab ahead of time by (a) attending class, and (b) reading through the lab in the Lab Manual.
  2. Refrain from beginning the lab ahead of time. The idea is for you to actually commence work on the lab when your lab period actually begins.
  3. Engage in doing the lab during your lab period. If you finish early, you should study your notes or one of the online textbooks listed in the Useful Resources section of this page. You will earn up to 70 points of the lab’s 100 points for appropriate participation in the lab during your laboratory period.
  4. Complete the lab on your own time, and indicate that you have done so by placing the relevant artifacts on your course web site. You will earn up to 30 points of the lab’s 100 points for doing so.

It is important to note that appropriate participation requires that you work from a hard copy of the lab. Should you fail to bring your Lab Manual or a hard copy of the lab to class, and determine to somehow proceed to work from an on-line copy of the lab, you will only be awarded 30 of the 70 points, at most, for being there and working on the lab.

Working on previous labs during your lab period is prohibited. If you need help in completing a lab that you did not finish during the lab period, you should seek help from a TA during one of their office hours.

Starting with week 3 of the course, it is required that you post artifacts from the labs on your web work site within two weeks of the lab period in which the lab was introduced.

If you miss no more than one lab period this semester, your point total will not be adversely affected. Your lab grade will be calculated as follows:

grade = minimum(100,score), where:
• score = ( ( ( pt + 70 ) / ( n * 100 ) ) * 100 )
• n = the number of labs
• pt = your point total based on the n labs


You may bring your three-ring lab binder to the exams, including any additional documents or notes you decide to augment it with. You may not bring any loose documents – they must be hole punched and organized in your binder. I recommend building this binder up incrementally as the course progresses.

Exams will be given during weeks 6 and 12 of the semester, as well as during finals week.

Each exam question will be assigned a point value, where the following general scheme will be used in grading it:

0 – Did not attempt / No serious attempt / Completely incorrect
1 – Mostly incorrect solution
2 – Somewhat incorrect solution
3 – Perfect solution

If the problem is a multiple of 3, then intermediate scores will be given as appropriate. If the problem is worth less than 3 points, partial points may be assigned. The total points received on all questions will then be summed and divided by the points possible and scaled as appropriate according to the percentages given above.


During the semester we will cover a great many topics, including:

Problem-solving strategies in programming
Good programming technique
Java syntax
Control flow of programs
Modeling classes in terms of state and behavior
String processing
Making use of external libraries
Array processing
Basic data structures such as ArrayList
File I/O

This syllabus and the course schedule are subject to change by the instructor. All changes and related justifications will be announced in class, and updates will be reflected in this web version.

1Monday8/26First day of class
Syllabus, Overview
Be sure to answer office hours survey!
Wednesday8/28TA office hours will begin 9/3!
Discussion of Lab 1
Algorithms and Algorithmic Thinking
Reading: Read Chapter 1: Entrance in the lab manual
Friday8/31Some thoughts on IntelliJ as a Cognitive Artifact
Introduction to Computational Microworlds
2Monday9/2No Class - Labor Day
Wednesday9/4Nonrepresentational Painting World (NPW)
Modular Melodic World (MMW)
Selected Sounds
Bring headphones to lab this week!
Thursday9/5Add Deadline
Friday9/6MMW, continued
MMW Example 2
CSA IDE Setup Workshop tonight at 6PM in Shineman 425
3Monday9/9MMW, concluded
Big Idea: Program like a tailor
Wednesday9/11Big Idea: Stepwise Refinement
A few notes on Lab 3
Assignment 1 due (demoed to a TA!) 9/25
Friday9/13How to Read a Program
Data Types
CSA Review Session: 6PM in 425 Shineman
4Monday9/16Drop Deadline
Variables, Constants and Expressions
Wednesday9/18Shapes World Problem Solving
Imaginative Construction
Assignment 2 due (demoed to a TA!) 9/27
Friday9/20Imaginative Construction
Data Types Revisited
Exam 1 is in 2 weeks!
5Monday9/23Practice Exam for Exam 1 on Blackboard
Exam Rules + Tips
Control Flow: Selection
Assignment 3 due (demoed to a TA!) 10/3
Wednesday9/25Introduction to Iteration
Superficial Signatures
Additional exercises for you to do to practice superficial signatures on Blackboard!
Friday9/27Anatomy of Methods
Iteration: Headers and Trailers
CSA Exam 1 Review Session 6PM in 425
6Monday9/30No Class - Rosh Hashanah
Wednesday10/2Examples of Headers and Trailers
Friday10/4Exam 1
7Monday10/7Start going over Exam 1
Wednesday10/9No Class - Yom Kippur
Friday10/11Finish going over Exam 1
Be sure to demo Assignment 2 by the end of the day today!
Be sure labs 1-5 are complete and on your website by Sunday!
Assignment 4 due (demoed to a TA!) 10/25
8Monday10/14Note-Taking Tips
Introduction to Arrays
446 closed from 10:30-1:30 for CSC241 Exam
10:15-11:15 office hours moved to Friday at the same time
Wednesday10/16Arrays, continued
Friday10/18Arrays & For Loops
9Monday10/21For loops, revisited
Arrays and ArrayLists
Do Lab 9a this week
Friday10/25Some ArrayList Tasks
Withdraw Deadline
List Processing
Assignment 5 due (demoed to a TA!) 11/11
Wednesday10/30Streams and Stream Pipelines
Practice exam for exam 2 on Blackboard!
Do Lab 9b this week
Dan's Thursday 8am office hours moved to Thursday 1pm this week
Friday11/1Class cancelled due to wind storm!
CSA Review 6PM in Shineman 425
11Monday11/4Streams, continued
Wednesday11/6Intro to Object Orientation
CSA Linux Workshop Wednesday 6PM in 425 Shineman
CSA Review Session Thursday 6PM in 425 Shineman
Friday11/8OO: The Card Class
12Monday11/11The Card Class, continued
Answers to the Stream exercises on Blackboard
Wednesday11/13Exam 2
Friday11/15The Card Class, continued
Test "Corrections" due November 22, start of class
Ground Rules for Test "Corrections"
13Monday11/18The Card Class, concluded
Dan at AMIA - video lecture to be posted on Blackboard 11/18 at 9am
Wednesday11/20Creating and Using Interfaces
Dan at AMIA - video lecture to be posted on Blackboard 11/20 at 9am
Friday11/22If you're registered for CSC221 next semester, there's an added section! Consider switching to it!
What Does it Mean to Learn Something New?
Assignment 6 due (demoed to a TA!) 12/6
14Monday11/25Exam 2 returned & reviewed
Final Exam Structure on Blackboard
Wednesday11/27No Class - Thanksgiving Break
Friday11/29No Class - Thanksgiving Break
15Monday12/2Lecture on Blackboard: Finish reviewing Exam 2
Reminder: Labs 1-12 must be posted to your website by the morning of 12/9.
Reminder: Last day to demo assignments is 12/6
Wednesday12/4Developing some algorithms...
Friday12/6Selection Sort
Last Day of Class
Finals WeekWednesday12/11Final Exam 8:00-10:00am in 315 Park

Academic Integrity:

SUNY Oswego is committed to Intellectual Integrity. Any form of intellectual dishonesty is a serious concern and therefore prohibited. You can find the full policy online. While it is acceptable to discuss general approaches with your fellow students, the work you turn in must be your own. You may not turn in code found on the internet. If you have any problems doing the assignments, consult the instructor. See my page on plagiarism for an explanation of what I consider cheating.


If you have a disabling condition which may interfere with your ability to successfully complete this course, please contact Accessibility Resources located at 155 Marano Campus Center, phone 315.312.3358, access@oswego.edu

Clery Act/Title IX Reporting:

SUNY Oswego is committed to enhancing the safety and security of the campus for all its members. In support of this, faculty may be required to report their knowledge of certain crimes or harassment. Reportable incidents include harassment on the basis of sex or gender prohibited by Title IX and crimes covered by the Clery Act. For more information about Title IX protections, go to https://www.oswego.edu/title-ix/ or contact the Title IX Coordinator, 405 Culkin Hall, 315-312-5604, titleix@oswego.edu. For more information about the Clery Act and campus reporting, go to the University Police annual report: https://www.oswego.edu/police/annual-report.