1.2.5 Resolving Feedback System Class Diagram Errors

Read the Feedback as a Difference Between the Model and the Requirement

When the Feedback System reports a class-diagram issue, first identify which structural category is involved.

Common introductory categories include:

  • missing class;
  • incorrect class name;
  • missing field;
  • incorrect field name;
  • incorrect field type;
  • incorrect visibility;
  • missing or incorrect class relationship;
  • extra element not required by the design.
Compare One Structural Element at a Time

If the feedback identifies a field issue, compare:

Activity diagram showing read feedback, then locate the diagram element, then make one focused revision, then save the Violet source, then submit the current file, then read the new result.
ReadFeedback.
  • New
  • Changed
  • Removed

Use the newest feedback as evidence about the newest diagram.

The Goal Is Correct Structure

The goal is not merely to make a message disappear.

The goal is for the class diagram to represent the required classes, fields, types, visibility, and relationships accurately.