Deprecated: The each() function is deprecated. This message will be suppressed on further calls in /home/zhenxiangba/zhenxiangba.com/public_html/phproxy-improved-master/index.php on line 456 Syllabus
Syllabus and Class Information
Computer Science 207
Spring 2013
Note: Remember to refresh your browser to see updates to this document.
Rooms, office hours, and other details are subject to change!
Meeting times
Lectures:
Section 2: MWF 9:00 in PEARSON 1105
Section 3: MWF 9:00 in HAMILTN 0169
Recitations:
In addition, there are recitations that you are expected to attend.
Section 2: W 3:10-4:00PM
Section 3: R 3:10-4:00PM
Note: There are no recitations during the first week of classes.
Dr. Ying Cai www.cs.iastate.edu/~yingcai
Office: Atanasoff 201
email: yingcai@iastate.edu
Office Hours: TBA.
Teaching Assistants
All TA office hours are held in Pearson 145 (in Pearson's basement).
TAs can also be reached
by appointment if you can't make the regular office hours and need to
speak to a specific staff member.
Prereq: Math 150 or placement into Math 140/141/142 or higher.
Description: An introduction to computer programming using an object-oriented programming language. Emphasis on the basics of good programming techniques and style. Extensive practice in designing, implementing, and debugging small programs. Use of abstract data types. Interactive and file I/O. Exceptions/error-handling. This course is designed for nonmajors. Credit may not be applied toward graduation for both Com S 207 and 227.
Course Objectives
Understand the role that computation can play in solving problems
Be able to read and understand programms written by others
Be able to write small scale programs using Java
Blackboard
We will be using Blackboard for this course. Students are expected to log in daily to check for announcements, sample code from lectures, and information about homework or exams.
In particular:
Announcements about the course, such as assignments, due dates, and
exam locations, will be
made via Blackboard.
Clarifications
and answers to common questions about homework will be announced
on Blackboard.
It is your responsibility to know how to log in,
read announcements,
submit homework via Blackboard.
You can log into Blackboard with your ISU NetID and password at
If you have a general question about the course, about an
assignment, or about Java, please do not hesitate to contact the instructors and/or
Teaching Assistants.
If you need to send an email to the instructors or the TAs, please begin
the subject line with "CS 207".
Textbook
Java for Everyone, by Cay Horstmann
Exams
This course has night exams
Exam 1: Feb 12, 6:45PM-8PM
Exam 2: Apr 02, 6:45PM-8PM
Final Exam: TBA
*** You must bring your university ID to all exams. ***
If you cannot attend an exam, you must notify your instructor at least
one week prior
to the exam to make other arrangements. The instructors will normally
adhere to ISU policies regarding exam scheduling.
Exams will be returned to you in lectures.
If you feel that an error was made in the grading of an exam,
please return it to your instructor with a brief statement
in writing indicating where you think the error was made.
Such appeals must be made within one week of the date on which
the exams are returned in lab. (Note that a regrade
may result in a lower score.)
The final exam will not be returned to you, but you may come to
the instructor's office hours during the following semester to review it.
Grades
Letter grades will be based on an overall weighted average
of the three exams and the homework
with approximately the following weighting.
Programming Homeworks: 25%
Short Homeworks: 10%
Quizzes, Recitation, Inclass Activities: 15%
Exam 1: 10%
Exam 2: 15%
Final Exam: 25%
Each recitation is worth 20 points. Each in class activity
is worth 10 points, and each quiz is worth 20 points.
Points scored on all these components
are worth 15% of your total grade.
To receive a passing grade you must score at least 55% in the exams, and at least 55% in the programming assignments. For example, if you score 100% in the exams, quizzes, recitations, activities, but score 54% in programming assignments, you will not receive a passing grade.
Letter grades are not assigned until the end of the course.
Below is an approximate grading scale.
90 and above
A-
80 and above
B-
70 and above
C-
60 and above
D-
Please note that the above scale is to be taken as an approximate guideline.
The instructors may adjust the scale at the end of the semester.
Homework
All homeworks and programming assignments will be posted on blackborad.
Short homeworks are pen and paper homeworks. You can type ypur solutions and submit via black borad.
In Programming projects you will develop a program according to the specifications and test it.
Programming projects will be turned in via blackboard.
Compilation and runtime errors
All code submitted must compile under the Java 6 or 7 JDK compiler.
If your code does not compile, you will normally receive zero points for the assignment.
Similarly, you are responsible for fully testing your code, whether or not
any sample test code is posted for you to try and whether or not
the test code is part of the assignment submission. You will lose additional points
for runtime errors (e.g., infinite loops, uncaught exceptions, memory leaks, etc.)
that occur during testing.
Submissions and feedback
In general, late assignments will NOT be accepted, except that
programming assignments may be turned in up to 24 hours late
with a 25% grading penalty (weekends and university
holidays are not counted in the 24 hours).
Results will be returned via Blackboard, normally accompanied by
an attachment indicating where points were taken off.
If you have questions about the grading or if you
feel an error has been made in grading your assignment,
contact the TA that graded it, either during office hours or by
email. In particular, requests for regrades must be made within
one weeks of the date when the results were made
available on Blackboard. Note that a regrade may result in a lower score.
If you are not satisfied with the response from the TA,
please contact your instructor promptly.
Correct submission of an assignment is your responsibility.
Remember that when submitting an assignment via Blackboard, you can immediately
check whether the submission was successful, and you can always download
your submission and verify that it is what you intended. Don't forget
that with Blackboard, it is NOT
enough to just select the file to be submitted. You also have to remember to click the
"Submit" button.
Attendance
It is very strongly recommended
that you attend all lectures and recitations.
If you don't want to come to class,
it is your responsibility to find out what was covered and to learn it
on your own.
Academic Dishonesty Policy
Unless specifically instructed otherwise, every assignment
and lab activity is to be the product of your own intellectual effort
and is to be done on your own.
Any violation of this rule will be considered
academic dishonesty, otherwise known as cheating.
Anyone guilty of academic dishonesty will
receive an automatic F in this course. Additionally, we will adhere
to university policies regarding academic dishonesty, which means that you
may receive any of the penalties described in the Policies and Practices
section of the Student Handbook under Academic Dishonesty:
http://www.public.iastate.edu/~catalog/2005-07/geninfo/dishonesty.html
There are two forms of academic dishonesty to be careful about.
Plagiarism:
If you present the work of someone
else as if it were your own, you are guilty of plagiarism. Plagiarism is
unethical at every level of every profession.
Tendering information:
In a university environment
(such as in this course), if you make your assignment available for someone else to
copy, you are guilty of tendering information, which is also
considered to be a form of academic dishonesty.
Here are just a few examples of things you may may not do when
working on an assignment:
Look at another student's source code. (*)
Allow another student to look at your source code. (*)
Type in a solution with another student and each turn in a copy.
Write a program with another student on paper and type it up separately.
Divide the work so that you an another student each write part of a
program (for example, 3 methods each), then combine
them, and each turn in a copy.
Discuss the code in detail with another student but type it in separately.
Get code from the an outside source (such as a web site) and turn it in.
Get code from the an outside source (such as a web site), modify it,
and then turn it in.
Make available all or part of your code for someone else to see, whether
by paper, email, ftp, Blackboard discussion, shared network folder, storing on a public
machine, letting someone else look at your screen, reading code out loud
while someone takes notes, posting in an online forum, etc.
Give another student your password.
(*) Exception: code may be shared after it can no longer be turned in for credit.
For programming assignments, this means after the "late deadline" (normally 24 hours
after the deadline, not counting weekends and holidays).
Things you may do when working with another student:
Talk about, and write down ideas about, how to do an assignment, as
long as you do not write actual code or "pseudocode" together.
Share test code or test data files that will not be turned in.
Share and discuss code that was presented as an example in
class or the text.
Share and discuss code for programming assignments after the
"late deadline" for the assignment has passed (normally 24 hours
after the deadline, not counting weekends and holidays).
The rules against sharing code are not intended to prevent students
from studying and working together. Remember that all the ideas
and techniques
you need to do an assignment will have been presented as examples in
class or in the book, and you can discuss all such examples freely.
In general, it is acceptable to discuss how to do the homework with other
students, but when it is time to sit down and write your code, you must
be able to produce the entire result without help from anyone else.
If you get help from any source besides the textbook(s), instructors, or TAs,
you must cite these sources. For example, if you look at code
on a website to get ideas for how to do the homework, you must clearly indicate
what the website was and what information you got from it. You may not receive
full credit for that work,
since you aren't handing in something that is solely your
own work, but at least you will not be guilty of plagiarism.
A W-W-W-Warning
Just as a word to the wise, note that random examples you find on the web
are likely to mislead you more than help you, since those who post them
have no idea of the ideas and techniques being covered in our particular class.
You will be much better off reviewing examples from class and posting
your questions on the Blackboard discussions, where the instructor, TAs, and
other students going through the same experience can help you.
Disabilities
Iowa State University complies with the American with Disabilities Act and Section 504 of the
Rehabilitation Act. Any student who may require an accommodation under such provisions should
contact me as soon as possible and no later than the end of the first week of class or as soon
as you become aware. Please request that a Disability Resources staff send a SAAR form
verifying your disability and specifying the accommodation you will need. No retroactive
accommodations will be provided in this class.