The Feedback System can help you compare your UML diagram with the requirements for the current activity.
Before submitting, make sure you know which Violet file is your current version.
A common source of confusion is having several similarly named files and submitting an older copy.
Use this sequence:
Edit → Save → Confirm the file → Submit
Open your diagram in Violet.
Make sure the model on the screen is the version you intend to submit.
Save the editable Violet file.
If the course specifies a filename or folder, follow that requirement exactly.
Do not substitute a screenshot when the Feedback System expects the editable diagram file.
A screenshot shows the appearance of the diagram.
The editable file preserves the model information the Feedback System needs to examine.
Use the Feedback System link or access method provided by the course.
Choose the activity associated with the UML diagram you are currently working on.
Select the saved Violet diagram file.
Before submitting, confirm that the selected filename matches the file you just saved.
Feedback may identify a difference involving:
Do not treat a feedback message as a command to make random changes until the message disappears.
Use it to locate the part of the model that needs attention.
Suppose the feedback indicates that player1 has the wrong type.
Return to the intended model.
Ask:
player1 represent?Then make the focused correction.
The same reasoning applies to fields and relationships.
The Feedback System helps point to a difference.
Your job is to understand why that difference matters to the model.
Make the correction in Violet.
Save the file again.
Then submit the revised file.
Avoid correcting only an exported image or screenshot. The editable Violet diagram is the artifact that needs to become accurate.
If several messages appear at once, begin with a problem you understand.
Fix one meaningful issue.
Save.
Submit again.
Then read the current feedback.
This is usually easier to reason about than changing several unrelated parts of the model simultaneously.
The Feedback System is most useful when it helps you understand the model.
A productive cycle is:
Represent the idea → Submit the model → Read the evidence → Revise the model
The goal is not to discover a combination of boxes and lines that makes every message disappear.
The goal is to produce a diagram whose identity, values, and relationships correctly communicate the intended system snapshot.