A new object appears during an interaction. Its lifeline must begin where creation happens rather than pretending it was present all along.
Inside a Controller method, Player has a parameterless constructor that sets Name to "New player". The next assignment changes the new instance's public Name field.
Player selected = new Player();
selected.Name = "Jordan";The controller creates one Player using the parameterless constructor
The constructor initializes Name to New player
The caller receives a reference in selected
The next statement changes that same object's Name to Jordan
No second Player is createdUse these words to follow one execution before drawing it. Keep the same order and the same alternatives as the source; simplify the wording without adding work that the code does not perform.
controller : Controller lifeline.selected : Player with its heading at the incoming creation request rather than at the top of the interaction.new Player() from controller to the new participant and show the constructor activation. Note Constructor sets Name to "New player".Caller directly assigns selected.Name = "Jordan"; same object. Do not turn that public field assignment into an invented setter call.Compare this reference with the diagram you built in Violet. Layout may differ; the source meaning, labels, and relevant connections should agree.
At the constructor's completion, Name is New player. After the following field assignment, it is Jordan. A sequence diagram can annotate these state facts without becoming a full object snapshot.