2
« on: July 18, 2015, 12:36:59 am »
OK, just so you understand, when we first started using EA, we weren't all that UML savvy so really just used it to document our requirements in a way we saw fit at the time. Probably true of many of your users. So, because the component element made for useful diagrams, we used that as a node in our project with many requirements as children. The top level package had at least 2 components in its hierarchy before reaching a requirement. Auto numbering was turned on and these became paragraph numbers in our output documents (We use eaDocX).
A way down the line I am using this original document as the basis of another one. However components don't fulfil my need so I am converting each component to a feature. Bearing in mind I want to use the same numbering (the documents are related), I create a new feature, move all the requirements as children of the feature and remove the component. When finished the features don't have the same order as the original components hence the need for the MOVE UP / DOWN.