CS 173 Introduction to Computer Science II Spring 2003  

Course Specifics

Course Computer Science 173 - Introduction to Computer Science II
Course Links Course links
Course Schedule Online Schedule
Required Texts Data Structures and Algorithms in Java, 2nd Edition, by Michael T. Goodrich and by Roberto Tamassia. John Wiley & Sons, 2001. ISBN: 0-471-38367-8.
Schaum's Outlines of Programming with Java, by John R. Hubbard. McGraw-Hill, 1998. ISBN: 0-07134210-9.
In the Beginning...Was the Command Line, by Neal Stephenson. Avon Books, 1999. ISBN: 0380815931.
Credits 1 unit
Prerequisites CS 171 (formerly Math 251). Mathematics 141 is strongly recommended.
Time MTuWF 2:10 - 3:00 PM
Location 108 Palenske (MTuWF)
Content This course is a continuation of Computer Science 171. Emphasis is on abstract data types (stacks, queues, lists, strings, trees, graphs, etc.) and analysis of algorithms. Other topics include pointers, recursion, searching and sorting, simulation, and an introduction to object oriented programming. Students also will refine their programming skills in the Java programming language.
Course Web Page http://zeta.albion.edu/~dreimann/Spring2003/courses/cs173/
Instructor David A. Reimann
Students http://zeta.albion.edu/~dreimann/Spring2003/courses/cs173/students.shtml
Student Assistants TBD
Office 304 Palenske
Office Hours MWF 11:00 - 12:00 noon, and by appointment
E-mail dreimann@zeta.albion.edu
Phone (517) 629-0426 (Office)
(517) 629-2646 (Home, 7-9 PM)

Overview

This course is designed to be the second computer course in computer science. There is a significant computer lab component, which involves programming in the Java language. We will be using the computers in the Sleight Computing Laboratory, which are running the Linux operating system.

Some may find the laboratory component to be difficult and time consuming, but it can also be the most fun and rewarding aspect of the course. Later labs build on knowledge you gain from earlier labs, so it is imperative that you keep up progress in each lab. Failure to do a lab will make it extremely difficult for you to successfully complete the next. You should ask any questions you might have as soon as possible. Do not hesitate to ask questions related to the projects in the laboratory. Unlike CS 171, much of the laboratory will be independent. This places a significant responsibility for time management in your hands.

Again, if you don't ask questions either in class, lab, or in my office during office hours, I will assume you understand the material. My purpose here is to help you understand computer science. In asking questions, you will hopefully gain the missing link which connects the information you have acquired and transforms it into a coherent conceptual model.

Performance Evaluation

Grade Element Possible Points
Attendance 106 (53 @ 2 points each)

Homework Problems
180 (Chapter Specific)
Computer Projects
See Schedule
273 (13 @ 21 points each)
Tests (3)
300 (3 @ 100 points each)
Book Response Paper 40
Final Exam 100
Total Possible Points 999
Your Points Your Grade
930+ 4.0
900-929 3.7
870-899 3.3
830-869 3.0
800-829 2.7
770-799 2.3
730-769 2.0
700-729 1.7
670-699 1.3
600-669 1.0
0-599 0.0

Some extra credit is possible. The daily response form gives you an opportunity for extra credit nearly every day. I might include an occasional extra credit exam question. I have also scheduled several weeks (2, 4, 8, and 13) where I will have special office hours where you will receive 5 points (up to 20 points total) for coming to talk with me in my office about course issues (above and beyond normal office hours). See this link for more details. I will not give much special extra credit beyond this. You should plan on doing the work assigned to succeed in the course.

No credit will be give for a missed test or other scheduled in-class assignment. No credit will be given for daily responses which are not received by the due date. All assignments are due at the beginning of class on the due date unless otherwise specified. Your promptness will allow my timely grading of your assignments. Work turned in late might not be graded and returned as quickly. Late assignments will be accepted, but marked down as follows: up to 24 hours late - 25% off. from 24 hours up to 48 hours late - 50% off. Assignments will not be accepted after 48 hours. Penalties are assessed from the earned score, rather than the possible points earned. Some credit on a partially complete assignment is better than no credit and the burden of an unfinished task. If you miss class on the date an assignment is due because of participation in an official College event you must make prior arrangements with me. In situations of a documented serious circumstance beyond your control, please contact me as soon as possible.

You have an opportunity to review your final and other term projects for four weeks after the start of the subsequent semester. After that time, I will discard all unclaimed materials.

Academic Policies

If feel you have a disability which might interfere with your success in this class, please contact the Office of Academic Affairs immediately so that we can coordinate any required accommodations.

The goal of this course is for you to learn computer science, not penmanship, typing, or other forms of plagiarism. Chapter III of the Student Handbook details instances and penalties for academic dishonesty. It also describes acceptable usage of the campus computing/networking facilities. In this class you are expected to do your own work unless explicitly stated. This includes programming assignments, homework problems, and exams.

Here are some things which will be considered cheating:

  • Using or turning in another's work as you own - with or without their permission.
  • Allowing someone else to use or turn in your work as theirs - in whole or in part.
  • Joint effort on an assignment with individual submissions represented as individual work.
  • Getting help by another with logical or design errors without acknowledgment.
  • If I receive two programs from different individuals which are too similar in structure and design to be from chance.
  • If a student cannot explain why the solution works or how the solution was obtained.
Here are some things which are encouraged:
  • A submission using help from the instructor, student assistants, or the texts.
  • Obtaining help for a minor programming error, For example, proper syntax and compiler options.
  • Discussion of the concepts related to the course material.
  • Discussion of assignments to understand what is required.

Class absences are only excusable in documented extreme cases of unforeseen hardship or official College event, as described in the Student Handbook. Please notify me in writing (email is preferred) prior to official college events (sporting, class trips, etc.) that make it impossible for you to attend class. In extreme cases of unforeseen hardship, please contact me as soon as possible. In either case, you are still responsible for all material and assignments.

Typically, I grade papers one problem at a time. If you turn in someone else's work as you own, it really stands out. Please do your own work! I often run sentences from papers through web search engines. This is often very interesting. Don't download a paper and pretend like its yours! For computer programs, I have written software to compare your program with all other students' programs (even in previous semesters if a project is similar). Please write your own code! If you are having trouble on an assignment come see me as soon as possible - I'm here to help!

We, as students and faculty, have the privilege and challenge of promoting higher standards of ourselves, the College, and society in general. Here are several expectations we should have this semester.

What you should expect of me. What I expect from you.
To attend class regularly and punctually and to adhere to the class schedule. To attend class regularly and punctually.
Come to class prepared. Come to class prepared.
Grade and return work in a reasonable amount of time. Fulfill all course assignments and requirements.
Know course material thoroughly and prepare and present it conscientiously. Uphold academic honesty in all activities.
Maintain scholarly, professional, and courteous demeanor in class. Maintain scholarly, professional, and courteous demeanor in class.
Be available at reasonable times for consultation. Keep all appointments except for extreme cases.

Communication is essential in any relationship. Our student-teacher relationship is no exception. If you have any concerns with the class material or logistics, please talk to me as soon as possible.

You can certainly survive this course without visiting me, however, as the above Frank and Ernest cartoon indicates, we can all do better with a little help from others. This is why I, and all other faculty, have office hours.


Copyright © 1996-2003, David A. Reimann. All rights reserved.