CSC 200 Undergraduate Problem Seminar: Assignments

First, internalize the problem...
-
The assignments will be posted here after the day's class,
along with the due date.
Assignments are due at the beginning of class on the due date.
In general, no credit will be allowed for for late assignments.
Turn what you have in in for partial credit.
-
For any assignment, I expect a well organized
report-style writeup that describes in detail what you did, why you did it,
and what the results were. This includes negative results.
Scratch work and computer code, if requested should be appended to the main
writeup with appropriate pointers.
-
Attribute ANY work that is not your own, including software off the
web, text cribbed from other sources, etc.
You are encouraged to look for resources, but not to the extent that
it negates the point of the assignment.
This is sometimes a fine line, especially in programming assignments.
I will try to be specific as to what I expect you to write
as a minimum. If in doubt, ask.
In any case, use of UN-attributed material is plagiarism, and a violation
of the University's academic honesty policy.
Plagiarism is taken VERY seriously in this department. DON'T DO IT.
If in doubt, reference.
-
Specifically, text taken from web pages, even a single sentence,
is plagiarism. Text paraphrased from web pages is plagiarism.
Sentences from web pages cut up into phrases and re-arranged are
plagiarism.
If you want to avoid possible problems, my suggestion is
never write while looking at text. Generate everything from your
own understanding of the subject.
-
Use of unattributed text in any written assignment will result in
zero credit for that assignment.
Text that comes from an outside source should appear in quotes.
Too much use of quoted material will tend to reduce your credit
for an assignment, as the point of written assignments is to
convey your understanding of a subject.
-
In general, you should consider written assignments for this course
to be public documents - just as published research papers are public
documents. As such I may place them in a forum where they may be
scrutinized by your colleagues for accuracy, clarity, and for
unattributed material.
-
You are encouraged to discuss general techniques and specific approaches
to general problems with your fellow students, or anyone else.
Unless specifically directed in an assignment, however, you are not to
share code you have written, or your written solutions to specific
problems.
Thursday, January 13, 2005
Tuesday, January 18, 2005
- Class activity: ITRUG Micro-proposal 2-minute ads.
Notes and evaluation.
- Assignment:
Voting systems
Due Thursday, January 20, 2000 (That's right, next class).
Thursday, January 20, 2005
Tuesday, January 25, 2005
- Class activity: Presentation of unprecedented project cost estimates.
- Assignment:
Digital millenium trial: Research
Due Tuesday, February 1, 2005.
Thursday, January 27, 2005
- Class activity: Digital millennium trial, planning and preparation.
- Assignment:
Digital millenium trial:
Planning (prosecution and defense);
Study of law and potential modification (jury)
Tuesday, February 1, 2005
- Class activity: Digital millennium trial.
- Assignment:
Preparation of group case summaries (prosecution, defense);
Preparation of DMCA revision recommendations (jury group).
Due Thursday, February 3, 2005.
Thursday, February 3, 2005
- Class activity: Digital millenium trial, Jury deliberation.
Tuesday, February 8, 2005
- Class activity: Introduction of semester projects and teams.
- Class activity: Team puzzle assembly contest.
- Assignment: Impossible projects,
individual brainstorming.
Due Thursday, February 10, 2003.
Thursday, February 10, 2005
- Class activity: Project group brainstorm sessions, presentation of
initial thoughts on projects.
- Assignment: Each group is to research the state of the art on the topic
of their project, and prepare a 5-10 page joint survey paper on the
relevant technology. This will be presented in class next Tuesday.
Due Tuesday, February 15, 2005.
Tuesday, February 15, 2005
- Class activity: Presentation and discussion of project
state-of-the-art survey results.
- Assignment: Each group is to prepare a (preliminary but detailed)
system design and research plan.
Both the design and plan should consist of well defined and individually
testable pieces that can be
implemented in less than a week.
Prepare a document showing schedule, dependencies, and potential
contributers for each piece, and be prepared to present the plan to
the class next Tuesday (Feb 22).
Thursday, February 17, 2005
Tuesday, February 22, 2005
- Class activity: Presentation and discussion of project
system design and research plan.
- Assignment: First week's activities as per group plan.
Presentation and discussion on Tuesday, March 1.
Also due, (every week) writeup of weekly results,
and updated plan.
Thursday, February 24, 2005
Tuesday, March 1, 2005
- Class activity: Presentation and discussion of week 1 results,
and updated system design and research plan.
- Assignment: Week 2 activities as per group plan.
Presentation discussion, and writeup due Tuesday March 15 (after break)
Thursday, March 3, 2005
Tuesday, March 15, 2005
- Class activity: Presentation and discussion of week 2 results,
and updated system design and research plan.
- Assignment: Week 3 activities as per group plan.
Presentation discussion, and writeup due Tuesday March 22.
Back to CSC 200 main page