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 ... 167
And don't forget that you can use intellisense. Unfortunately, when typing a SQL statement like this into EA's SQL builder

select c.Connector_ID as id, from t_connector c where"External Reference"

you don't get intellisense when you type c. but if you type t_connector. then you will see all the fields available in that table.

General Board / Re: Mind map connectors
« on: June 21, 2018, 02:17:16 pm »
Nothing to do with shape scripts, it's the nature of Bezier connectors. Bezier connectors have three points: the two end points and a control point that determines how far the line bends (visible if you select the connector). If you select and move both the source and target diagram objects at the same time, all three Bezier points will move by the same amount. If you only move one end, the control point won't move, so the line will bend to a different degree and you will probably need to adjust the control point manually.

The problem:
- In my MDG, how can I assign each diagram type to a specific perspective?

I think the only way to do this is to separate each diagram out into a different technology, because that is the granularity that perspectives work with.

General Board / Re: Re-use existing MDG diagrams within a custom MDG?
« on: June 08, 2018, 02:51:41 pm »
I notice there's nothing in the Example Model. I don't know if Sparx Support have anything more substantial than what's in the help, but if you get in touch then the least they can do is record a feature request for additions to the Example Model.

Suggestions and Requests / Re: New standard element property: ID
« on: June 06, 2018, 11:12:57 am »
One question - the view preference settings that control Alias usage on diagrams (ie 'Alias only' or 'Alias and Name', are these model settings or user settings?  If I turn on 'Alias and Name' will that be reflected in the model and other users get he same behaviour or will only I get this?

Everything in the Preferences dialog is a user setting, so only you will see it. (Although be aware that in a shared model, you may see elements resizing if they have more text to display, which may mess up other people's diagram layouts.)

General Board / Re: Re-use existing MDG diagrams within a custom MDG?
« on: June 06, 2018, 09:44:05 am »
In EA14, you can use diagram views to modify SysML diagram types without losing their associated SysML functionality.

NB: It does work for metaclasses of type association and dependency

Transition could be a special case then. Please send in a bug report.

Suggestions and Requests / Re: New standard element property: ID
« on: June 06, 2018, 09:11:35 am »
1) Auto Naming: This has most of the capability I am looking for *except* that:
- It is implemented as a substring embedded in the name field - the numbering is created at the time it is applied but can be deleted afterwards
If you look at the Auto Name Counters dialog, you can apply to the Alias field instead. This takes it out of the name field, and there are various diagram-level settings that allow you to display name, alias or both.

I am certainly able to create a connector between two elements on a diagram and drag the connector to another element. I suspect we are using different kinds of diagram, element and/or connector. Could you be more specific please?

General Board / Re: Reusing a Use Case, generic or template?
« on: June 05, 2018, 03:26:16 pm »
You can extract these steps into a separate use case and include it in all the others.
I can embed/inherit/include a use case in a use case? Or have I misunderstood you?

Side note: what's with the reCAPTCHA? I have to click it 20 times to prove I'm not a robot???

From UML 2.5 specification:
Include is a DirectedRelationship between two UseCases, indicating that the behavior of the included UseCase (the addition ) is
inserted into the behavior of the including UseCase (the includingCase ). It is also a kind of NamedElement so that it can have a
name in the context of its owning UseCase (the includingCase ). The including UseCase may depend on the changes produced by
executing the included UseCase. The included UseCase must be available for the behavior of the including UseCase to be
completely described.

The Include relationship is intended to be used when there are common parts of the behavior of two or more UseCases. This
common part is then extracted to a separate UseCase, to be included by all the base UseCases having this part in common. As the
primary use of the Include relationship is for reuse of common parts, what is left in a base UseCase is usually not complete in
itself but dependent on the included parts to be meaningful. This is reflected in the direction of the relationship, indicating that the
base UseCase depends on the addition but not vice versa.

All of the behavior of the included UseCase is executed at a single location in the included UseCase before execution of the
including UseCase is resumed.

The Include relationship allows hierarchical composition of UseCases as well as reuse of UseCases.

Regarding the captcha, no idea. It clearly doesn't work 100% because I am having to delete spam posts every day...

Yes it needs to be in the same location as the pattern and have the same name with the ".xml" replaced by ".rtf". It may be case-sensitive (including extensions), so check for that. I have no idea if there are different RTF standards, but if you want to guarantee that you are using the same RTF standard as EA then copy-paste your document into a Document Artifact in EA and export it from there (ribbon: Edit|File|Save as).

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.

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.


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.

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?


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.

Pages: [1] 2 3 ... 167