Aim:

Master object-oriented programming and design.

Objectives:

On completion of this course, you should be able to:

• Justify the philosophy of object-oriented design and the concepts of encapsulation, abstraction, inheritance, and polymorphism.
• Design, implement, test, and debug simple programs in an object-oriented programming language.
• Describe how the class mechanism supports encapsulation and information hiding.
• Design, implement, and test the implementation of "is-a" relationships among objects using a class hierarchy and inheritance.
• Compare and contrast the notions of overloading and overriding methods in an object-oriented language.
• Explain the relationship between the static structure of the class and the dynamic structure of the instances of the class.
• Describe how iterators access the elements of a container.

Topics:

Course Basics

Prerequisite: CS150 Introduction to Computer Science I with a grade of C or better
Meeting Times: MWF 09.00 - 10.00 AM
Location: Marsh LL12

Course Assessment:

Grade Distribution:

Percent Breakdown:

Important Dates:

Dates for Exams:

Date of Final:

Tuesday, 15 May, 3.00-5.30 PM in Marsh LL12

Other Dates:

Course Policies:

Class Policies

1. Your attendance is expected at each class meeting. It is in your own best interest to attend class, as your grade will almost certainly suffer indirectly if you choose not to attend. In addition, I reserve the right to consider attendance in instances of borderline grade assignments. Of course, excused absences (sickness, family emergencies, varsity athletic participation) will not be held against you. Scheduled absences should be communicated to me well in advance. If you must miss a class, be sure to check with me or another student to get what you missed. Exams will be given in class on the day scheduled and may not be made up. The material in the course is, by necessity, cumulative. Be warned that if you fall behind, you will not be able to catch up easily.

2. Computers are not to be used during lecture time. Once I begin lecturing, the keyboards should be pushed under the desk and the monitors should be ignored. Failure to do so will result in you being excused from class.

3. Cell phones are to be turned off and put away during class. Any cell phone that rings during class will be confiscated. Leaving during the middle of class to answer a page/call is extremely rude.

4. If you have a documented disability covered under the ADA then services and accomodations are available from LSS (Learning Support Services). If you need reasonable accommodations to fully participate in course activities or meet course requirements, you must contact Edna K. Gehring, Director of LSS, at X2107. She will meet with you, review the documentation of their disabilities, and discuss the services Pacific offers.

Assignment and Exam Policies

1. Assignments are to be turned in at the beginning of class on the day they are due.

2. Assignments can be turned in up to 24 hours late with a penalty of 10% of the grade. If the assignment is between 24 and 48 hours late you will lose 20% of your grade. Anything later will not be accepted.

3. One exception. Programming takes time and is fraught with hazards. It may happen that you postpone too long, have a system failure, lose a file, get sick, have family problems, or any number of other difficulties. Many times coding takes longer than you had planned. None of these events are reasons for exceptions to the assignment submission policy. But I do allow one programming assignment per semester to be turned in one day late without penalty. Your reason does not matter and I do not need to know why. All other late assignments will carry the standard loss of points (your reason still does not matter and I do not need to know why).To use this gift, you need to send me an email when you submit the assignment. This email is to have GIFT as the subject. In the email include your name, the assignment you want it applied to and the date you submitted the assignment. If this information is not included in the email, the assignment will not count as a gift.

4. Make sure to test your program before you turn it in. You may turn in your program only once.

5. The coding standards for this course can be found here. You must adhere to these coding standards on every assignment to receive full credit.

6. A program that does not successfully compile or produces no output loses 70% of the assignment grade.

7. No early or late exams/finals will be given under any circumstance. Do not make early Spring Break or end of term arrangements.

8. No incompletes will be given.

9. You may generally discuss programming problems with other students in the class, but the programs themselves must be your own. You may have general conversations about problem strategies, but you must leave these conversations without having written anything down. When it comes time to write your programs, you are on your own. Sitting next to someone in the lab while you discuss each line of code is unacceptable. Keep in mind that it is quite easy for me to tell when two students have been working too closely. In such cases, I am obliged to report the instance to the Assistant Dean. You may not get help from students outside the class, with the exception of the student tutors, whose hours will be posted shortly. If you have questions, ask the tutors, or come see me and I will be happy to help. Pacific University has no tolerance for academic dishonesty. It is university policy that all acts of academic dishonesty be reported to the Assistant/Associate Dean. Sanctions that may be imposed for academic dishonesty range from an F for the assignment to an F for the course. Every piece of code written for CS150 is to be an original design and an original implementation. The Web, textbooks and any other references are simply references for you. This means that copying code from any source is prohibited. Further, source code is not to exchange hands in any form or by any medium except when sending your solutions to the instructor. Please consult the Academic Conduct Policies in the A&S Catalog.

10. All code in any form generated from this course becomes the intellectual property of Pacific University. You may not share this code with anyone at any time (including after this course is over) without obtaining written permission from Pacific University.

11. Computer failure, software failure, and lack of computer access are not accepted as excuses for late programs; therefore, start work on the programs as soon as they are assigned, don't put them off until the last minute. Make sure to keep backup copies of your assignment. Corrupting or accidentally deleting your programs is also not an acceptable excuse for late programs.

12. If you have a complaint regarding a grade on an assignment or exam, write a one paragraph description of why you feel the grade is incorrect and deliver it to the instructor. The paragraph must be delivered to the instructor within one calendar week of when the graded material is returned to the student.