Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - ngong

Pages: 1 [2] 3 4 5
16
Bugs and Issues / Alias does not show
« on: May 19, 2017, 03:03:01 am »
What I did:
Placing several InteractionOccurence elements on an InteractionOverview diagram and give some InteractionOccurence an Alias text. Now switch on in the diagrams properties "Use Alias if Available".

What I expected:
to see the Alias text on the diagram instead of the names of InteractionOccurence elements.

What I got:
I still see the names of InteractionOccurence elements.

Doing the same on the same diagram e.g. with Requirement elements works as expected.

17
Bugs and Issues / Re: Problem to check-in to PTC
« on: May 11, 2017, 11:28:42 pm »
I intensified my analysis and found out, that the characterset idea was not the solution. It was a lengthy line that did not go away when formatting the XMI file using Eclipse formatter. For some reason, EA writes the UML:TaggedValue tag="$ea_attsclassified" and the UML:TaggedValue tag="$ea_oprsclassified". For one UML:Class in the XMI holds line 21222 and line 21223 each with 16695 characters.

I substituted that class by a new one and got rid of the problem.
What are these tags for?

18
Bugs and Issues / Re: Problem to check-in to PTC
« on: May 10, 2017, 09:11:29 pm »
Thank you, qwerty.

the failure screenshot can be looked at here: http://picpaste.de/2017-05-10-NoCheckIn-aNLWHHyE.PNG

Yes, the failure seems to be identified: PTC is justifying the new package xml as binary and refuses to check it in, over a text file. (Strange!)

As my current user account at PTC is not strong enough to view the link you, qwerty, supplied (I love open source) I found this link:
https://www.ptcusercommunity.com/thread/40277

They propose - as a workaround - to format the XML. However, it was formatted and I formatted it newly using Eclipse XML plugin. Nothing solved the issue.
Could it be a characterset issue?

19
Bugs and Issues / Problem to check-in to PTC
« on: May 10, 2017, 06:37:13 pm »
For some weeks now, I am using "Package Control" together with PTC, prior to roll it out in the team. Once you get used to it, it seems to be quite productive.
However, today I tried to check-in a package and got the message MKS125628: Could not compute text delta ... (see attached).
I repaired the data base, compacted it. But nothing helped.

Any suggestion?

(how to attach a screenshot?)
The whole failure message from PTC is: MKS125628: Could not compute text delta. Likely cause is that you are attempting to check in binary data into a text archive.
I am using EA13 producing into an .eap file, PTC/Integrity 10.7.0.7925 with APIU 4.15.7925.

20
Automation Interface, Add-Ins and Tools / How to find a role by name?
« on: November 18, 2016, 10:06:26 pm »
Sometimes I remember just a name. Trying to find it with Simple or Extended find does not reveal it. What helps is, looking through all diagrams and eventually I catch it, e.g. a name of a Role of an Aggregation.
Is there an easier way to locate that name?

21
Automation Interface, Add-Ins and Tools / Re: xmi:id how to?
« on: November 18, 2016, 09:54:47 pm »
Thank you very much for this superb answer, Simon.
The XMI snippet about a Tag export from SysML to XMI looks very promising.
I will investigate it. Do you think I can repeat that in plain UML?
I must say, I have not understood it fully, yet. Could not identify the Tag-name and Tag-value.
One fear of mine: Is XMI spec silent about this? Does it have to be covered by vendor-extension?

22
Automation Interface, Add-Ins and Tools / Re: xmi:id how to?
« on: November 18, 2016, 12:32:30 am »
Hi, Simon

everyone in the UML world knows that XMI like UML is an OMG standard. That is not the point.

XMI uses an xmi:id attribute as a surrogates for each UML element, uniquely. From the XMI standard afaik tool vendors like Sparx may choose their algorithm to find a unique code given to xmi:id in order to uniquely identify a UML element.

XMI is ment to be vendor independent.

I am not sure whether Tags are properly reflected in the XMI exported by EA. I tried to find that in the XMI 2.4.1 spec but without success in the time I could spend for it. Tags are exported by EA solely in the vendor specific part of the XMI albeit they are part of the UML specification. I would expect Tags in the UML part of the EA XMI export, not the vendor specific part - but I am not sure about this, yet.

On import of XMI, in general the EA tool excepts any value for xmi:id attribute, as long as it is unique per UML element. This is imported for XMI interchange.

For this general rule EA import has at least one exception: Tags - in the vendor specific part of the XMI, that is not standardized for exchange. xmi:id attributs in this part - at least for tags - have to follow the Sparx way of unique key generation.

My question is: why violating the requirements for xmi:id attributes in the vendor specific part? And if there is a good reason: am I able to reflect that key generation in my process tools?

Now these questions are rhetorical as I have accepted not to get a sufficient answer - there are proprietary algorithms in the vendor specific part of XMI export.

23
Automation Interface, Add-Ins and Tools / Re: xmi:id how to?
« on: November 15, 2016, 08:43:35 pm »
Yes, thank you qwerty and Simon,

seems my knowledge comes close to what is known.

About the idea not using the API but XMI: I have a dream: XMI holds what is in the model - and - in an openly specified way. My lifecycle tools would work regardless what modelling tool to use. We are getting closer.
And I agree: xmi:id should be a surrogate, unique but without further information.

I did what you said: getting information about the xmi:id from experience exporting packages.

I was wondering whether there is some documentation about it. I could not find any.

Rolf



24
Automation Interface, Add-Ins and Tools / xmi:id how to?
« on: November 14, 2016, 06:03:45 am »
I have been successful so far in generating xmi files for to import in an eap file. So far it work by keeping xmi:id just unique, no more rules. However, now I started to produce tags against some profile. When I use an arbitrary - but unique - xmi:id for a tag element, it will not be imported.
What I did was manually enter tags in the eap file and then exporting the package, copying the xmi:id's to my file to get imported. That works.
What I found out so far is, that I shall not change the first 24 characters for the tag's xmi:id. For uniqueness I may change the last 17 characters.

Is there anywhere a rule that I can follow, to successfully produce the first 24 characters of an xmi:id?

Here you can see the xmi file that can be imported successfully. E.g. when I change the beginning of the xmi:id EAID_EC46D93B_5E30_7e5e_0000_000000000001 the tag Bit_No will not be imported.

Code: [Select]
<?xml version="1.0" encoding="windows-1252"?>
<xmi:XMI xmlns:uml="http://www.omg.org/spec/UML/20110701" xmlns:xmi="http://www.omg.org/spec/XMI/20110701" xmlns:SignalProfile="http://www.sparxsystems.com/profiles/SignalProfile/1.0">
<xmi:Documentation exporter="Enterprise Architect" exporterVersion="6.5"/>
<uml:Model xmi:type="uml:Model" name="EA_Model">
<packagedElement xmi:type="uml:Package" xmi:id="RSCID_Signals" name="Signals">
<packagedElement xmi:type="uml:Interface" xmi:id="RSCID_Signal1" name="Signal1" isAbstract="true"/>
<packagedElement xmi:type="uml:Interface" xmi:id="RSCID_Signal2" name="Signal2" isAbstract="true"/>
</packagedElement>
<profileApplication xmi:type="uml:ProfileApplication" xmi:id="profileap_13E3FB92-0">
<appliedProfile xmi:type="uml:Profile" href="http://www.sparxsystems.com/profiles/SignalProfile/1.0#13E3FB92-0"/>
</profileApplication>
</uml:Model>
<xmi:Extension extender="Enterprise Architect" extenderID="6.5">
<elements>
<element xmi:idref="RSCID_Signal1" xmi:type="uml:Interface" name="Signal1" scope="public">
                <properties documentation="comment to Signal Function of Signal1" isSpecification="false" sType="Interface" nType="0" scope="public" stereotype="Signal" isRoot="false" isLeaf="false" isAbstract="true"/>
<tags>
<tag xmi:id="EAID_EC46D93B_5E30_7e5e_0000_000000000001" name="Bit_No" value="3" modelElement="RSCID_Signal1"/>
<tag xmi:id="EAID_9A779570_3D05_a03d_0000_000000000002" name="Byte_No" value="1" modelElement="RSCID_Signal1"/>
<tag xmi:id="EAID_640BFE5F_7DD4_4a7d_0000_000000000003" name="Cycle Time" value="CycleTime_100#NOTES#Values: CycleTime_40,CycleTime_100,CycleTime_1000,CycleTime_10000,NoCycleTime&#xA;" modelElement="RSCID_Signal1"/>
<tag xmi:id="EAID_04C5B725_62DA_ee62_0000_000000000004" name="Default" value="6" modelElement="RSCID_Signal1"/>
<tag xmi:id="EAID_A1E56D61_FA76_75fa_0000_000000000005" name="direction" value="s#NOTES#Values: r,s&#xA;" modelElement="RSCID_Signal1"/>
<tag xmi:id="EAID_7DCA38DC_C011_cdc0_0000_000000000006" name="Launch Parameter" value="LaunchParameter_20#NOTES#Values: LaunchParameter_10,LaunchParameter_20,LaunchParameter_100,LaunchParameter_200,NoLaunchParameter&#xA;" modelElement="RSCID_Signal1"/>
<tag xmi:id="EAID_462950BD_42D2_6942_0000_000000000007" name="Launch Type" value="CyclicAndChange#NOTES#Values: Cyclic,CyclicAndChange,Spontanious,None&#xA;" modelElement="RSCID_Signal1"/>
<tag xmi:id="EAID_034EE602_6F17_866f_0000_000000000008" name="Length" value="3" modelElement="RSCID_Signal1"/>
<tag xmi:id="EAID_736065D1_2526_7c25_0000_000000000009" name="Not_Available" modelElement="RSCID_Signal1"/>
</tags>
                <xrefs value="$XREFPROP=$NAM=Stereotypes$NAM;$TYP=element property$TYP;$VIS=Public$VIS;$PAR=0$PAR;$DES=@STEREO;Name=Signal;FQName=SignalProfile::Signal;@ENDSTEREO;$DES;$SUP=&lt;none&gt;$SUP;$ENDXREF;"/>
</element>
<element xmi:idref="RSCID_Signal2" xmi:type="uml:Interface" name="Signal2" scope="public">
                <properties documentation="comment to Signal Function of Signal2" isSpecification="false" sType="Interface" nType="0" scope="public" stereotype="Signal" isRoot="false" isLeaf="false" isAbstract="true"/>
<tags>
<tag xmi:id="EAID_EC46D93B_5E30_7e5e_0000_000000000010" name="Bit_No" value="0" modelElement="RSCID_Signal2"/>
<tag xmi:id="EAID_9A779570_3D05_a03d_0000_000000000011" name="Byte_No" value="1" modelElement="RSCID_Signal2"/>
<tag xmi:id="EAID_640BFE5F_7DD4_4a7d_0000_000000000012" name="Cycle Time" value="CycleTime_100#NOTES#Values: CycleTime_40,CycleTime_100,CycleTime_1000,CycleTime_10000,NoCycleTime&#xA;" modelElement="RSCID_Signal2"/>
<tag xmi:id="EAID_04C5B725_62DA_ee62_0000_000000000013" name="Default" value="27" modelElement="RSCID_Signal2"/>
<tag xmi:id="EAID_A1E56D61_FA76_75fa_0000_000000000014" name="direction" value="s#NOTES#Values: r,s&#xA;" modelElement="RSCID_Signal2"/>
<tag xmi:id="EAID_7DCA38DC_C011_cdc0_0000_000000000015" name="Launch Parameter" value="LaunchParameter_100#NOTES#Values: LaunchParameter_10,LaunchParameter_20,LaunchParameter_100,LaunchParameter_200,NoLaunchParameter&#xA;" modelElement="RSCID_Signal2"/>
<tag xmi:id="EAID_462950BD_42D2_6942_0000_000000000016" name="Launch Type" value="CyclicAndChange#NOTES#Values: Cyclic,CyclicAndChange,Spontanious,None&#xA;" modelElement="RSCID_Signal2"/>
<tag xmi:id="EAID_034EE602_6F17_866f_0000_000000000017" name="Length" value="5" modelElement="RSCID_Signal2"/>
<tag xmi:id="EAID_736065D1_2526_7c25_0000_000000000018" name="Not_Available" modelElement="RSCID_Signal2"/>
</tags>
<xrefs value="$XREFPROP=$NAM=Stereotypes$NAM;$TYP=element property$TYP;$VIS=Public$VIS;$PAR=0$PAR;$DES=@STEREO;Name=Signal;FQName=SignalProfile::Signal;@ENDSTEREO;$DES;$SUP=&lt;none&gt;$SUP;$ENDXREF;"/>
  </element>
</elements>
</xmi:Extension>
</xmi:XMI>

25
General Board / Re: How to make property type visible.
« on: December 08, 2014, 09:31:50 am »
Works, thank you Phil.

26
General Board / How to make property type visible.
« on: December 08, 2014, 06:20:55 am »
SysML: I placed a property in an internal block diagram by dragging a block in that diagram expecting to see some text like /PropertyType inside that block. But it did not appear.  :-[

Probably I am too blind to find the regarding checkbox. Can someone help me here and point me to a solution? :)

I am using EA11.1112.

Rolf

p.s. in the Sparx example I found some properties which show their type but cannot tell the difference to properties which hide their type.

27
General Board / How to delete an Association from the model?
« on: October 11, 2014, 02:16:07 am »
EA 11.1.1112
What I did:
put 2 classes on a class diagram, put an association in between.
deleted the association by right-clicking it and clicking on the red cross next to the word "Delete".
Deleted one class from the diagram by selecting it and using the delete button. (It is still part of the model)
Draw the deleted class from Project Browser back on the class diagram.

What I expected:
Two unrelated classes.

What I got:
The association appeared back, too. It is still part of the model. How can I definitely delete an association from the model?

Work around:
Put a third class on the diagram. Drag the association from one of the two other classes to the new one. Delete the new one by selecting it in Project Browser and using the right-click-Delete.

Any one to know a more straight forward way for deleting an association not only from a class diagram but from the model?

28
General Board / move a message from one liveline to the other
« on: July 14, 2014, 03:35:21 am »
Dear EA experts,
I am using sequence diagrams to explain use-cases.
I do that in two steps:
1. create a somewhat "generic" sequence, that is: leave types and formal parameters of operations in for message definitions.
2. copy that generic sequence to a number of fully explored examples, changing any variability to fixed valued messages, e.g. "interger" to 5, Color to blue, TimeSpan to 5s.

Now the problem: Sometimes I have to exchange a class by a more specific one and have to move one end of all messages from the old to the new lifeline.
This gives me a hard time: in 4 of 5 cases I cannot select the message end but exidentially select the whole lifeline.
Is there any trick to select the end of the message for sure?

Any help welcome.

29
General Board / Re: How to connect to an attribute or operation
« on: July 05, 2014, 03:42:55 pm »

30
General Board / How to connect to an attribute or operation
« on: July 05, 2014, 02:42:25 pm »
In this http://community.sparxsystems.com/white-papers/623-95data-mapping-in-uml example I found the neat feature to source a <<represents>> dependency from an operation to something else.
A nice right square bracket is drawn right to the attribute/operation at the source of the arrow.

How can I accomplish this?

If I try myself the dependency link alwas starts from the complete interface instead of a single attribute or operation.

Pages: 1 [2] 3 4 5