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 5 ... 163
Or you extend them in your own MDG thereby adding whatever tagged values you need.

Alexey, you don't say which version of EA you are using. Hopefully it is a recent version, because the functionality to do what you want to do was added at EA 13.0

You can add tagged values to an existing stereotype by using the redefines Generalization. See the help file topic "redefine_ster_other_prof" (ribbon|Start|Help|Go to Help Topic, and paste "redefine_ster_other_prof" into the dialog - without the quotes).

You will need an abstract stereotype "Archimate2::ArchiMate_ApplicationComponent" and a stereotype "ArchiMate_ApplicationComponent", with a redefines Generalization between them. The stereotype "ArchiMate_ApplicationComponent" will hold the additional tagged value declarations. Once you have built and deployed your technology, you will need to set the technology "Active" after which every Archimate2::ArchiMate_ApplicationComponent you create should have the additional tagged values you defined. Synchronizing tagged values should add them into all existing elements.

I hope this helps.

But how to extend class so that the default scope for its attributes (and operations too) is public instead of EA default of private?

There is no setting for this. The only solution would be to write an add-in that implements the EA_OnPostNewAttribute broadcast handler.

_AttPub has no meaning in a Toolbox Profile.

Use _AttPub in a UML Profile. If you have a stereotype that extends Class (for example), you might set _AttPub to "0" in order to hide all public attributes owned by the stereotyped Class (by default, EA shows all attributes).


That kind of information is usually stored in the registry


Update 2: No.

Uml Process / Re: BPMN Import - Diagram does not draw correctly
« on: August 03, 2017, 04:41:00 pm »
Arrows don't Connect to boxes. They just stop in dead Space on the canvas.

This shouldn't happen. All connectors in EA have two ends with an element at each end. If a connector appears to end in midair, then where's the element? It could be invisible, it could be hidden behind another element. It needs to be found!

In general though, transferring models between tools is a lot easier than transferring diagram layouts, so expect to spend some time rearranging diagrams manually...

Which language are you using? I notice that SysML has a <<Stakeholder>> stereotype with a "concern" tagged value that provides a memo field. But if you prefer the Relationship Matrix to memo tagged values, you could create your own <<Concern>> stereotype and use that.

Suggestions and Requests / Re: Role name vs. attribute
« on: August 02, 2017, 11:49:36 am »
Is the difference between a class and a datatype that instances of a class have identity whereas instances of a datatype are distinguishable only by their value? (This Fred is not that Fred, but a 3 is a 3 is a 3).

General Board / Re: Can't add attributes or operations using toolbox???
« on: August 01, 2017, 04:52:35 pm »
I don't think it has ever been possible to drop unstereotyped attributes or operations from a custom toolbox. Only stereotyped attributes and operations. If you think that's worth a bug report, please use the "Report a Bug" link at the bottom of the page.

General Board / Re: What is a "property"?
« on: August 01, 2017, 10:37:33 am »
When dropping a class element in a diagram a dialog appears asking of what kind the dropped element shall be created: Link, Instance, Child, Property.

Paolo is correct that Property has many meanings depending on context. In this context, it is used as a synonym for Part.

Bugs and Issues / Re: SysML Item Flow with item property
« on: August 01, 2017, 09:33:05 am »
This is still a problem in V13. I am trying to implement the Water Distiller example in Chapter 16 of the Practical Guide to SysML book (Iss 2 so SysML 1.3). This is a showstopper as you can't create an Item Flow item than can be allocated to from an object flow. I want to be able to map between logical model object flows and physical model items flows, e.g. a real-world value like temperature in the logical model is represented by a sensor voltage in the physical model.

I don't have the book so can you describe the diagram please?

Suggestions and Requests / Re: Role name vs. attribute
« on: July 31, 2017, 05:04:44 pm »
So what is an association that's not going to be an attribute? A ghost?

I think the question should be the other way around: what is an attribute that's not going to be an association end? The convention used in the UML specification itself appears to be that they use associations between classes, but attributes with data types (primitive or otherwise).

On the Preferences dialog, there is an Allow Free Sorting option that you should tick, if not already.

ribbon|Start|Workspace|Preferences|General|Project Browser|Allow Free Sorting

Can anyone tell me what/how to set/clear?

A quick check of the diagram's extended style shows the parameter isn't in there... nor do I see any other obvious location for it.

Thanks - Julian

t_diagram.StyleEx includes "CEE=1;"

Instead of * you need a %.


Or use '#WC#' which will substitute the appropriate wildcard character for the database you're running the search on.

If all you want to do is display one of a BPMN Activity's tagged values on a diagram, then rather than messing around with shape scripts and risk losing BPMN functionality, add a Note to the activity (right-click > New Child Element > Attach Note), right-click the note link and "Link this note to an element feature".

Pages: 1 2 [3] 4 5 ... 163