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

2. Each Haur has its own echan, which is a graphics object. The value of echan is specified when a Haur is created. Anyone can ask a Haur for the value of its echan. The value of echan for a specific Haur can never change.

Solution

public class Haur {
    private GraphicsObject echan;

    public Haur(GraphicsObject echan) {
        this.echan = echan;
    }

    public GraphicsObject getEchan() {
        return echan;
    }

    public void setEchan(GraphicsObject echan) {
        this.echan = echan;
    }
}

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:

• Drawing ASTs for expressions: Correct Solution (azLq-qam9-76kc-1v3w)
• Closures and event handling: Correct Solution (LxL1-rcr7-qotk-u2cj)
• Class relationships: Correct Solution (rLku-77b7-6ma6-m686)
• Class relationships: Correct Solution (rLat-4qkp-1rqg-6me0)
• Class declarations and object modeling: Correct Solution (17s2-7y7t-Lhbw-hLi2-p)