The Renumber Element command allows you to automatically renumber an element and all of its descendants. For example, you can renumber a segment of a requirements tree, a functional tree, or a component tree (the descendants of an element are those elements related hierarchically to the element via its parent-child relation). Renumbering a requirement via this command will automatically renumber the requirement, all direct children found using the refined by relation (the parent-child relation for Requirements), all children’s children, and so on. If you simply want to renumber the requirement without renumbering descendants, you do so by editing the number on the requirement's property sheet.
When renumbering an element, you are prompted to enter the new number and the sort block to use when renumbering the descendants. The number defaults to the element's current number but can be changed to any hierarchical number as the initial number in the hierarchical tree. Clicking OK will proceed with the renumber operation.
If the element being renumbered has a structured decomposition (functions for example), you will have a special sort block option selected by default. The "_Follow Decomposition" sort block will traverse the structure (as shown in an activity diagram or EFFBD) and assign the numbers sequentially.
 |
Tips and Tricks When you renumber an element, entering 0 for the new number will number the child elements 1, 2, 3, ... |
| |
What permissions are required to renumber an element? Renumbering an element involves updating the number for the element and each of its descendants. To successfully complete the renumber action, you must have read permission for each of these elements and write permission for each number attribute. At the completion of the renumber process, CORE will display a list of any elements that could not be renumbered due to insufficient permissions. |