Requirements Numbering Scheme in Nested Packages

Discussions about requirements management product Cameo Requirements+ functionalities

Moderator: Moderators

Requirements Numbering Scheme in Nested Packages

Postby 543SysML » Thu Feb 08, 2018 6:56 pm

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]
You do not have the required permissions to view the files attached to this post.
Forum Newbie
Forum Newbie
Posts: 19
Posts Rating:1
Joined: Thu Apr 13, 2017 1:00 pm

Re: Requirements Numbering Scheme in Nested Packages

Postby Rolandas » Mon Feb 12, 2018 12:41 am


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?

No Magic Support Team
Customer Support
Customer Support
Posts: 234
Posts Rating:18
Joined: Mon Jul 30, 2012 3:59 am

Return to Cameo Requirements+

Who is online

Users browsing this forum: No registered users and 0 guests