A Wildcats Player has an identifier that should not be reassigned after initialization. The diagram needs to distinguish that restriction from private visibility.
This complete class uses a field initializer so no constructor knowledge is needed. Each instance stores this teaching value; it is not a unique-ID generator.
public class Player
{
public readonly int TrainingGroup = 1;
public int NumberOfTurns;
}Define a Player with a public TrainingGroup integer
Initialize TrainingGroup to 1 and restrict later reassignment
Also define a mutable public NumberOfTurns integer
Describe the two field contracts independentlyThese words describe the class contract, not a sequence of runtime actions. Identify the types, stored members, operation inputs and results, and relationships before choosing compartments and connectors.
Player.+TrainingGroup : int {readOnly}. Keep the braces as annotation text in the diagram.+NumberOfTurns : int. Do not apply the readOnly marker to this mutable field.Compare this reference with the diagram you built in Violet. Layout may differ; the source meaning, labels, and relevant connections should agree.
NumberOfTurns can change during training. TrainingGroup cannot be reassigned by ordinary code after initialization. Later constructor lessons show another permitted initialization point.