I can’t assign Package or Subsystem to Model on requirement diagram.
Our methodolgy is harder to use, because in the stage of system architecture definition we divide system to subsystems and assign functional requirements to them. Of course we can add requirements as children, but using <> relationship is more natural.
The next step is adding classes to subsystems and assigning requirements to them. Sometimes we assign requirements to operations. It doesn’t work in VP too.
Could You add these functionalities to Requirement diagrams?
Thank you for quick response.
Assigning requirements to classes is not a problem. I can use Requirement diagram for it -> add Model to diagram, assign class to it, and establish <> relationships between model and requirements.
Great. By the way, I am glad to inform you that we will support assigning package and subsystem to Model in the coming build. Hopefully this will be available within today.
Glad to let you know that the release that supports assigning package and subsystem to model is ready. Please run the product updater to advance to it.