Thanks for your post. Using composition in your case is correct, and derive relationship does not fit into your case. According to SysML Specification v1.1:
“A DeriveReqt relationship is a dependency between two requirements in which a client requirement can be derived from
the supplier requirement.”
Attached you can see a sample of derived requirement which I picked from SysML Specification v1.1. Hope this helps.
Lilian Wong sample_from_SynML_Spec.png
I just tried creating a report (custom requirements report loop) and the requirements list out of order. For example, Requirement ID 1.1 appears before Requirement ID 1 in the list. 1 is composed of 1.1, 1.2, … so they should logically appear after it.
Thanks for replying. I’ve forwarded the issue to our engineers to follow-up, and will let you know if there is any feedback.
And we will support sorting elements by Name and ID in VP Suite 4.1 SP1 or 4.2.
Thanks for your inquiry. We are sorry that we do not support generate requirement diagram in tabular view, but we plan to support this in VP Suite 4.2 (VP-UML 7.2).
By the way, you can export the requirement diagram to Excel file, the exported Excel file will contains the details exist in tabular view. For VP-UML, export Excel feature is available in Standard Edition or above.
Sorry for my late response. We support sorting ID of requirements in tabular view of requirement diagram in latest patch (build sp1_20091125f). Please follow the steps in following link for update to latest patch:
Create a requirements diagram, switch to “Tabular View” (right click and click “Switch to tabular view…”). Create a few requirements. Now you can reorder with the up and down arrows, I use this to put higher priorities up top.
You can also reorder from the column headers, so click on the ID header and they will be sorted by ID. Problem is, that once a column header is sorted it seems impossible to turn that sort off. Usually programs have a click 3 times to take off the sort (1st click ascending, 2nd descending, 3rd=OFF). So whenever you want to prioritize your requirements and you hit the column sort, you are up the creak because it seems your prioritization ordering is gone and you have to live by your column sort. Either I’m missing something or the devs forgot to write the feature into their requirements/use cases while engineering VP.