edaena/edaena-cs371p-grades

Automatically exported from code.google.com/p/edaena-cs371p-grades

edaena-cs371p-grades's Issues

Alignment Issue

Trying to align the table to account for small set of scores as well as large 
set of scores

Original issue reported on code.google.com by [email protected] on 9 Mar 2012 at 9:04

Implementation

Use assert to check pre-conditions, post-conditions, argument validity,
return-value validity, and invariants.
Worry about this last, but your program should run as fast as possible
and use as little memory as possible. 

Original issue reported on code.google.com by [email protected] on 6 Mar 2012 at 11:32

Letter grade should reflect rounded total, not actual total

ID    Unique TA       Scores Total   Z    G
----- ------ -------- ------ ------- ---- -
A3456  51050 Mao           0   0.00% 0.00 F
A5432  51005 Oursland  69999  70.00% 0.00 D
A9876  51050 Mao       70000  70.00% 0.00 C
A5678  51005 Oursland  79999  80.00% 0.00 C

Original issue reported on code.google.com by [email protected] on 9 Mar 2012 at 9:12

Design

The UML diagram. 

Original issue reported on code.google.com by [email protected] on 6 Mar 2012 at 11:33

Unit Tests

The grader will set up a public Git repository at Assembla:

    Oliver Jensen
    https://www.assembla.com/code/ojensen-cs371p-grades/git/nodes/

Write unit tests before your write the code.
When you encounter a bug, write a unit test that fails,
fix the bug, and confirm that the unit test passes.
Write at least 3 unit tests for every function.
Tests corner cases and failure cases.
Name tests logically.
Push and pull the unit tests to and from the grader's repository.
Prepend <cs-username>- to the file names at Assembla.
Reach consensus on the unit tests.
Use Valgrind. 

Original issue reported on code.google.com by [email protected] on 6 Mar 2012 at 11:31

Student can't access Course data

Grades.h:107: error: invalid use of nonstatic data member 
‘Course::total_events’

Trying to access elements in Course, the class that contains Student.

Original issue reported on code.google.com by [email protected] on 7 Mar 2012 at 10:37

Acceptance Tests

Write acceptance tests before your write the code.
When you encounter a bug, write an acceptance test that fails,
fix the bug, and confirm that the acceptance test passes.
Write an auxiliary program to randomly generate acceptance tests.
Create at least 100 acceptance tests of up to
1000 records, separated by a blank line.
Tests corner cases and failure cases.
Push and pull the acceptance tests to and from the grader's repository.
Prepend <cs-username>- to the file names at Assembla.
Reach consensus on the acceptance tests.
Use Valgrind. 

Original issue reported on code.google.com by [email protected] on 6 Mar 2012 at 11:32

round exists?!

We tried writing a round function, but when compiling found that one exists but 
doesn't produce what we want (round to 2 decimals)

In file included from RunGrades.c++:37:
Grades.h: In function ‘double round(double)’:
Grades.h:26: error: declaration of ‘double round(double)’ throws different 
exceptions
/usr/include/bits/mathcalls.h:310: error: from previous declaration ‘double 
round(double) throw ()’

Original issue reported on code.google.com by [email protected] on 9 Mar 2012 at 9:47

Rounded output causes issues with letter grade and mean

Showing a rounded scored causes mean to look off, and also causes z-score to be 
skewed since z-score doesn't reflect what is being displayed.

Original issue reported on code.google.com by [email protected] on 20 Mar 2012 at 8:56

neg zscore messes up output

negative zscore skewed the table a little bit

Original issue reported on code.google.com by [email protected] on 9 Mar 2012 at 10:07

Seg fault with new line at end of input

Seg fault occurs when new line is at end of input.
Removing the new line temporarily fixes issue.

Original issue reported on code.google.com by [email protected] on 21 Mar 2012 at 6:06

Issue Tracker and Wiki

Set up a public issue tracker and wiki at Google Project Hosting:

    http://code.google.com/p/<cs-username>-cs371p-grades/

Issue Tracker
Track the 8 deliverables on this page.
Track bugs and features, both open and closed.
Categorize, prioritize, and describe each issue adequately.
Track at least 5 more issues in addition to the 8 issues on this page.
Wiki
Describe the design of the algorithm.
Write at least 30 lines of description.
Use bullet points where appropriate.
In general, write grammatically correct, typo free, clear English.
Have someone else read what you wrote and critique it.
Write neatly. 

Original issue reported on code.google.com by [email protected] on 6 Mar 2012 at 11:30

Google Form

Fill out the grader's Google form:

    Oliver Jensen

Original issue reported on code.google.com by [email protected] on 6 Mar 2012 at 11:33

Documentation

Use Doxygen to document the interfaces.
The above documentation only needs to be generated from Grades.h.
Comment each function meaningfully.
Use comments only if you need to explain the why of a particular implementation.
Choose a coding convention and be consistent.
Use good variable names.
Write readable code with good indentation, blank lines, and blank spaces. 

Original issue reported on code.google.com by [email protected] on 6 Mar 2012 at 11:33

seg fault

tried fixing comparison issue by changing int to size_t where appropriate, but 
causes seg fault

Original issue reported on code.google.com by [email protected] on 21 Mar 2012 at 11:06

Remove print statements from TestGrades.c++

Currently, TestGrades.c++ has print statements, it prints reports etc. These 
should be removed and replaced with assertions of the outputstream.

Original issue reported on code.google.com by [email protected] on 20 Mar 2012 at 10:51

sort function isn't working

sorting not working

ID    Unique TA       Scores Total   Z    G
----- ------ -------- ------ ------- ---- -
A3456  51050 Mao           0   0.00% 0.00 F
A5432  51005 Oursland  69999  70.00% 0.00 D
A9876  51050 Mao       70000  70.00% 0.00 C
A5678  51005 Oursland  79999  80.00% 0.00 C

Original issue reported on code.google.com by [email protected] on 9 Mar 2012 at 9:13

Private Git Repository

Set up a private Git repository at Assembla:

    https://www.assembla.com/code/<cs-username>-cs371p-grades/git/nodes/

Invite the grader to your repository:

    Alon Farchy (afarchy)
    Oliver Jensen (ojensen5115)

Commit at least 5 times.
Commit once for each bug or feature.
If you cannot describe your changes in a sentence,
you are not committing often enough.
Write meaningful commit messages and
identify the corresponding issue in the issue tracker.
Create a log of the commits.
Push frequently.
It is your responsibility to protect your code
from the rest of the students in the class.
If your code gets out,
you are as guilty as the recipient of academic dishonesty. 

Original issue reported on code.google.com by [email protected] on 6 Mar 2012 at 11:31