A3-Drawing with Turtles

On This Page Overview Program Specifications Extra Credit Grading Criteria (30) What to Turn In Overview There are three parts to this assignment: Review Exercises: First make sure you have completed and turned in the exercises from lesson 3. Then complete the exercises in CodeLab 3. These exercises will help prepare you for the problem-solving program and should be completed first. You can look at solutions if you miss your first attempt. Problem Solving Program: Complete the programming project following the Program Specifications listed below. You may make extra credit additions to this program as outlined in the section on Extra Credit. Tutorial Exercises: Type the program area2.cpp from the textbook on page 120 into a text editor, and then compile and run the program. Submit your working area2.cpp file to Blackboard for grading. Complete the Tutorial Exercises in CodeLab 3 before the specified due date. Refer to the assigned reading for the next lesson to help you understand the problems. Also, you can use the online lecture notes for more information as the notes become available. ^ top Program Specifications Note that you must complete this program either by yourself or by working with one other student of this class following the rules of Pair Programming for Homework Assignments. Write a graphics application that uses the Turtle class to draw the following shapes: Your initials Equilateral triangle Square Pentagon Hexagon The shapes must overlap on the bottom side and produce the same diagram as shown in the sample output below. In addition to the regular polyhedron shapes, you must draw at least three initials of your name. In the sample output I drew my three initials but you must draw your initials and NOT the instructor's initials. If you do not have three names, then you may use "X" for the extra initial. If you are working with another student, then use the first and last initials from both your names (four initials total) with a + sign between them. You may use any functions of the Turtle API to draw the shapes. However, you cannot use any other graphics functions to draw the required shapes or make any changes to the Turtle class. The name of the source code file must be turtletracks.cpp and all your code must be in this file. Be careful of the spelling, including capitalization, as you will lose points for a misspelled name. Remember to include a file comment block and follow all the style rules we have covered so far. Submit your files to Blackboard as explained in the section of this document: What to Turn In. Sample Output of Program ^ top Extra Credit The following are worth extra credit points: Complete the assignment using pair programming. (1 point) Use your imagination and add some creative shapes to your program (NOT a separate file) using a turtle. (0-1 point for each shape; 2 points maximum) Make certain that your README.txt file describes 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. Lesson Exercises 2: All lesson exercises attempted and turned in 1: Some lesson exercises completed and turned in 0: No lesson exercises completed or turned in Program Compilation 4: Source code compiles with no errors or warnings 3: Source code compiles with 1 warning 2: Source code compiles with 2 warnings 1: Source code compiles with 3+ warnings 0: Does not compile or wrong file turned in Program Functionality 10: Demonstrates mastery of 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 Attempts to meet 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 Attempts to meet 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 Attempts to meet 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 Attempts to meet 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 including: Name, date, and program description in file comment block Follows specified format for file comment block Proper use of spaces around operators No tab characters are present in the source code As described in How To Document and Organize C++ Code Correct file name used 3: Code has a minor documentation error 2: Code has some documentation errors 1: Code has many documentation errors 0: No apparent attempt to write documentation comments CodeLab and Other Tutorial Exercises Number CodeLab completed correctly / number exercises * 8 and rounded up to the nearest integer. -1 if the area2.cpp file does not compile -2 if the area2.cpp file is not turned in README.txt File 2: README.txt file submitted following the instructions 1: README.txt file submitted but some information was missing 0: No README.txt file submitted Total possible: 30, plus extra credit ^ top What to Turn In Submit your assignment to Blackboard, in the assignment folder that matches the name of this assignment, following the instructions for submitting homework. Include the following items for grading: README.txt file All the exercise files from Lesson 3 area2.cpp turtletracks.cpp You must submit all the files needed to complete your assignment. Your assignment must work as submitted. You may assume that I have the turtle classes we discussed in class and you do not need to turn in the source code for those classes. ^ top Home | Blackboard | Announcements | Day Schedule | Eve Schedule Course info | Help | FAQ's | HowTo's | Links Last Updated: March 11 2009 @11:55:17