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 ... 4 5 [6] 7 8 ... 434
76
- Viewpoints often have focus on a particular types of interaction so the ability to control connector visibility by connector type would be useful (possible enhancement to the 'Set Visible Relations' window to group select by type)
EA 14.1 has custom view specifications, and each diagram has the option to filter to the applied view (also called metamodel in places) By default it will use the fade effect, but you can fully hide elements and connectors that don't match the view by changing the diagram filter to use hide.

BUT THE MOST IMPORTANT THING is to provide a "widget" to indicate that there are hidden arcs on a given diagram.  We created our own to do that. It is vitally important that the view is informed that they are NOT seeing the "full story".
This should be part of the next UML standard. Unfortunately the mills at OMG grind event slower than those at Sparx.

q.

I disagree. Something like this is highly process specific and not part of the language itself. In the example of different views that have a different set of connectors visible, it would often be something you wouldn't want. Other than that, where do you draw the line for when this should appear? Is it just connectors? Just ones where the other end is on the diagram?

77
General Board / Re: Resizable pipe shape script
« on: October 01, 2018, 03:41:04 pm »
Bottom
Code: [Select]
shape main
{
setfixedregion(0,80,0,100);
startpath();
moveto(100,90);
setfixedregion(0,0,0,20);
arcto(0,00,100,20,100,10,0,10);
setfixedregion(0,80,0,100);
lineto(0,90);
endpath();
FillAndStrokePath();

ellipse(0,80,100,100);
}

Left
Code: [Select]
shape main
{
setfixedregion(0,0,20,0);
startpath();
moveto(10,100);
setfixedregion(80,0,100,0);
arcto(80,0,100,100,90,100,90,0);
setfixedregion(0,0,20,0);
lineto(10,0);
endpath();
FillAndStrokePath();

ellipse(0,0,20,100);
}

Right
Code: [Select]
shape main
{
setfixedregion(80,0,100,0);
startpath();
moveto(90,0);
setfixedregion(0,0,20,0);
arcto(0,0,20,100,10,0,10,100);
setfixedregion(80,0,100,0);
lineto(90,100);
endpath();
FillAndStrokePath();

ellipse(80,0,100,100);
}

Note: I removed the redundant lineto from before arcto in these scripts.

I just noticed that the arc portion of the script doesn't appear to obey the fixed region. To get it working nicely you would convert the scripts to use two bezier sections.

78
General Board / Re: Resizable pipe shape script
« on: October 01, 2018, 03:23:34 pm »
Hmmm yes but going the other way.  That looks like a database :-)
Which other way? I can think of three obvious ones.

79
General Board / Re: Resizable pipe shape script
« on: October 01, 2018, 11:05:18 am »
You mean a cylinder?

Code: [Select]
shape main
{
setfixedregion(0,0,0,20);
startpath();
moveto(0,10);
setfixedregion(0,80,0,100);
lineto(0,90);
arcto(0,80,100,100,0,90,100,90);
setfixedregion(0,0,0,20);
lineto(100,10);
endpath();
FillAndStrokePath();

ellipse(0,0,100,20);
addsubshape("top",0,0,100,20);
}

Changing the height of your object changes the length of the pipe. Changing the width changes the view angle.

80
General Board / Re: Local User Guide v14?
« on: September 26, 2018, 03:19:57 pm »
Start | Help | Explore Online Resources | Install Help Locally

81
If you had a meta model\blue print defined in your model  then you can follow this tutorial
(Quick Link Definition Simplified)
for generating an automated Quick Link .
I can't imagine that being easier to manage than using the spreadsheet. You end up with one connector on the one diagram for every row in your target file. In most cases I've seen, that's hundreds of entries. Best case, that I can think of is that you organize the diagram with each source element having a list of target elements with the corresponding connector types. But that's just as achievable using the spreadsheet, except it's easier to sort on different columns etc.

I'm sorry, but it would be easier to manage my quicklinks by directly editing a CSV file in a text editor.

82
General Board / Re: More 'natural' curved connectors ?
« on: September 25, 2018, 12:09:55 pm »
Call it what you like, a Feature, Design Limitation, Oversight or Bug no matter what it certain is an inconvenience to the user.
It's very inconvenient to me as a user that I don't have a button for 'do all my work for the day'.

While managing the control points of a bezier when one end is moved doesn't fit into that level of difficulty, I don't think that there is a single "right" behavior. It may be feasible to make a better automatic choice, but I would expect that in many circumstances a user will still want to tweak it.

83
Yes, I have an extension to the base «metaclass» Component because that's what an E.A. consultant told me to do.
In the mdg_technologies.pdf p.28, the note says: If you are adding any of the Metaclass element Attributes to your stereotype, or if you want to use the Profile Helper to create a toolbox profile, your stereotype Class must extend a metaclass as well as specialize a stereotype.

That PDF is out of date, and so is your consultant.

I ran through your steps.

Step 1:
...
- Created new Stereotype LBC_ArchiMate_ApplicationComponent. I add a tag value attribute to differentiate from parent class.
...
- Component is correctly instantiated but the stereotype in properties is empty.
In the properties dialog, the tagged value will be in a separate page with the name of your profile. In the docked tagged values window you'll see it under <profilename>::LBC_ArchiMate_ApplicationComponent

Step 2:
- Add «redefines» stereotype to Generalization Relationship establish in step 1
Result:
- Component is correctly instantiated but the stereotype in properties is empty.
Now the tagged value should show up under ArchiMate3 in the dialog. In the docked window it shows up under ArchiMate3::ArchiMate_ApplicationComponent.

I can't see anything wrong with this behavior. As an added bonus, if you set your technology as Active in the manage technologies dialog. Any time you create an Application Component, it will use your stereotype instead of the one from ArchiMate 3.

Step 3:
- Add «metaclass»Component
- Establish Extension Relationship from LBC_ArchiMate_ApplicationComponent to Component
Result:
- toolbox has now the folder icone. If I drad&drop on the diagram, I'm asked to select between ApplicationComponent and ApplicationComponent  ::).
- I've tried with both and same result: Components are correctly instantiated including the stereotype that now has the «LBC_ArchiMate_ApplicationComponent» value
As I said, that will cause the behavior. Take my advice instead of some random "E.A. consultant". Not only is it not necessary in the current version of EA, it breaks things.

84
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

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

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

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

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

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

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

Pages: 1 ... 4 5 [6] 7 8 ... 434