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

2. Each Phal has its own voAn, which is a list of strings. The value of voAn starts out as an empty mutable list. Anyone can ask a Phal for the value of its voAn. Anyone can set voAn to a new value.

Solution

public class Phal {
    private final List<String> voAn;

    public Phal() {
    }

    public List<String> getVoAn() {
        return voAn;
    }
}

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:

• Static and runtime types: Correct Solution (wtd3-zL8q-apL2-oboc)
• Class relationships: Correct Solution (rgxx-ddf9-2uww-efna)