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

Requirement Diagram additional content

medini_1066727069

Hi all,

I´m trying to generate requirement diagrams automatically based on the linking "Contributes to". This is currently working fine.
Now I´m trying to display additional information within the shapes

like:

- Description Text

- Status

- Parent Requirement model

- and some more

Does anybody have an idea how to display this information?

Other than this i want to update the style of the connections to avoid obstructions, has anyone had a similar issue before?

Thanks in advance
Christian

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1079531107

Hi Christian,

The Cybersecurity templates have a feature to display labels at Attack Tree events for showing additional information, see "Best Practices Template (Cybersecurity)" on the Help > Online Support Page > Sample Projects. It's contained in .lib/Paint Attack Trees.js, function createFeasibilityLabel().

A similar functionality exists in the "Aero Cybersecurity Template DO-356A v25.1a"

Maybe you can adapt it to your requirements diagram needs.

Not sure what you mean with "update the style of the connections" - I don't have experience with that.

Cheers, Nils

medini_1024169437

Christian, you ma yuse the Atribute View to navigate from the diagram to "edges" to at least see which attributes you can change for any diagram connector.

Happy Scripting

Jan

medini_1063548292

Hallo,

I guess this is only possible a for a "regular" diagrams. ( create a note, update shapes, .. ), right ?

I once tried to do similar (through batch script) with a Dependency diagram editor (SysMl, Cause-effect ) as it contains a diagram at the lowest layer, but got and Error that I cannot modify the properties of the diagram or its shapes.

"Cannot modify resource set without a write transaction"

Marian

medini_1066727069

Hi all,

thanks for the feedback.

i tried to display some elements via decoration node:

var childTypes = ["5015", "5017", "5019"];

for (var i = 0; i < childTypes.length; i++) {

var decNode = NotationFactory.eINSTANCE.create(Metamodel.notation.DecorationNode);

decNode.type = childTypes[i];

decNode.visible = true;

shape.children.add(decNode);

}

Those are the standard DecorationNodes. I thought there may some additional once and tried out different other types. Unfortunatelly i received error messages on all of the numbers i tried.

I´ve also checked my code for setting the avoidObstructions

// avoidObstructions

try {

edge.avoidObstructions = java.lang.Boolean.TRUE; // Java Boolean

console.log(" avoidObstructions: " + edge.avoidObstructions);

} catch (e) {

console.log(" ⚠ avoidObstructions: " + e);

}

When i have a look inside the attributes it set correctly.

Once I open the diagram I had a look on the same Element the property avoidObstructions is unset:

Looks like the diagram connections are updated once a diagram is opened.
Is there a way to keep the original settings?

Best regards Christian

medini_1024169437

Hm, this is strange, maybe the modification you do is not "consistent" so its reset, but I dont think it is ignored when opening the diagram. I suppose you are working on a local project? or is it a shared one?

Jan

medini_1066727069

Do you know which attributes I need to set in order to avoid inconsistency?

I've tried to open the diagram during script execution and modify the attributes afterwards to ensure that most of the attributes are set already.

Since the connections are drawn automatically base on the contribution, I thought this may help. But it seems that opening diagrams is not a synchronous process, thus the execution in a single script seems not to bring a solution on my script.

medini_1024169437

Hello Christian,

I do not have myself but I rely on others here in the forum. As Nils mentioned, the Cybersecurity template is a good source as this one manipulates diagram objects on the fly (adding notes, coloring shapes). An I am pretty sure it works, whether the diagram is open or not. However, I am not sure it manipulates "edges/connectors" at all.

@Nils, do you know?

Happy Scripting

Jan

medini_1063548292

HI Christian,

I did try to excessive it long time agoubut :

avoid obstructions works ( and presrves th settog) when thI configure it through the properties, do it yourself and compare the differemnce if donethrough script I suscpect some missing property ...
decoration nodes:
this one is a but special as inside a medini every ediPart is rendered based on the view type .
Every diagram ( sysml , fta , rbd m, requirements,.. ha its own registry with "supported types" and if the corresponding type id is not found it is marked as an invalid View.
So in providing extra information through as decrationNode might bericky as it mus have element, parent and type correctly se
You can inspect this when in debug mode using ShowEditPartDetails

If you want you can provide reliably more details using a Note/Text shape eventually with NoteAttachment ( Connector). I believe that the solution's in cybersecurity uses Note + NoteAttachment
there are available default types for the text ediParts

//$EXPERIMENTAL$ demo of generic non-number diagram views
//execute this on PJDiagram
var demo = {
 /*appplicable for shapes, evey shape must have 2 children decorationNode decorationTypes*/
 types: ["Note", "Text", "cylinder", "diamond", "hexagon", "octagon", "oval", "pentagon", "rectangle", "rectangle3D", "roundRectangle", "shadowRectangle", "triangle"],
 attacherType: ["NoteAttachment"],
 decorationTypes: ["DiagramName", "Description"],
 iconTypes: ["imageIcon"]
};

var NotationFactory = Metamodel.notation.Shape.ePackage.eFactoryInstance;
var diagram = selection[0].diagram;
var textshapes =
 demo.types.forEach(function noteIt(typeKey) {
 var shp = NotationFactory.create(Metamodel.notation.Shape);
 shp.type = typeKey;
 shp.element = null;
 demo.decorationTypes.forEach(function decorIt(decType) {
 var decNode = NotationFactory.create(Metamodel.notation.BasicDecorationNode);
 decNode.type = decType;
 decNode.element = null;
 shp.children.add(decNode);
 });
 //layout constraints, mandatory, default x/y 0.0 , w/h = -1
 shp.layoutConstraint = NotationFactory.create(Metamodel.notation.Bounds);
 // optional, fontName = "Segoe UI", fontColor (Integer), fillColor(Inetger)
 // optinal styles. added styles.add()... line style, text style 
 //if not valus are set to default (from Shape class)
 shp.description = "Demo of shape type ::" + java.lang.String.valueOf(shp.type) + "\n children(" + shp.children.size() + ")";
 diagram.children.add(shp);
 return shp;
 })

last note eremaybe some better options but you would have to spend some time playing around the configurations of type element etc.... I accidentally populated also an element property into those shapes and it somehow did not invalidate the view but probably good to do this without knowing what it effects
If you update diagram view form a script and it will not reflect in the opened editor it is best to reopen the editor or trigger diagram editor viewer's refresh so that all ediparts are synchronized with the views on the diagram.

PS: I also somehow managed to overcome the "Cannot modify resource set without a write transaction" problem when trying to create similar shapes on an dependency diagrams ... So now I can even place new shapes ( notes, ...) onto the cause-effect and sysml dependency diagram or modify the exiting shapes:)

Happy Shaping,

Marian

medini_1024169437

Great post, thanks Marian (despite you seems to have written it in haste :-)

Jan

medini_1024169437

Just to add that I played with marians idea to compare two edges after I manualyl changed them via diagram and for me the onyl difference having set "avoidObstructions" manually to true or false via the poperties panel is really just that poperty. And setting/unsetting it via a script, either with open or closed diagram is working fine for me. So I wonder whats he difference in your case Christian.

Jan