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 - Simon M

Pages: [1] 2 3 ... 431
The abstract superclass shouldn't extend anything. Just extend at the concrete stereotypes.

That's correct. The only time it will override the body is when you do a complete overwrite instead of a synchronization.

Quite some time ago someone in the community wrote something that implemented a protocol handler to do that, but there's nothing in EA itself.

Generally I'd be recommending WebEA for that purpose now,

General Board / Re: Search Diagrams and Elements by UserID
« on: October 17, 2018, 10:29:22 am »
The author field matching a security user name like that is almost coincidental.

I'm not sure doing that linkage is really want you want. Author is the person who originally created it. Ownership might be that there is a security lock on it. (Either at the group or user level)

Bugs and Issues / Re: How to "Publish Diagram as Pattern"?
« on: October 17, 2018, 10:22:00 am »
If both HTML and local help would refer to a common git repository it would be possible to synch both. Just as an idea.

"Synching" the local help is installing an updated msi. They are built at the same time from the same source. Typically updates get uploaded at the same time too.

Bugs and Issues / Re: How to "Publish Diagram as Pattern"?
« on: October 16, 2018, 12:23:13 pm »

Bugs and Issues / Re: Metamodel Constraints - Meta-Relationship
« on: October 16, 2018, 11:19:59 am »
It's likely that Generalize is valid between the two base classes that you are using.

You can also add the attribute _HideUmlLinks=True to your source metaclass element to suppress that. Then you should only get the types you have modeled.

What don't you understand?

I modified the ecoSystem profile in the example model to use the constraints, then started writing up the instructions to replicate it. But I don't think it's going to help.

stereotyped relationship is used to specify a specific source/target/connector triple. It's almost the same as a spreadsheet line (but it also can be a reverse entry.) Multiple connectors are used to specify multiple valid targets for that connector type.

metarelation is the same thing. The only difference is that the connector is a UML one instead of a profile one.

You use those when the valid targets depend on what the source is. It's also the simplest when there is only one valid source and target.

To define a quicklinker using metaconstraint, the source will be the connector type. You need at least one umlRole=source and at least one umlRole=target to make it work.

It's simpler to use metaconstraint in this way if there are a number of valid source and target connectors.

That much will get a you a basic quicklinker. But you probably want to add the _MeaningForwards and _MeaningBackwards attributes to the metaclass for your connectors. This will show on the quicklinker and exposes 'reverse' relationship creation.

The other thing to consider is using abstract supertypes for your stereotypes.

Bugs and Issues / Re: Metamodel Constraints - Meta-Relationship
« on: October 16, 2018, 09:18:06 am »
That's correct. The quicklinker will be filtered to the metamodel view. If you want to include Generalization, add an expose connector to a metaclass with the name Generalization.

Created a trace relationship using the quicklinker with "Filter to toolbox" checked => Abstraction
Created a trace relationship using the quicklinker with "Filter to toolbox" unchecked => Dependency

That is feasible. It would imply that a trace extending dependency is added first. The quicklinker then only displays the first record with that label. When the filter is applied, only the one in the common toolbox is shown, so it comes out correctly.

There's a similar issue with the music player sample from the example model. The Stop message doesn't show up in either of the play states.

I'm not sure what has changed.

General Board / Re: Source code import C++ problem
« on: October 12, 2018, 09:00:44 am »
Not sure about a solution for version 12.

Trace has probably been a mix of abstraction and dependency connectors in your model since the Abstraction connector type was added to EA 10. Before that it was always a dependency because abstraction was also a stereotyped dependency.

I just tried creating a trace from the quicklinker, from the common relationships toolbox and from the extended requirements toolbox. All have a base connector type of abstraction.

General Board / Re: Requirement Property Fields
« on: October 11, 2018, 02:35:48 pm »

By "similar tools" are you referring to requirements management tools, visual design tools or something else?

EA covers a huge scope and is used by a huge variety of different types of experience.

The Type field gives you a choice from the basic element types available in EA. Requirement is one of these types.

Stereotype is a bit more complex, it's an extension mechanism. What you see in here will depend on what technologies you have enabled and what type you have selected. Continuing with the requirement example, SysML provides a number of different types of requirements. (eg. Functional Requirement, Interface Requirement and Performance Requirement.) Each of those can have additional properties, which are commonly called tagged values.

I would do what you have done inside a substate instead. That way you're never leaving the other state.

Personally, I would also prefer to more the constraint on the time reaching zero to a transition from the child state to a final node. The unguarded transition from the parent will then be considered a completion event. It's a little neater and fits with (my understanding of) the the philosophy of state machines better.

Pages: [1] 2 3 ... 431