How to create DCFailureModeEntry with the Factory

Question

Hi all,

I want to create some additional DCFailureModeEntry to "emulate" the "Split Evaluation Group" feature.

I'm running into to Problems:

1) What is the scope for createMethod? I assume the failureModes member of the owning DCComponentEntry.

2) When I'm executing the following code:

var dcEntry = Factory.createElement(compEntry.failureModes, Metamodel.dc.DCFailureModeEntry);
I get the following error message: "
Cant find method de.ikv.medini.util.emf.edit.MediniModelModificationUtil.addValueOfFeature(org.eclipse.emf.common.util.ECollections$UnmodifiableEList,org.eclipse.emf.ecore.impl.EReferenceImpl,de.ikv.analyze.metamodel.dc.impl.DCFailureModeEntryImpl)."When looking into the factory.ps I can find the following fragement:function __createDCFailureModeEntry(scope) {

if (!scope) {

console.error("Scope is undefined in create method!");

}

var entry = DCFactory.eINSTANCE.create(Metamodel.dc.DCFailureModeEntry);

// XXX changing containment is not supported in 3.1.0 API

var feature = Metamodel.FMEA.ComponentEntry.failureModes;

MediniModelModificationUtil.addValueOfFeature(scope, feature, entry);

return entry;
}Does this mean that I can not add DCFailureModeEntries? Or do I do something completey wrong?
Thanks a lot in Advance for your help.
Regards,Michael

medini_1024169437 · Answer

Hello Michael,

it's good to see some power scriptwriters at work. Though it gives me some headache. As mentioned the FMEDA / DC worksheet especially when it comes to split groups and other fancy options like individual metrics and stuff is very difficult to script and we have no examples for that and no good guidance.

Please be careful here.

Happy Scripting (anyway)

Jan

medini_1035261689 · Answer

Hi all,

I have to correct some informations I provided to Peter (who has forwarded) it to this thread.

If you want to create a new DCFailureModeEntry then you need the corresponding DCComponentEntry, which will be the first Parameter for the createElement call.

You MUST NOT try to add the new object into the failureModes array. This will cause an Exception (which I have overlooked). The correct call is just:

var dcEntry = Factory.createElement(compEntry, Metamodel.dc.DCFailureModeEntry);

I assume the createElement is somehow context sensitive and does know where to store the new element. In out example, into the failureModes Array of the DCComponentEntry.

After filling the other properties, e.g. element, the new DCFailureModeEntry Shows up correctly in the Model Browser and also in the "Related Elements" information.

In the next step I will try to "emulate" the split/remove Evaluation Group. I will post a new comment when I have been sucessfull.

Best regards,

Michael

medini_1036016653 · Answer

Good morning all,

Michael actually was able to solve it and I hope it is fine to share his solution here (for future reference):

var dcEntry = Factory.createElement(compEntry, Metamodel.dc.DCFailureModeEntry);
compEntry.failureModes.add(dcEntry);

He gave the remark that the second line is important (and necessary) in order to ensure that the newly created failure mode entry is linked/appended to the FMEDA component's failure modes.

The further steps should be "simply" assigning the evalutionGroup, but I haven't heard back yet.

Best regards and nice job Michael!

Peter