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

2. Each Peldin has a siInste, which is a list of strings. A siInste is part of the internal state of a Peldin: no other classes can see the value of siInste or directly change it. When a Peldin is first created, the value of its siInste starts out as an empty mutable list.

Solution

public class Peldin {
    public List<String> siInste = new ArrayList<>();

    public Peldin() {
    }
}

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:

• Variable scope and lifetime: Correct Solution (gexy-84mi-1r70-8zfr)
• Static and runtime types: Correct Solution (wtsa-5d18-smdp-nmuj)