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 ... 428
1
General Board / Re: Empty tags of a class not shown in diagram
« on: September 20, 2018, 05:02:14 pm »
Have I got it right now?
Almost.

which references the target element (a property).
The target element could be a property. But it could be any concrete UML Element.

  • A Stereotype is a class.
  • A Stereotype may extend one or more Metaclasses
  • A Stereotype has a collection of Properties, each of which has a corresponding type (and UML allows a multiplicity)
  • Applying a stereotype is creating an instance. The instance includes a reference to exactly one instance of one of the metaclasses. (The one you are applying the stereotype to)
  • Slots are the containers for the values for each property.
  • Everything in those containers are instances of the property type.
  • The number of items in the container should match the multiplicity of the property. (Although UML explicitly allows for a multiplicity lower than the minimum during creation)

Some notes as far as EA is concerned.
An empty tagged value (including intial value when none is specified) would be the same as having no value conceptually. Except for the string, memo and possibly Addin broadcast or custom tagged value types.
EA profiles don't include multiplicity information

2
Then I was right selecting ArchiMate3::ArchiMate_ApplicationComponent as my parent class but I still have my problem with the toolbox that doesn't behave properly:
 instead of showing the component icon, I have a folder icon and when I drag and drop on a diagram, I have to select between two component types that look the same.
Did you include an extension as well as the generalization? I don't know a reason (off the top of my head) why you would see two components from the menu, but the behavior sounds like what happens when you have two different extensions, including an inherited one.

That means: you did something wrong. Unfortunately A does not tell you what  >:( >:( >:( So you are left to try and error. What I do is: a) wait a day and have enough sleep. b) check each details by comparing it to a working part. c) re-generating everything by exporting files and running the creation wizard (what a wizard, more the sorcerer's apprentice).
Actually, it usually means that's what you asked for. It's not intrinsically wrong so there's no reason for EA to report it as an error.

3
General Board / Re: Empty tags of a class not shown in diagram
« on: September 20, 2018, 08:51:51 am »
Instances of the type.

Where 5 is an instance of int, "" or "value" are instances of string.

4
General Board / Re: Empty tags of a class not shown in diagram
« on: September 19, 2018, 01:44:50 pm »
By here I meant on this forum. If I remember correctly, with the two of us taking slightly different sides.

Yes, tagged values haven't been officially called that since UML 2.0 was released. However, it's still an easier term to use.

Technically, when you apply a stereotype to an element, you create an instance of that stereotype, which references the target element. The tag is a slot referencing the property, and the tagged value is zero or more of the type for the property.

5
General Board / Re: Disable the abilty to Manage Add-Ins
« on: September 19, 2018, 11:35:18 am »
Can't be done with security permissions because they are model based. When in another model (or no model) they would have no effect.

In EA there's not much to you can do. The main option that I can think of is to lock down their computer so they can't install an add-in in the first place.

6
I can select between ArchiMate3::ApplicationComponent or ArchiMate3::ArchiMate_ApplicationComponent.

Any stereotypes in the ArchiMate3 technology that don't have the "ArchiMate_" prefix are abstract types used to implement metamodel rules between the types. From memory, ApplicationComponent is extending a different UML type than one of its specializations, which meant that we needed to separate that fact from the inheritance.

7
Bugs and Issues / Re: Profile only partially imported
« on: September 19, 2018, 10:56:08 am »
I suspect the issue is still with cross package relationships.

In the owl profile, take every stereotype extending something from rdf, and create a new abstract stereotype in the owlProfile package with the name RDFProfile::<name>. Then move the generalizations to those.

8
Bugs and Issues / Re: State machine diagrams in EA 14 and 14.1
« on: September 18, 2018, 06:40:22 pm »
I sympathize with your position.

I personally don't like having a diagram frame showing on my diagrams most of the time, and believe that the surface itself is the frame.

However, I also know that there are a lot of users who have previously thought EA incapable because they didn't see a frame.
e
Are you aware that you can disable the default diagram frame on State Machine and SysML diagrams with the context menu item when clicking on the diagram background?

You should be able to achieve something close to what you wanted by marking the diagram details as non-printable. This means that it is shown on the diagram, but not included in other situations including reporting.

Having said that, it sounds like some of what you are describing are bugs in what we have tried to do with the diagram frame. I think you'll find that at least some of them were corrected in EA 14.1.

9
Bugs and Issues / Re: Bizarre bug in QuickLinker!
« on: September 18, 2018, 06:30:57 pm »
I'll take an example from the ArchiMate3 technology that you can see in your install directory.

Code: [Select]
          <Stereotype name="Application Internal Behavior" notes="" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0" isAbstract="true" generalizes="Internal Behavior" baseStereotypes="Internal%20Behavior">
            <stereotypedrelationships>
              <stereotypedrelationship stereotype="ArchiMate3::ArchiMate_Access" constraint="ArchiMate3::ArchiMate_DataObject"/>
              <stereotypedrelationship stereotype="ArchiMate3::Dynamic Relationship" constraint="ArchiMate3::Application Internal Behavior;ArchiMate3::ArchiMate_ApplicationEvent"/>
              <stereotypedrelationship stereotype="ArchiMate3::ArchiMate_Realization" constraint="ArchiMate3::ArchiMate_ApplicationService"/>
            </stereotypedrelationships>
          </Stereotype>

The ArchiMate 3 technology is describing its relationships mostly using the stereotyped relationship connector. The relationships it specifies go into the stereotypedrelationships node under the stereotype, grouped by the target connector type.

I've taken this example to illustrate what is different about this. It has specified that an abstract stereotype (Application Internal Behavior) has a number of valid relationships both concrete and abstract to different types, again both abstract and concrete. Instead of maintaining a spreadsheet with all of those expanded to concrete types you can specify it in the model itself. In this case, there are four connectors.

You lose a little flexibility by not defining all the rows explicitly, but gain model validation and hopefully a little sanity.

PS. Your @element relationship becomes a metaConstraint for the source and target of your Nsting stereotype referencing the metaclass Element.

10
Bugs and Issues / Re: Profile only partially imported
« on: September 18, 2018, 06:11:31 pm »
I believe what you're seeing is that owlClass doesn't have an extension connector and base_Class property. It has generalizations to other types, which indirectly lead to other profiles (specifically to http://www.omg.org/spec/ODM/20131101/RDFProfile.xmi#_16_5_2_630020f_1250725403251_896961_1023). As a consequence the inheritance chain will probably be broken during import.

Are you aware that EA comes with a built-in ODM profile? Is there a reason you're trying to define it yourself?

11
General Board / Re: BPMN Pool and Lane title freeze
« on: September 18, 2018, 06:03:33 pm »
I don't think there is an option for this available.

12
General Board / Re: Empty tags of a class not shown in diagram
« on: September 18, 2018, 06:02:26 pm »
It was an intentional change. Probably to clear some unnecessary clutter since there is no value there. (Although we have had some discussions here about whether an empty string is a value)

I don't believe there's an option to revert to the previous behavior. If you really want the empty value displayed, maybe you could insert a zero width space?

13
And don't forget the fill in the metatype on the stereotype. Leaving that blank will also not make the icon appear (for obvious !NOT! reasons :-X)
EA doesn't customize the icon based on a stereotype. It customizes it based on a metatype. (Not that saying that explains why)

14
Bugs and Issues / Re: Bizarre bug in QuickLinker!
« on: September 17, 2018, 11:52:40 am »
It's completely new, and doesn't generate anything that earlier versions know to look for.

In terms of backwards compatibility, it will override an existing quicklinker table if one exists. (If you have a metamodel only stereotypes not mentioned in the metamodel will be taken from the quicklink table.) So your technology can include both.

15
General Board / Re: Named default value constraints
« on: September 17, 2018, 09:18:17 am »
Looks similar to the primary keys and uniqueness constraints etc that are modeled using a separate stereotyped operation.

Pages: [1] 2 3 ... 428