A10: Shape Control Redux

On This Page Overview Specifications Test Cases Extra Credit Grading Criteria (20) What to Turn In Overview During this assignment, you will: Extend your shape painter to allow any number of shapes. Use a linked list and iterators. ^ top Operation This assignment operates the same as assignment 8 except the user can enter any number of shapes. ^ top Specifications Using your shape painter application that you developed earlier, change your application to allow the user to enter any number of shapes. If you had points deducted for your assignment 8 solution, you may either correct your solution to meet assignment 8 specifications or use the instructor's solution. Store the shapes drawn in a LinkedList class so that resizing windows will not erase the drawing. You must use the final version of the LinkedList class that we covered in lesson 11. You will need to modify the data type stored in the linked list to operate with your MyShapes hierarchy. Do NOT change the name of the LinkedList class. In addition, you must use the ListIter class to iterate through the linked list. Make an executable JAR of your program containing all the files described in the section of this document: What to Turn In. Do not forget to document the LinkedList class. Hints To access the inner class, you need to include the outer class name. For example: LinkedList.ListIter lit = shapes.iterator(); ^ top Extra Credit The following are worth extra credit points: Add a method to the linked list class named addToEnd() that adds items to the end of the list. (1 point) Make certain that your README.txt file lists any extra credit attempted. ^ top Grading Criteria The instructor will evaluate your assignment using the following criteria. Each criteria represents a specific achievement of your assignment and has a scoring guide. The scoring guide explains the possible scores you can receive. Some scoring guides have a list of indicators. These indicators are a sign of meeting, or a symptom of not meeting, the specific criterion. Note that a single indicator may not always be reliable or appropriate in a given context. However, as a group, they show the condition of meeting the criterion. For information on grading policies, including interpretation of scores, see the course information page. Program Compilation 4: Source code compiles with no errors or warnings 0: Does not compile Functionality 10: Demonstrates mastery of the assignment Has extra features or demonstrates techniques beyond the assignment Applies concepts from the lessons appropriately Meets all specifications (see above) with particularly elegant solutions Runs to completion with no abnormal error conditions Generates correct output given correct input Behaves in a reasonable way in response to incorrect data 8: Has all the functionality expected of the assignment Demonstrates many techniques from the lesson Meets all specifications (see above) Implementation seems more complicated than necessary. May have one minor error 6: Has most of the functionality expected of the assignment Demonstrates some techniques from the lesson Meets all but one of the specifications (see above) Implementation seems excessively complicated. May have 2-3 minor errors 4: Has some of the functionality expected of the assignment Demonstrates some techniques from the lesson Meets at least 1/2 of the specifications (see above) Implementation seems excessively complicated. May have more than 3 minor errors 2: Serious functional problems but shows some effort and understanding Meets less than 1/2 of the of the specifications (see above) Has a major error or many minor errors Implementation seems very convoluted Demonstrates few techniques from the lesson 0: Does not execute Program Style 4: Code is well-documented As described in How To Document and Organize Java Code 3: Code has minor documentation errors Has 1 documentation error 2: Code has some documentation errors Has 2-3 documentation errors 1: Code has many documentation errors Has more than 3 documentation errors 0: No apparent attempt to document code README.txt File 2: README.txt file submitted with specified information included 1: README.txt submitted but some information was not included 0: No README.txt submitted Maximum Score: 20, plus extra credit ^ top What to Turn In Submit your assignment following the instructions for homework. Include the following items for grading: README.txt file All of your source code (i.e. .java files) Any other source code needed to make your program function You must submit all the files needed for your assignment to compile and work correctly. Do not assume that the instructors has any files. Also, do not turn in files that are not part of your assignment, especially ones that do not compile. Your assignment must compile and work as submitted. ^ top Home | WebCT | Announcements | Schedule | Room Policies | Course Info Help | FAQ's | HowTo's | Links Last Updated: November 24 2006 @17:07:23