 |
 |
|
|
C&IT 295 Object-Oriented Programming
Catalog Description | Organization and Schedule | Prerequisites
Course Description | Course Audience | Course Manager | Course Instructors
Required Textbooks, Lab Manuals, and Supplies | Suggested Books and Resource Materials
Final Grade Determination | Course Policies | Academic Dishonesty Policy | Course Outline | Semester Project
This course focuses on using object-oriented programming languages in the development of modern business applications. Topics include object-oriented design, encapsulation, object interfaces, inheritance, aggregation, abstract classes, polymorphism, data structures, and exception handling.
Organization and Schedule Lecture 3 hours, PSO 1 hour, Credit 3 hours
Semester Meeting Type Days Time Location Instructor Spring 2008 Lecture 1-1 Tues, Thurs 4:30-5:45 GRIS 180 Dr. Purdum Lab 1-1 Wed 7:30am - 8:20am KNOY 376 Mr. Pandey Lab 2-1 Wed 8:30am - 9:20pm KNOY 376 Mr. Pandey Lab 3-1 Wed 11:30am - 12:20pm KNOY 376 Mr. Pandey Lab 4-1 Wed 12:30am - 1:20pm KNOY 376 Mr. Pandey Midterm Exam See Calendar Semester Project See Calendar Final Exam TBA help sessions scheduled as needed last day to add 1-11-2008 CPT policy last day to drop 1-18-2008 with no transcript record last day to drop 2-4-2008 without a grade
CPT 255 or strong computer programming experience. Familiarity with relational databases, SQL and HTML is recommended.
Course Description and/or Theme
This course focuses on using object-oriented programming languages in the development of modern business applications. Topics include object-oriented design, encapsulation, object interfaces, inheritance, aggregation, abstract classes, polymorphism, data structures, and exception handling. Students gain experience with Object-Oriented programming principles by designing and writing programs in the Java programming language.
Information Technology Used In This Course
(listed in alphabetical order)
Java 2 SE, Version 5
Bluej, NetBeans (later in semester)
This programming course is for students with prior desktop-based application development experience who have an interest in gaining a working knowledge of Object Oriented programming techniques and technologies.
Instructor Office Phone Office Hours Dr. Purdum KNOY 217 49-66839 jpurdum@purdue.edu See above
Required Textbooks, Lab Manuals, and Supplies
How Final Grades will be Determined (subject to change with notice)
Assessment Mechanism Total Points
Quizzes 10 @ 5 each = 50
Programming Exercises 10 @ 10 each = 100
Semester Project 100 Coding Exam 1 100 Coding Exam 2 100 Mid-Term Exam 100 Final Exam 200 Total 750 Grading Scale
A 90% and above B 80% - 89.9% C 70% - 79.9% D 60% - 69.9% F below 60%
Incompletes
An incomplete will only be granted for serious, extenuating circumstances. Written proof of the particulars will be required. Any makeup work must be completed within a period of time not to exceed the time of the absence, beginning immediately after the absence, as discussed with the course instructor. Extended absences must be documented through the Dean of Students Office and will be validated by the instructor. Do not expect to receive an incomplete to cover up failure in this course. Incompletes will not be given for non-mastery of programming assignments or poor attendance without prior instructor approval.
Contacting Course Instructors
1. Students should not contact instructors just before, during, or just after class to discuss personal affairs. Matters of this type should be scheduled via email and discussed during office hours. 2. The sender of all email correspondence must be clearly identifiable or it may not be answered. For example, it is recommended you include CPT 295 in the subject line and your full name, student ID, and local telephone number in the message body. Additionally, email should be written in a professional, courteous, non-offensive manner. Email that contains unprofessional, discourteous, or otherwise offensive language will likely not be answered. 3. Teaching Assistants only have authority to help with programming assignments. Personal matters should be directed to the course instructors. Attendance, Preparation, and Courtesy Expectations and Policies
1. Students are expected to be present, be prepared, and display a positive, professional attitude throughout the semester in every class meeting. All students are also expected to share in classroom meetings by asking relevant questions and offering suggestions and answers to questions. Disruptive, argumentative, and other unprofessional behavior will result in the student being dismissed from the class. 2. If you must miss a class for a valid reason, contact the instructor immediately (in advance if possible) about the possibility of rescheduling any missed work. You should also have the names of two or three other students in the class that you can contact to get class notes, announcements or assignments if you must miss class. 3. In the event of an extended absence (usually three days or longer), you should contact the Dean of Students Office to report the absence and receive advice on how to proceed. Upon your return to campus, you must promptly contact your instructor to determine if, and how, missed work will be made up. Add/Drop Expectations and Policies
1. According to CPT educational policy, this course may not be added to any student's academic schedule after the third week of a Fall or Spring semester (or equivalent for a Summer semester) except under very extenuating circumstances to be approved by the Department Head of Computer Technology. 2. According to CPT educational policy, no independent study course can be substituted for this course. 3. You may drop this course without a failing grade so long as you do so before the published University deadline for dropping the course. After the initial withdrawal period, you will need your instructor's signature. Quiz and Exam Policies
1. Make-up quizzes and examinations will only be given under extenuating and unavoidable circumstances. The burden of proof of said circumstances is on the student. All CPT faculty members have e-mail and voice mail, so messages can be left for them at any time.
Homework Policies and Quality Expectations
1. Lab assignments will generally be posted one week prior to their due date unless otherwise noted by your instructor. Labs must be submitted via eSub. Trying to submit assignments to the instructor or professor via email will be ignored and not graded. 2. Assignments can be turned in early, but late homework assignments will not be accepted. NOTE: the eSub system clock may not be exactly the same as your system clock, so don't wait to the last minute to submit assignments via eSub. One second past the deadline as determined by the eSub system clock is considered late by eSub and will NOT be accepted. 3. All assignments must be prepared in a professional manner. Always check your assignments for correct spelling and grammar. Unprofessional work may not be graded. Points may be subtracted for submitting poorly or improperly organized work, or for not following instructions. 4. To protect your privacy, graded materials will never be passed around the classroom or placed outside of an instructor's office door. 5. Scores and grades will be posted on the course web page. Scores will be identified using your 10-digit student id number. 6. The course instructors reserve the right to lower the grading scale expectations but will never raise the minimum grade requirements. 7. Deadline extensions and extra credit assignments will not be given. 8 Unless otherwise noted, all programming homework assignments that contain compile/syntax errors will automatically receive a score of zero. Re-Grading Policies
1. Students wishing to appeal any score must return their work to their course instructor with a written statement explaining the appeal no later than one week after the original scores were posted. You may send an email to the instructor or deliver a typed memorandum to the instructor via the CPT office (KNOY 242) stating the appeal. 2. Any work submitted for re-grade (other than misrecorded material) may be totally re-graded. Do not assume the instructor will only re-grade those portions that the student wishes to be re-graded. This also means you could end up with a lower grade if new errors or other program shortcomings are found. 3. According to University regulations, only final course grades can be "appealed." There is a formal School of Technology and University timetable and process for grade appeals. It must be followed exactly! Questions about grade appeals should be directed to the Assistant Department Head of Computer Technology or the Chair of the School of Technology Grade Appeals Committee. Lab Policies and Expectations
1. When using TCN computer laboratories, you are responsible for any and all laboratory policies - including the security policies that govern your account. Failure to do so may result in the loss of all laboratory privileges, with no reduction in course requirements. Policies do change from time to time; therefore, you should review the TCN Policies and Standards (http://www.tech.purdue.edu/tcn/policies) at the beginning of each semester. Accounts can be temporarily or permanently suspended for policy violations. 2. In the event that your account is suspended for any laboratory or network policy violation, this course will not extend deadlines for assignments that could not be completed because of the suspension. Labs are always submitted via eSub. 3. You are responsible for maintaining adequate backups of all programs you create (If you don't understand backup procedures, ask before it's too late!). Furthermore, you are responsible for keeping an exact copy of anything you hand in for a grade. Your instructor is not responsible for loss of data or workstation or printer failure. Loss of programs due to inadequate backups may result in work that cannot be submitted on time. 4. You are expected to be present during the entire lab/PSO session unless you receive permission from the instructor to be excused. 5. All computer assignments will require some work outside of scheduled class meetings. Check the TCN lab schedules (http://www.tech.purdue.edu/tcn/labs) for available lab facilities. Workstations are available on a first-come, first-serve basis. Workstations may not be available when other courses' scheduled laboratories are in session. Be considerate of other students and professors when using these workstations! Also, plan your schedules so that you will have time outside of class to get your assignments done in a timely manner. 6. Computer viruses pose a danger to any files you create in public labs (or on private systems on which foreign disks have been introduced). Use anti-virus software on a regular basis to protect yourself against virus infection. 7. Software piracy is a serious matter. Making copies of the software in the lab is considered theft of Purdue University property. Any student stealing software is subject to administrative action and/or disciplinary penalties. The LAN software constantly monitors software copying. Students may not install any software on the workstations or the file servers. Academic Dishonesty ("Cheating") Policies
1. The maximum penalty for cheating on any assignment, project, or exam is an "F" grade for the course. 2 Is it worth the risk to receive an F in a class after a considerable investment of time/effort or worse yet to be suspended from school for one or more semesters at any time during your academic career? Don't Cheat! 3. You are expected to do your own original work and to acknowledge correctly the work of others. Copies of the original authors' work(s) must be submitted with your assignment. One student doing/taking another's work (in whole or part) or collaborating with other(s) and submitting that work (in whole or part) as his/her individual effort (perhaps with cosmetic changes) constitutes cheating. Using unauthorized crib sheets or copying answers from another student/written material/diskette when completing in-class assignments, quizzes, and exams constitutes cheating. Gaining unauthorized access to exams, quizzes, or instructor's keys or any student's answers is cheating. 4 Your instructor recognizes the learning value in exchanging ideas with others and learning from the mistakes and solutions of others; however, this type of unauthorized sharing can result in suspiciously similar work that is not an individual effort. All work that you submit must truly represent your individual effort. You should be aware that it is next to impossible for someone to forget a unique, creative approach once it has been seen/shared/heard. Most of the work in this class requires multiple levels of creativity, so it is not difficult to detect work submitted under suspicious circumstances. The best way to avoid being caught in the middle of a suspicious situation is to not discuss/show/share your work (in whole or part) with/to others. 5 Throughout the semester, your instructor will work through related problems and make assignment solutions available. You are encouraged to use these solutions to improve your understanding of course concepts and to facilitate your completion of course assignments. However, you are not permitted to exchange/give/take/use any other person's work without prior, written permission from your instructor. Failure to abide by this policy is considered cheating. If you experience difficulty in completing course assignments, you are encouraged to seek the assistance of your instructors during scheduled class meetings and scheduled office hours (or to schedule an appointment). Additional assistance will also be made available as needed and can be arranged. 6 Giving another student access to your computer account, or negligently permitting another student to access your computer account constitutes cheating on your part if that other student copies any files that become implicated in a cheating case. Protect your account as if your academic career depends on it! 7. Cheating, or helping another student to cheat, are considered equal cases of academic dishonesty and will be dealt with as noted below. 8 All cases of academic dishonesty are forwarded to the Office of the Dean of Students for record-keeping purposes and consideration of other, appropriate disciplinary action.
Course Outline (subject to change)
See online calendar
Each student will complete a team project that will demonstrate his or her ability to apply what she or he has learned in the course. The project will be chosen by the instructor, or the team can propose a project idea of their own (pending instructor approval). Teams must have no more or less than three members.