Introduction to Object-Oriented Development I

Course Information

Instructors:    Stephen Edwards      Dwight Barnette Office: McBryde 604 McBryde 624 Office Hours: Tuesdays and Thursdays, 11:00-12:00 Fridays, 10:00-12:00 Mondays and Wednesdays, 1:30-3:30 Tuesdays and Thursdays, 3:30-4:30 Office Phone: 231-5723 231-7350 E-Mail: edwards@cs.vt.edu barnette@vt.edu

Prerequisite:    CS major Text: Objects First with Java: A Practical Introduction Using BlueJ, David J. Barnes and Michael Kölling, Prentice Hall, 2003. Karel J. Robot: A Gentle Introduction to the Art of Object-oriented Programming in Java, Joseph Bergin, Mark Stehlik, Jim Roberts, and Richard Pattis, unpublished manuscript available on the web or in the course notes pack. Optional: CS 1705 Course Notes will be available at A-1 Copies, University Mall. Karel++: A Gentle Introduction to the Art of Object-oriented Programming, Joseph Bergin, Mark Stehlik, Jim Roberts, and Richard Pattis, John Wiley & Sons, 1997. On the Web: http://courses.cs.vt.edu/~cs1705/

Course Description

This course teaches fundamental concepts of programming from an object-oriented perspective. Basic software engineering principles and programming skills are taught with a programming language that supports the object-oriented paradigm. Simple data types, control structures, array and string data structures and algorithms, testing and debugging are all covered.

Grading Policy

Grading for the course is based on the following distribution of credit across graded work:

Final Grades: In order to receive a grade of C or higher in this course, you must achieve a grade of C on the final exam. This is a threshold criterion--if your final exam score is below C, you may not receive a grade above C- for the course, no matter what your total percentage turns out to be. Note that if you plan to continue in the Computer Science curriculum, you are required to have a C or higher in this course.

Homework Assignments: Your solutions for each homework assignment must be prepared with a word processor (e.g., Word or LaTeX), and are due at the beginning of your lab period each week.

Programs: For each programming assignment and lab assignment, you will submit an electronic copy of your work for grading. No paper printout is required. You will also receive your comments and feedback on program assignments electronically. Full submission instructions are posted on the course web site describing electronic submission and grading criteria.

Statute of Limitations: Any question or complaint regarding the grading of any assignment or examination must be raised within two weeks after the corresponding grade is made available (not when you pick it up).

Homework assignments are due at the beginning of your scheduled lab period. Work is late if it is not turned in at the beginning of lab,

Homework Assignments: Late homework assignments may be submitted before the end of your scheduled lab period for a 10% penalty. No other late homework assignments will be accepted.

Programs: Except in the very rare case when an extension is granted, late submissions may be submitted for a penalty of 10% per day (10% for up to 24 hours late, 20% for up to 48 hours late, etc.). No late submissions will be accepted more than 5 days after the due date. Any request for an extension must be made at least 24 hours prior to the due deadline.

Note: Delays resulting from machine availability, lab schedules, hardware failures or your failure to maintain a backup of your work do not merit an extension.

You are expected to attend class always--please arrive on time. If you must miss a scheduled lab period, you must discuss it with your instructor at least 24 hours in advance to make alternative arrangements. If a serious illness prevents you from taking a test, notify your instructor in advance of the test; you must also provide a note from your physician or the Health Center. Excuses other than an illness on a test day must be requested through the Dean's office. No makeup tests will be given without a verified excuse. Also, note that only the Dean's office can excuse you from the scheduled final examination time, and no makeup final will be given without the Dean's approval.

Labs: You will be working in pairs during closed lab sessions. All lab work must bear your name and the name of your lab partner, and is treated as joint work. During lab period only, you may freely offer and receive verbal assistance on lab tasks with any other student in your lab section or any of the course TAs. However, you may only type at the keyboard when working with your lab partner to produce written work with your name on it.

All other work: except for lab assignments completed during lab period, all other work is considered individual work and cannot be developed or written up with assistance from individuals other than the course TAs, the course instructors, and ACM or UPE tutors. Any discussion of program source code must be limited to these people. Examples of honor code violations include:

• Working with another student to derive a common program or solution to a programming assignment or homework problem.
• Discussing the details required to solve a programming assignment. You may not share solutions.
• Copying source code (programs) in whole or in part from someone else, with or without their knowledge or consent.
• Editing (computer generated) output to achieve apparently correct results.
• Taking another person's printout from a lab printer, remote printer, trashcan, etc.

It is acceptable to discuss with others the nature of an assignment or what behavior it requests--that is, what your program is to accomplish--but you may not discuss how to achieve that goal. Note that all electronic work submitted for this course is archived and subjected to automatic plagiarism detection and cheating analysis.

If any student needs special accommodations because of a disability, please contact the instructor during the first week of classes.

Home  |   Notes  |   Homework  |   Labs  |   Programs