papers
| Paper | Title | Publication | Year | Wiki |
|---|---|---|---|---|
| 1 | All I Really Needed to Know about Pair Programming I Learned in Kindergarten |
CACM | 1999 | |
| 2 | UML Basics: The class diagram | IBM | 2004 | Michael Conlon |
| 3 | Gender Differences in Computer Science Students | ACM | 2003 | Trey Briggs |
puzzlers
| Puzzler | Name | Files | Rank List | Links | Wiki |
|---|---|---|---|---|---|
| 1 | The 3n+1 Problem |
3n+1.c++ 3n+1.in 3n+1.out harshd / cs371ppz1 |
100 |
Collatz Problem Collatz Conjecture |
|
| 2 | Jolly Jumpers |
JollyJumpers.c++ harshd / cs371ppz2 |
10038 | Ryan Beberwyck | |
| 3 | Bicoloring |
Bicoloring.c++ harshd / cs371ppz3 |
10004 |
Bicolorable Graph Bipartite Graph |
Richard Kean |
| 4 | Australian Voting |
AustralianVoting.c++ harshd / cs371ppz4 |
10142 |
Arrow's Theorem Preferential Voting |
|
| 5 |
Self.c++ Self.out |
Kenneth Logan | |||
| UVa | |||||
| UVa Live | |||||
Puzzlers will be posted two weeks before they're due, and are always due on a Sun at 11:59pm.
Puzzlers are worth 15 points: 5 points for correctness (no partial credit), 5 points for acceptance by the UVa online judge without a presentation error (no partial credit), 5 points for documentation. The first 5 points must be earned for the rest of the points to be available.
A puzzler that does not compile, link, run, and produce the correct output from the provided input will count as zero.
To get credit for a puzzler, you must post the following:
- execution time
- rank
- test suite (as an attachment)
to the *** Consensus on Final Results *** topic on the class discussion board in Blackboard.
Puzzlers must compile, link, and run with GCC in the Intel Lab or Taylor Lab, and must be submitted to Turnin.
Puzzlers must be done individually.
For every day that a puzzler is late, one third of the points will be lost, so that in three days it will be worth zero. Corrupt or incomplete submissions will count as one day late.
Puzzlers will be compared using Moss. You may share design ideas with your fellow students. You may not share code in any way with your fellow students.
The grader will not provide the solution to the puzzler. The grader will grade and post the grade of the puzzler within one week. The grade can only be disputed within the following one week. All grade disputes must be made in writing by e-mail to the grader with supporting evidence or arguments.
projects
| Project | Name | Files | Wiki |
|---|---|---|---|
| 1 | Date |
Date.zip harshd / cs371ppj1 |
|
| 2 | Allocator |
Allocator.zip harshd / cs371ppj2 |
|
| 3 | Graph |
Graph.zip harshd / cs371ppj3 |
|
| 4 | Darwin |
Darwin.zip harshd / cs371ppj4 |
|
| 5 | Life |
Life.zip harshd / cs371ppj5 |
Projects will be posted two weeks before they're due, and are always due on a Sun at 11:59pm.
Projects are worth 45 points: 20 points for correctness (no partial credit), 10 points for additional correctness, 5 points for testing, 5 points for design, and 5 points for documentation. The first 20 points must be earned for the rest of the points to be available.
A project that does not compile, link, run, and produce the correct output from the provided input within the specification will count as zero.
To get credit for a project, you must post the following:
- results (as an attachment)
- test suite (as an attachment)
to the *** Consensus on Final Results *** topic on the class discussion board in Blackboard.
Projects must compile, link, and run with GCC in the Intel Lab or Taylor Lab, and must be submitted to Turnin.
Projects must be done in pairs using a technique called pair programming. One solution will be turned in for the pair.
For every day that a project is late, one third of the points will be lost, so that in three days it will be worth zero. Corrupt or incomplete submissions will count as one day late.
Projects will be compared using Moss. You may share design ideas with your fellow students. You may not share code in any way with your fellow students.
The grader will not provide the solution to the project. The grader will grade, comment, return, and post the grade of the project within one week. The grade can only be disputed within the following one week. All grade disputes must be made in writing by e-mail to the grader with supporting evidence or arguments.
html & css validators
