Derived property for requirements on diagram

Question

Hi

I'm trying to create a derived property in the requirements list editor to display where a requirement is contained on a diagram.

I current have the code:

let diagrams:Sequence(notation::Diagram) = self.mediniGetOpposites('element')->selectByType(notation::Shape).diagram->selectByType(notation::Diagram)

in projectmodel::PJDiagram.allInstances()->select(d | (diagrams->includes(d.oclAsType(projectmodel::PJDiagram).diagram) )))

This gets me all the diagrams that a requirement is displayed on, but I would like to further filter the results to a certain area of the model. I have tried the code below, but it does not yield any results.

let diagrams:Sequence(notation::Diagram) = self.mediniGetOpposites('element')->selectByType(notation::Shape).diagram->selectByType(notation::Diagram)

in projectmodel::PJDiagram.allInstances()->select(d | (diagrams->includes(d.oclAsType(projectmodel::PJDiagram).diagram) and (d.canvasElement.oclAsType(sysml::SysMLContainerPackage).name.matches('System Model System Architecture Design & TSC') )))

It's probably a misunderstanding how to use the oclAsType method, but any guidance would be much appreciated!

medini_1024169437 · Answer

Aha, thats the root cause: child diagrams are bit different and difficult. The hierarchy you see is only virtual I think, that needs some investigation. Stay tuned.

Jan

medini_1061189784 · Answer

Hi Jan

Appreciate you spending your time on this.

This is what my structure is (with redacted information). I think its much more different which could be causing the issues.

I am trying to filter for diagrams underneath the expanded '...TSC Diagrams...' section. They are child diagrams if that helps

Thanks

Reece

medini_1024169437 · Answer

Hi Reece, not sure whats different in your side, here at least as it looks on my side:

The diagram is located top level in the requirements model. Note that I of course changed the OCL to match 'TSC'. One way to improve is to rename the diagram so it has a different name than the model. That helped me to better see things. If you want to match against a package, you probabaly have to navigate from the model to its parent, so add one more navigation I guess.

Happy Scripting

Jan