This is a very hands-on class: every student will be involved in the design, implementation, and programming for the laboratory exercises. Note that this component of the class will involve a non-trivial amount of time; students should plan their schedules accordingly.
Topics will include:
Login with your 4+4 (typically the first four letters of your last name followed by the last four digits of your student number), using your standard OU password. If you have difficulty logging in, call 325-HELP. This software provides a number of useful features, including a list of assignments and announcements, an electronic mailing list, newsgroups, and a grade book.
I will update the main web site and the D2L page several times a week. When I update the site in any significant way, I will post an announcement on D2L telling you what has been added and where it is located. You are responsible for things posted on the site within 48 hours of the post.
If you need assistance in accomplishing any of these tasks, contact 325-HELP.
The five project milestones will be performed in collaboration with 3-4 other people. Within groups, you are expected to discuss and share solutions. General discussion between groups is fine. However, unless otherwise stated, the sharing of project-specific circuit diagrams or code is considered cheating.
You may make use of the net as a reference as you are working on homework and labs. However, downloading specific homework or project solutions from the net is considered cheating.
Make sure that your computer account is properly protected. Use a good password, and do not give your friends access to your account or your computer system. Do not leave printouts, floppy disks or thumb drives around a laboratory where others might access them.
Programming projects will be checked by software designed to detect collaboration. This software is extremely effective and has withstood repeated reviews by the campus judicial processes.
Upon the first documented occurrence of collaborative work, I will report the academic misconduct to the Campus Judicial Coordinator. The procedure to be followed is documented in the University of Oklahoma Academic Misconduct Code ( http://www.ou.edu/studentcode/OUStudentCode.pdf). In the unlikely event that I elect to admonish the student, the appeals process is described in http://www.ou.edu/provost/integrity-rights/.
A more effective use of tutoring services is to do problems that are similar to the assigned work, instead of doing assigned work. For example, it would be fine to work unassigned problems from the textbook with a tutor. This requires significant discipline, both on the part of the tutor and the part of the student. Copying from a tutor is as unacceptable as copying from another student. If your tutor doesn't know how to teach properly, please ask them to call or visit me and I will provide training and guidance. If you are tutoring someone else in the class, you can be accused of academic misconduct if this person copies your work.
Disruptions of class will also not be permitted. Examples of disruptive behavior include:
To receive full credit for a major component, you must be one of (at most) two group members who perform the design and implementation of the subsystem. Your other group members should be involved in reviewing your design, testing your implementation, and helping you to debug. But - a primary contributor will have a significantly larger role in the subsystem.
In general, group members will receive the same group grade. However, if it is clear from the personal reports that some group members are not contributing to the group work, then their group grades can suffer.
Project materials must be handed in (and shared with group members) using subversion. We will use doxygen to automatically generate code-level documentation. Other associated documentation may be done in HTML or PDF. In addition, individuals will be asked to hand in a short text evaluation of the project (more information to follow).
Projects may be handed in late. If late by 0-24 hours, the project grade will incur a 10% penalty; if late by 24-48 hours, a 20% penalty will be imposed. Projects that have not been handed in by 48 hours will receive no credit.
Copyright notice: Many of the materials created for this course are the intellectual property of Andrew H. Fagg. This includes, but is not limited to, the syllabus, lectures and course notes. Except to the extent not protected by copyright law, any sale of such materials requires the permission of the instructor.