Colorado State University Logo | Spring 21: CS 150 - Culture and Coding (AUCC 3B/GT-AH3) Colorado State University Logo | Spring 21: CS 150 - Culture and Coding (AUCC 3B/GT-AH3)
Spring 21: CS 150 - Culture and Coding (AUCC 3B/GT-AH3)
Computer Science

Lab 07 - Baker Helper


Hello future bakers and artisans of the fine gourmet. You love to throw parties, and what goes better at a party than cake! The problem is that you only have enough flour to bake a limited number of cakes. In this lab, you will write a small program to figure out if you have enough flour to bake the number of cakes needed for the people attending.

You will learn:

  • Use of the final keyword
  • Use of class level variables
  • Complex conditionals
  • Practice declaring methods

Step 0

As always, update your name, email and take a look at the provided code. In this case, we have provided minimal code, that will later help with random tests after you have developed your application. Random testing is always good, as it can sometimes come across unexpected errors. However, before you random test, you will need to put in your own tests.

Step 1 - using final

At the top of your class, you should declare the following variables as static and final

    Initialize it in the same line to 2.3. As such, it should be a double.
    Initialize it to 8. As such, it should be an int.
    Initialize it to -1
    Initialize it to 0
    Initialize it to 1

here an example of declaring the first one to give you an idea:

static final double CUPS_FLOUR_PER_CAKE = 2.3;

These variables are final / constants (meaning you can’t change them) and are available at the class level. This last part means every method in the class has access to them and can be used in every method!

To test this, go to your main, and put in the following code:


Run your program, and it should simply print 2.3 and 8 to the console.

Step 2 - calcNumCakesBaked

For this step you will write the method calcNumCakesBaked. Here are some important things you need to know before writing this method

  • Math.floor
    Math.floor takes in a double value, and returns whole number portion. It is a static method in the Math object. For example, if I put in Math.floor(10.6) it will return 10.0. If I put in Math.floor(10.1) it would also return 10.0. Notice it is returning a double.
  • Casting
    Sometimes you want to convert a double to an int. As there is a loss of precision (the decimals), you have explicitly state you want to do that. As such, you use (int) for example, (int)3.14 returns the int 3 (notice no decimal point).

Write calcNumCakesBaked

Now go to the method section of your file, and write a public static method
called calcNumCakesBakes that returns an int. It takes in a double in the parameter that represents the number of cupsOnHand. For example the method signature could look like this:

public static int calcNumCakesBaked(double cupsOnHand)

Inside the method you need to do the following:

1) It needs to return - as a whole number - the number of possible cakes one can build based on the cups of flour the baker has on hand.

  • cupsOnHand is the amount of flour the baker has
  • CUPS_FLOUR_PER_CAKE tells you how many cups it takes to bake a cake

  • As such, the formula to figure out how many cakes you can bake is:

    cakes = cupsOnHand / CUPS_FLOUR_PER_CAKE

  • You must declare cakes as a variable of type int inside your method.

2) The problem - you have to return an int, rounded down that represents the number of cakes. Use the Math.floor method, and casting to help you with that.

Test calcNumCakesBaked

Always test each method after writing (ideally while writing). So go down to your main method, and put in the following tests:

System.out.println("#### Testing calcNumCakesBaked");

Now double check the output. Is it what you think it should be?

Step 3 - getCakeEnthusiasts

There is a little known fact, that no matter how large of the party, only a max of 19 people want cake. This “fact” is even stranger, the number is actually based the remainder of the total guests at a party divided by 20. So if there are 100 guests, no one wants cake, but if there are 117 guests 17 of them want cake. Ok, we made it up, to give you practice with modulo, but let’s get this party started.

  • % operator - as a quick reminder, the modulo operator returns the remainder of a long division. If you have 17, and you divide by 10, the remainder would be 7. Written in java, that would be 17 % 10. Extra tutorial.

Write getCakeEnthusiasts

The public static method getCakeEnthusiasts returns an int. It also needs the parameter of type int that represents the number of party goers (e.g. partySize) to work. What would that method signature look like?

Using the partySize, simply mod it (%) by 20, and return the answer.

Test getCakeEnthusiasts

We just wrote three to four lines of code, time to test!

Go to your main, and add the following tests:

System.out.println("#### Testing getCakeEnthusiasts ####");

Did the results come out as you expected?

Step 4 - getMessage

It is very common in applications to have a method return a message based on a message ‘type’ passed to it. This allows for easy language integrations, and one place to change the messages. This method follows the same model with three messages. You will pass in an int value (the message type), and return one of three possible messages.

Write getMessage

You will write a public static method called getMessage that returns a String. The method will have a single int parameter that represents the message type. What would the signature look like?

Now you will have the method signature return a message String based on the type, as follows:

  • Sorry. You do not have enough flour to bake a cake.
    Message Type: anything less than 0
  • No left over cake.
    Message Type: equal to 0
  • Yay, left over cake!
    Message Type: anything greater than 0

You will notice there are only three message types: less than 0, 0, or greater than 0. This is fairly common in programming.

Test getMessage

You just wrote three to four lines of code - time to test again! Put the following into your main method, and run the program. Did you get what you expected?

System.out.println("### TESTING getMessage ###");

Step 5 - determineLeftoverCake

This method wants to look at the total number of cakes you can bake and compare it to the number of folks at the party who want cake. Based on the answer, you will return NOT_ENOUGH_FLOUR, EXACT_CAKE, or EXTRA_CAKE.

This method will use:

  • complex logic
    Both || and &&

Write determineLeftoverCake

determineLeftoverCake is a public static method that returns an int value which is either NOT_ENOUGH_FLOUR, EXACT_CAKE, or EXTRA_CAKE. For the method to work, you will need both the number of people, and the number of cakes. Putting that together, our method signature could look like:

 public static int determineLeftoverCake(int cakes, int people) 

The first thing you will want to do is determine the number of pieces of cake. This is done by multiplying the PIECES_PER_CAKE times the number of cakes. We called the answer variable numPiecesCake.

You will then write the following conditions:

  • if cakes is less than or equal to 0 or numPiecesCake is less than people, return NOT_ENOUGH_FLOUR.
  • if people is greater than 0 and the numPiecesCake minus the number of people is 0, return EXACT_CAKE
  • Lastly, it means you have more than enough cake, so return EXTRA_CAKE

Test determineLeftoverCake

You wrote a few more lines of code, it is best to test it. Put the following in your main method

System.out.println("### Testing determineLeftoverCake ###");
System.out.println(determineLeftoverCake(10, 10));
System.out.println(determineLeftoverCake(10, 80));
System.out.println(determineLeftoverCake(0, 9));
System.out.println(determineLeftoverCake(1, 8));

Is it returning what you think it should?

Step 6 - Gluing it together!

Go ahead and uncomment the randomTests method, and the method call to randomTests in main. And run it!

Look through randomTests how is it working to put it all together?

Step 7 - Turning in

Once you have run the program and are satisfied it is working, you may submit for grading. Note that you only get five submission attempts, so make sure it is mostly working before you submit. We will bypass the main method in our tests, running our own tests on each method you wrote.

Computer Science Department

279 Computer Science Building
1100 Centre Avenue
Fort Collins, CO 80523
Phone: (970) 491-5792
Fax: (970) 491-2466

Spring 21: CS 150 - Culture and Coding (AUCC 3B/GT-AH3)

Survey of computer science, formal logic, and computational thinking. Explores the historical, gender, and cultural perspectives on the role of technology in society. Includes learning a basic programming language. Students will be expected to write small programs, and construct written arguments on ways in which technology influences our modern culture. Previous computer science experience not necessary.