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; } } }

Codebeamer interact with medini

medini_1047650437

Hi all，

The Background：

Codebeamber has two trackers：Customer Requirement & System Requirement

What we expect：TSR be imported into Customer Requirement，and FSR be imported into System Requirement, at the same time, the relationship between them shall be preserved.

Please advise how to define the mapping file？ Thanks a lot~

Qianqian

Sincerely.

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Hi Qianqian,

I assume you mean export to Codebemaer, is that correct?

One solution is to have two separate medini models, one for TSR one for FSR, then have two different mapping files, one for each module.

Define relations only in one of the mapping files, in TSR maybe. The relation should be exported when teh TSR is export and FSR was already exported.

Note that for codebeamer we only support "References", not real relations.

Second option (if TSR and FSR are mixed in one module) is to sue scripted selectors, there are a few articles here in the board. namely https://medini.freshdesk.com/support/discussions/topics/1000093110

Make sure you also read https://medini.freshdesk.com/support/discussions/topics/1000113563

Regards

Jan

medini_1047650437

Hi Jan,

You are right, the SR would be exported from medini to Codebeamber.

TSR and FSR are mixed in one module,and we use scripted selectors.

If kind=Functional (in medini),the SR shall be exported to tracker System Requirement.

And If kind=technical (in medini),the SR shall be exported to tracker Customer Requirement.

How to use scripted selectors define the mapping file, could you please offer one mapping sample?

Thanks for your support~

Qianqian,

Sincerely.

medini_1047650437

Hi Jan,

we meet one new problem:

when export SR to Codebeamber, the requirement sorting are out of order, unlike the sorting in medini.

detail shown in below screenshort.

So, could the export ordering be configurated?

Qianqian,

Sincerely.

medini_1047650437

Hi Jan,

[Define relations only in one of the mapping files, in TSR maybe. The relation should be exported when teh TSR is export and FSR was already exported.]

the solution works well, thanks~

Qianqian,

Sincerely.

medini_1024169437

Hello Qianqian,

please check these articles:

https://medini.freshdesk.com/support/discussions/topics/1000093110

https://medini.freshdesk.com/support/discussions/topics/1000113563

I dont have a codebeamer example but in general it should work as in the attached Jama example (script and mapping).

See and adapt isSourceElementOfKind('NON_FUNCTIONAL')

I have no idea about the order. We use the order that is given by the CB API.

Happy Scripting

Jan

medini_1047650437

Hi Jan,

We want to export the attribute “allocation” into Codebeamber.

But I can't find the corresponding attribute in medini.

How to define the mapping rule? Do we need to transform the attribute in medini ?

Thanks~

Qianqian,

Sincerely.

medini_1024169437

Hm, that might be difficult or impossible. An allocation between a requirement and a system element is a "Trace" I think (you can confirm that). So from that perspectuve you can use mediniAttribute="Trace".

Buuut: mapping a Trace to a relation will check the Trace Kind and only map it if the Trace kid is "Allocation" in your case.

Jan

medini_1047650437

Hi Jan，

Uh...is there any script that could convert the "trace" attribute to a string attribute in the requirements list in medini, as the contents of the string attribute can then be imported into the codebeamber.

Qianqian,

Sincerely.

medini_1047650437

Hi Jan，

Qianqian,

Sincerely.

medini_1047650437

Hi Jan,

Is there any more material about the interaction between medini and codebeamber?

On the issue of out-of-order, codebeamber technical support wanted more interactive detail.

Thanks for your support in advance~

Qianqian,

Sincerely.

medini_1024169437

Sure, that should be easy. Just create a new derived property for Safety Requirement, maybe use OCL to make the statement short.

Pseudo code could be

self.mediniGetTracedElements(sysml::SysMLElement).oiclAsType(sysml::SysMLElement).map(m | m.name)

Note this is pseudo code, no valid OCL, I did not check but it should look similar

Jan

medini_1024169437

From CB perspective, medini is just another client using their API. We are partners, but not too many in CB know medini. So I do not expect that they will be able to help you.

What did you ask them?

Jan