A for loop writes initialization, test, and update in one header, but they happen at different points in the flow.
This excerpt runs inside a method and models three completed Wildcats training rounds. The assignment records a completion; it does not perform the physical drill.
If the underlying C# feature is unfamiliar, use the lesson below while reading this example.
int completedRounds = 0;
for (int round = 1; round <= 3; round = round + 1)
{
completedRounds = completedRounds + 1;
}Set the completed-round count to 0
Initialize the round label to 1 once
Before each pass, test whether round is at most 3
When true, record one completion
After that body, increase round by 1 and test again
When false, leave without running body or updateUse 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.
completedRounds = 0 and round = 1.round <= 3?. Its true route reaches completedRounds = completedRounds + 1.round = round + 1. Draw the return arrow from this update back to the condition, bypassing both starting assignments.false route directly to the activity final. It must not visit the body or header update.Compare this reference with the diagram you built in Violet. Layout may differ; the source meaning, labels, and relevant connections should agree.
Trace round values 1, 2, and 3 through the body. The next update produces 4; the check at 4 is false. There are three body executions and four checks. The flow diagram shows a conceptual counter even though the C# for variable is scoped to its loop.