CS/COE
1501 Algorithm Implementation
|
Lecture:
|
Recitation:
|
|
T H 2:30PM –
4:15 PM – SENSQ 5129
[CRN 11496 – Regular Section]
[CRN 11786 – W Section]
Make sure you are in the correct section
|
H 4:30PM –
5:20PM
SENSQ 5502
|
|
Instructor:
|
John Ramirez
|
|
Office:
|
SENSQ 6141
|
|
Phone:
|
624-8441
|
|
Email:
|
ramirez@cs.pitt.edu
|
|
Web:
|
http://www.cs.pitt.edu/~ramirez
|
|
Office Hours:
|
Tue 1:00PM – 2:00PM
|
|
|
Wed 11:00AM – 1:00PM
|
|
|
Thu 1:00PM – 2:00PM
|
|
|
and by
appointment
|
|
TA:
|
Recitations/Grading:
Lei Jin
(jinlei@cs.pitt.edu; Office: 5802 SENSQ; Office
Hours: Tuesday 11-12; Wednesday 1-3)
Grading: Onur Cobanoglu
(onc3@pitt.edu; Office: 5106 SENSQ; Phone:
412-624-8847; Office Hours: Monday 12-1, Friday 11-1)
|
Online
Information
Required Text: Algorithms
in C++ (Robert Sedgewick, ISBN: 0-201-51059-6)
Optional Texts: Algorithms
in Java Parts 1-4 (Robert Sedgewick, ISBN: 0-201-3620-5)
Algorithms in Java Part 5 (Robert Sedgewick, ISBN: 0-201-36121-3)
Recommended
Text for W Section: Handbook of Writing
for the Mathematical Sciences (Nicholas J. Higham,
ISBN: 0-89871-420-6)
Languages/Environments: Java
Course Web
Site:
http://www.cs.pitt.edu/~ramirez/cs1501
Course Policies
(both sections):
General
Requirements
|
Exam
One:
|
25%
|
|
Exam
Two:
|
25%
|
|
Programming
Projects:
|
40%
|
|
Quizzes:
|
10%
|
- Attendance will be taken in recitations where the
programming projects will be assigned. Students who skip recitation should
not expect course staff to individually reiterate this material during
office hours.
- Attendance and participation in lecture and recitation
may be used to decide borderline grades.
- Each student is expected to do his/her own
work. For a first offense, a
student caught collaborating/cheating in any way will receive a zero for
the exam/homework/project in question.
In the event of a second offense, the student will receive an F for
the course and may be subject to stronger action. Note: Submissions that are alike in a substantive way (not due
to coincidence) will be considered to be cheating by ALL involved parties.
Protect yourselves by only storing
your files in private directories,
and by retrieving all printouts promptly.
- Students are encouraged to attend all lectures,
which frequently include material that is not directly taken from the
text. If a student misses a
lecture, he/she is still responsible for the material covered and is
advised to copy the notes from a classmate.
- An abundance of information, including
announcements, handouts, review sheets and solutions will be posted on the
CS1501 Web page throughout the term.
Students are expected to be aware of all information that is posted
on the CS1501 web pages, and should access them frequently.
- All graded materials that a student receives back
should be saved in a safe place until after the term has ended and he/she
has received and accepts his/her final grade. In this way, any grade discrepancies can
be easily resolved.
Exams
- Please see Important Dates below for exam dates.
- Exam Two may be partially cumulative.
- Students are expected to be present for both
exams. Make-up exams will only be
given in the event of an emergency, and only if I am informed in
advance. If you cannot contact me directly, send me email or call
the CS department
(624-8492) and leave a message. Failure to notify me prior to missing an
exam will result in a zero for the exam.
Programming
Projects
- There will be approximately 5-6 equally weighted
Programming Projects assigned throughout the term.
- Most programs are to be written in Java
(recommended). Thorough knowledge
of Java by the students is assumed (through the courses CS401 and CS445 or
their equivalents). Programs may
involve some advanced features of the language and good reference books
(e.g. CS401 and CS445 textbooks) are strongly recommended.
- In addition to programming, projects may involve
write-ups and analyses. These
should be well written and will be graded for both form and content.
- Projects will be given out electronically (via
the CS1501 Web page) and will be discussed in recitations or office hours
-- NOT in lecture.
- Projects will be submitted electronically to a
submission directory set up for the course. More details on submission guidelines
will be provided on the course Web site.
- On-time projects must be received at the submission site
by 11:59 PM on the due date. Projects submitted after that time will
be graded as late submissions.
- Projects will be accepted late up to the specified late due date,
but 15 points will be deducted from the grade if the assignment is
late. No assignment will be accepted after the specified late due
date.
- Students are expected to have a backup disk (or AFS directory) for
every assignment they turn in.
In this way, if there is any
problem with the copy that is handed in (corrupted data, etc) the backup
can be used for grading purposes.
- Factors that will determine the grade given to a
Programming Project include correctness of the algorithm and the program
code, good programming style, documentation, and analysis and write-up of
results.
- More details on the programs will be given with
the first assignment.
Quizzes
- Quizzes will be given during recitations, and
will be announced at least one week before they are given. They will
generally include material covered in the previous class(es) and recitation(s).
- Two quizzes will be given, each counting for 5%
of the final grade.
- As with exams, quizzes can only be made up if you
contact the recitation instructor in advance. If you miss a quiz
without informing the recitation instructor, you will receive a zero for
that quiz.
Additional
Requirements for W Section
- The write-ups for the W Section students will be
substantial and will have significant weight toward the overall assignment
grade. They will also be graded
with scrutiny for proper writing form.
Additional writing issues may be discussed in lecture and in
recitation.
- At least one paper will be subject to one or more
revisions after feedback from the course instructor or grader. The grade for the paper or papers will
be based on the overall sequence of revisions, and not on just one version
of the paper.
Important
Dates:
|
Event/Item
|
Date(s)
|
|
First Class meeting
|
Tuesday, May
12, 2009
|
|
Last Day to Add/Drop
|
Monday, May
18, 2009
|
|
Exam One
|
Thursday,
June 18, 2009
|
|
Last Day to Withdraw
|
Thursday,
July 2, 2009
|
|
Exam Two
|
Thursday,
July 30, 2009
|
Course
Agreement
I,
the undersigned, have read and understood the Course Policies as presented in
this handout.
(signed)
________________________________________ (date) ___________________
(printed name)
_______________________________________
Additional
Information
Phone Number _______________________
Academic Year ________________________
Major __________________________
Email __________________________
Other Courses, CS Experience