| ITEC 120 |
| 2019fall |
| asbrennem ibarland |
|
|
|
ITEC120 is an introduction to programming principles. It approaches programming as problem-solving, emphasizing:
As per the official syllabus, students who successfully complete ITEC120 will be able to:
Office hours:
You don’t need an appointment to drop by during scheduled office hours.
These hours (if printed) are subject to change;
see the class web page for the most up-to-date times.
| MWF | 16:00–17:00 |  |
| H | 10:00–12:00 | |
| or email me some times that work better for you (incl. weekend zoom/discord chat, possibly). | ||
You are encouraged to post (and answer) questions on the D2L discussion board, since you might get another student’s ideas within a few minutes, instead of my response perhaps a day or more later. If your question requires giving away part the answer (e.g. part of your solution), feel free to email me; please include “ITEC120” in the subject, thanks.
 |
Author | Lewis, DePasquale, Chase |
| Title | Java Foundations: Introduction to Program Design and Data Structures | |
| Publisher | Pearson | |
| ISBN | 5ed: 978-0-135-20597-6 4ed: 978-0-134-28543-6 |
|
| Note | This text is also used in ITEC 220 and ITEC 324, so recommended if you are likely to take those (all CS concentrations). The 4th edition may also suffice, though for ITEC220 the chapter on making GUIs in Java is a bit different. |
|
Author | Cay Horstmann |
| Title | Big Java, Late Objects | |
| Author | Cay Horstmann | |
| Publisher | Wiley | |
| ISBN |
978-1119-32107-1 (eText; available via vitalsource.com); 978-1-119-33045-5 (kindle) 978-1-119-62615-2 (1st ed., the only printed version )-: |
|
| Note |
This text covers the topics much closer in the order we'll follow in class.
Recommended if you are unlikely to take ITEC220 (IS concentrations, perhaps). Any other “Late Objects” Java book by Horstmann will also suffice. |
Evaluation:
| Exams (2-3) & Quizzes | 50% |
| Homework & Lab Assignments | 50% |
Homeworks may be spot-graded -- some problems graded in detail, others with a cursory ✓+ / ✓ / ✓- / 0. Some problems might be auto-graded (and perhaps not further examined), so be sure to use any function/program/type names specified in the homework. Programs will be graded not only for the extent to which they produce the required results, but also for good style. In particular, the code should be well designed, straightforward and use meaningful identifier names. Every function should have a purpose-statement, signature, and unit tests. A program which does not compile/run might summarily get a 0. (Beware making a last-moment change right before submitting, without verifying that it still passes all unit tests.)
Clarity counts in all work for this class (including spelling, grammar, and layout). All submitted material (hardcopy or electronic) must contain both your name and the hw/quiz/exam-number near the top. If something is due both on-line and hardcopy, the hardcopy must be turned in by the start of first lecture on/after the electronic deadline. Your homework hardcopies must be stapled.
The material in this course is extremely cumulative; nearly every lecture and homework requries understanding previous lectures. Do not fall behind! You are expected to read the indicated sections of the book before coming to each lecture. There will be frequent short quizzes in class; fair game for these quizzes include the book's self-review problems from current or previously assigned sections, as well as any previous homework problems.
Late Policy No late homework is accepted. You'll submit assignments both on D2L, and a hardcopy in-class (missing either of these may count as a missed assignment). The hardcopy is due at the start of the first class at/after the deadline. See the attendance policy for some details.
There may also be some short quizzes in class (with or without advanced notice). Fair game for these quizzes include definitions and examples from the assigned reading/comprehension-quiz, as well as any previous lecture material or homework problems.
Final Exam: 2019.Dec.09 (Mon) 10:15, as per the final exam schedule based on our lecture time-slot (not lab). In case of inclement weather, the university may move the exam-slot to Friday, Dec.13.
If you know in advance you won't be able to make it to class or 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 (but with later documentation), notify/email the professor as soon as possible.
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 material on any 120 web page, 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, and tutors.
However, you cannot show your code to other 120 students for help, receive homework code from others (electronically or otherwise), 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 one 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 start your assignments early (just enough to get a feel for exactly what the assignment is asking, and what approach you'll need), you'll have better opportunity to come by office hours for any clarification.
If you aren't sure whether a certain level of help is acceptable, stop—don't give/receive it until you've clarified it with the instructor.
Class Courtesy Please refrain from texting during lecture, and use a computer only for taking notes and looking up material related to lecture (e.g. looking up “java static variable” on Wikipedia). Please do not: check texts, browse other sites, etc.. Other students can be distracted by your screen, and your inattentiveness detracts from the class experience for all. However, in labs—which are more self-paced—these activities are okay within reason, when we are not in group-discussion.
Other University Resources: Radford has many resources to help you in different ways, including the student counseling services (x5226), and the Harvey Knowledge Center (“HKC”, formerly “LARC”, x7704, radford.edu/hkc ) including access to tutorTrac.
Students seeking academic accommodations under the Americans with Disabilities Act must register with RU's Center for Accessibility Services (CAS) in Russell Hall 301. Qualifying students should meet with me to arrange accommodations. For more information, call the CAS at 540-831-6350.
 This page licensed CC-BY 4.0 Ian Barland Page last generated | Please mail any suggestions (incl. typos, broken links) to ibarland  radford.edu |
 |