CSC 160 Computer Science I
Winter 2016

Course Description

CSC 160 Computer Science I (3.50)

CSC 160 An introduction to computer science and programming emphasizing the development of algorithms and their implementation in Java using both procedural and object-oriented approaches. Topics include data types; assignment statements; I/O; arithmetic, relational and logical operators; control structures for selection and iteration; functions; the use of classes and objects; simple data structures, such as arrays; graphical user interfaces and event-driven programing. Extensive programming required. May not be taken after a higher level programming class.

Instructor Accessibility

My office is in Carnegie Hall 311 B. You can stop by in person, or call my office at 630-637-5174. If I am not at the office and you need immediate attention, you can call me at home at 630-759-2110. You can email me at gcmuganda@noctrl.edu. Winter term office hours are Mondays and Wednesdays 5:00- 6:15 pm; Fridays 9:30-12:00 Noon.

I can also see you by appointment.

Course Textbooks

Tony Gaddis and Godfrey Muganda, Starting Out With Java: From Control Structures through Data Structures, Third Edition, Pearson, 2016

Course Outline

This schedule of weekly topics is highly tentative and subject to alteration as the term progresses.

Week Course Topics Chapters
1 Introduction to Computers and Java Chapters 1 and 2
2 Data Types and Control Structures Chapters 2, 3, and 4
3 More on Control Structures; Intro to Arrays and Files Chapter 4
4 Classes and Methods Chapters 5 and 6
5 More on Classes Chapter 6
6 Class Inheritance and Interfaces Chapter 10
7 Graphical User Interfaces Chapter 12
8 More on Graphical User Interfaces Chapter 12
9 Array Searching and Sorting Chapter 7
10 Exceptions and Exception Handling Chapter 11

Schedule of In-class Quizzes and Tests

All tests and quizzes will be on Mondays unless otherwise announced.

Class Event Date Percent Weight
Quiz 1 Week 3 5%
Test 1 Week 5 15%
Test 2 Week 8 15%
Final Exam Week 11 25%

In addition to the tests, there will be a number of homework/ programming assignments. These will will count for 40% of the course grade. They will be designed to help you understand course concepts and prepare you for the in-class quizzes and tests. Some of the tests and quizzes may involve writing short programs based on the concepts covered in lectures and in the programming assignments.

Email Communication

All assignments and projects must be submitted via email using your College email account. and must have a subject that begins with CSC 160 Homework Submission, followed by the assignment or project being submitted. For example, CSC 160 Submission of Project 1, or CSC 160 Submission of Homework 3. When asking a question or requesting help via email, your subject must begin with CSC 160 Help: ...

Late Policy

All assignments and projects should be turned in by midnight on the day due. A 10% penalty will be assessed on projects turned in late, but in general this penalty will not be levied if the assignment is turned in before I have completed grading the batch of assignments to which it belongs. No assignment/project turned in after the due date for the next assignment/project will be graded. I will make an exception to this rule for students who have been coming to see me for help, where I judge that the student is reasonably close to getting the assignment or project done.

Policy on Missed Quizzes and Tests

In-class tests and quizzes missed without a legitimate excuse cannot be made up. If you have to miss quiz or test (for some legitimate reason) please let me know at least a week before and I will make arrangements for a make up. In the event some unexpected reason beyond your control prevents you from being in class on the day of a test, contact me as soon as possible by phone or email to arrange a make up.

Ethics Policy / Academic Dishonesty.

No student should turn in for grading work that has been done by someone else, or work on which they have received help but which they do not understand. Any work turned in by a student will be considered to have been plagiarized if the student can not explain it when requested to do so by the instructor. It will also be considered to have been plagiarized if there is clear evidence that the work has been copied from another source, even if the student can explain it.