I have a problem with the Interaction overview diagram in EA.
I cannot connect any control nodes to InteractionUse element I added to the diagram. Or even between two InteractionUse elements.
I'm getting the following error:
The requested connection is not UML compliant.
Can anybody give me some advice on this?
Here are some images to demonstrate the problem:
The problem seems to have been solved in version 16 (tested on build 16.0.1605)
In version 15.2.1560 the problem still occurred.
If upgrading is not an option, you can still disable the strict connector syntax (even if only temporarily) through the settings:
According to the UML specification (2.5.1) this is indeed a valid connection since in ยง 17.10.1.1 Graphic Nodes it says:
Inline Interaction diagrams and InteractionUses are considered special forms of CallBehaviorAction.
Related
I am busy putting together a component diagram using EA by Sparx System (version 15.1).
I would like to achieve the top diagram (component A and B). However when I setup an assembly relationship you need to configure a required and a provided interface (with / without port). I have tried a few options (C & D / E & F) but am unable to link the lolipops like A & B.
Any experience here would be useful how to achieve this. The EA documentation is very poor.
If you want to add an assembly connector between components, you need to disable Strict Connector Syntax in Start > Desktop > Preferences > Links > Strict Connector Syntax:
The basic issue (unfortunately) is a constraint of the UML 2.5 metamodel (which was not present in 2.1.1). This allows assembly connectors only between Property metaclasses (being Port and ExtensionEnd). So when you're doing the above from a port to another port you will see the assembly in the quick linker.
If you want assmeblies between components you have to use them explicitely from the toolbox.
(Either show the Composite toolbox or go via the context menu)
I'm using them during early design since I know that I'll replace them later when I got the real interfaces. However, one must know that such a model is not compliant to the UML standard. But who cares about standards if you can make your own ;-) ?
Original answer (probably still usefull)
The top is just an assembly connector. Use that for a first sketch when you have no details about interfaces.
The middle one is the preferred one in design. You draw a dependency relation from the required to the provided IF (pointing left to right).
The lower one is not ok. You use an assembly in conjunction with a real provided IF with the assembly being oriented the wrong way. I suggest to use that assembly only in an early design stage and once you get the IF right (sockets and lollipops) to connect these with a dependency.
Since EA behave consistently inconsistent: In order to create an assembly you can not use the quick linker. Dragging from one component to another just offers
Rather with the component diagram focus hit the space bar and you get the toolbox
Select the assembly connector (you could as well have the toolbox window open and select the connector there, but I prefer this way). Now you can drag from source to target component.
I built an application which is integrated in open source program( you just download the binary of the program, run it and then my integrated module will execute when you click on one single button called translate. That's all. )
What the application does is that when user builds some schema in the open-source project I mentioned above it generates C++ code for the schema. It's java program written in OOP style( classes, polymorphism, inheritance, encapsulation). There also runs some algorithms like top sort for finding topological sorting or bfs.
Since I study software engineering and will be presenting the application I would like to draw some UML diagrams or diagrams in general which would help me to better describe the application/ behavior of application itself.
Since it's not typical web-based project ( does not use any database etc... ) except for class diagram I don't know what what would be good to use.
Could anyone give me some diagram names which would help me to describe the behavior of my application better? I appreciate all the help.
You are looking for sequence diagrams, activity diagrams and/or state diagrams to describe behavior.
I'm studying some UML materials and I came across one weird thing for me: cross on the side of arrow/association. What does it mean? It's frequently used in the materials, which I am studying. Please see the picture below
It means non-navigable. Please check page 205 of UML2.5.1 specification
I have been looking around for this for ages, but could not find any way to link a UML note to an operation of a class or to display the provided implementation in the specification of an operation. The idea is illustrated in the picture.
I tried to add the implementation to the operation, but I don't manage to make it appear in my diagram. I also tried making a note and then connecting it to the method, but this leads to unclear floating line-ends.
If anybody could let me know how this could be achieved with visual paradigm or let me know it is impossible, that would be nice.
Thanks in advance.
I have no idea how or whether this is possible with VP (I know for sure that you can't do it with Enterprise Architect which is pretty much UML2.x compliant). But you could hook the link near the position in the appropriate compartment (EA also has a feature to lock the connector at a certain position of an element).
Edit I have looked into Superstructures 2.5:
Comment [Class]
Description
A Comment is a textual annotation that can be attached to a set of Elements.
So actually what you want to do is not UML compliant. A comment can only be attached to an element. Attributes/operations are not UML elements.
I have a need to describe a hierarchical finite state machine in a standard and portable format. Is there a widely-accepted and supported file format that I should use?
I see that the Graphviz DOT language supports sub-graphs that may be referenced by directed edges. (Although rendering connected clusters using Graphviz is a bit of a problem.) Interpreting the text label on a generic directed edge as a transition event/criterion seems like a slight semantic stretch, but not unusable.
I see that a UML Statechart has support for hierarchically nested states. However, the accepted answer to this question implies that describing a statechart in XMI myself may not actually be properly interoperable with tools that nominally support UML.
I see the W3C SCXML Standard. However, this is still a working draft (and has been for almost 7 years), and I'm not certain if any tool supports this format (other than through conversion).
Is there a more widely-acceptable alternative than one of the above? Should I use one or the other of the above?
One of the examples of portability is that I would like for the graph to be able to be read and used by an HSM simulator like Matlab Stateflow.
There is an OMG standard for UML diagram interchange. But I don't thing it is widely accepted. You can also use the eclipse EMF UML2 format, for which you can develop yourself translators for other formats.