UMBC CMSC313

CMSC313

Policy on Programming Projects and Exercises

Critical programming skills cannot be learned by attending lecture only. You should budget enough time to work on the programming assignements as well. Please consult the time table given on the lecture schedule and plan ahead. Programs are due by 1 minute before 11:59 of the due date. Programs will be submitted using the Blackboard system at UMBC. Late assignments will not be accepted. Programs will be graded on five criteria: correctness, design, style, documenation, and efficiency. So, turning in a project that merely "works" is not sufficient to receive full credit. For this course, programming projects must be developed using the NASM assembler for the Linux operating system. running on an Intel Pentium CPU. This arrangement is not compatible with other flavors of UNIX, with Linux running on non-Intel CPUs or with assemblers for Windows 95/98/2000/ME/XP/NT. When in doubt the UMBC machine linux.gl.umbc.edu will be the final arbiter of what constitutes a working programming. You may work on your own machines running Linux, but you will have to be your own system administrator. None of the instructors, TA or support staff at OIT will be available to help ou install or debug Linux.

NOTE: UMBC's Linux Users Group (LUG) can be a resource for you to get help with the installation of Linux and Linux questions in general. However, when you contact them for assistance, you must first tell them that you are taking CMSC313 and you can not try to have them answer any of your homework questions.

Cheating

Read this section carefully! It describes what constitutes cheating for this course. If you have questions, ask the instructor. Ignorance will not be accepted as an excuse after the fact.

All programming assignments and circuit simulation exercises must be completed by your own individual effort. You should never have a copy of someone else's program either on paper or electronically under any circumstance. Also, you should never give a copy of your program or circuit, either on paper or electronically, to another student. This also means that you cannot work on the programming assignments or circuit simulation exercises together. Cases of academic dishonesty will be dealt with severely. Cases of cheating will be reported as a major infraction. In this case, you will not be allowed to drop the course. We will attempt to have any cheating student expelled from the University. Failing that, it will be considered as a major infraction and you will not be allowed to drop the course, which means the course will 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. We will use all appropriate means to check for cheating, manual and automatic. The software is quite sophisticated, has been tuned for assembly language programs 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 also forewarned that there is no difficulty in comparing every pair of submitted projects. Furthermore, all parties concerned will have their prior programs checked for cheating. If someone else's work is significantly similar to yours, this is considered cheating. Sites like rentacoder.com are monitored and any attempt to get anyone else to do your projects are cheating. Getting a similar version off the Internet is cheating.

UMBC | CSEE |