CSE 503 Spring 2004 Syllabus

Instructors

Name

Office

Phone

E-mail

Web page

Adrienne Decker

130 Bell

645-3180x161

adrienne@buffalo.edu

www.cse.buffalo.edu/~adrienne

Course Description

This course provides an introduction to computer science using object-oriented techniques for design and implementation.  Topics covered include, but are not limited to, objects, classes, basic UML class diagrams, inheritance, polymorphism, encapsulation, event-driven programming using NGP, variables, operators, sequencing, selection, iteration, and arithmetic, relational and logical expressions.

A detailed schedule of topics is available on the course web site.

Required Reading

Textbooks

Andries van Dam's chapters on Java and OOP (referred to as “The Brown lecture notes”). [Available at Makin' Copies, located in the UB Commons.]

Cay Horstmann. 2004.  Object-Oriented Design and Patterns, John Wiley & Sons, Inc.  (ISBN: 0-471-31966-X)

Deborah S. Ray & Eric J. Ray.  1998.  UNIX: Visual Quick Start Guide, Addison Wesley. (ISBN: 0-201-35395-4)

Course Web Site

http://www.cse.buffalo.edu/faculty/adrienne/SP2004/cse115

Grade Breakdown

The following table indicates the grade breakdown which we will use in assigning grades in the course. We reserve the right to make adjustments to the breakdown if we feel it is necessary.   Please note that the details of the “Homework, quizzes, etc.” category will be made more explicit in the first week or so of classes.

10%

Homeworks, quizzes, etc.

40%

Lab (programming) assignments

50%

Exams

 

Examination Grading

Two options

There are two options for calculating your score for the exam component of the course. Under the first option each in-class exam counts for 15% of your grade, while the final exam counts for 20%. Under the second option the final exam counts for 50% of your grade. The option which gives you the highest score in the course will be used automatically.

You must attempt both in-class exams in order for the final-exam only option to be available to you. If you do not write the in-class exams, you cannot make use of the final-exam only option.

What does this mean?

The motivation for having two grading options available is to ensure that you are not penalized if you have a rough start in the course, but manage to do really well on the final exam. If you do poorly on the in-class exams, you can still do well in the course by demonstrating that you have learned the material on the final exam. Of course, if you do poorly on the in-class exams, this means you are playing without a safety net.

Examination pass requirement

In order to receive a grade higher than F in the course, you must have at least a 50% exam average.

Letter Grades

The following table indicates the number to letter grade mapping we will use to assign final grades at the end of the course. The grade points column is included for your convenience only, and is not official information. The official mapping can be found on page 176 of the 2003-2004 Undergraduate Catalog.

Percentage score

Letter grade

Grade points

90-100

A

4.0

85-89

A-

3.67

80-84

B+

3.33

75-79

B

3.0

70-74

B-

2.67

65-69

C+

2.33

60-64

C

2.0

55-59

C-

1.67

50-54

D

1.0

0-49

F

0.0

Policies

Early Policy

Many students have a tendency to procrastinate on lab assignments.  To encourage you to start early, we are implementing an early hand-in policy.  You will receive an extra 4% on any lab assignment for submitting it up to 2 days early.

Late Policies

Assignments submitted past the due date are late and will suffer penalties as shown in the following table:

Labs

50% (of maximum score obtainable) per day

Homework – due in class

Not accepted

Homework – due online

50% (of maximum score obtainable) per day

DISTRACTIONS IN THE CLASSROOM - BEHAVIORAL EXPECTATIONS

The following policy regarding classroom behavior was adopted by the Faculty Senate on 5/2/2000.  You are expected to know and adhere to this policy.

To prevent and respond to distracting behavior faculty should clarify standards for the conduct of class, either in the syllabus, or by referencing the expectations cited in the Student Conduct Regulations.  Classroom "etiquette" expectations should include:

·       Attending classes and paying attention.  Do not ask an instructor in class to go over material you missed by skipping a class or not concentrating.

·       Not coming to class late or leaving early.  If you must enter a class late, do so quietly and do not disrupt the class by walking between the class and the instructor.  Do not leave class unless it is an absolute necessity.

·       Not talking with other classmates while the instructor or another student is speaking.  If you have a question or a comment, please raise your hand, rather than starting a conversation about it with your neighbor.

·       Showing respect and concern for others by not monopolizing class discussion.  Allow others time to give their input and ask questions.  Do not stray from the topic of class discussion.

·       Not eating and drinking during class time.

·       Turning off the electronics:  cell phones, pagers, and beeper watches.

·       Avoiding audible and visible signs of restlessness.  These are both rude and disruptive to the rest of the class.

·       Focusing on class material during class time.  Sleeping, talking to others, doing work for another class, reading the newspaper, checking email, and exploring the internet are unacceptable and can be disruptive.

·       Not packing bookbags or backpacks to leave until the instructor has dismissed class.

Academic Integrity

We will follow the Computer Science and Engineering Policy on Academic Integrity, detailed at http://www.cse.buffalo.edu/academics-academic_integrity.shtml, as well as University Policy on Academic Integrity, detailed in the Undergraduate Catalog. For more information, see the Student Conduct Rules, University Standards and Administrative Regulations. A good application of these rules to computer science is given on the department's web page. Take the time to familiarize yourself with the contents of these pages.

Pursuant to the Department's policy, anyone found to be in violation of the policies on academic dishonesty will be given a grade of F in the course.  This policy applies equally for all violations, be it cheating on an exam or a homework assignment.  For especially flagrant violations, formal proceedings will be initiated. Such proceedings can call for harsher sanction including expulsion from the University. Your work may be evaluated for infractions of academic integrity at any time up until the time you graduate.

We have recently acquired access to an electronic means of cheating detection that make it possible to check the entirety of class submissions with ease. All submissions for this class will be run through the analyzer.

Nearly every semester someone is caught in one of our classes, and each person has been failed from the course. Academic dishonesty will not be tolerated.

Example Infractions of Academic Integrity

Examples of conduct considered in violation of the policies on academic integrity include but are not limited to:

  • Use of unauthorized notes/materials during an exam/quiz
  • Copying answers off another student's exam, quiz or homework
  • Obtaining code (or other types of) solutions or parts thereof from others be they classmates, schoolmates, friends, code-jockeys in foreign lands.
  • Collaborating with others on assignments, say, sitting next to one another in the lab working on the assignment together.
  • Decompiling demos to "reverse engineer" or hand in as your own solution.
  • Obtaining solution materials from books, websites or other means and using them without attribution to the original author.

Writing code is a lot like writing an essay for an English class. While you and classmates might be writing on the same topic, you would not sit down and each write different parts of the essay. Likewise, even writing on the same topic there is tremendous room for individuality.

Asking a classmate for help is always a lateral move. If you are stuck, ask a TA or the instructors. We are here to help you learn.

 

Incomplete (I) Grades

We will follow the UB Undergraduate Catalog Statement on Incomplete Grades, outlined in the Undergraduate Catalog. Take the time to familiarize yourself with the contents of this page.

Generally, incomplete ("I") grades are not given. However, very rarely, circumstances truly beyond the student's control prevents him or her from completing work in the course. In such cases the instructor can give a grade of "I". The student will be given instructions and a deadline for completing the work, usually no more than 30 days past the end of the semester. University and department policy dictate that "I" grades can be given only if the following conditions are met:

  • An Incomplete will only be given for missing a small part of the course.
  • An Incomplete will only be given when the student misses work due to circumstances beyond his/her control.
  • An Incomplete will only be given when the student is passing the course except for the missed material.
  • An Incomplete is to be made up with the original course instructor within the time specified by the appropriate University regulation (see appropriate document above), and usually within the following semester.
  • An Incomplete will not be given to allow the student to informally retake the entire course, and have that grade count as the grade of the original course.

Incompletes cannot be given as a shelter from poor grades. It is the student's responsibility to make a timely resignation from the course if he or she is doing poorly for any reason.

Re-grading of Work

If you have a question about the grading of any piece of work, first consult with the teaching assistant who graded your work. If you cannot resolve your questions with the teaching assistant, you should consult with the instructor of the course. Any questions about the grading of a piece of work must be raised within 1 week of the date that the work was returned by the teaching assistant or the instructor. In other words, if you do not pick up your work in a timely fashion, you may forfeit your right to question the grading of your work. Please note that we reserve the right to regrade the entire assignment brought to our attention, possibly leading to a reduction in the overall assignment grade.

Disabilities

If you have a diagnosed disability (physical, learning, or psychological) that will make it difficult for you to carry out the course work as outlined, or that requires accommodations such as recruiting note-takers, readers, or extended time on exams or assignments, please advise the instructor during the first two weeks of the course so that we may review possible arrangements for reasonable accommodations.

Signature Form (for your records)                                                                                                                           

I, _______________________________(print name), agree to all of the terms and conditions presented in the syllabus for the University at Buffalo class entitled Introduction to Computer Science I (CSE115). By signing this form, I am stating that I have fully read and understood all sections of the syllabus, including my rights and responsibilities. 

I also understand the definition of academic integrity as outlined by the syllabus, and understand that if I violate the University at Buffalo’s Department of Computer Science and Engineering’s academic integrity policy, I will minimally receive a grade of F for the course.  I understand that any work performed in the completion of this class can be reviewed at any time for academic integrity compliance.

I also understand that I am required to have successfully completed the assigned pre-requisites for this course.  I understand that if I do not have the required pre-requisites, that I can be forcibly dropped or resigned from the course.

_____________________________________________________            _____________________________

                                   (Signature)                                                                                   (Date)


Signature Form (tear off, sign and hand in)                                                                                                             

I, _______________________________(print name), agree to all of the terms and conditions presented in the syllabus for the University at Buffalo class entitled Introduction to Computer Science I (CSE115). By signing this form, I am stating that I have fully read and understood all sections of the syllabus, including my rights and responsibilities. 

I also understand the definition of academic integrity as outlined by the syllabus, and understand that if I violate the University at Buffalo’s Department of Computer Science and Engineering’s academic integrity policy, I will minimally receive a grade of F for the course.  I understand that any work performed in the completion of this class can be reviewed at any time for academic integrity compliance.

I also understand that I am required to have successfully completed the assigned pre-requisites for this course.  I understand that if I do not have the required pre-requisites, that I can be forcibly dropped or resigned from the course.

__________________________________________            _______________________

                     (Signature)                                                                            (Date)