A3: Methodical Improvement

On This Page Overview Programming Project Specifications Project Extra Credit Lab Specifications Grading Criteria (22) What to Turn In Overview Complete the following for full credit on the assignment: Lesson Exercises Make sure you have completed the exercises from lesson 3. Programming Project Follow the Programming Project Specifications to develop your own unique scenario. Lab exercises Complete the lab by following the Lab Specifications listed below. Zip your lesson, project and lab files and submit the zipped archive file to Blackboard as explained in the section of this document: What to Turn In. ^ top Programming Project Specifications Update your project from the last assignment by completing the following specifications. Remember that this is an original project with the specifications applied to something other than Bug World or Crab World. To your project from the last assignment, add random movement to at least one actor using the Greenfoot getRandomNumber() method. If you prefer, you may start a new scenario as long as the scenario meets all the specifications of the last assignment (like original characters) and this assignment. Use at least two relational operators in your scenario. Develop an interaction between at least two types of objects in your scenario, calling both of these methods covered in the lesson: canSee() eat() Organize your scenario code by writing and calling at least five (5) new methods besides act(). Add keyboard controls for the player or user of your scenario by using the Greenfoot isKeyDown() method for at least one actor. Play at least two sounds in your scenario using the Greenfoot playSound() method. Please do not use large (> 1 mB)sound files. Call the Greenfoot stop() method when your scenario ends. Update the README.TXT file for your project to fill in all the information like your name, project title and version or date, as well as providing the current status. Submit a zip file (with all source code) of your original project to Blackboard as explained in the section of this document: What to Turn In. ^ top Project Extra Credit Adding the following are worth extra credit points: Use the constructor of your world subclass in your scenario to construct the actors and set up your scenario as discussed in chapter 4 of the text. (2 points) Make certain that your README.TXT file describes any extra credit attempted. ^ top Lab Specifications Scan the textbook chapter 4 to get an overview of the material. Complete the in-chapter exercises that are listed throughout chapter 4. You can download the starting files from: Book scenarios. Follow the exercise steps exactly and read the textbook as you progress through the chapter to enhance your understanding. Upload the completed scenario files to Blackboard as explained in the section of this document: What to Turn In. ^ 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 syllabus 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 Lab Exercises 4: Demonstrates mastery of the lab exercise: Applies concepts from the lessons appropriately Follows the steps exactly Exercises perform correctly 3: Has all the major functionality expected: Demonstrates many techniques from the lesson May deviate from the specified steps in some way Implementation seems more complicated than necessary. 2: Has much of the functionality expected: Demonstrates some techniques from the lesson Deviates from the specified steps in some way Implementation seems excessively complicated. 1: Serious functional problems but shows some effort and understanding: Follows at least 1/2 of the of the specified steps Has a major error (detected by the browser) or many minor errors Demonstrates few techniques from the lesson 0: Not turned in Program Compilation 4: Source code compiles with no errors or warnings 2: Source code compiles with warnings 0: Does not compile or wrong file turned in Functionality 10: Demonstrates mastery of the assignment Has extra features or demonstrates techniques beyond the assignment Applies concepts from the lesson(s) appropriately Meets all specifications (see above) with particularly elegant solutions No errors encountered during operation 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 or no specifications met README.TXT File for Project 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: 22, plus extra credit ^ top What to Turn In Follow these instructions to turn in your assignment: On your computer, create a folder for the lesson exercises named "lesson" and place all the exercise files from Lesson 3 into this folder. Create another folder named "project" and place your complete programming project into this folder. Create yet another folder named "lab" and place all the lab files (the completed scenario) into this folder. Create a zip file containing all three folders, and submit the zip file to the assignment slot of Blackboard that matches the name of this assignment. Please do not put any spaces or special characters like #, : or $ in zip file or folder names. Your assignment must work as submitted. Remember to test and double check your files before submitting them. If you make a mistake, you can resubmit up to the deadline. If you have problems uploading to Blackboard, see: How do I upload my assignment files?. ^ top Home | Blackboard | Schedule | Syllabus | Room Policies Help | FAQ's | HowTo's | Links Last Updated: April 21 2012 @23:23:47