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

Pages: 1 [2] 3 4 ... 167
16
surely calling a method to test for the existence of a property on an element couldn't have the side effect of actually just 'magically' creating that property?  That would be madness (!)

It's more that the command "Use Rectangle Notation" is hidden if your shape script doesn't need or use it. That's not madness; that's just being considerate.

17
General Board / Re: Adding attributes to MDG stereotype element
« on: May 30, 2018, 10:21:57 am »
The proper UML way to repeat attributes is to use generalization.

+1

If you have 50+ classes all with the same 4 attributes, that is a poorly designed class model. Create an abstract superclass with 4 attributes and inherit from it.

18
I'm not importing into the repository as a resource (I thought this was deprecated - may be wrong).

The old version of importing to resources was deprecated. That used to break out all the parts of the technology and import them into their respective tables (e.g. profiles imported into the t_stereotypes table). The new version of importing to resources imports the whole technology file undigested and then uses it as just another place to read technologies from at start-up. (I have no idea if what I just said makes sense)
It does make sense, Neil,

But presumably, if we do that then EVERYBODY has to use the same version of the MDG at the same time yes?  We allow multiple versions of the MDG to be "Live" at the same time. Can that still be done under the imported scenario?

Paolo

Presumably you do that by having some of your people using the technology at one location and the rest using the technology at a different location? Unfortunately, for imported technologies I don't think you can switch off the internal location, so yes that's the version that everybody will get.

19
I'm not importing into the repository as a resource (I thought this was deprecated - may be wrong).

The old version of importing to resources was deprecated. That used to break out all the parts of the technology and import them into their respective tables (e.g. profiles imported into the t_stereotypes table). The new version of importing to resources imports the whole technology file undigested, and then uses it as just another place to read technologies from at start-up. (I have no idea if what I just said makes sense)

20
But it would indeed be a great help if a locked diagram was ... locked(!). And it should be a very minor and simple change in Sparx.

That's a diagram centric view not a model centric view.  A diagram is a representation of a number of elements in the model.  Elements that can belong to anyone, not just the creator of the diagram.

And it is MUCH easier to hide a connector that you can see than show a connector that you can't see. If you open a diagram and see that a new connector has suddenly appeared, that means that there is new information in the model that the person who created the diagram wasn't aware of. If it belongs in the diagram, great; if it doesn't, hide it. Better that than opening a diagram and not knowing if there is new information that may need to be shown.

21
Bugs and Issues / Re: EA 14.0: Find in Browser odd behaviour
« on: May 23, 2018, 10:35:23 am »
It's full of sheep, snakes, and poisonous spiders.

We have never to my knowledge had a sheep in the office. We've had a couple of Redback spiders though, and one of the guys downstairs claims they saw a snake disappear into the skirting board near Roy's desk but I reckon it was more likely a Blue-tongue Lizard. You're right about the utes. I don't know what "tight stubbies" are but they sound like a 70s fashion so probably only found in Sydney.

22
I think that just setting the tick mark is not enough. You need to transfer to an empty Jet-formatted EAP (it's somewhere on Sparx site available for download). Check this forum for Jet4.

q.

EA now comes with a Jet 4 base model: "C:\Program Files (x86)\Sparx Systems\EA\EABase.eapx"

23
General Board / Re: Are Relationships Model Entities
« on: May 16, 2018, 09:35:22 am »
purely for display?

Absolutely not!

24
The zoom slider on the right of the status bar is a user preference that is additional to the other zoom controls. If you have a small monitor, you may want all your diagrams to be zoomed out - move the slider to the left. If you have poor eyesight, you may want all your diagrams to be zoomed in - move the slider to the right. This does not affect the way other people see the diagrams, it just redefines (for yourself only) what 100% zoom looks like.

25
Uml Process / Re: Security Classification for Table Columns
« on: May 15, 2018, 08:54:57 am »
You might be able to redefine the column stereotype to add a tagged value. Follow the instructions on this page:

http://www.sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/redefine_ster_other_prof.html

The stereotype you are trying to redefine is "EAUML::column". My main worry is that while it works with other stereotyped elements, I haven't tried it with stereotyped attributes and they have a slightly different mechanism internally. If it doesn't work, then I'm afraid you will just have to add the tagged values manually, as suggested above.

26
For layouttype="border" there are two arguments: name and location. For other layout types, there are either one, three or five arguments: name, width, height, X position, Y position.

27
I read it like:

This requires an additional argument to the addsubshape method

And indeed we see

   addsubshape("triangle","center");
   addsubshape("name","s");


That must be it no?

Geert
No, the description is technically ambiguous I could read it that way, but I could (reasonably) read it differently.  The absence of a formal syntax for that use case in BOTH the help system and the tooltip, makes it even more so.

FWIW, exactly such an ambiguity is what started me on this "modelling lark" four decades ago!  (Blame it all on James Martin)

Paolo

Geert is of course correct.

28
<<invokes>> and <<precedes>> were ICONIX extensions, so will still be available in the ICONIX use case toolbox.

29
My version is 14.0.1419 and have problem with even and junction when link with triggering rel to any other element

This is the first time you have mentioned "junction" so I assume it's a new issue. Junctions are a bit of a special case in ArchiMate because they aren't part of the metamodel but are a drawing artefact and need to be treated differently by the quicklinker; long story short, we are aware of the issue and are working on it. For now, please switch off the option at "Ribbon|Start|View|Preferences|Links|Strict Connector Syntax" to create connectors to and from junctions.

30
General Board / Re: 'Link' Connector type - did I imagine it ?
« on: May 09, 2018, 08:33:51 am »
Thanks @KP  - good to know how to (probably) make things backwards compatible. Could we have a note somewhere in the final V14 documentation to say that this has changed?

Nothing has changed. Except possibly the labels in the quicklinker (used to say "Link" or "Directed Link", now says "Association", but they're all Associations).

Pages: 1 [2] 3 4 ... 167