You are responsible for all material covered in class, even if it is not in the textbook. You are responsible for all material in the readings, even if it is not covered during class. If you should happen to miss a lecture or a lab, you are responsible for getting any missed notes or announcements from a classmate.
Project grades will be mailed to your UMBC email account. The Midterm exam will be returned to you either in lecture or in lab. After each grade is returned, there is a grace period of one (1) week during which you may discuss any problems you have with your grade. After that time, your grade will stand.
Students in sections 0101 - 0108 (Mr. Frey) must discuss grade changes any project or exam, in person with Mr. Frey. No grade change requests will be granted via email.
Students in sections 0201 - 0208 (Mr. Raouf) should discuss grade changes with their TA.
In the event that you are unable to finish the assignment during the lab period, it is your responsibility to email your completed assignment to the lab's "Lead TA" within 48 hours.
Late projects will not be accepted. If your project is late, you will recieve a score of zero.
There will be five graded projects, each counting for 8% of your final grade. In addition, Project 0 is a mandatory ungraded project. The purpose of Project 0 is NOT to make sure you know how to use the submission system, but rather to make sure that the submission system is prepared to accept projects from your account. If you fail to submit Project 0, no future project submissions will be possible and your grade for those projects (which ARE graded) will suffer.
Network and computer failures at UMBC are a fact of life. They are out of your control and out of our control. However, they are not an excuse for a project to be submitted late, nor are they a reason for project deadlines to be extended, even if the outage occurs on the due date. Plan accordingly. Waiting to submit your project until 5 minutes before your project is due is a recipe for disaster. In the event of network outages or computer failures you are still responsible for submitting your projects on time. There are labs on campus even if your dialup or ResNet connections are down. Also, it is your responsibility to take care of any problems with your account, such as quota overages, which interfere with your ability to complete and submit projects for the course. Project extensions will not be given for such problems.
Every project must be submitted with a makefile. It is to be named either makefile or Makefile (your choice). No other names are acceptable for your makefile. The grader will compile and link your submitted project by typing 'make ProjN' (where N is the project number), so your makefile must correctly compile and link your project. This includes correct naming of the executable; the executable file produced for Project n must be named Projn ; no other names for the executable are acceptable (note the uppercase P).
A number of tutorials on makefiles are available. One is the UCS tutorial. Another is an excerpt from the GNU tutorial.
All projects must compile and link on UMBC's Linux system using the g++ comipler/linker. To ensure you are accessing Linux, log on to linux.gl.umbc.edu. Do not develop your projects on the Irix machines (irix.gl.umbc.edu); different compilers are installed on the two systems, and what compiles on one may not compile on the other. All students must use the g++ compiler in the directory /usr/local/bin. You should do the following to insure you are using the correct compiler:
To check that you are using the correct g++ compiler, execute the command which g++. The response should be /usr/local/bin/g++ .
- In your project makefiles, explicitly specify the compiler as /usr/local/bin/g++ rather than simply as g++.
- Modify your .cshrc file (found in your home directory -- note the leading dot) by creating an alias for g++ by adding the following line near the bottom of your file:
alias g++ /usr/local/bin/g++
Further, the compiler switches -ansi and -Wall must be used when compiling. These must be included in your makefile rules and used whenever you compile "by hand" (e.g. /usr/local/bin/g++ -ansi -Wall MyProgram.cpp)
Unless otherwise noted, all exams are closed-book, closed-notes. A picture ID is required to take the exam.
Review questions for the exams will be made available approximately one week prior to the exam.
A discussion board will be established for each programming project. Students are encouraged to post general project questions, answer questions posted by other students or just browse the discussion board to find answers to project questions. Your instructors and TAs will also be posting questions and answers. Your questions may be posted anonymously.
Other discussion boards for topics such as general C++ questions will also be established. The course BlackBoard is accessed by logging on to my.umbc.edu and clicking on the Blackboard tab at the top of the page.
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 you need help with your project, see your instructor, your TA, the Computer Science Help Center (room
ITE 201E), or tutors provided by the Learning Resource Center. We also
encourage you to consult your textbook and the course web pages.
Safeguard hard copies of your programs; excuses such as "I must have
left a copy of my code in the lab where someone else must have found it"
will not be accepted.
Safeguard hard copies of your programs; excuses such as "I must have left a copy of my code in the lab where someone else must have found it" will not be accepted.
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, or if it is determined that someone else wrote your project for you, then at a minumum you and the other student (if applicable) will receive a grade of zero for that project. Furthermore, all parties concerned will have their prior projects re-checked for cheating. Any second incident will result in a grade of 'F' for the semester. Also, checking for cheating may occur at any time during the semester. Therefore, if you cheated on Project 1, you may be confronted about that at any time; receiving a grade for a project does not mean you are "in the clear".
Any act of dishonesty WILL BE reported to the University's Academic Conduct Committee for further action, which may include, but is not limited to, academic suspension or dismissal from the university.
In addition, due to the volume of student email during each semester, please note the following: