search

Eden-06 / FRaMED-2.0

FRaMED 2.0 is the reimplementation of the Full-fledged Role Modeling EDitor allowing the graphical specification of Role-based Software Systems by means of compartments (aka. contexts), objects, roles, and relationships.
Eclipse Public License 2.0
3 stars 0 forks source link

Generation of standard names for attributes/ operations buggy #11

Open SriousTaken opened 6 years ago

SriousTaken commented 6 years ago

E.g. standard names for attributes are created the following: "attribute:type", "attribute:type1", "attribute:type2", ... The number should not be added to the type, but to the "attribute" part of the standard name! The same problem exists for operations.

zointblackbriar commented 4 years ago

This problem could come from the following function in the package of org.framed.iorm.editpolicymodel a function named createTrueConstraintRule

public TrueConstraintRule createTrueConstraintRule() {
    TrueConstraintRuleImpl trueConstraintRule = new TrueConstraintRuleImpl();
    return trueConstraintRule;
}

The above-mentioned function creates a new instance in each iteration. Each instance has setID() parameter that should be updated. Therefore, a singleton pattern for trueConstraintRule object might be enough.

SriousTaken commented 4 years ago

Example: attribute names of natural types Currently the standard names of these attributes are generated like attribute:type, attribute:type2, attribute:type3,... forbiidenisd1

Instead it should be generated like attribute:type, attribute2:type, attribute3:type,... forbiidenisd