UMBC CMSC 104 CSEE | 104 | current 104



Section 6082

Instructor: Sue Bogar
Office: ECS 225D
Office Hours: TuTh 3:30 - 4:30 or by appointment
Telephone: 410-455-3964

Teaching Assistant: Wiboonsak Wattayu
Office: ECS 335A
Office Hours: TBA

Section 6081

Instructor: Dawn Block
Office: ECS 332
Office Hours: TuTh 4:30-5:30 or by appointment
Telephone: 410-455-6336

Teaching Assistant: Sunder Parameswaran
Office: ECS 335A
Office Hours: TBA

Lecture Times and Places

Section 6081: Tues & Thurs 6:00 p.m. - 8:20 p.m., ACIV 014 Block Section 6082: Tues & Thurs 1:00 p.m. - 3:20 p.m., ACIV 014 Bogar


C How to Program by H.M. Deitel and P.J. Deitel, Prentice Hall, 3rd edition

Course Homepage

The homepage for this course can be found at:

Course Description

This course will give the student an overview of Computer Science focusing on problem solving and algorithm development. The C programming language will be introduced by covering the beginning chapters of the textbook. The following is a list of the topics that will be covered:


Your final grade will be broken down as follows.

3 Homeworks = 12% (each Homework worth 4%) 4 Projects = 28% (each Project worth 7%) 3 Exams = 60% (each Exam worth 20%) Total = 100%

Final letter grades will be determined as follows.

90% <= A <= 100% 80% <= B < 90% 70% <= C < 80% 60% <= D < 70% 0% <= F < 60%

Final grades will NOT be curved.

A grade of "I" (Incomplete) will only be given in the case of a verifiable medical emergency or other such dire circumstance. See Taking Responsibility below.

Taking Responsibility


You are expected to attend all classes. If you miss a class, you are responsible for getting the notes and any verbal information given during class from a fellow classmate. (If handouts were given out, you may come to my office to get them.)


Please be on time! Class begins at the scheduled time. Being late is disruptive to the class. Habitual tardiness will not be tolerated.

Responsibility for Class Material

You are responsible for all material covered in lecture, even if it is not in the textbook. You are responsible for the material in the readings, even if they are not covered during lecture. The readings are listed in the Lecture Schedule.


Use e-mail in an appropriate and mature manner. See Making the Most of E-mail below.


Project Submission and Grading

The critical programming skills cannot be learned simply by attending class. You should budget enough time to work on the projects as well. Programming projects will be graded based on the following:

All projects must:

If a project does not compile and produce reasonable output, it will receive a zero. "Reasonable output" will be explained in class. If you ever have a doubt as to whether or not your project produces reasonable output, ask your instructor before submitting it.

All projects must compile on the linux computer under the "gcc" compiler ( This is the compiler that the grader will use to compile your program.

All projects are due by midnight on the date listed in the Lecture Schedule. No late projects will be accepted.

Be aware that the linux system may go down from time to time. You are given ample time to complete your projects, so such downtimes, no matter how long and when, are no excuse for your project being late. For those using the network via ResNet, ResNet being down is no excuse for a late project either. If ResNet goes down, get to a computer lab and complete your project.

You will be turning your projects in electronically. Details will be explained in class before you need to submit your first project.

Your Project Must Be Yours

All projects must be completed by your own individual effort. You should never have a copy of someone else's project either on paper or electronically under any circumstance. Also, you should never give a copy of your project, either on paper or electronically, to another student. This also means that you cannot "work" on the project together.

I will be using special software to check for cheating. The software is quite sophisticated and has "surprised" some students in the past. We will, of course, not release the details of the internal workings of this cheat-checking software, but you are forewarned that there is no difficulty in comparing every pair of submitted projects --- even for projects submitted to other sections of this course.

Your project will be checked for similarities with all other student projects. If your project is found to be "substantially similar" to that of another student, both you and the other student will receive a grade of 0 for that project. Furthermore, all parties concerned will have their prior projects checked for cheating. A second incident will result in a grade of 'F' for the semester.

Any act of dishonesty may be reported to the University's Academic Misconduct Committee for further action. Egregious cases of cheating will be written up as a "more serious" infraction. In this case, you will not be allowed to drop the course. Also, a "more serious" infraction would appear as a permanent part of your student record and would be seen by potential employers when they ask for an official copy of your transcript.


The exams will be closed-book and closed-notes. The test dates for the exams are listed in the Lecture Schedule. In the case of a verifiable medical excuse or other such dire circumstance, arrangements must be made with your instructor immmediately for a makeup exam. You are responsible for initiating these arrangements, not your instructor.

The date and time for your final exam (Exam 3) is listed in the Lecture Schedule.

General Academic Dishonesty

Academic dishonesty is serious and will be dealt with severely, including the possibility of being reported to the University's Academic Misconduct Committee. Academic dishonesty includes, but is not limited to:

For a more complete description of academic dishonesty, refer to the UMBC Student Handbook.

Making the Most of E-mail

E-mail is a great way to communicate. It can save both of us a lot of time and also allows you to receive answers to questions outside of class. Realize, however, that it is not always the most appropriate way to communicate with me. Some topics are best discussed during my office hours or an appointment.

Using E-mail For This Class

In order to facilitate communication, please observe the following rules.

Any e-mail that does not follow these rules will be returned unanswered. It is up to you to determine which rule was not followed. Any e-mail that is disrespectful, offensive, or threatening will receive no reply.

I do my best to answer my e-mail in a timely and thorough manner. But backups do occur, especially around project due dates. Do not hold up turning an assignment in because you are waiting for a reply to your e-mail.

When I reply to your e-mail, I will reply to the address from which it was sent. However, if I initiate an e-mail, it will be sent to your gl account. So, be sure to check your gl account regularly and frequently.

For your benefit, hold on to all e-mails concerning policies and grades.

Last modified: Monday, 27-May-2002 13:11:40 EDT