This course is an introduction to programming principles, including object-oriented programming. Programming is useful, enjoyable, and rewarding skill; you will continue learning and improving as a programmer as long as you practice the skill, long after the class has ended.
Themes of the class include organizing data and program to fit the problem at hand, thoughtful testing, and abstraction. Particular skills taught will include classes and interfaces, processing sets, arrays and loops, unit testing, and more. This course happens to use Java as a programming language, but the focus is on issues which transcend a particular language, not on encyclopedic knowledge of Java-specific names and libraries.
|
If you send mail directly to me (rather than post on the WebCT discussion board), include “ITEC120” in the subject. |
| If these hours aren't convenient enough, they may be modified (w/ a 1-week warning); check online for the up-to-date office hours. | We also have peer instructors who have office hours in the lab: Josh Gibson: Thurs 13:00–14:00; Nathan Good: Tues 14:00–15:00. |
Lewis and Loftus, Java Software Solutions: Foundations of Program Design (5e) (publ. Addison Wesley; ISBN 0-321-40949-3). | |
If you instead purchase a used copy of the fourth edition, it will require some extra work on your part to smooth over differences; see me. I do not advise getting an earlier edition. |
Exams (2) & Quizzes | 30% | |
Homework & Lab Assignments | 60% | |
participation | 5% | (In-class, or on message boards) |
attendence | 5% | (sharp reduction upon missing ≥six lectures) |
Pair Programming: Some homework assignments for this class will be with a partner. In pair programming, both partners are at the same computer together, with one person typing while the other thinks and contributes too. (You should alternate who types, every 30min or so).
For pair assignments, include both your names at the top of the work; turn in a single hardcopy, but you'll each submit the (same) file via WebCT. Pair-programming assignments will have a ‘p’ at the end of their name—for example, hw01p is to be done in a pair, while hw01i is to be done individually.
Honor Policy: As with all your RU classes, the university honor code governs all work turned in.
You are encouraged to discuss and interpret the homeworks, and general approaches to solutions, with your fellow students. You can freely access all previous class material, and general web references (for example, Java language features, or Java library documentation). And of course, you can always interact freely with the professor, other faculty, tutors, and (in the case of pair programming assignments) your partner.
However, you cannot show your code to others for help, or have others type in any code for you. You must be the direct author of all your submitted work. If you got significant advice which you'd like to credit somebody for, cite them in your work.
The gray area is when you are stuck with a particular small error which is preventing progress. You can always ask what a compiler message means, including (if needed) the line causing the problem. (The class discussion board is a particularly good place for this.) You may also show your code to a lab assistant, and receive specific, short advice. Otherwise you should come ask during office hours.
If you aren't sure whether a level of help is acceptable, stop—don't give/receive it until you've clarified it with the instructor.
Late Policy: If you know in advance you won't be able to turn in homework on time (e.g. participating in university sports) you must get permission in advance to turn the homework in late. For significant illness or family crisis without advance notice, contact the professor as soon as possible, to see whether homework can still be turned in late.
If you otherwise miss a homework deadline, you are still encouraged to finish it for partial credit, albeit with a late penalty as determined by the first applicable entry in the table. A “day” is 24hrs, and includes weekends and holidays, and is determined by the time you submit to WebCT. If you submit homework late for any reason, you must include and sign the following statement (or, include a note explaining why the statement isn't true): In addition to the honor policy, I pledge that I was not exposed to any posted solution set for this homework. |
|
Other University Resources: Radford has many resources to help you in different ways, including the student counseling services (x5226), and the Learning Assistance Resource Center (“LARC”, x7704, www.radford.edu/~larc, larc@).
If you need any special accomodations for a class, and have registered with the Disability Resource Office (x6350, Tyler Hall Suite 64), please contact the professor at the start of the semester.