Assignment 1

Part A: (ungraded) If you haven't yet, do the following on-line jGRASP tutorials: overview, installation, getting started, and the debugger at http://www.jgrasp.org. If you want to use your own computer for assignments, install the sun JDK and (optionally) jGRASP on your machine. Directions are on the main course webpage.

Part B: (ungraded) If you haven't yet, read Chapters 1-3. Look at the review questions for each chapter. Recommended exercises to do on your own as practice for the midterm: 1-13, 2-5, 2-6, 3-6, 3-10, 3-11, 3-16. Write and run a JAVA program to check your answers. You are permitted to work together on any ungraded work for the course.

Part C: Complete the survey from part C of assignment #0 if you haven't yet.

Part D: [8 points] Read through programming assignment 1B and do the first phase: problem analysis. Write up two sample runs that show the complete user interface: all the input and output as it would appear if you were running the actual program you will write (similar to our GPA example). One sample run must use the input values that are given in the problem description.

For the other sample run, make up your own data that differs enough to demonstrate another case the program must be able to handle. Do the calculations by hand or with a calculator to figure out what the correct output will be. You must submit your sample runs on Blackboard as assignment w1 in a plain text file (not a Word document) named w1.txt. We will not collect a printout. A solution will be distributed via email after the deadline for help in writing and testing your actual program next Wednesday - absolutely no late submissions will be accepted.

Before graphical user interfaces and icons were common-place, we used plain character sequences to create "pictures" on computers, called "ASCII graphics". Write an application program that displays a snowflake of your design by printing lines of characters in a pattern that resembles one. Use String variables to hold any parts of the pattern that are repeated. For example, I might have my program display the following (somewhat lame) figure. Try to incorporate your initials into it somehow. Everyone's snowflake should be unique. There is no input for this program! Name your program pg1a.java and remember to submit it on Blackboard.

Suppose that you are pursuing a regular fitness regimen and want to plan and track your exercising based on calories burned. In this first version, we will restrict our data to the following types of exercise, and average numbers of calories burned/hour. (These are fictional values based on various websites; actual calories burned depends on your weight and the speed at which you do them.)

This program will deal with planning a weekly regimen, taking into account how many calories you want to burn in one week, and how you would like to distribute your exercise among the activities above. Therefore the program user must input the total calories to burn in one week, and the percentage of calories for each of the activities above. For now we will expect the user to enter percentage data that adds up to exactly 100% for the week. Based on this data, your program must calculate and output how many calories must be burned per activity, and how many hours must be spent doing each activity in order to reach those goals. Lastly, your program should calculate and display the total and the average amount of time you will spend per activity. When displaying these values, give the time as (whole) hours (rounded down) and minutes (rounded up).

Exercise	Calories/Hour
Running	700
Biking	650
Weight Lifting	300
Dancing	400

Make sure your program is very user friendly. Include detailed prompts so that the user knows exactly what type of data to input, and nice descriptions and formats for the output. You should not use any Java constructs that we haven't covered in class (such as loops). Name your program file pg1b.java and be sure to follow all the assignment details below. Don't forget to submit two sample runs as instructed in part D of the warm-up assignment #1!

Development Hints: Here is an incremental coding approach to solving this problem. At each stage make sure the program compiles and runs correctly. If not, fix it before going to the next stage.

General assignment requirements, style and submission details:

Reflections: Reflect briefly on each program you write, as a comment at either the beginning or end of each main file. Comment on things like: how useful was the warm-up exercise (if any)? how hard was the program and why? what did you learn from it? where did you need help? how long did it take to complete? what was the best part of the assignment and why? how would you redesign this assignment if you were the teacher? You should have a paragraph of well-written (properly formed English) reflections for each program. These reflections are part of your assignment grades.
Naming: You are required to name your main files and program classes pg1a.java, pg1b.java, pg2a.java, etc. (changing the number and part as appropriate each week). Use all lower-case letters. Any exceptions to this will be detailed in the assignment descriptions.
Identification: You must include a header comment with your name, this course number (600.107), the date, the assignment number, your phone number, Blackboard login, and preferred email address in every java file you write.
Compilation: Source code (*.java) must compile in standard Java; however, you must not use Strings in switch cases. Remember: you will receive NO credit for programs that do not compile. Use incremental coding to insure that you always have a working program, even though it might be incomplete.
Electronic Submission: Submit an electronic copy of all graded assignment parts via Blackboard. You may submit on Blackboard multiple times for any assignment - we will only grade the last (most recent) submission unless you request otherwise. Warm-ups must be submitted as *.txt or *.pdf files only.
Deadlines: If you miss the due deadline for a warm-up part, it will not be accepted and you will receive no credit because solutions are posted once the deadline has passed. On the other hand, there is a 1/2 hour grace period for program submission. If you submit in this timeframe, you will get a standard 5 point late penalty, even if only 1 minute late. After the grace period, programs will not be accepted and you will receive no credit.
Printouts: Submit a printout of all your original program source files (Java code, not the program output) for each assignment part when you come to class on the due date. You must staple together all the printouts for each assignment. Usually we do not collect printouts for the warm-ups.
Style: Always remember to use good programming style, including indentation, spacing and descriptive variable names (see Appendix A). You should include comments to describe what is going on in your program.

600.107 Introduction to Programming in Java Spring 2013

600.107 Introduction to Programming in Java
Spring 2013