You know how to make objects, properties, methods, variables, and functions. There are practically no limits as to how you can combine them. Programming is not an assembly line job where you are given something, you perform the same procedure to it you do every day, and then you have a set result. Programming is problem solving. The problem might be a broken loop, or a broken function, or a broken class, or a total program. But the important thing to keep in mind is that there is no simple single answer for anything. I'm harping on this only because around now is when people complain "But you didn't show us how to make a banana for my fruit salad! How can I do my homework?!?" I showed how to make a class and how to plan a program. You make the fruit salad.
Oh yeah, and I'm also harping on this because the drop date is coming up. If you don't like programming you can still get a W. I personally think y'all should commit and stay because programming is the best job ever.
Spec:
Here we have composition (object property) and association (pointer property) only, and fewer classes than the text assignment. No aggregation (owner of dynamic memory). Write a program for a super hero group. (Avengers, X-Men, X-Force, Justice League, Teen Titans, whatever.) The program needs to track basic information about each hero or villain. Height, weight, primary power, primary weakness, and primary enemy. You don't need to actually look these up - you can invent whatever data you want.
The program needs to be able to add a new hero to the super hero group and set any of those properties with proper public/private and get/set usage. I also want to keep track of everyone's costume; color and material are enough.
Use cases:
A use case is a description of a common user performing actions with a given goal. This helps you decide if your objects are sufficient. "Get money out of an ATM," "Grade an assignment," anything related to why you are writing the program.
I want to add a new member to the group. (Whether the group tracks member or the people track what group they are in is up to you. User doesn't care.)
I want to find the name of someone's enemy.
I want to have a bunch of heroes switch to using the same costume.
Your main:
Test everything you wrote. You don't test the use cases though. You just make sure they could happen if you were asked to do them later.