Requirements Numbering Scheme in Nested Packages

[543SysML]

Trying to figure out how to apply a numbering scheme from parent package and ensure that all the nested packages and the requirements contained with in will abide by the same numbering scheme and stay unique when new requirements are added. I have attached a project for reference. i.e. no matter which package a new requirement is added in the numbering scheme and next available ID is applied automatically.

Update : Eventually figured out that you have to have the <NumberOwner> stereotype applied to a package and then at least have one requirement in the root of that package. Customize the numbering scheme then all nested packages follow. It will be nice to apply the numbering scheme from the package and target the requirement.

Also, which stereotype is preferred and what are the differences or limitations. <numberOwner>[MD Customization for SysML] or <NumberOwner> [UML]

[Rolandas]

Hello,

Numbering is done depending who the scheme is set up. For requirements only it's id is shown in browser as it's the default schema. For custom numbering you can choose which one is default.
Or what do you mean by, which stereotype is preferred?

Regards,
No Magic Support Team