Improve naming of coupling/decoupling constraints
CURRENT STATE
When a coupling/decoupling constraint is created, a generic name
(Pattern n) is assigned to it.
EXPECTED BEHAVIOR
A more expressive name should be assigned, e.g. coupling(t_1, …, t_n),
where t_1, …, t_n are the tasks required to be coupled., similarly to
what happens for allocation/dislocation constraints.
This would help the selection of constraints when creating a new rule
set and would make the info in the DSE navigator more readable.
TEST
Try to load/create any model (e.g., the one enclosed) in the DSE
perspective.
Go to the Constraint Modeling section and create a new
coupling/decoupling constraint.
Check the name that gets assigned to the constraint.
(from redmine: issue id 3812, created on 2019-09-05, closed on 2019-09-09)
- Uploads: