SysML Requirements Table Features

[bdfears1]

After trialing Cameo Enterprise Architecture 17.0.4 to create a SysML model, I was very impressed. However, an area which I feel could be improved is its features regarding SysML requirements handling. New features which I would like to see are:

1) The ability to show the names of requirements in a table with indentation making the containment hierarchy easier to see e.g.:

Req1
-->Req2
-->Req3
---->Req4
---->Req5
Etc.

2) Following on from the previous idea …

The ability to include packages in the containment hierarchy e.g.:

Systems Requirements (pkg)
---->Req1
---->Req2
---->Environmental Requirements (pkg)
-------->Req3
-------->Req4
---->Operational Requirements (pkg)
-------->Req5
-------->Req6

3) The generation of a unique “lifetime ID” for each requirement. Currently an ID changes when a requirement is moved to different parent requirement.

4) The ability to select multiple requirements in the table and set their properties (e.g. setting text to HTML). Currently this has to be done for each requirement separately.

5) Paragraph wrapping to be the default setting in the requirements table. Currently the text becomes hidden when a field is not wide enough.

6) More advanced filtering options for the requirements table e.g. NOT, AND, OR etc.

7. The ability to place two requirement tables next to each other on screen (e.g. Customer and System Requirements) as well as the option to quickly create relationships between them (e.g. derive).

8. The ability to display requirements and derived requirements next to each other e.g. if I have requirements:

CR1
SR1 (derives from CR1)
SR2 (derives from CR1)

A query could show:

Query Rows:
ID_CR1 CR1_Text ID_SR1 SR1_Text
ID_SR2 SR2_Text

9. The ability to set table cell font style based on a requirement attribute (e.g. Type=Heading) and level (e.g. level 2) thus helping readability of a set of requirements.

I hope this is of interest.

Regards,

Ben Fears

[jusgre]

Hello,

Thank your for your valuable suggestions. Some of your suggestions are already included into our future feature list. Others will be considered shortly.

If you have any questions or suggestions, please feel free to contact us.

[prdubois]

This post is already one year old but I'd just like to say that I strongly agree with most of these feature requests (especially #3). It doesn't seem like any of the suggested improvements made it to the new v18 release unfortunately.

[saulius_p]

Hello,

Thank you for your feedback. Requirements support multi-level and consecutive numbering style. It is possible to switch from multi-level (default one) to consecutive. Please right click on any requirement choose Element Numbering, change the style to consecutive and renumber requirements. All inner requirements will inherit the owner numbering style.

Consecutive numering.png

It is common that both Multi-level (for requirements structure representation in the table) and Unique - consecutive IDs are required. In such case requirements needs to be extended with additional property with different numbering style.

Instructions are following:
In order to use custom property for hierarchical ID standard requirements needs to be extended. Follow the steps to extend it:
1. Create Profiling diagram

Profiling+diagram.png

2. Extend standard requirements stereotype with custom one. Create property in it to store hierarchical property.

req+extension.png

Note. Custom requirement type inherit all the capabilities and properties of standard requirement. However icon is not inherited. You will need to specify custom.

custom+icon.png

Hope this will be helpful. We are planing to include custom requirement with hierarchical property into standard configuration in future. Also hierarchical tables are very expected capability in the future.

[prdubois]

Thanks Saulius. Very helpful as always.