A2-Metabolic Energy

On This Page Overview Lab Exercises Project Specifications Extra Credit Grading Criteria (22) What to Turn In Overview The main points of this assignment are to: Develop a conversion algorithm Use variables and arithmetic statements Output numbers and text to the console Document your code following Java standards Check your coding style using CheckStyle For more information on metabolic energy, see: University of South Carolina Compendium of Physical Activities: Metabolic equivalent: article from Wikipedia ^ top Lab Exercises In these exercises you explore the basics of Java programming. Specifications Prepare a single text file named: exercises.txt. Record answers to all the exercises in this file, labeling each answer with the exercise number. Complete self-test exercises 1, 2, 3 and 4 on page 61 of your textbook. Complete self-test exercises 10, 11 and 12 on page 86 of your textbook. When finished, do not forget to upload your file to Blackboard as part of this assignment ^ top Project Specifications Complete programming project 1 from chapter 1 of the textbook (pg. 54-55). Additional Specifications Place all your source code into a single class named: MetabolicEnergy. Be careful of the spelling as you will lose points for a misspelled class name. You must document and organize your code following the requirements in the How To Document and Organize Java Code. Your program must pass CheckStyle configured with the grade_checks.xml for full credit. Note that the CTC has this configured on their computers and that I have instructions for setting up TextPad to use CheckStyle and instructions on Running CheckStyle from the Command Line Do not use any package statements. Do not use any user input statements. Do not round your numbers or format them in any way Hint Make sure to look up the conversion ratio for kilograms to pounds. ^ top Extra Credit The following are worth extra credit points: Install CheckStyle (see TextPad and Running CheckStyle from the Command Line) and use it to check your programming style. Document your installation and usage experience and how you tested the installation in your README.txt file. (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. Lab Exercises 2: All exercises attempted and turned in 1: Some exercises completed and turned in 0: No exercises completed or turned in Program Compilation 4: Source code compiles with no errors or warnings 2: Source code compiles with warnings 0: Does not compile 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 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 Programming Style 4: Code is well-documented Has your name, date, and program description in opening comment block Uses the specified class name Meets all requirements in How To Document and Organize Your Java Code covered to date Passes CheckStyle configured with the grade_checks.xml with no errors or warnings for those items covered to date 3: Code has a minor documentation error 2: Code has some documentation errors 1: Code has many 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: 22, 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 exercises.txt MetabolicEnergy.java 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 after removing all the .class files and running: javac *.java. In addition, your code must work as submitted. ^ top Home | Blackboard | Schedule | Room Policies | Syllabus Help | FAQ's | HowTo's | Links Last Updated: March 21 2010 @13:16:23