Summer 2000, CSC 134 70 2, MW 6:00-9:00 PM, Curtis 208

Norm Lippincott, Curtis 105, 610-606-4666 ext. 3697

July 5 to August 10, Monday & Wednesday, 4:30-6:00 PM.

Hanly, J. & Koffman, E.; Problem Solving & Program Design in C, 3ed., Addison Wesley, 1999.

Structured programming in C/C++ is implemented to solve larger and more complex problems. Topics covered are string processing, record structures, file organization, and dynamic data structures including linked lists and nonlinear structures. Prerequisite: CSC 133.

The grade for the course will consist of five components weighted as follows:

Lab Assignments (5) 50%

Tests (2) 25%

Final Exam 20%

Class Participation 5%

Lab assignments will involve the C/C++ programming language. Microsoft Visual C++ is available on-campus for programming assignments. Any other standard C++ compiler may be used as well. A good free compiler is available at http://www.delorie.com/djgpp.

The tests and final exam will be written and may include problems, short answer questions, and essays. The final exam is comprehensive.

A final grade percentage will be computed according to the weights above and rounded to the nearest full percent. Final grades will be awarded as follows:

93-100 A 77-79 C+

90-92 A- 73-76 C

87-89 B+ 70-72 C-

83-86 B 67-69 D+

80-82 B- 60-66 D

0-59 F

Date Topic / Reading List

7/5 CSC 133 Review

7/5, 7/10 Ch. 9 – Strings

7/12 Ch. 11 – Structure and Union Types

7/17, 7/19 Ch. 12 – Text and Binary File Processing

7/19 Test 1 – Chapters 9 & 11

7/24, 7/26 Ch. 10 – Recursion

7/26 Ch. 13 – Programming in the Large

7/31, 8/2, 8/7, 8/9 Ch. 14 – Dynamic Data Structures

8/2 Test 2 – Chapters 10, 12, & 13

TBA Final Exam

This schedule is to be used as a guideline for the reading required for the class. You should read the class material in advance of coming to class. This course schedule is subject to change.

Assigned on Due on

Lab #1 7/5 7/12

Lab #2 7/12 7/19

Lab #3 7/19 7/31

Lab #4 7/26 8/7

Lab #5 8/2 8/14

When turning in lab assignments, turn in a printed copy of the C/C++ source code (".c" or ".cpp" file), as well as your written analysis of the problem. Your written analysis should be done before you start writing the program, and it should be your plan as to how you will solve the problem.

Also e-mail your source file (".c" or ".cpp" only) to the instructor at nlippinc@cedarcrest.edu. Begin the subject line of your e-mail with "CSC133" in all caps with no space. This will cause your e-mail to be saved to a special folder for grading. Do not include the executable (".exe") or any other project files.

Programs should be well documented, including comments throughout that describe what you intend the program to do. You should also include a comment block at the top of each program that includes your name, course number, date, and a brief description of the program.

Be sure to obtain a network login account by the second day of class, as we will be using Microsoft Visual C++ during class.

Attendance will be taken for each class, however record of attendance does not directly affect the student’s grade. The student is responsible for all material covered in class. If a student has excessive absence and is not showing responsibility for the course material, an academic performance notice will be issued to the Advising Center. If a student will be absent on the day of a test, arrangements for a makeup must be made in advance of the test. Failure to do so will result in a grade of zero for the test.

Assignments and projects are due at the beginning of class on the day they are due. By turning in assignments on time your work will be graded and returned in a timely manner (usually by the next class meeting), and with comments as appropriate.

Work turned in late will be subject to any or all of the following:

1. A 1 point penalty (on a scale of 10) will be assessed; 2 points if work is a week late or more.
2. The assignment may be graded without comment.
3. The assignment will be graded and returned at the instructor’s convenience, possibly as late as the end of the semester

The Cedar Crest College Student Handbook, Honor Philosophy (pp. 10-12) part III, Community Standards for Academic Conduct, includes the following:

"As a student at Cedar Crest College, each student shall:

• Only submit work which is his/her own.
• Adhere to the rules of acknowledging outside sources, as defined by the instructor, never plagiarizing or misrepresenting intellectual property.
• Neither seek nor receive aid from another student, converse with one another when inappropriate, nor use materials not authorized by the instructor."

Unless specifically designated by the instructor, assignments for this course are individual assignments, not group projects. It is reasonable and appropriate for students to discuss an assignment outside of class, particularly for programming projects. However, the actual assignment work, whether programming or written, is to be one’s own. It is not appropriate to collaborate on programming assignments, nor is it appropriate to copy another student’s program, alter the program’s appearance (e.g. changing formatting, variable names, output text), and present it as your own individual work. Evidence of such behavior will be considered a violation of the Honor Philosophy and will result in a grade of zero for the assignment. A second offense will result in a grade of "F" for the course.

Appropriate classroom behavior is implicit in the Cedar Crest Honor Code. Such behavior is defined and guided by complete protection for the rights of all students and faculty to a courteous, respectful classroom environment. That environment is free from distractions such as late arrivals, early departures, inappropriate conversations and any other behaviors that might disrupt instruction and/or compromise students’ access to their Cedar Crest College education.