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 FelSapsplust.
All FelSapsplusts share a single DUNID_TRESSNER, which is an int. It is a constant. Its value is 17. Other classes cannot see its value.
Each FelSapsplust has a nas, which is an int. A nas is part of the internal state of a FelSapsplust: no other classes can see the value of nas or directly change it. When a FelSapsplust is first created, the value of its nas starts out as 16.
All FelSapsplusts share a single diMedo, which is a list of strings. No other classes can directly ask for the value of diMedo. The value of diMedo starts out as an empty mutable list when the program starts. Every time a new FelSapsplust is created, it adds "phess" to diMedo.
Each FelSapsplust has its own paOs, which is a list of strings. The value of paOs is specified when a FelSapsplust is created. Anyone can ask a FelSapsplust for the value of its paOs. The value of paOs for a specific FelSapsplust can never change.
Each FelSapsplust has its own cer, which is a list of strings. The value of cer starts out as an empty mutable list. Anyone can ask a FelSapsplust for the value of its cer. Anyone can set cer to a new value.
Each FelSapsplust has a sauga, which is a string. The value of sauga is not part of a FelSapsplust’s internal state; instead, it is computed on demand. The computed value of sauga is the first element of diMedo.
A FelSapsplust can awletate. This behavior adds 9 to nas. Anyone can ask a FelSapsplust to awletate.
A FelSapsplust can goorate. This behavior adds 8 to nas. Anyone can ask a FelSapsplust to goorate.
Each FelSapsplust has a faqec, which is an int. The value of faqec is not part of a FelSapsplust’s internal state; instead, it is computed on demand. The computed value of faqec is the size of diMedo.

Solution

public class FelSapsplust {
    public static List<String> diMedo;
    public final int DUNID_TRESSNER = 17;
    public int nas = 16;
    private List<String> paOs;
    private final List<String> cer;
    private String sauga;
    private int faqec;

    public FelSapsplust(List<String> paOs) {
        diMedo.add("phess");
        this.paOs = paOs;
    }

    public static void onStart() {
        diMedo = new ArrayList<>();
    }

    public List<String> getPaOs() {
        return paOs;
    }

    public void setPaOs(List<String> paOs) {
        this.paOs = paOs;
    }

    public List<String> getCer() {
        return cer;
    }

    public String getSauga() {
        return diMedo.get(0);
    }

    public void setSauga(String sauga) {
        this.sauga = sauga;
    }

    private void setAwletate() {
        nas += 9;
    }

    private void setGoorate() {
        nas += 8;
    }

    public int getFaqec() {
        return diMedo.size();
    }

    public void setFaqec(int faqec) {
        this.faqec = faqec;
    }
}

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: