|UMBC CMSC 104 Spring 2001||CSEE | 104 | current 104|
Note that we will not be using the PowerPoint slides that are linked from this page. We will be using slides found under the Lectures link at
You may find it helpful to get a printed copy of the lecture slides before the class in which they will be used. I will show you how to get printed copies of the slides when I take you to the computer lab. Until that time, I will bring printed copies to class for everyone.
Final letter grades will be determined as follows.
Final grades will NOT be curved. Do not ask.
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.
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.
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.
You have exactly one week from the time that you receive any grade to discuss it with me. After that time period, the grade remains as is.
A grade of "I" (Incomplete) will only be given in the case of a verifiable medical emergency or other such dire circumstance. This is for circumstances that occur at the last moment in the semester only.
Use e-mail in an appropriate and mature manner. See Making the Most of E-mail below.
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 (linux.gl.umbc.edu). 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.
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. Cases of academic dishonesty will be dealt with severely.
If your project is turned in by someone else, both you and the person copying your project will receive a zero for that project. This includes "substantially similar" projects.
The date and time for your final exam (Exam 3) is listed in the Lecture Schedule. Make a note of it now. I have no plans to give any early or makeup exams.
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.
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.
Before you send an e-mail to anyone, it is a good idea to ask yourself the following questions.
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.
In addition, please do not send me e-mails expressing "tales of woe." If you have such a situation, please see me during an office hour, make an appointment with me, or give me a call. If I receive a "tale of woe," I will instruct you to handle it in one of these manners rather than by e-mail.
I do my best to answer my e-mail in a timely and thorough manner. But backups do occur, especially around project due dates. Also, do not expect a reply on weekends, over holidays, or late in the evening. And 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.