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 - PeterHeintz

Pages: 1 ... 22 23 [24] 25 26 ... 37
346
Now I realized the _SourceNavigable and the _TargetNavigability attribute is represented as a tag as expected/I was afraid?.
I can even change the Navigability within the properties roles dialog, however now this settings are out of sync with the tags. :'(

347
Ok!
Setting the attribute on the stereotype rather than on the meta class works.

I will issue a bug because neither user guide not profile helper does what is implemented at the end.

348
Bugs and Issues / Re: Setting _lineStyle has no effect
« on: June 07, 2016, 06:09:48 pm »
Ok!
Setting the attribute on the stereotype rather than on the meta class works.

I will issue a bug because neither user guide not profile helper does what is implemented at the end.

349
General Board / Re: SysML allocated note
« on: June 07, 2016, 05:52:24 pm »
I have not used that feature yet, but I am interested in your investigation results.
SysML in EA is sometimes mystic. ::)

350
General Board / Re: SysML action pin info on diagrams
« on: June 07, 2016, 05:47:56 pm »
Yes that is as it is.  :'( :'(
I remember a post also raising the action pin direction information issue and I would also very much appreciate to have EA showing the direction as done for ports.

351
As I remember yes.
But I did not find any response from Sparx in my mailbox.
So I will post it again.

352
On meta class “Association" I set _SourceNavigable to "Navigable" and _TargetNavigability  to "Unspecified" but when using my stereotype extending the meta class _SourceNavigable is set to "Non-Navigable" and _TargetNavigability  is set to to "Navigable".

353
Bugs and Issues / Setting _lineStyle has no effect
« on: June 06, 2016, 07:39:07 pm »
On meta class “Association I set _lineStype to treeV but when using my stereotype extending the meta class the line style Orthogonal-Square is used instead.

354
General Board / Re: An element several times on a diagram?
« on: June 06, 2016, 06:49:37 pm »
Hello Paulo,
I appreciate those discussions, sharing opinions, agreements and disagreements very much.
According to your definition I have not tree and probably even not a lattice as well.

This is because I do not have a parent child relation (at least from my perspective), it is basically boolean algebra connection events to logical gate (and, or,...).

In some other thread I read something like “Any model is wrong but some are useful” what fits very much to my mind set. According that, we could say on a very dogmatic way, all of us are lying.
So for instance what the project browser shows of EA is wrong as well, but useful.

For me a diagram arranging elements in a tree style way even if the elements do not have a tree relation, is ok as long as it is useful instead of confusing.

I decided to arrange the elements tree style but allowing cross branch connections is the way I intent to go (only one element link per diagram).

355
Well, I did neither use BPMN not Archimate ut to now.
But I assume that you will find all this relations as well, but maybe not with the right wording of your links.
Just figure it out.

358
General Board / Re: An element several times on a diagram?
« on: June 02, 2016, 07:01:09 pm »
Thank you Paolo,
I also thought about using instances or objects however I have (only sometimes) just exactly the same thing on different possions in the tree.

I agree with both Geert and Glassboy even they argue somehow in opposite direction.
A diagram is not the model, it is a view on model content for humans and it should be as understandable as possible.

Having the same thing several times on a diagram introduces the risk to get the humans confused (maybe just by not realizing the two boxes are the same thing). One the other hand having lost of connector going all around the diagram makes reading/understanding difficult as well (I know there is Suppress Line Segment).

A fault tree is a technic to answer the question what can cause something undesired. This can be modeled and shown in many ways but a fault tree is just a graphical representation of that information expected to be in a tree. The users more focus on what causes what and there is not so much focus on what is the same and what is different.

359
General Board / Re: SysML requirements, block compartments
« on: June 02, 2016, 06:10:17 pm »
I also use several times attributes rather than property values (even I am not sure if this is SysML), just because I am not able to define values for the value properties when used somewhere.

The update of the block compartments I belief do not depend on time, but on diagram refresh triggers which are not fired but others user triggers are fired late. To be sure what is happening I always verify what is in the project browser?

When I do SysML modelling I only have role names if something is there more than once (just go with the bug). This is because of role names in my models are often noises but no information.

Show element types, you can enable under Options/Objects/Port and Part types visible by default.

The “Structural elements” command is the only way (AFAIK) to do that. Once done and deleting some relations on the BDD means, you have to delete your properties manually (“Structural elements” is one short).

360
Bugs and Issues / Re: Diagram List View and SysML Memo content
« on: June 01, 2016, 10:49:13 pm »
Due to the fact that Tagged Values cannot be edited as easy as element alias and notes, I do not use those tags as specified in SysML. ID I put in alias (autogen) and description in notes.
If a situation would come when I have to strictly comply to SysML, I would just cope all that stuff to the tags by a script (do not see that situation in near future for me).


Pages: 1 ... 22 23 [24] 25 26 ... 37