| |
CSE 113 - Spring 2008 - Introduction to Computer Programming I |
|
|
Syllabus
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Name |
Office |
Phone |
Email |
Web |
|
Adrienne Decker |
130 |
645-3180 x 161 |
adrienne@cse.buffalo.edu |
http://www.cse.buffalo.edu/faculty/adrienne |
Course Information
Credit hours: 4
Course Website: http://www.cse.buffalo.edu/faculty/adrienne/SP2008/cse113
A Lecture: Monday, Wednesday, Friday 3:00 – 3:50 201 NSC
B Lecutre: Monday, Wednesday, Friday 4:00 – 4:50 112 Norton
Recitation Times:
A1 Monday 8:00
– 9:50 340
A2 Wednesday 9:00
– 10:50 340
A3 Tuesday 11:00
– 12:50 340
A4 Thursday 9:00 – 10:50 340
B1 Tuesday 3:00
– 4:50 340
B2 Tuesday 9:00
– 10:50 340
B3 Thursday 1:00
– 2:50 340
B4 Friday 1:00 – 2:50 340
B5 Wednesday 2:00 – 3:50 340
Course Description
Introduction to computers and
computer programming intended for nonmajors. Currently required for some
Schedule of Topics
The following is a tentative schedule of topics. A more detailed schedule is maintained on the course website and should be checked often for updates.
2 weeks – Introduction to computers and programming
3 weeks – Variables, assignment, functions
3 weeks – Looping
3 weeks – Conditionals
3 weeks – Classes and object-oriented programming
Course Objectives
At the end of this course, students will have been introduced to several of the main concepts in computer programming including sequencing, selection, and iteration. Students will be able to use these constructs to create a solution to solve a simple problem and create a small to medium sized software program. Students will have also been introduced to some of the main concepts of object-oriented programming and be able to write and use their own classes in their programs.
Prerequisites
There are no formal prerequisites for this course. However, if you have never used a computer before or do not feel comfortable using web browsers, email clients, instant messaging programs, word processors, or spreadsheets and would like a general introduction to these type of concepts, this is not the course for you. In this course, we will be creating computer programs in a modern high-level language (Java). If you are not comfortable working with a computer, you will not do well in this course.
Textbooks and Materials
The required textbook for
this course is:
·
Mark Guzdial and Barbara Ericson. 2007. Introduction to Computing
& Programming with Java: A Multimedia Approach, Prentice Hall. (ISBN: 0-13-149698-0)
Additional reading material
may be assigned during the course, and will be announced in lecture.
Computing Resources
You will be provided with a
computing account through the school of engineering. You may use the lab
facilities in
The name of the server that
you will be connecting to in the lab will be unix.eng.buffalo.edu. You have the ability to connect to this
server remotely from other sites, on or off campus.
You
are expected to become proficient at using the machines in the lab, the Unix
system, the Java compiler, and whatever other software development tools the
course requires you to use. It is your responsibility to ensure that any
programs you write for this course compile using the Java compiler installed on
the department's machines.
By virtue of having a
Engineering account, you receive another email account, whose address is
UBitName@eng.buffalo.edu. You can choose to use this email account in addition
to your regular UB mail or forward mail sent their to your UB account. In
either case any e-mail communication that you send regarding this course must
be sent from your Engineering e-mail account or your UB e-mail account. Under
no circumstances will e-mail from non-UB accounts be acknowledged or answered.
You must include an informative subject line in all e-mail, and include your
full name in any e-mail correspondence.
All e-mail that we send in
reply to your e-mail will be sent to the address from which you sent your
e-mail. Our feedback on materials you hand in electronically will be sent to
your CSE e-mail account only. Since you may request re-grades of work only
within a set period from the time that the feedback was provided to you, it is
in your best interest to read your CSE e-mail account on a daily basis.
Course Organization
The course has both a lecture
component and a lab component. Each component plays a role in helping you
achieve the objectives of the course. If you do not participate fully in both
you should not expect to do well in the course.
Lectures
The conceptual and
theoretical course content will be delivered primarily in the lectures,
complemented by readings from the text books. You must review readings prior to
attending a lecture, and you are expected to review the readings again, along
with any notes you took, after the lecture.
Some of the topics will be
difficult. It is therefore absolutely essential that you ask questions whenever
something is said which you do not understand.
You are expected to attend
all lectures. If you are unable to attend a lecture because of sickness or
similar reasons, make sure you get the notes from a classmate. If you are out
of class for an extended period of time because of sickness, notify your
instructor as soon as possible, and see your instructor immediately upon your
return in order to determine how to catch up. If you have missed a significant
portion of the semester due to illness, it is recommended that you resign from
the course.
Labs
The labs are an integral part
of the course. In each recitation section, the TAs will answer questions about the
currently assigned programming modules.
You are free to ask any questions about the modules and get assistance
from the TAs during this time on your personal assignment. Labs meet in a computer lab so you are free
to work on your assignments during this time.
Do not expect to finish your assignment in the allotted lab time each
week. You will have to work on your own
outside of lab to complete the assignments for this course. You can return to the computer lab during
open lab hours to work on your assignments.
Labs do not meet in the first
week of classes.
Time outside of class
Office hours
Office hours offer you the
opportunity to ask more individual questions about the course material than can
typically be addressed in lecture. Both the instructor and the teaching
assistants have scheduled office hours. Office hours are held on a first-come
first-served drop-in basis. No appointment is necessary to attend office hours.
Be aware that office hours become increasingly busy the closer it is to a project
deadline. Plan your use of office hours accordingly. Individual appointments
may be arranged, if needed, as schedules allow.
Study time
In this course, as in any
course, you are expected to put in additional time beyond the scheduled class times.
Professors generally expect that for each credit hour a class carries a typical
student will put in 2 - 3 hours of time each week outside of class. Since this
is a 4 credit course that translates into 8 - 12 hours of time outside of
lecture and recitation times, each week. During this time you should review
your lecture notes, attend office hours as needed, get hands-on practice
applying the concepts and theoretical constructs discussed in class, and
possibly arrange to meet in small groups to study or review the concepts from
class. As a rough guide, you should expect to spend at least the following time
working on this course, each week:
o
Lectures: 3 hours
o
Lab time: 2 hours
o
Programming
assignments: 4 hours
o
Individual study:
4 hours
Course evaluation
The grading scheme for this
course is based on level of achievement.
The more modules and exams you complete, the better your grade. If you complete a certain number of modules
and exams and are happy with the grade you have achieved, you need not complete
any more.
Programming Modules
Successful completion of a
programming module involves achieving a minimum grade of 70% on the module. If you
do not achieve a grade of 70, you have not completed the module. There are no opportunities to re-do and
re-submit a programming module for re-grading after the deadline for submitting
the module has passed. However, up until
the final due date, you can continue to work on and re-submit more completed
versions of the program. Once the
deadline has passed, modules are considered late. Late modules are assessed a
penalty of 50 points per day (or portion thereof) late. Therefore, submitting a perfectly working
program the day after the deadline will only achieve a grade of 50, not enough
to pass the module. You must turn in
your module on time for hope of grade of successful completion.
Exams
There will be ten
examinations throughout the term. The exam dates are posted on the course
website. Each exam will cover the
material presented in class since the previous exam. (Exception is March 21st. Test would have occurred on this day, but to
avoid conflicts with the Easter holiday, if celebrated, the test has been moved
to March 31st).
Topics and sections for each
exam will also appear on the course website.
The successful completion of an exam involves achieving a minimum grade
of 70% on the exam. If you do not have a
grade of 70% on the exam, you have not successfully completed it. Students who have achieved a grade between 65
and 69 on an exam *may* be awarded the opportunity on some exams to write
corrections for the exam to bring their grade up to a 70. Grades below 65 will always be considered
failing on an exam.
There will be no makeup exams
given under any circumstances if you miss an exam.
You must bring a valid form
of picture ID with you to each examination (a UB Card will suffice).
There is no final exam for
this course. The ten exams will be given
during class time.
Attendance and
Participation
You are expected to attend
all lectures and lab sessions. Students
who do not attend lectures and labs generally do not do as well as those
students who do. At random times during
the semester, attendance quizzes will be taken that could be worth as much as
five points additional for your latest module or exam grade. Also, there may be lectures where module
assignments will be discussed in detail.
Attending these lectures will be beneficial to successfully completing
the module. Neither of these will be
announced ahead of time.
Letter grades
The following table indicates
the number of modules and exams completed to letter grade mapping I will use to
assign final grades at the end of the course. The Grade points for each letter
grade can be found in the Undergraduate Catalog.
|
Letter Grade |
Number of Exams Successfully Completed |
||||||||||
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
||
|
Number of Programming Modules Successfully Completed |
1 |
F |
F |
F |
F |
F |
F |
F |
F |
F |
D |
|
2 |
F |
F |
F |
F |
F |
F |
F |
F |
D |
C- |
|
|
3 |
F |
F |
F |
F |
F |
F |
F |
D |
C- |
C |
|
|
4 |
F |
F |
F |
F |
F |
F |
D |
C- |
C |
C+ |
|
|
5 |
F |
F |
F |
F |
F |
D |
C- |
C |
C+ |
B- |
|
|
6 |
F |
F |
F |
F |
F |
C- |
C |
C+ |
B- |
B |
|
|
7 |
F |
F |
F |
F |
F |
C |
C+ |
B- |
B |
B+ |
|
|
8 |
F |
F |
F |
F |
F |
C+ |
B- |
B |
B+ |
A- |
|
|
9 |
F |
F |
F |
F |
F |
B- |
B |
B+ |
A- |
A |
|
|
10 |
F |
F |
F |
F |
F |
B |
B+ |
A- |
A |
A |
|
Re-grading
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 one 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.
Incomplete (I) grades
We will follow the UB
Undergraduate Catalog Statement on Incomplete Grades, found in the
Undergraduate Catalog.
Generally, incomplete (“I”)
grades are not given. However, very rarely, circumstances truly beyond a
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:
o
An Incomplete
will only be given for missing a small part of the course.
o
An Incomplete
will only be given when the student misses work due to circumstances beyond
his/her control.
o
An Incomplete
will only be given when the student is passing the course except for the missed
material.
o
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.
o
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 your responsibility to make a timely
resignation from the course if you are doing poorly for any reason. The last
day to resign the course is Friday, March 28th.
General Notes
If you don't understand
something covered in class, ask about it right away. The only silly question is
the one which is not asked. If you get a poor mark on an assignment, quiz, or
exam, find out why right away. Don't wait a month before asking. The instructor
and teaching assistants are available to answer your questions. Don't be afraid
to ask questions, or to approach the instructor or T.A. in class, during office
hours, or through e-mail.
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, you must consult with the Office of Disability Services
(25 Capen Hall, Tel: 645-2608, TTY: 645-2616, Fax: 645-3116, http://www.student-affairs.buffalo.edu/ods/).
You must advise your
instructor during the first two weeks of the course so that we may review
possible arrangements for reasonable accommodations.
Your attention is called to
the
Distractions in the Classroom - Behavioral
Expectations
The following is the text of
a policy adopted by the Faculty Senate. You are expected to know and adhere to
this policy.
OBSTRUCTION OR DISRUPTION IN THE CLASSROOM –
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:
Academic Integrity
Source:
http://www.cse.buffalo.edu/academics-academic integrity.shtml
The academic degrees and the
research findings produced by our Department are worth no more than the
integrity of the process by which they are gained. If we do not maintain
reliably high standards of ethics and integrity in our work and our
relationships, we have nothing of value to offer one another or to offer the
larger community outside this Department, whether potential employers or fellow
scholars.
For this reason, the
principles of Academic Integrity have priority over every other consideration
in every aspect of our departmental life, and we will defend these principles
vigorously. It is essential that every student be fully aware of these
principles, what the procedures are by which possible violations are
investigated and adjudicated, and what the punishments for these violations
are. Wherever they are suspected, potential violations will be investigated and
determinations of fact sought. In short, breaches of Academic Integrity will
not be tolerated.
Departmental Statement on Academic Integrity in Coding Assignments and
Projects
The following statement
further describes the specific application of these general principles to a
common context in the CSE Department environment, the production of source code
for project and homework assignments. It should be thoroughly understood before
undertaking any cooperative activities or using any other sources in such
contexts.
All academic work must be
your own. Plagiarism, defined as copying or receiving materials from a source
or sources and submitting this material as one's own without acknowledging the
particular debts to the source (quotations, paraphrases, basic ideas), or
otherwise representing the work of another as one's own, is never allowed.
Collaboration, usually evidenced by unjustifiable similarity, is never
permitted in individual assignments. Any submitted academic work may be subject
to screening by software programs designed to detect evidence of plagiarism or
collaboration.
It is your responsibility to
maintain the security of your computer accounts and your written work. Do not
share passwords with anyone, nor write your password down where it may be seen
by others. Do not change permissions to allow others to read your course
directories and _les. Do not walk away from a workstation without logging out.
These are your responsibilities. In groups that collaborate inappropriately, it
may be impossible to determine who has offered work to others in the group, who
has received work, and who may have inadvertently made their work available to
the others by failure to maintain adequate personal security In such cases, all
will be held equally liable.
These policies and
interpretations may be augmented by individual instructors for their courses.
Always check the handouts and web pages of your course and section for
additional guidelines.
Departmental and Course
Policy on Violations of Academic Integrity
If, after following the
procedures required by the University for investigation of suspected breaches
of academic integrity, a student is found guilty, the policy of the department
of Computer Science & Engineering is that the student minimally receive a
grade of F in the course.
University at
Department of Computer Science & Engineering
I, ____________________________________________(PRINT
name), acknowledge that I have read and understood the syllabus for this
course, CSE 113 Introduction to Computer Programming I.
I also acknowledge that I
understand the definition of academic integrity as outlined in the syllabus,
and that I will minimally receive a grade of F in the course if I am found to
have breached academic integrity.
Signature:
________________________________________________ Date: _____________
Announcements | Assignments | Meetings | People | Resources | Schedule | Syllabus |
Page Maintained by: Adrienne Decker |