CPSC 170: Fundamentals of Computer Science II

Spring 2003

Instructor:Dr. Adrienne Bloss Office Hours: Mon, Wed: 2:40 - 3:40
Office: 365-C Trexler Tu, Th: 10:00 - 11:00
Phone: 375-2434 Also by appointment
E-Mail: bloss@roanoke.edu

Course Objectives: This course is a continuation of an introduction to the discipline of computer science. The course focuses on the design of algorithms to solve problems and the implementation of the algorithms in the programming language Java. Students will learn the programming concepts of arrays, list data structures, recursion, and object-oriented programming. Students will be introduced to formal proofs (with an emphasis on mathematical induction) and computational complexity and learn to apply these concepts to reasoning about algorithms and programs.

Text: Java Software Solutions: Foundations of Program Design, 3rd Edition, by John Lewis and William Loftus, Addison-Wesley, 2003.

Lab: This course has a required three-hour lab every Tuesday afternoon from 2:40 until 5:40. The purpose of the lab is to give the student a structured experience in software design, implementation, testing, and measurement, and to increase the student's ability to use and understand the tools available for software development in the Linux environment. Some labs may have a pre-lab assignment designed to prepare the student for lab. The assignment must be handed in at the beginning of lab. Unless otherwise specified, the lab itself must be done during the lab session and turned in before leaving. Some labs will have a post-lab assignment designed to reinforce lab concepts. Typically the post-lab assignment will be due the second class period following the lab. Late lab work (including pre-lab and post-lab hand-ins) will receive no credit unless special arrangements have been made.

Programming Projects: Programming projects are designed to give the student the opportunity to put into practice the problem solving and programming skills they have learned. As such they are one of the most important aspects of the course both for student learning and for assessment. There will be 4-5 projects during the semester to be handed in for a grade. You are encouraged to start on your projects immediately when assigned and get help from the instructor as needed.

Important: Projects are to be done individually. You may ask class members, lab assistants, and others for help with system questions (e.g., "How do I save a file in emacs?", "How do I run my Java program?") or general information about a topic covered in class (e.g. "What is the symbol for boolean AND?") provided you can do so without divulging or receiving information specific to the solution of the programming project. You may not discuss any aspect of the design or coding of a programming project with anyone except me. This policy will be strictly enforced; see the section on Academic Integrity below.

Late Policy for Projects: Unless otherwise specified, projects are to be turned in by 4 pm on the due date. Five percent per calendar day (24 hours) will be deducted for late work; work more than 5 days late will usually receive no credit. If you anticipate being unable to meet a deadline, talk to me before the deadline; in extenuating circumstances we may be able to make special arrangements.

Attendance Policy: Class attendance is crucial for success in this course. The student is expected to attend every class and lab and is accountable for any missed classes and labs.

Course Topics and Schedule (Tentative)

Week of Topic Sections in text
Jan 13 Arrays 6.0-6.1
Jan 20 Sorting (selection, insertion)
Searching (linear, binary)
2D arrays
Jan 27 Computational complexity
Functions (poly, exp, log)
Sums(i, i^2)
Applications in searching, sorting
Class notes and handouts
Feb 3 Inheritance and abstract classes
** TEST 1 **
Ch 7
Feb 10 More inheritance
7.6,7.7, Ch 9
Feb 17 Mathematical induction
Class notes and handouts
Feb 24 Recursion
** TEST 2 **
Ch 11
March 3 !!!!!!!! Spring Break !!!!!!!!
March 10 Recurrence relations Class notes and handouts
March 17 Software engineering, collections Ch 10, 12.0
March 24 Linked Lists 12.1
March 31 More linked lists
Stacks and queues
** TEST 3 **
Ch 12.1-12.2
April 7 Exceptions and IO Streams Ch 8
April 14 Wrap-up and catch-up

Grading Policy: The course grade will be based on 3 tests, lab work (including pre and post lab assignments), programming projects, and a comprehensive final examination. The course grade is determined using the following weights:

tests.....40%       lab.......15%       projects.......20%       final exam......25%

Tentative Test Dates: Test #1 Friday, Feb 7
Test #2 Friday, Feb 28
Test #3 Friday, April 4
Final Exam Monday, April 28 (8:30 - 11:30 am)

Grading Scale: 93-100A        83-86B        73-76C        63-66D
90-92A-        80-82B-        70-72C-        60-62D-
87-89B+        77-79C+        67-69D+        below 60F

Make-up Policy: Everyone is expected to take tests and the exam and do labs at the scheduled time. Make-ups will be given only for legitimate, documented absences that the instructor has been notified of ahead of time. Make-up tests, if given, may be oral.

Academic Integrity: All tests, exams, and programming projects are to be the work of the individual student. You are encouraged to get help from the instructor if you need help with any aspect of the course including programs and assignments. Student assistants, tutors, and classmates may help you in the operation of the computer but not with the substance of any work, other than lab work, that is to be turned in for a grade. They may help you understand course concepts but may not show you how to do any particular aspect of a programming project. Students may discuss lab work (including the pre and post lab assignments) and help each other but in all cases the work you turn in must be your own. Copying someone else's work or turning in someone else's work is NEVER allowed. Using someone else's work or ideas as your own is plagiarism and an academic integrity offense. Examples of academic integrity violations include copying a program or part of a program (even one line) from someone else, writing code for someone else, telling someone else how to solve a problem or having someone tell you how to solve a problem. Discussion among students about programming projects (besides labs) should be limited to general concepts, not specific aspects of how to complete the work.

Computer Use Policies: All students must abide by the Computer Use policies of Roanoke College. Failure to do so will result in involuntary withdrawal from the course.