nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

how to automatically link imported DOORS requirement (contribution relationship) together, based on imported attribute containing ID list

medini_1068896534

Hello,

i am importing two DOORS classic modules in my projects.

In DOORS, those two modules are properly linked to each other, but the DOORS classic connector is not able to import such information automatically.

As a workaround I created DXL attributes in both DOORS modules, containing a list of the DOORS identifiers, one attribute for the inlinks and one for the outlinks. So each imported DOORS requirement in medini has a list of DOORS IDs for the out and inlinks.

i added a screenshot to show the situation

I would like to have a script which enables the automatic linkage between the two modules, based on the IDs lists contained in those imported DXL attributes.

IMPORTANT: i don´t want to create TRACES between the requirements, i would like to create "contribution" relationships.

thanks for the support!

ciao ciao

Francesco

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1028038066

Hi Francesco,

I have a similar example. In your case you'll need to iterate over all modules + care about the direction of the contribution. Hope this helps otherwise please comment in this thread:

medini_1068896534

Hi Krasimira,

thanks for your quick reply, but unfortunately i was not able to make the script work for me:

already replaced the name of the identifiers list and the separator character, but the script already blocks on my side at line 28, because the selected is not a single requirement model.
i also tried to replace the "Metamodel.safetygoals.SafetyRequirementsModel" with the type of my selected DOORS requirement model (got it via debug mode -> right click -> What is this?)

either i am not triggering the script in the proper manner, or my adaption of the script was not successful.

any kind of help will be highly valued!

thanks in advance!

ciao ciao

Francesco

medini_1024169437

Hello Francesco,

you adoption as far as I understood them, sound reasonable. A few comments though:

* If you use "What is this" on models, make sure you resolve them, either check the "Resolve" option in the attribute view or follow the "originalModel" reference. Otherwise you have Metamodel.projectmodel.PJProxyModel instead of Metamodel.doorsrequirements.DoorsRequirementsModel as it should be

* DoorsRequirementsModel is an extension of SafetyRequirementsModel

* The code in line 27 is not really "modern", instead of comparing the .prototype with a fixed metaclass, it shoudl use instanceof, to support subclasses

* So change "selection[0].prototype != Metamodel.safetygoals.SafetyRequirementsModel" to "!(selection[0] instanceof Metamodel.safetygoals.SafetyRequirementsModel)" and it shall work

Btw. Krassi is OOO

Happy Scripting

Jan

medini_1068896534

Hi Jan,

I Know Krassi is OOO, she wanted to send me the scripts before her vacations

thanks for your hints, i implemented and at least the script works till line 41 with this failure

i then tried to manually change the names of the requirements models for which the script is looking for (see screenshot) (e.g.

with this the scripts runs till the end without errors, but no contribution relationships were created

maybe an additional info which could also be behind the issue: my separator are two "newlines" with a space character in between. Unfortunately i cannot change it so easily (like with a # or so), therefore i left it like that and declared the separator like that

any idea how i can make it work?

thanks!

ciao ciao

Francesco

medini_1024169437

Hi Francesco,

well, not that easy but I try.

The script logs some output, like "Not attributed" etc. do you get anything of those?
Maybe you try only "\r\n" or "\n" as separator and trim the strings afterwards, ignore any empty

I popose to add a few more logs to see whats going on or to use $DEBUG$ at least once to step through the code

Regards

Jan

medini_1068896534

Hi Jan,

i am not very familiar with the $DEBUG$ you are mentioning. so i tried the other way: i took the original script from Krasimira, i created 3 dummy requirements in the ESL example:

- one test child requirement (on TSR level) which should be linked to the 2 test mama reqs (on FSR level)

- i adapted the script, by updating the attribute name and the separator

- i started the script (right clicking on the TSR module, execute, select the script)

RESULTS: the script runs without error, but also without logs saying that is linking req x with req y or so... In the end no relationship is created. My impression is that the block, which is supposed to search the requirements to be linked, is simply not finding anything... but i don´t understand why

medini_1024169437

Francesco, sorry for the delay, I overlooked your comment.

There are too many possibilities here which ma ynot work as expected, so I suggets to maybe add a few more logs to come closer?

For example, there is a line:

console.log("Investigating1: FSR {0}", fsrRequirements);

That should at leats tell you whether the script is finding anythign, same for logs like:

console.log("Investigating: {0}", from.identifier);

Do you see output for your tets requirements? if not, maybe already the code that finds the models is not working, I mean:

var fsrRequirementsModel = finder.findByType(Metamodel.safetygoals.SafetyRequirementsModel).and("name", "Functional Safety Requriements").first();

is picking by name and there is eve a typo in it :-)

I suggest to add more logs also later when it comes to the id check, so before code like

var to = tsrRequirements.and("identifier", id).first();

you can insert a log to see what id is current set to.

All in all abit more so you understand what and what no the script is doing.

Happy Scripting

Jan

medini_1068896534

Hi Jan,

i just want to say that actually in the end (for a long time i had not time to script around) i managed to get this script working. the test worked, and i also tried on a copy of a productive project. The drawback is of course that the names of the requirements models to be checked for links have to be inserted in the script manually each time, but ok, maybe this might be the next improvement for the script.

so in the end thanks a lot for your support!

ciao ciao

Francesco

medini_1024169437

Francesco, glad it works.

May I suggest to use tags instead of hard coding model names? So you can add a tag like "#sync" to the modle and use the special finder methods withTag("sync") to filter.

Jan

medini_1068896534

oh, that´s a good idea, i will try it out!