| Course Title | CS 162 Computer Science II |
| Prerequisites | CS 161 or equivalent |
| Section | 30388 |
| Credit hours | 4 |
| Time | Monday and Wednesday 6:00 PM - 8:20 PM |
| Place | PCC-Sylvania , Room SS 103 |
| Instructor |
Matthew Mead E-mail: mmead@pacifier.com Home/office: (360) 892-5174 |
| Office hours | Monday and Wednesday 5:00 PM - 5:50 PM in the Computer Center Lab and after class. |
| Textbook | Programming and Problem Solving with C++, by Nell Dale, Chip Weems, and Mark Headington. You can download a file that contains all of the programs in the textbook here . There is also a lab book for this course entitled Introduction to Programming in C++ A Laboratory Course, by James Roberge and George Smith. A file is available that contains all of the programs in the book. You can get it here . |
| Course description | Continues the study of problem solving using program design methodology and structured programming. Introduction to software design using a variety of data structures. Covers algorithms for storing and manipulating data including records, files, linked lists, stacks and queues among others. |
| Goals | This course is a continuation of the topics learned in CS 161. New concepts will also be discussed which will allow the student to implement more complex programs. Emphasis will be on the design of programs as well as the data structures and methods used in larger programming projects. Upon completion of the course, the student should have a good understanding of the C++ language and how to apply it in solving real-world problems. |
| Computing Environment | Students will complete programming projects using both MS-DOS and UNIX. Borland's Turbo C++ will be used on the DOS platform, and the xlC compiler will be used under AIX in the CRC lab at PCC. It is possible that by the time class begins in the summer Microsoft's Visual C++ may be installed and in-use in the lab instead of Turbo C++. Students are welcome to use any environment at home or at their work to complete the programming assignments. |
| Attendance | Attendance is not mandatory, but it is strongly suggested as you will be responsible for all material covered in class, whether or not it is in the textbook. |
| Homework | Homework is due at the beginning of class. The paper copy is due in class and any e-mailed portion is due before the time class begins. Late assignments will not be accepted. It is better to hand in an incomplete assignment than none, since partial credit will be liberally given. If either the hard copy or email copy is not turned in, the assignment is considered late. Repeat: No late assignments will be accepted. 25% percent of the grade on a homework assignment is based on programming style, comments, clarity, and documentation. This means that even if you turn in a program that runs perfectly, you can expect a grade no higher than a C if you fail to adhere to good programming standards. Remember, partial credit will be awarded for incomplete assignments. Details for submitting homework are here. |
| Exams | There will two exams during the term. If you are unable to attend the exam on the date and time given in the syllabus, you must reschedule the exam (with the instructor's permission) in advance. The exams will be closed-book and closed-notes. |
| Grading | The midterm will account for 20% of your grade, and the final will
account for 30%. The homework assignments will account for 50% of your
final grade. Letter grades are awarded as follows:
|
| Students with Disabilities | PCC encourages students who have disabilities to contact the Office for Students with Disabilities for assistance in requesting classroom accommodations. I encourage students who have disabilities to meet with me to arrange for accommodations related to lectures and programming lab assignments. |
| Got Questions? | Email is the best way to get a quick response to a question. I am usually connected to the internet throughout the day, so I receive email constantly. Email works best when you encounter a problem while working on the programming assignments and don't want to wait until office hours. If you send questions or problems via email, be as concrete as possible. Sending me your whole program with a question like "Why doesn't my program work?", will probably get a response like "I give up, why doesn't it work?" If you are getting error messages when compiling or running your programs, you should write down the exact error message that you received. There are many, many possible error messages, and some are only slightly different than others. Also, if you are given the line number of the error, be sure to include the number and the line of code that generated the error. Tell me what you have tried to do to solve the problem on your own before asking for help. Learning how to debug programs is a very important skill that you must acquire if you are to be a successful programmer. |