requirements copy

[nada]

Hello, if I would like to use the same tags and some attributes for a new requirements I can use Template of requirement or Convert linked element to a local copy. What is the difference between them? Thanks

[marcelloh]

I suppose it's because i'm not a native englishman, that I think about your question like "a lot of words, but what is Nada saying".  :-?

[Paolo F Cantoni]

Hello, if I would like to use the same tags and some attributes for a new requirements I can use Template of requirement or Convert linked element to a local copy. What is the difference between them? Thanks

Be careful, the "Convert" option (which in build 850 is named: Convert to Instance)  does NOT convert the existing element (from a Classifier) to an Instance of the Classifier, but creates a NEW instance from the Classifier and THEN replaces the Classifier in the diagram with the Instance.

It another example of an incorrectly named functionality.

Using a Requirement template will create a new occurrence of a Requirement Classifier when you drag the requirement tool onto the diagram.  The "Convert" will create a Requirement Instance - not the same thing.

HTH,
Paolo

[KP]

It another example of an incorrectly named functionality.

A better name would be?

[KP]

Hello, if I would like to use the same tags and some attributes for a new requirements I can use Template of requirement or Convert linked element to a local copy. What is the difference between them? Thanks

The easiest way to create a copy of an element (on a diagram) is to Ctrl+Drag it to a new place on the diagram.

[KP]

Hello, if I would like to use the same tags and some attributes for a new requirements I can use Template of requirement or Convert linked element to a local copy. What is the difference between them? Thanks

Be careful, the "Convert" option (which in build 850 is named: Convert to Instance)  does NOT convert the existing element (from a Classifier) to an Instance of the Classifier, but creates a NEW instance from the Classifier and THEN replaces the Classifier in the diagram with the Instance.

Actually, "Convert to Instance" and "Convert Linked Element to Local Copy" are different commands. The former, given a class on a diagram, will replace it on the diagram with a newly-created instance of the class. The latter, given a class from package A on a diagram in package B will create a copy of the class in package B which replaces the original class on the diagram. In both cases, connectors will copied to the new element. Obviously, these descriptions are a bit long as command names, so I'd still be happy to hear a better name for either command!

[Paolo F Cantoni]

It another example of an incorrectly named functionality.

A better name would be?

Not using the word convert...

The length or complexity of the name is not the problem.

Convert: to change (something) into a different form or properties; transmute; transform.

Conversion implies the changing of something not the creation of a new something.

I accept that I got the commands conflated, but the the issue has to do with the verb (in both cases).

I would (as you did in your explanations - hint, hint.  Notice how you didn't use the word convert once?) replace Convert with Replace (pun intended!).

Paolo

[KP]

No, "Replace" doesn't work for me. While it does suggest that a substitution is taking place, it doesn't convey the idea of anything being created. Any more ideas?

[Paolo F Cantoni]

No, "Replace" doesn't work for me. While it does suggest that a substitution is taking place, it doesn't convey the idea of anything being created. Any more ideas?

Then why did you use it?  

Seriously, though.  I do think replace is the best available solution, it "does the least harm".

For example:  Convert to Instance could become: Replace with New Instance;

while: Convert Linked Element to Local Copy could become: Replace Element with New local copy.

Which, I think, explicitly embody the explanations you made above.

Paolo

[KP]

For example:  Convert to Instance could become: Replace with New Instance;

Better but still not there. You see I'm currently making changes to the command so that something like a SysML Block which supports properties rather than instances would have the command "Convert to Property". With your suggestion, that would become "Replace with New Property" which I don't like, but I think my issue is with the overloading of the word "Property" - the "Replace with New" bit is fine  :-/

Thanks for your help anyway...

[son-of-sargasso]

OFDS!

"Create a new repository element as a copy of this foreign one in the current repository branch and then replace this diagram widget with an instance of that element."

Get back to work, the lot of you. And while you're there fix the fact that "Copy" on the attribute popup doesn't respect the Const setting!!!

grrrrrrrrrrrrr
bruce

[Yves C]

In both cases, connectors will copied to the new element.

In build 834, "Convert linked element to local copy" doesn't copy all connectors but only those in the local diagram. Is this the correct behavior ?

[KP]

In both cases, connectors will copied to the new element.

In build 834, "Convert linked element to local copy" doesn't copy all connectors but only those in the local diagram. Is this the correct behavior ?

Yes