Content: This course is a rigorous, systematic approach to problem solving and programming, and the primary objective for the course is for you to gain the following:

1. the problem solving skills needed for further studies in computer science
2. a working knowledge of a high level programming language (Java)

To accomplish these objectives you will learn to use the programming language Java to create computer programs that solve (relatively simple) problems. Programming will be done using the Microsoft Windows environment. We will be using version 1.5 of Java which is a significant revision of earlier versions. If you are using an earlier version on your home machine, you will want to upgrade to version 1.5 for this course. Currently 1.5 is only available in a beta version, but the release version is expected to be out soon.

Postrequisite: You must earn a grade of C or better in this course before you can continue with any ITEC courses (the next courses are ITEC 220 and 225). If you get a grade of D or F, then you will have to retake this course and earn at least a grade of C before you can continue with 220 or 225.

Schedule and Location: The format of this course is three hours of lecture and two hours of lab per week. Lecture days are Monday, Tuesday, and Thursday. Lab days are Wednesday and Friday, in Davis 225. Please remember that starting this year RU is on break the full week of Thanksgiving, and there is no Fall break.

Peer Instructor: There is a peer instructor for this course who will be present at the lab sessions to help. He will hold one office hour each week where he will be available to answer questions you might have. You are welcome to attend the office hours of any of the peer instructors.

Required Text: Java Software Solutions, Fouth Edition, 2004, John Lewis and William Loftus. (The earlier editions are significantly different from the fourth, and I don't recommend trying to use them. In particular, this edition uses Java 1.5.)

Course web page: http://www.it.radford.edu/~nokie/classes/120

Evaluation:

Per cent	Activity
10	Labs
15	Lab Quizzes
10	In Class Quizzes/Homeworks
15	Programming Assignments
30	Two in-class tests
20	Comprehensive final exam (2:00 p.m. Thursday 12/16/2004)

Lab grading:

• All or nothing. Checked off by the peer instructor
• If you are not finished with your lab by the end of the lab period, then it may be checked off only during the first 10 minutes of the next scheduled lab period. There will be no help given on that lab during those 10 minutes - labs will only be checked off - so you must complete your lab before that lab period. If you need further help on the lab, you will need to get it from me or from the lab Peer Instructor before the next lab period.

Quiz grading:

• 10 point scale
• Missed quizzes cannot be made up; dates for quizzes will be announced
• You will submit lab quizzes electronically and I will grade them
• Each class quiz will be based on a homework assignment which you will complete before the quiz
• There will be a homework assignment and corresponding class quiz for each chapter we cover
• The lowest class quiz grade will be dropped at the end of the semester

Program grading:

• 20 points - Compiles
• 50 points - Runs and gives correct output
• 10 points - Documentation: header, name, comments, spacing and indentation
• 10 points - Style: variable names, understandable code, approach to problem
• 10 points - Submission: properly submitted with correct name

Late policy: Unless otherwise specified, late work will not be accepted.

Exams: In exceptional circumstances I may give permission to miss an exam, if you contact me in advance. In such cases the weight of your final will be increased. Otherwise a missed exam will be worth 0 points.

Grades:

• Later in the semester you will be able to check your grades for this course online. Please do this regularly in case I make a mistake entering your grade. Please keep your graded work in case there is a question about your grade.
• Please do not modify assignments after you submit them. This will preserve the modification date in case there is a question about a submission. Some students keep a special folder where they keep an archive of submitted assignments.
• Normally I don't curve individual assignments, but I may add a point or two at the end of the semester.
• I don't give extra credit, but if you come to class regularly it can help you if you are on the borderline.
• No grades are given for effort, only for results.

Honor Code: This class will be conducted in strict observance of the Honor Code. Please refer to your Student Handbook for details of expected behavior. Of course, all work that you submit for grading must be your own.

• Programming assignments are your own work.
• Lab quizzes and in-class quizzes are your own work.
• Exams are your own work.
• You may work together on the labs, but you must still make every effort to make sure you understand the finished product. You are responsible for understanding your work.
• You cannot learn how to program unless you do the programming assignments. You need to be able to understand and explain the code you turn in to me.

Please be aware that if I suspect that you have violated the Honor Code, then I will not hesitate to file charges with the Dean of Students Office.

Thoughts on Success: Many students find this to be a difficult course. For success, you must be strong in the fundamentals:

• Do the reading and homeworks, and come to class and lab, with questions.
• Start your assignments early. Give yourself time to learn new concepts and deal with problems.
• Be willing to get (appropriate) help.
• Don't get behind. The material is cumulative and many find catching up impossible. Stay ahead of the wave!
• Remember the rewards of success.
• In the words of a speech by Winston Churchill in 1941: Never give in, never give in, never, never, never, never - in nothing, great or small, large or petty - never give in except to convictions of honour and good sense. Never yield to force; never yield to the apparently overwhelming might of the enemy.