JetUML validates that diagrams created in the application are semantically valid. This is currently support by the DiagramBuilder functionality, which prevents the addition of nodes and edges that violate semantic constraints. There are three problems with the current design:
Diagram files loaded in are not semantically validated. Therefore, it is possible to hand-craft (or used tools) to make a file that describes an invalid diagram, and load it in.
The constraint validation code cannot easily be reused to do batch validation of existing diagrams.
The constraint validation code does not easily support providing useful error messages when validation rules are not respected.
We need to refactor the constraint validation code so that it is more modular, reusable, and extensive to support the above scenarios.
The current design is to have the following workflow for all validation scenarios:
Create or update a diagram without any constrain validation;
Run all the validation rules, record violations
If there are any violations, undo the last update command.
JetUML validates that diagrams created in the application are semantically valid. This is currently support by the
DiagramBuilderfunctionality, which prevents the addition of nodes and edges that violate semantic constraints. There are three problems with the current design:We need to refactor the constraint validation code so that it is more modular, reusable, and extensive to support the above scenarios.
The current design is to have the following workflow for all validation scenarios: