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

Difference and Scripting: Dependency, Requires, and Uses

medini_1028110424

Hi Jan,

Hope you aren't getting tired of all my questions - hopefully other people will have similar questions and will benefit too.

Can you tell me if there are any major differences between Dependency, Requires, and Uses? I am assuming they are all similar in the background but are more defined; for example, requires can only be used between functions? Is this somewhat correct?

Also, can you give a super simple example of scripting in a requires relation between new_func1 and new_func2 from below?

var new_func1 = Factory.createElement(receptor,Metamodel.sysml.SysMLActivity);

new_func1.typeCode = 'function';

new_func1.name = 'Function_1';

var new_func2 = Factory.createElement(receptor,Metamodel.sysml.SysMLActivity);

new_func2.typeCode = 'function';

new_func2.name = 'Function_2';

new_requires_connect = Factory.createRelation(new_func1, new_func2, Metamodel.sysml.SysMLConnector); (I know the bold is incorrect, just for showing purposes)

I do not know if this is the correct approach or not; could you please advise?

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hi Anthony,

I never get tired of such things, don't worry :-)

Your analysis is right, all three relationships are in principle "SysML Dependency" relationships with different stereotypes. A "normal" dependency (no stereotyp) can be drawn between any SysML Element while <<uses>> and <<requires>> just between functions. However, that's just a limitation on the surface. You may for example draw a normal <<dependency>> to a part, then change the stereotype to <<uses>> or you may draw a <<uses>> relationships between two functions, remove the stereotype, re-target the connection to a par and rename the stereotype back to uses.

Attached an excerpt from a presentation on function net modeling (PDF).

Your script code looks fine as well, just use a different meta class here like this:

var p1 = Factory.createElement(scope, Metamodel.sysml.SysMLPart);
p1.name = "p1";
var p2 = Factory.createElement(scope, Metamodel.sysml.SysMLPart);
p2.name = "p2";
var d1 = Factory.createRelation(p1, p2, Metamodel.sysml.SysMLDependency);
d1.stereotype = "uses";

Happy Scripting

Jan

All comments

medini_1024169437

Hi Anthony,

I never get tired of such things, don't worry :-)

Attached an excerpt from a presentation on function net modeling (PDF).

Your script code looks fine as well, just use a different meta class here like this:

var p1 = Factory.createElement(scope, Metamodel.sysml.SysMLPart);
p1.name = "p1";
var p2 = Factory.createElement(scope, Metamodel.sysml.SysMLPart);
p2.name = "p2";
var d1 = Factory.createRelation(p1, p2, Metamodel.sysml.SysMLDependency);
d1.stereotype = "uses";

Happy Scripting

Jan

medini_1028110424

Hey Jan,

Perhaps I am missing the latest Factory, I tried the latest in the factory forum but I do not see:

Metamodel.sysml.SysMLDependency

Could you please advise?

Thank you!

medini_1024169437

Well, should be in this thread but I'll attach it here for your convenience.

Happy Scripting

Jan

medini_1028110424

Thank you!!!!!! Just fyi, the factory in the thread is a 28 KB file; perhaps an older version?

medini_1024169437

Oops, indeed I forgot to upload the update. Many thanks

Jan

medini_1040753747

What is the syntax to see if a SysMLPart is dependent on another SysMLPart? For example, how would I correct this?...

return (p1.dependentOn.contains(p2))?true:false;

Is there a method get dependencies to other elements (or dependencies from other elements)?

medini_1024169437

Hi Johan,

that depends a little bit on which relations you want to consider. medini has many of them and they are semantically different,

allocations, plain traces, containment, connectors, ... there is currently nothing that "aggregates" all relations.

Though it should be possible to script that I guess.

Happy Scripting

Jan

medini_1040753747

To be specific... I have 2 objects that can be either SysMLActivity, SysMLPart, SysMLFlowPortUsage, or SysMLPortUsage.

And I just want to determine if one object is dependent on the other. Is there a method to determine this relation?

medini_1024169437

So that would include "Is a port attached to a given part" or "is a part a sub-element of another part",

or "is an activity contained in a certain part" or only "is there any allocation in between" or "any trace"?

Jan

medini_1040753747

Yeah that sounds correct. Except maybe checking for trace link could be a totally separate method (which I would be interested in using as well).

medini_1024169437

Hi Johan,

there is currently no such easy to use syntax as mentioned in your original question, though the information are all there. Some of what you are seeking for is implemented in the tool, typically in the "Related Elements" menu but each of those functions is a separate thing and its not available for scripting.

So the only solution I currently see is to write your own functions or your own object mapping which you initially fill yourself, so you may use the syntax you mentioned above.

Happy Scripting

Jan

medini_1040753747

Re-reading your response... I think we are referring to different things with respect to my initial dependency question (I figured out the trace link relationship). I am interested in the "Dependencies to other elements" and "Dependencies from other elements" relationship. So in this example, the SysMLActivity is dependent on the SysMLPart:

What is the javascript syntax to check this relationship?

medini_1024169437

Ah, okay. These are instances of Metamodel.sysml.SysMLDependency. You can find (navigate) via SysMLElement.dependencies which is a collection of the element type mentioned before.

To create them please check the factory.js and the TestFactory.js. An example:

var d1 = Factory.createRelation(p1, p2, Metamodel.sysml.SysMLDependency);
d1.stereotype = "custom";

Please note that in case you *allocate* elements to each other, its a special sub class named SysMLAbstraction.

Happy Scripting

Jan

medini_1040753747

So in my example, if I have the SysMLActivity and the SysMLDependency (that is connecting it to the SysMLPart), how do I grab the SysMLPart?

medini_1024169437

Well, assuming that you have only one relation, that would be:

OCL:

self.dependencies->first().the_target_element

JS:

self.dependencies.get(0).the_target_element;

Happy Scripting

Jan