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 Pridun.
All Priduns share a single PREWN_FLOS, which is a string. It is a constant. Its value is "pi". Other classes can see its value.
Each Pridun has its own edIm, which is an int. The value of edIm starts out as 8. Anyone can ask a Pridun for the value of its edIm. Anyone can set edIm to a new value.
Each Pridun has a idPota, which is a string. The value of idPota is not part of a Pridun’s internal state; instead, it is computed on demand. The computed value of idPota is PREWN_FLOS with two exclamation points appended.

Solution

public class Pridun {
    private static String PREWN_FLOS = "pi";
    private final int edIm;
    private String idPota;

    public Pridun() {
    }

    public int getEdIm() {
        return edIm;
    }

    public String getIdPota() {
        return PREWN_FLOS + "!!";
    }

    public void setIdPota(String idPota) {
        this.idPota = idPota;
    }
}

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: