CSE 115 - Introduction to Computer Science for Majors I
Summer 2001 Syllabus
Monday - Friday 9:15am to 10:25am – 337 Bell
Instructor Information:
Adrienne Antkowiak
email: ama5@cse.buffalo.edu
Office: Trailer B – Station 11
Office Hours: Tuesday - Thursday 10:30am to 11:30am
Where to get information for this course:
Course Webpage: http://www.cse.buffalo.edu/~ama5/SU2001/cse115
TextBooks:
Andres van Dam's chapters on Java and OOP. [Available at Makin' Copies, located in the UB Commons.]
David J. Barnes. 2000. Object-Oriented Programming with Java: An Introduction, Prentice Hall. (ISBN: 0-13-086900-7)
Deborah S. Ray & Eric J. Ray. 1998. UNIX: Visual Quick Start Guide, Addison-Wesley. (ISBN: 0-20-135395-4)
Course Description:
Designed to provide the fundamentals of the field to computer science majors, this course introduces students to algorithm design and implementation in a modern high-level programming language. It emphasizes problem-solving by abstraction. There will also be a brief coverage of the social and ethical aspects of computing. Topics include data types, variables, expressions, basic imperative programming techniques including assignment, input/output, subprograms, parameters, selection, iteration, boolean type and expressions, and the use of aggregate data structures including arrays and records. Students will also have an introduction to the basics of abstract data types and object-oriented design, as well as the mathematics of computer science such as Boolean algebra, basic number theory, etc.
Prerequisites: Willingness to learn new things, to put forth effort in learning, and willingness to work hard to understand new concepts and ideas. A background with mathematics will be helpful, but not necessary. A few years of high school math should be sufficient. You are not assumed to have previous knowledge of programming, or of a particular programming language. However, those students that do have some knowledge in these areas might find this course easier than those who do not. This does not mean, however, that those students who have programming experience will do better in the course than those who do not.
Course Policies:
We will follow the University Policy on Academic Integrity, detailed in the Undergraduate Catalog. For more information, see Article 5A of the Student Conduct Rules, University Standards and Administrative Regulations and the UB Teaching and Learning Resources Student Conduct Rules web page. A good application of these rules to computer science is given on the department's web page, and this is the policy we will follow. Please read the policy and understand the implications.
Anyone caught in violation of the policies on academic dishonesty on any assignment will immediately be given a grade of F in the course. For especially flagrant violations, formal proceedings will be initiated. Such proceedings can call for harsher sanction including expulsion from the University.
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, I have seen assignments for which there is strong evidence of academic dishonesty. There is always proper sanction taken against these violations. 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, or 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 everyone might have to write an essay on the same topic, each person would not write a paragraph of the essay and then turn in the resulting paper. There is a lot of room for individuality, even when writing on a topic - coding a solution to a problem is the same.
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 can not 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.
Regrading of Work
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, we reserve the right to regrade the entire assignment brought to our attention, possibly leading to a reduction in the overall assignment grade.
Disablities
If you have a diagnosed disability (physical, learning, or psychological) and are registered with the Office of Disability Services, please inform the instructor during the first two weeks of the course. Do not assume that the instructor has received any paperwork about it. It is the student's responsibility to make sure that the instructor receives the paperwork as soon as possible from Disability Services.
Obstruction or disruption in the classroom
The University recognizes that faculty members are responsible for effective management of the classroom environment to promote conditions which will enhance student learning. Accordingly, instructors should set reasonable rules for classroom behavior and must articulate these rules, in writing, in materials provided to the students at the start of the semester.
Fortunately, student obstructions or disruptions in UB classrooms are rare and seldom lead to disciplinary actions. The term "classroom disruption" means behavior that a reasonable person would view as substantially or repeatedly interfering with the conduct of a class. Examples could include persistently speaking without being recognized, continuing with conversations distracting the class or, in extreme cases, resorting to physical threats or personal assaults.
Lawful, civil expression of disagreement with the instructor or other students is not in itself "disruptive behavior" and is not proscribed under these or any other regulations. However, when student conduct interferes with or prevents the conduct of classes or other university functions or when the safety of members of the campus community is endangered by threats of disruption, violence, or violent acts, the administration has approved the following course or actions:
If a student is disruptive, he/she should be asked to stop and warned that continuing such disruptive behavior can result in academic or disclipinary action. Many students may be unaware that their behavior is disruptive so that a private conversation with the student is often effective and preferable as an initial step.
Should the disruptive behavior continue, the faculty member is authorized to ask the student to leave the classroom or site.
A student may be dismissed from the course for the remainder of the semester, subject to Student Conduct Regulations and due process proceedings, as appropriate.
If a student refuses to leave the area after being instructed to do so, the student should be informed this refusal is a separate violation subject to additional penalties.
If, in the instructor's best judgment, the behavior creates a safety risk or makes it impossible to continue class or function, the instructor should contact Public Safety to assist in removal of the student and/or may dismiss class for that day.
Behavioral Expectations
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 class and paying attention. Do not ask an instructor to go over material you missed by skipping 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 instructor has dismissed class.
Grading Policy:
The following table indicates the grade breakdown which I will use in assigning grades in the course. I reserve the right to make adjustments to the breakdown if I feel it is necessary.
20% - Homework assignments & Quizzes
40% - Lab (programming) assignments
40% - Exams
Examination Grading:
There will be one midterm exam held on June 19th, 2001, during class time that will be worth 20% of your grade.
The final exam will be held on July 20th, 2001, during class time and will be worth 20% of your grade.
Please be on time for the exams. After the first person completes the exam, turns in the paper and leaves the exam room, no late arriving people will be permitted to start the exam.
If you do not attend an exam, you will receive a grade of 0 (zero) for the exam. An exception to this rule will be made only in the case of a documented medical or family emergency. You must bring your UB Card to the exams.
In order to receive a passing grade in the course, you must have a passing exam grade. In other words, your average over the two exams must be a grade of at least 50% in order for you to receive a passing grade in the course.
The following table indicates the number to letter grade mapping I 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 16 of the 2000-2001 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
Handouts & Attendance Policy:
All handouts, lab assignments, homework assignments, quiz questions and solutions, and other printed course material (including this syllabus) are available on the course webpage.
Attendance is required for all lectures and recitations. Students who do not attend class regularly generally do not do as well in the course as those who do. If for any reason you can not attend a lecture, it is the student's responsibility to make up the missed work. I will not take time out of my office hours to reteach material to students who did not attend class. If you are absent, get the notes from someone. Handouts and important announcements are always available on the webpage, so if you need to be absent, you can get the materials you missed. Attendance at the exams is mandatory. Attendance may be taken on occasion and may be used to determine how to resolve borderline grades at the end of the course.
Homework Assignments:
There will be assigned problems that students are responsible for doing outside of class time. These problems are assigned to reinforce the ideas given in class. The answers will be made available one or two days after the assignment has been made. In general, the answers to these problems will not be collected, nor graded, but it is to the student's best interest to complete the assigned problems. These problems and solutions will be announced in class as well as posted on the webpage. If the homework is to be handed in for a grade, this will be announced at the time the assignment is given.
Quizzes:
There will be 12 quizzes given during the semester. The lowest 2 grades will be dropped and then your quiz grade computed. The questions for the quizzes will come from assigned homework problems, assigned readings, and class lecture. There will be no makeups allowed for quizzes. Two quizzes can be missed without penalty to your grade. After two missed quizzes, each missed quiz will count as a zero. Quizzes will be given at any time during the lecture, and answers will be discussed immediately following the end of the quiz. Quizzes will be given approximately every three class days. The schedule is as follows:
Quiz 1 May 23, 2000 Quiz 7 June 22, 2000
Quiz 2 May 29, 2000 Quiz 8 June 27, 2000
Quiz 3 June 1, 2000 Quiz 9 July 2, 2000
Quiz 4 June 6, 2000 Quiz 10 July 6, 2000
Quiz 5 June 11, 2000 Quiz 11 July 11, 2000
Quiz 6 June 14, 2000 Quiz 12 July 16, 2000
Labs:
There will be weekly labs for this course. Labs are programming assignments designed to complement the lectures, and sharpen the programming skills of the students. They are graded and worth 40% of your final course grade. There will be 8 assignments this semester. Each of them are equally weighted. Lab assignments will not be given out in hard copy, but will be available on the web. Due dates for the labs are stated directly on the assignment. Late labs will receive a 1/3 penalty per day late. Any lab handed after three days will be given a grade of zero. If the solution to a lab is given in class, NO LATE LABS WILL BE ACCEPTED.
Extra Credit:
Every semester in every class there are always some students who want to know what he/she can do to receive extra credit in the course. In this course, extra credit assignments will be given. There will be five assignments throughout the semester. Each of them will count for 20 points. For each assignment, there will be a lab associated with the points. The points will be added to that lab. If the student does not complete the extra credit, they will not be penalized. If the student does not correctly complete the extra credit, partial credit will be given.
Resources:
The Resources page of the course website has points of interest for all students taking this class. There are links to the source code that I have written in class, as well as links to computing resources, and links to resources about computing at home. Please become familiar with the Java API specification, whose link is on this page. These docs can be a huge help in this course, and in future courses.
Schedule:
A tentative course schedule is available on the course website. We will cover the entire contents of the Brown Notes and Chapters 1-14 (skipping 11 & 12) of the Barnes Book.
Disclaimer:
I reserve the right to change this syllabus and the contents herein if circumstances of the class/semester require me to do so. These changes will be announced and posted to the class website.
Student Portion: Signature form - Student Copy
I 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 the form below, 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 form the course.
I have read the above statement and have read the syllabus and understand what the expectations are in this course.
CSE 115: Introduction to Computer Science I Summer 2001
Student Portion: Signature form
I 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 the form below, 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 form the course.
I have read the above statement and have read the syllabus and understand what the expectations are in this course.
Student Name (print): _____________________________________________________
Signature: _______________________________________________________________
Date: ________________