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.

Topics - Paolo F Cantoni

Pages: 1 ... 4 5 [6] 7 8 ... 78
Bugs and Issues / Can’t suppress Notes display for Constraint
« on: August 23, 2017, 09:59:57 am »
We're using Stereotyped UML Constraints in our MDG (for technical modelling constraints rather than Business Constraints for which we use the ArchiMate Constraint).  We entered a narrative description of the Constraint in the Notes field and it displays.  BUT on some diagrams, we only want to show a small indication of the constraint (i.e. as if no notes were present).  However, we can't suppress Notes.  A Constraint will not respond to the [Ctrl+SHift+Y] Feature and Compartment Visibility, nor is there a specific context menu item.

Please rectify,

Adding an arc on one diagram with a default line style (say Orthogonal Square), it gets added to other diagrams with Custom Line Style.  Annoying to say the least!

But the real problem is it's WRONG!

Concistency, konsistency, consistensy! TMUffe - after Paolo


This bug is probably related to Proxy Connectors don’t move correctly when moving multiple vertices on diagram.  If you grab a relationship between relationships and try to drag it, it won't move.  This is probably because the ProxyConnectors (actually Connector Proxies) at the ends of the relationship aren't handled correctly.  Interestingly, and annoyingly, if you drag one of the related (end) lines, the proxies move!


If you have aligned vertices (of the same size) and you connect them via an orthogonal (square or rounded) arc, you can only drag it to the edge of the vertex.  You can't drag it past.  If the vertices, are of different sizes or are not aligned, then you can get the additional waypoints to bend the arc as required.  It would be good to be able to do this also when the vertices are the same size and aligned.

I decided it was a feature request, but it could be considered a bug.

If you select multiple vertices on a diagram and move them (as a unit), the arcs between the vertices move appropriately.  However, if there are arcs between arcs (expressing relationships between relationships), the proxy connectors get scrambled in the move.


Uml Process / What is an "Instance"?
« on: August 17, 2017, 10:15:10 am »
As promised in another post, here it is...

When modelling systems and application programs, this is fairly clear.
"Car" is a Classifier, "BMW 318i" is a (specialised) Classifier, "BMW 318i with plate # XXX 888" is an instance of the Classifier BMW 318i".  We implement Classifiers with Classes and Instances with Objects.  Everyone agree?

A classifier can be defined as anything that aggregates a set of instances according to some property set.  Agreed?

Now let's look at modelling some other things.
ArcfhiMate 3.0 when talking about (Business) Actors observes:
"Business actors may be specific individuals or organizations; e.g., “John Smith” or “ABC Corporation”, or they may be generic;e.g., “Customer” or “Supplier”."

This introduces the notions of "specific" vs "generic".

It seems to me that generic Actors fall under the definition of Classifier whereas specific actors don't (seem to).  Colloquially, we say "John Smith is an instance of an actor".  Can we also say "Customer is an instance of an actor"?

So what's going on?  Should we have Actors (for Generic) and Actor instances (for specific)?


Bugs and Issues / PDF Print DOESN'T include Diagram Name
« on: August 15, 2017, 05:03:44 pm »
If you try to print a number of diagrams to PDF, you have to manually replace the Model Name with the Diagram Name.

Why can't the Diagram name be supplied?  Since the supplied name is ALWAYS the Model name, you run the risk of overwriting a previously printed, but different, diagram.


While checking t_xref for other reasons, we discovered duplicate entries for "DefaultDiagram" rows.   That is, there was more than one entry in t_xref with the same Client and Supplier ea_guids for that Name!  The Integrity Checker [Shift+F9] has not detected them!  It should!

Since there can only be one such diagram per element, having duplicates in the DB is, by definition, an error.


Dragging a new item off toolbox will honour shapescript defsize() for rectangular form, creating one via browser (<context menu> | Add Element...) doesn’t.  The size created is related to the values in the MDG definition for the element. 
Code: [Select]
<Stereotype name="element" metatype="Element" notes="" cx="100" cy="60" When creating via browser, IF the size specified in either (or both) cx and cy is greater than the size specified in the shapescript, THEN EA will apply the shapescript size, but if the sizes are less than the shapescript size, it will apply the MDG size.   Dragging from the toolbox will always setup the correct size.


Please rectify!

Reported (I think for the second time, but at least I know WHY it happens now.)

Bugs and Issues / Connector Labels and Dotted Line styles
« on: June 21, 2017, 05:33:04 pm »
I'm sure I've reported this over the decade or so, but I can't find it in the search.

If you create a label for a connector (such as add name of Association), if the line is a Solid line, then the text of the label can be positioned so that it overrides the line and you can CLEARLY see the text.  However, if the line is one of the non-solid (setlinestyle()) lines, then the underlying line will "peek" through - making the text unreadable.  Can this be fixed, please?


General Board / Inconsistencies between Help and t_connectorTypes
« on: June 15, 2017, 03:55:15 pm »
There are inconsistencies between what the help says in .../User%20Guide/model_domains/transformingconnectors.html and the t_connectortypes table in the repository.

Connector_Type   Help Document
Abstraction      Abstraction
Aggregation      Aggregation
Assembly         Assembly
Association      Association
Collaboration      Collaboration
Connector      Connector
ControlFlow      ControlFlow
Delegate         Delegate
Dependency      Dependency
Deployment      Deployment
ERLink         ForeignKey
Generalization      Generalization
InformationFlow   InformationFlow
Instantiation      Instantiation
InterruptFlow      InterruptFlow
Manifest         Manifest
Nesting         Nesting
NoteLink         NoteLink
ObjectFlow      ObjectFlow
Package         Package
Realisation      Realization
Sequence         Sequence
Substitution      Substitution
Usage         Usage
UseCase         UseCase

Should these be identical or, if not, why not?


We use stereotyped Notelinks for various administrative metatypes in our repository.  We've observed that if we create the first link from the Toolbox, the [F3] (repeat last connector) functionality will work correctly and create a new arc of the correct metatype.  However, if we use the QuickLinker to create that first link, the [F3] function will create an unstereotyped Notelink.  Obviously, the same functionality is not being used...  Can we please ensure that the behaviour is the same (for ALL metatypes) - regardless of the first instantiation method?


Bugs and Issues / Tooltips show HTML codes
« on: June 15, 2017, 09:58:43 am »
If you enable "hovering" tooltips (don't know if this bug also occurs for the status bar tooltips) and the tooltip cutoff occurs in the middle of a HTML element, the HTML code is visible.  Since there is no formatting on a tooltip, the HTML should have been stripped off in the first place.


Increasingly, we are developing scripts that operate directly on the Selected Diagram Link (rather than the underlying Selected Connector).  Similarly with Diagram Objects.

However, there is no SelectedDiagramLink or SelectedDiagramObjects attributes for the Diagram Class.  We are forced to scan the appropriate collections to determine the diagram link from the underlying connector.

Can we have direct access to the diagram specific items?


The [ ] Use Rectangular Notation context menu item is created on the fly by EA by inspection of the shapescript.

However, for a number of element types, Activity, being the one that caught us out today, this is NOT respected.

Please rectify.  I see no reason why, if the shapescript has the requisite coding, that the context menu items shouldn't be provided.


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