FRQ skill buckets (methods, arrays, classes) - Computer Science A AP Study Notes

Think of programming like baking a cake. You have a big recipe, but it's broken down into smaller, easier steps like 'mix dry ingredients' or 'bake for 30 minutes'. In computer science, we use special tools to break down big problems into smaller, manageable pieces.

• Methods (Your Mini-Recipes): Imagine your cake recipe has a step called 'Make the Frosting'. Instead of writing all the frosting steps every time you need frosting, you just say 'Make the Frosting'. A method is like a mini-recipe or a set of instructions that does one specific job. You can call (or use) this mini-recipe whenever you need that job done, saving you from writing the same instructions over and over.
• Arrays (Your Egg Carton): When you bake, you often need a bunch of the same thing, like a dozen eggs. You don't just put them all over the counter; you put them neatly in an egg carton. An array is like an egg carton for your computer. It's a special box that holds a list of similar items (like numbers, words, or even other objects) in an organized way, each with its own numbered spot.
• Classes (Your Cake Blueprint): Before you bake a cake, you have a mental picture or a recipe that describes what a cake is: it has layers, frosting, flavor, etc. A class is like a blueprint or a detailed description for creating something complex. It tells the computer what kind of information an object will hold (like a cake's flavor or size) and what actions it can perform (like 'get eaten' or 'be decorated'). You use this blueprint to make actual cakes (which we call objects).

Let's imagine you're building a video game where players collect different types of fruit.

1. The Fruit Class (The Blueprint): First, you'd create a class called Fruit. This class is like the blueprint for any fruit in your game. It would describe what all fruits have in common: a name (like "Apple" or "Banana"), a color (like "red" or "yellow"), and a pointsValue (how many points the player gets for collecting it). It might also have a method (a mini-recipe) called displayInfo() that, when called, prints out the fruit's name and points value.

2. Creating Fruit Objects (Actual Fruits): Using your Fruit blueprint, you can now create actual fruits in your game. You might make apple1 = new Fruit("Apple", "red", 10); and banana1 = new Fruit("Banana", "yellow", 5);. These apple1 and banana1 are objects – actual instances of your Fruit class.

3. The collectFruit() Method (The Action): You'd probably have another method in your game, maybe called collectFruit(Fruit collected), which takes a Fruit object. This method's job is to add the collected fruit's pointsValue to the player's score and then remove the fruit from the game world. It's a reusable action.

4. The inventory Array (The Storage): As the player collects fruits, you need a way to store them. You could use an array called playerInventory to hold all the Fruit objects the player has collected. So, playerInventory might look like [apple1, banana1, apple2]. Each fruit is stored in its own numbered slot, easy to access later.