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 ... 430
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.

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.

Bugs and Issues / Re: MSSQL Connection Warning [-2147217900]
« on: October 11, 2018, 08:43:06 am »
I'm guessing that he has defined a model view, or an add-in is running sql etc.

Bugs and Issues / Re: UAF ERROR:"Model Template Pattern failed to load.
« on: October 10, 2018, 08:57:19 am »
I'm in the (similar?) boat, I have just upgraded to v14, I'm attempting to use the Model Wizard and get TOGAF patterns.


Does this have to do with me only having Sparx EA Professional Edition?
According to, togaf is included in the Unified or Ultimate editions.

It can also be separately purchased for the editions that don't include it.

Bugs and Issues / Re: Ribbon Sets - NO Help
« on: October 10, 2018, 08:53:03 am »
I wondered what is the Ribbon Sets page doing way down in the Workspaces branch? It doesn't make sense (and, is had to find).
How can I automate the creation of a default setup?  i.e. this workspace and that ribbon set.  (By pre-populating the AppData Roaming?)
I'd say it's intentionally hard to find because people using any kind of menu customization inevitably results in issues with people unable to find what they need.

No idea how to automate it.

Bugs and Issues / Re: Ribbon Sets - NO Help
« on: October 09, 2018, 02:06:36 pm »
Isn't it one of the central tenets of searching that if a specific search finds a set of items "My Ribbon Sets", the more general search e.g.  "Ribbon Sets" MUST also find the same set of items?
If I search for ribbon sets, the help shows 14 pages of results. I don't know how it orders those pages, but I don't think I'm going to find what I want. Advanced and selecting phrase search comes up with the right answer.

If I select only one section on a ribbon, say Package Section in the Design Ribbon (the others are deselected), the entire Ribbon displays, not just the selected Section.  I don't think that's the way it's supposed to work.
Just tested this. I unchecked the simulate ribbon, which unchecked all the sections inside. I then checked the Show section. It also checked the Simulate grouping. When I go to this ribbon it only contains the show group. Am I missing something?

I think we should, at least be able to display/not display the Start section option sets.  Perhaps, a few need to be permanently available (to inhibit foot shooting), but the rest should be controllable.
I can imagine allowing the removal of the Collaborate section. The rest seem pretty essential, so the advantage of this seems minimal at best.

The last two sections aren't there.  I can hide all the available ribbons except "Start"
The last two sections mentioned are dynamic/context driven. But like 'Start' you don't get the option of hiding anything in them, so they don't show in the list.

BTW: What is the relationship between the Ribbon Sets and Workspaces?  They seem to be orthogonal.  Is that correct?
Workspace is the position and size of all the docked windows, and does not impact the ribbon.

General Board / Re: Automatically create aggregation relationships?
« on: October 09, 2018, 01:51:11 pm »
The ArchiMate direction is the reverse of the UML direction, so properly modelled connections look backwards in the traceability view.  Years ago I asked Sparx if they could just flip the ArchiMate shapescript but that idea seemed to fall on deaf ears.
Alternatively, ears that have heard too many complaints already about changing anything like that.

If we just changed it, it would be reversed on all existing diagrams.
If we changed the way they were created, anyone using the API or querying the database would be unable to resolve them.
If we provided an option, the previous issue multiplies.

There are issues with keeping it that way too, but I'm not sure if they are worse.

Pages: [1] 2 3 ... 430