| Instructor: | Rich Maclin |
| Email: | rmaclin |
| Office: | 319 Heller Hall |
| Phone: | 726-8256 |
| Office Hours: | 2:00-4:00 Tuesday, Wednesday, and by appointment |
| Texts: | Forouzan and Gilberg, Computer Science: A Structured Programming Approach Using C, PWS Publishing |
| Nagler, Learning C++: A Hands-On Approach, West |
Your recitation instructor's office number, phone number and office hours will be announced at your first recitation session.
This course is the second part of an introduction to computer science. In the first two thirds of the course we will cover topics starting from Chapter 8 in the Forouzan and Gilberg book. In the last third of the course we will discuss the programming language C++ in terms of how it differs from C and some of the unique features of C++. As with 1621, this is not just a course in computer programming, you will also learn to solve problems in a top-down fashion, how to modularize your code, and how to document your programs properly.
| Item | Points | Date and Time |
|---|---|---|
| Midterm Exam 1 | 75 points | January 8 (Friday), 12:45-13:50 |
| Midterm Exam 2 | 75 points | February 5 (Friday), 12:45-13:50 |
| Final Exam | 150 points | February 23 (Tuesday), 8:00-9:55 |
| In-Lab Assignments (10) | 50 points | weekly |
| Programming Assignments (5) | 200 points | TBA |
| Homework Assignments (6) | 50 points | TBA |
| Total | 600 points | Grade based on total points |
We will meet in large lecture on Mondays, Wednesdays, and Fridays, when new material will be presented. We will follow the text generally, but non-text material may also be included in the lectures. The midterms and final exam will also be given in large lecture (the midterms will occur during class hours). Dates are given on the above schedule.
On Thursdays you will meet with your recitation group in an assigned (non-lab) room. In these sessions, you will discuss the material presented in lecture, go over exams, hand out and discuss programming assignments, and work problems from the text. Your lab supervisor and recitation instructor will be a Computer Science Department graduate student. Dates of all important lab and recitation events are also given on the term schedule.
On Tuesdays you will meet in lab (SBE 45 or Engr 204). During the lab sessions you will have an opportunity to apply what you learn from the lectures and reading by designing, writing, and testing programs under the supervision of your recitation instructor. Each lab day will have a short lab assignment you must complete as part of your lab. You will also have time to work on your programming assignments. For all but the simplest programming assignments, the one hour of supervised lab will not be enough to complete them. You will also need to work on them outside of your scheduled lab hour.
No exam will be given early. Exams can be made up only in the case of emergencies such as severe illness or death in the immediate family. You must contact me 24 hours in advance in order to arrange a makeup.
Lab Reports: Programming is only a small part of the total discipline of computer science. When you turn in a lab report documenting a programming assignment, it is not just a copy of the program that you wrote, it is a report of the entire process by which you conceived, designed, wrote, and tested a solution to the original problem. This report is expected to be well thought out, neat and complete. You will receive guidelines for producing this report when you report to your first lab.
Cheating: Programming assignments and homework must be your own work. You may discuss general ideas with other students, but should not discuss actual code with others. If you are having problems with an assignment, please come and see me or send me email.
Late Assignments: Homework assignments are due at the start of class on the due date. Since you will generally review some of the problems from the homework during class, homework assignments can not be handed in late. All programming assignments will be collected by 4:00 on the due date. You may hand in the assignment during class or you may put it in your TAs assignment box (note, make sure to put it only in YOUR TAs box, placing the assignment in another box does not guarantee it will be counted as being in on time). Boxes for the TAs are located in the Computer Science department office (Heller Hall 320), the boxes are on top of the cabinet that is around the corner to the left when you first enter the office (across from the reception desk). For the quarter you will be allowed a total of two late days for programming assignments. This means that you may hand in one programming assignment two days late or two assignments one day late each. An assignment is late if it is handed in past 4:00 on the due date. One late day will then be charged if the assignment is handed in by 4:00 on the next school day, two late days will be charged if the assignment is handed in by 4:00 on the second school day after the assignment is due. Note that once you use up your two late days you must turn in all assignments on the due date.
As instructor I shall make every attempt to treat all students equally, without regard to race, religion, color, sex, handicap, age, veteran status, or sexual orientation. I encourage you to talk to me about your concerns of equal opportunity in the classroom. To inquire further about the University's policy on equal opportunity, contact the Office of Equal Opportunity (6827), 255 DAdB.
If you have any disability (either permanent or temporary) that might affect your ability to perform in this class, please inform me at the start of the quarter. I may adapt methods, materials, or testing so that you can participate equitably. To learn about the services that UMD provides to students with disabilities, contact the Access Center (8727), 104 Cina Hall, or the Office of Equal Opportunity (6827), 255 DAdB.