CS 183/184
Computer Science Clinic
- Prof. Dodds's brief contact information:
Zach Dodds,
dodds@cs.hmc.edu, x71813,
Beckman B111.
- CS secretary: Joyce Greene, Olin 1258, x18225
- Clinic secretary: DruAnn Thomas
- Clinic meetings: T 11-noon; others TBD
The key to clinic is team-organized effort. To facilitate this teamwork,
the bulk of the clinic work will be lab-based work
Clinic is a difficult but rewarding course. To help you get through
it, I have compiled a separate document listing
what is expected of you on a
clinic project.
You are expected to be intimately familiar with that document.
Grading clinic is always a difficult task, both because of the group
nature of the course and because of the nebulous criteria for project
success. To help you understand what goes into grading, here is a
partial list of what is expected for each letter grade. Of course,
nobody will fall neatly into a particular category; instead, the
"preponderance of evidence" will carry the day.
Also, remember that clinic is a team project, not a competition. It
is definitely possible for everyone to get an A. Phrases such as
"major contribution" do not mean that you have to do more
than your fair share of the work.
A:
An "A" is awarded for outstanding work that can serve as an example
for other students in later years. "A" work represents a professional
attitude, reflects thoughtful understanding of the project, meets all
expectations, and is complete in every respect.
- You did not miss any clinic meetings
unless excused by your advisor or the clinic director.
- You were never late for clinic meetings.
- You did not miss any Tuesday-morning clinic presentations
unless excused by your advisor or the clinic director.
- All of your weekly status reports were filed on time,
with significant content.
- You were always prepared for clinic meetings.
- The lab notebook was kept neatly, was well organized,
and served as a clear record of the entire project.
- Your clinic teammates viewed you as a major contributor and a
hard worker.
- You made major contributions to the design of
the project.
- You made major contributions to the
implementation of the project.
- You used source control regularly and properly.
- Your code was easily readable by others, both inside and
outside the project.
- You documented everything that you produced, both
internally and for the user.
- You contributed significantly to both writing and delivering all
clinic presentations.
- You showed a strong desire to improve your presentation
skills over the course of the year.
- All of the clinic deliverables (reports, presentations,
poster, and source code) arrived on time.
- Your midyear and final reports were complete, clear, and
thorough.
- Your written clinic deliverables contained no significant
spelling or grammar errors, except for infrequent and minor
typographical errors that could not be detected by automated tools.
- The customer was very happy with the outcome of the project.
- In addition, if you were the team leader:
- Each team member thoroughly understood his or her
responsibilities.
- Team conflicts were handled extremely well.
- Difficulties with the project were always reported
quickly to the advisor and liaison.
B:
A "B" is awarded for good work that has only a few flaws. A "B" effort is
characterized by an excellent attitude and good understanding of the
project. It meets most expectations and is complete in nearly every
respect.
- You had at most one unexcused absence from clinic
meetings during the term.
- You were rarely late for clinic meetings.
- You had at most one unexcused absence from Tuesday-morning
clinic presentations during the term.
- Nearly all of your weekly status reports were filed on time,
with significant content.
- You were nearly always prepared for clinic meetings.
- The lab notebook was reasonably well organized
and provided a good record of your participation in the
project.
- Your clinic teammates viewed you as helpful.
- You made significant contributions to the design of
the project.
- You made significant contributions to the
implementation of the project.
- You used source control frequently.
- Your code was readable by others, both inside and outside
the project.
- You documented nearly everything that you produced, both
internally and for the user.
- You participated in both writing and delivering all
clinic presentations.
- You made an honest attempt to improve your presentation
skills over the course of the year.
- Nearly all of the clinic deliverables (reports, presentations,
poster, and source code) arrived on time.
- Your midyear and final reports were almost complete, quite clear, and
pretty thorough.
- Your written clinic deliverables contained only a few significant
spelling and grammar errors.
- The customer was fairly happy with the outcome of the project.
- In addition, if you were the team leader:
- Each team member understood his or her
responsibilities fairly well.
- Team conflicts were handled without lasting effects.
- Difficulties with the project were nearly always
reported quickly to the advisor and liaison.
C:
A "C" is awarded for satisfactory but uninspired work. A "C" effort is
characterized by a positive attitude and some understanding of the
project. It meets some expectations and is reasonably complete in all
important respects.
- You had at most two unexcused absences from clinic
meetings during the term.
- You were occasionally late for clinic meetings.
- You had at most two unexcused absences from Tuesday-morning
clinic presentations during the term.
- Many of your weekly status reports were filed on time,
and they usually had significant content.
- You were often prepared for clinic meetings.
- The lab notebook provided a fairly good record of your
participation in the project.
- Your clinic teammates did not view you as a detriment to
the team, but were not happy with your contribution or the
level of effort you devoted to the project.
- You contributed to the design of the project.
- You contributed to the
implementation of the project.
- You used source control often enough that no critical
data was placed at risk.
- Your code was reasonably readable by your teammates.
- You documented most of what you produced, both
internally and for the user.
- You participated in both writing and delivering most
clinic presentations.
- You made some attempt to improve your presentation
skills over the course of the year.
- Some all of the clinic deliverables (reports, presentations,
poster, and source code) arrived on time.
- Your midyear and final reports were somewhat complete, fairly
clear, and somewhat thorough.
- Your written clinic deliverables contained quite a few
spelling and grammar errors.
- The customer was not actively unhappy with the outcome of
the project.
- In addition, if you were the team leader:
- Each team member had some idea of his or her
responsibilities.
- Team conflicts were eventually resolved.
- Difficulties with the project were usually
reported quickly to the advisor and liaison.
D:
A "D" indicates substandard work. A "D" effort is
characterized by a negative attitude, little understanding of the
project, and meeting only a few expectations. It is incomplete in a
number of important respects.
- You had more than two unexcused absences from clinic
meetings during the term.
- You were often late for clinic meetings.
- You had at more that two unexcused absences from Tuesday-morning
clinic presentations during the term.
- Nearly all of your weekly status reports were missing or filed late,
or they rarely had significant content.
- You were rarely prepared for clinic meetings.
- The lab notebook provided a poor record of your
participation in the project.
- Your clinic teammates felt that you contributed little, if
anything, to the project.
- You did not contribute significantly to the design of the project.
- You did not contribute significantly to the
implementation of the project.
- You used source control only rarely, so that critical
data was placed at risk.
- Your code was very difficult for your teammates to read.
- You documented little of what you produced.
- You participated in writing and delivering only a few
clinic presentations.
- You made almost no attempt to improve your presentation
skills over the course of the year.
- Only one or two of the clinic deliverables (reports, presentations,
poster, and source code) arrived on time.
- Your midyear and final reports were incomplete,
hard to follow, and missed some important areas.
- Your written clinic deliverables contained many
spelling and grammar errors.
- The customer was not happy with the outcome of
the project.
- In addition, if you were the team leader:
- Each team member had little idea of his or her
responsibilities.
- Team conflicts lingered for long periods without
resolution.
- Difficulties with the project were rarely
reported to the advisor and liaison until it became
impossible to avoid doing so.
F:
An "F" indicates unacceptable work. A failing effort is
characterized by an obstructionist attitude, no understanding of the
project, and meeting almost no expectations. It is incomplete in
nearly every respect.
- You had repeated unexcused absences from clinic
meetings during the term.
- You were consistently late for clinic meetings.
- You had repeated unexcused absences from Tuesday-morning
clinic presentations during the term.
- All of your weekly status reports were filed late,
or they never had useful content.
- You were never prepared for clinic meetings.
- The lab notebook was almost never used and provided no useful
record of the project.
- Your clinic teammates felt that you were a detriment to the
project.
- You did not contribute to the design of the project.
- You did not contribute to the
implementation of the project.
- You did not use source control.
- Your code was nearly impossible to read.
- You documented none of what you produced.
- You participated in writing and delivering almost no
clinic presentations.
- You made no attempt to improve your presentation
skills over the course of the year.
- None of the clinic deliverables (reports, presentations,
poster, and source code) arrived on time.
- Your midyear and final reports were seriously lacking on
content, incoherent, and had major gaps in coverage.
- Your written clinic deliverables were riddled with
spelling and grammar errors.
- The customer was so unhappy with the outcome of
the project that they will probably not return next year.
- In addition, if you were the team leader:
- Each team member had no idea of his or her
responsibilities.
- Team conflicts were not resolved, or were exacerbated
by your poor handling of the situation.
- Difficulties with the project were covered up and
were never reported to the advisor and liaison.
This page is borrowed from Geoff
Kuenning.