Scribd
Upload
31 views1 page

Assignment2 4

The document outlines the requirements for a programming assignment to create a SparseMatrix class. It lists 5 parts that must be submitted: 1) the code for the SparseMatrix class, 2) a description of the class, 3) an analysis of time and space complexities, 4) a description of testing completed, and 5) contributions of team members. It also provides instructions on printing and submitting the assignment for review. Quality criteria include submitting all parts, code that compiles and passes all tests, a sound complexity analysis, and professionally printed materials.

Uploaded by

keteg87703
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
31 views1 page

Assignment2 4

The document outlines the requirements for a programming assignment to create a SparseMatrix class. It lists 5 parts that must be submitted: 1) the code for the SparseMatrix class, 2) a description of the class, 3) an analysis of time and space complexities, 4) a description of testing completed, and 5) contributions of team members. It also provides instructions on printing and submitting the assignment for review. Quality criteria include submitting all parts, code that compiles and passes all tests, a sound complexity analysis, and professionally printed materials.

Uploaded by

keteg87703
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

create). Put this in a plain text file, called description.txt.

3) Your brief argument about what the time and space complexities are for each operation.
Put this in a plain text file, called complexities.txt.
4) A brief description of which test cases (from those we provided) you have tested your
code on; name them explicitly. Did all of your tests give results as expected (as in the test
results we provided)? Did you encounter any unusual (special) cases and if so how did
you deal with them? How would you deal with the special case of a matrix of all zeros –
what is a good way to store it and does that affect time and space complexities of future
operations on such a matrix? Put this description in a plain text file, called
testing.txt.
5) A brief description of who (of the two partners in the team) did what part of the
assignment: the different parts of the code, the testing, the complexity arguments, and
anything else you did. Be sure to include your names and emails here. You are
encouraged to work on all parts together, and if so, indicate that this is indeed the case. If,
however, you decided to split the work, we also need to know that, as well as how you did
it. Put this description in a plain text file, called contributions.txt.

In addition, print and bring to class on the due date:


1) The code of the SparseMatrix class only. (Please, do not print header files, packages, or test
modules/classes!)
2) The description text files 2-5 (described above). To save paper and trees, please merge
them together into one file and then print.
Do not forget to write the names of both partners on the printed sheet you submit.

Printing guidelines. Double-sided printing and condensed code printing (i.e., double-sided at 2
pages of code per side) is highly encouraged! Modern printers, including many of those available
at UW facilities, can do that. Ask the lab person for assistance if you are unsure how to do that.

Where to submit. Instructions on where to electronically submit your assignment will appear on
the course web page and will be announced on the mailing list.

Quality criteria.
For full credit, you need to meet the following quality criteria:
1) Your submission needs to contain all parts described in the previous section.
2) Your code needs to:
- Compile and run without errors or warnings. (We will follow the instructions you will
have provided us with, so those need to be accurate.)
- Give the same results on the test cases as the test results provided by us (unless you
found an error in our test results).
- Contain comments, making it easier for a human to understand what you have done.
3) Your argumentation about the time and space complexities of all operations needs to be
sound. Brevity is encouraged but not at the expense of clarity or soundness.
4) Your printed materials need to look professional (i.e., be printed and stapled together
rather than hand-written and loose).

Our advice.
Be sure to start early, as this first programming assignment may prove more challenging that you
expect.

Good luck!

You might also like