STARIONGROUP
Possibility to adapt engineering model with high impact changes according to lessons learned
High level first issue, open for discussion:
The current setup offers limited possibility to fix errors or update an engineering model which is already well underway due to changed premises, lessons learned or just (as said) to fix mistakes.
example: when a user has already created a lot of element usages, and has created relationships for these (e.g. with requirements, or other modelling items), it is impossible to change the nesting of the modelling item (i.e. changing it to a different parent Element definition) without deleting and adding it as new item. This means all the related modelling information will be lost, with a need to redo all the related work.
It is clear that this has a huge impact on the model and the current implementation. from a user perspective, this is a use case that can easily happen and has a high added value to be able to work with the model.
