Project 5: Matrix Abstract Data Type

Due: Tuesday 12 November 2007

Description (Draft)

The Code

In this project you are asked to implement several methods in a file Matrix.java, which will contain a class that represents a matrix. The final Matrix objects should be able to perform the following nine operations: add, subtract, (matrix and scalar) multiply, transpose, identity matrix, trace, and random matrix, and a method that converts a matrix to an array. In this project, you will need to rely on your knowledge of loops and build on your understanding of arrays, constructors, method overloading, exception handling, and static and non-static methods. In this project you will decide on the underlying implementation. I will, of course, review your code. But unlike before, I will also subject your Matrix class to a series of correctness tests. To pass the correctness tests, your implementation need only follow the specifications described below.

First, we need to know how to create new Matrix objects. Here is a list of constructors that you need to implement:

The methods that you need to implement are:

Be sure to comment your code fully and prefix your Matrix class file with comments that include your name, course title, date, and the project number and title. For example:

// Joshua Reyes
// CSIT 114
// 12 November 2007
// Project 5: ADT Matrix

The Write-up

Once you have implemented the method above, write longer essay detailing your experience programming in a plain text file called memo.txt. (Do not use an editor like MS Word.) Remember that your analysis counts for the majority of your grade. Please write in clear, proper English. As above, be sure to include your name, class, and project title.

Here are some questions to keep in mind:

If you worked with others, explain what each person contributed to your project. Cite others appropriately. Even if you worked with others, the code you pass in ought to be your own.

Turning the Project In

Use a secure FTP client to create a subdirectory of csit114 called project4. Upload your Picture.java (and Pixel.java, SimplePicture.java if necessary) and memo.txt to that directory by Tuesday, 16 October 2007. Please make sure that your file names are spelled correctly. It is frustrating for me to have to search for your files by hand.

Rubric

RequirementAdvancedProficientNeeds ImprovementMaximum Points
Picture.java
Comments and Coding Style Well commented. Code conforms to naming and style conventions. Mostly commented. Code mostly conforms to naming and style conventions. Few or no comments. Code does not conform to conventions. 25
Compiles Compiles without error. Compiles without error. Does not compile. 6
renderEffects() Is named correctly, renders four image processing filters, at least two of which are listed above, and calls at least four helper method. Is named correctly, renders four image processing filters, and calls at least four helper methods. Is neither named correctly, renders less than four processing filters, and calls fewer than four helper methods. 14
Code Structure Modular design: most repeated patterns in code are stored in individual helper methods or executed using loop constructs. Semi-modular design: Blocks of code that perform a different tasks are logically and physically separated. There is heavy evidence of copying and pasting throughout the code. 20
memo.txt
Analysis Provides clear and complete exposition of the design and implementation process; addresses all or most of the questions above. Provides a mostly clear and nearly complete exposition of the design and implementation process. Provides an unclear and incomplete exposition of the design and implementation process. 35
Grammar and Style Well written. No obvious grammar or punctuation errors. A pleasure to read. A few grammatical errors such as punctuation or spelling, although most errors do not interfere with the overall message or the substance of the text. Many grammatical errors including punctuation, spelling or usage problems. 15
Organization Written work is neat and well organized. Written work mostly organized. Written work messy and disorganized. 10
Total 125