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.)

One kind of thing that exists in our model is a TirWhe.
All TirWhes share a single ARDOL_TONU, which is an int. It is a constant. Its value is 7. Other classes can see its value.
Each TirWhe has its own poFo, which is a graphics object. The value of poFo starts out as a rectangle with a width of 16 and a height of 42. Anyone can ask a TirWhe for the value of its poFo. Anyone can set poFo to a new value.
Each TirWhe has a xuo, which is an int. The value of xuo is not part of a TirWhe’s internal state; instead, it is computed on demand. The computed value of xuo is the width of poFo.

Solution

public class TirWhe {
    private final int ARDOL_TONU = 7;
    private final GraphicsObject poFo;
    private int xuo;

    public TirWhe() {
    }

    public GraphicsObject getPoFo() {
        return poFo;
    }

    public int getXuo() {
        return poFo.getWidth();
    }

    public void setXuo(int xuo) {
        this.xuo = xuo;
    }
}

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: