Class declarations and object modeling: Correct Solution

Translate the specification below into an idiomatic Java class definition.

(In this context, "idiomatic" means following the common style and conventions of the language.)

1. One kind of thing that exists in our model is a Cliou.

2. Each Cliou has a firar, which is a graphics object. A firar is part of the internal state of a Cliou: no other classes can see the value of firar or directly change it. When a Cliou is first created, the value of its firar starts out as a rectangle with a width of 26 and a height of 24.

Solution

public class Cliou {
    public GraphicsObject firar = new Rectangle(0, 0, 26, 24);

    public Cliou() {
    }
}

Things to check in your solution:

• Is every public and private modifier correct?
• Are the correct items static?
• Are the correct items final?
• Are all the variable types and method return types correct?
• Are the class members in the correct order? It should be: (1) static variables, (2) instance variables, (3) constructors, (4) methods.
• Do members have the correct capitalization?

Acceptable variations in the solution:

• It is OK if you initialized non-static variables in the constructor instead of in the declaration. (Ask your instructor if you aren’t clear what this means.) Note that static variables must be initialized in the declaration.
• It is OK if you used a slightly different but equivalent form of an expression, such as += 1 instead of ++.

Related puzzles:

• Stack frames and objects (like the Idea Lab activity): Correct Solution (1day-xidi-zi46-bpw9-6)
• Variable scope and lifetime: Correct Solution (gett-t4e9-a639-era0)
• Class relationships: Correct Solution (rkbL-0qbj-5rh0-wao4)