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] 4 5 ... 433
Profile Metatype (bad) Component, (good) ArchiMate3::ArchiMate_ApplicationComponent.

This sounds like when you exported, the definition was type, now it's profile metatype. Changing it back to Type may get you going.

Bugs and Issues / Re: Can't order Responsibilities
« on: November 05, 2018, 11:20:16 am »
Element Responsibilities (aka - Internal Requirements) can't be ordered.  The ONLY order available is alphabetic.

Please rectify.

Every collection in EA should be able to be ordered.
While I appreciate what you are saying that "every" collection could have an order applied, there are other factors at play here.

UML itself has several "unordered" collections. My interpretation of this is that there is no meaning in the order, and it can be validly be presented in any order.

For an EA specific issue, there's nowhere for EA to store a user specified order on these. That alone means you're probably better off adapting.

Yes that is correct for the current version.

General Board / Re: Change of stereotype to "Functional"
« on: October 29, 2018, 04:15:17 pm »
This isn't a new issue. I've seen it reported/discussed/etc many times over the years. But in my opinion it's not wrong.

I would say that EA's implementation of a Requirement is that it has a 1..* relationship to Requirement Type.

As a result, any requirement without a requirement type is incomplete. There are many ways to manage this, and none of them are going to satisfy everyone.

The dialog automatically fills the type during load to ensure it is complete. The user then presses 'save' which writes the value being displayed.

I would personally recommend that Ian accepts that the requirement will have a stereotype. (from the 1..*) relationship above and use it how it's intended to be used.

Regarding your personal issues. If I've searched our system correctly I can see a mix of issues that have been confirmed but not yet fixed, fixed or considered not a bug. (Including at least one "bug report" for behavior that if changed would break existing diagrams for every ArchiMate user)

General Board / Re: Change of stereotype to "Functional"
« on: October 29, 2018, 10:26:43 am »
"Oh that feature doesn't really work and doesn't appear to be getting fixed anytime soon, here are some ideas on how you can build your own solution instead"

It works, but there are always differing views on how people would like it to work. There are also people here that seem to enjoy complaining.

The 'Type' field for any requirement like type is implemented using stereotypes. They are most useful when used with a profile that provides additional fields for each type. But there is also a model wide list of requirement types that act like a simple profile for those that don't want to build a profile (or use a built-in one like SysML)

The idea is that without a type, a requirement is like an abstract metaclass.

General Board / Re: Meta-Constraints
« on: October 29, 2018, 10:10:00 am »
Not to EA.

It may make a difference to you if you want to be strict when describing your profile. From a technical view, not all metaclasses have the same umlRoles.

client/supplier would be for dependency types
source/target would be for directed relationship types
end[0].role/end[1].role would be for associations
informationSource/informationTarget would be for information flow.

General Board / Re: Hide stereotype on Information Items Conveyed
« on: October 26, 2018, 11:43:25 am »
SysML is a language of it's own and EA just mimics it with a profile.
Actually, the current version of SysML is defined as a UML profile. SysML 2, which is still in very early stages is expected to be defined as both a metamodel and profile.

Code: [Select]
[ 16.5,11.5 ] x 96 = [ 1584,1123 ]Although those page sizes are only accurate to one decimal place.

ISO 216 which defines those sizes was updated in 2007, so you could be right. But I expect the page size didn't change.

I don't deal with that directly, so I don't know how academic licenses are counted.

It won't hurt to fill out the form.

Doesn't WebEA require a separate licence?
It doesn't necessarily cost you more. Last I knew you could get a license for Pro Cloud Express that provides access to WebEA. The only requirement was a minimum of 5 corporate licenses.

The advantage of WebEA over the lite version is that the user doesn't need to install a copy of EA to view it. They can even view it, contribute to discussions and make some changes from a mobile device. Like your idea of the first free heroin shot, WebEA aims to lower the boundary of getting involved even further.

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.

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