Bugslayer: 10 days into EA14

My first 10 days into EA14 have passed by and I am discovering some issues ranging from nuisances to real distractors … So here is my list of bugs and SO questions. I will update the list as I receive updates from Sparx or other sources.

CaseId 18058962 – confirmed

Package Validation in Enterprise Architect does not warn about Deployment Specification Instance deployments to Nodes or Devices

A good hint from Geert Bellekens on how to roll your own validations: EAValidator

Official answer from Sparx: A fix for this is scheduled in the next build of EA 14 (1421)

Note: contradicting with Sparx support the update 1421 does not solve the error

CaseId 18058942 – under investigation

“Override Attribute Initializers” behaviour in EA14.0 changed over “Set Run State” in EA12.5

This is a breaking change from EA12.5 leaving all my Deployment Specification Instances unusable in EA14. See the question for more details.

Official answer from Sparx: To follow this up, this has been confirmed as an issue and lodged for correction. At this stage we do not know of any work-arounds.

CaseId 18058947 – under investigation

Deployment Diagram Connector Toolbox Icons: Nesting Connector is missing

According to https://www.sparxsystems.com/enterprise_architect_user_guide/14.0/model_domains/deploymentdiagram.html the “Deployment Diagram Connector Toolbox Icons” should include a “Nesting Connector”. However, when opening a “Deployment Diagramme” the “Nesting Connector” is missing.

Steps to Reproduce:
1. Create a package with an arbitrary name.
2. Within the package create in the previous step, create a “Deployment Diagramme” with an arbitrary name.
3. Open the “Deployment Diagramme” created in the previous step.
4. Open the Toolbox Icons with “Alt+5”.
5. Go to the “Deployment Relationships” section.
6. You will find the following connectors: Associate, Communication Path, Association Class, Generalize, Realize, Deployment, Manifest
7. The “Nesting Connector” is missing.

CaseId 18058855 – confirmed

Public Attribute Icons of Components in Project Browser are displayed as Black Squares

This happens when you have a high resolution display like my Microsoft Surface Book 2 with a custom DPI scaling of 200%.

Official answer from Sparx: This happens when the DPI scaling is not 100%

CaseId 18059034 – fixed

EA Version 14.0 Build 1421 does not allow to use Deployment Connector from Artifact to Execution Environment

After today’s upgrade from EA 14.0 1420 to 1421 I am no longer able to use the Deployment Connector when trying to deploy an artifact to an execution environment (or any other node type).
The error is: “The requested connection is not UML compliant.”

However, the requested connectio actually is valid UML, according to UML v2.51 section 19.2.

This differs from the behaviour in v1420, where it was possible to connect an Artifact and an Execution Environment with a Deployment Connector.

Steps to Reproduce:
1. Create a Deployment Diagramme with an arbitrary name.
2. Open the Deployment Diagramme created in the previous step
3. Create am element of type Execution Environment with an arbitrary name and place it on the open diagramme.
4. Create an Artifact with an arbitrary name and place it on the open diagramme.
5. Use the Toolbox and try to create a Deployment connector connecting from the Artifact to the execution environment.
6. You get a pop up letting you choose from a list of possible connectors: Communication Path, Abstraction, Dependency, Information Flow, Realization, Usage, Trace. The connector “Deployment” is not on the list.
7. If you cancel the popup from the previous step without choosing a connector type the following error message dialogue box is displayed: “The requested connection is not UML compliant.”

Existing Deployment Connector

Existing Deployment Connector

Trying to Create a new Deployment Connector

Trying to Create a new Deployment Connector

Invalid UML Error Dialogue

Invalid UML Error Dialogue

Official answer from Sparx: We have confirmed that this is an issue and we will fix in a future release of EA

Official recommended workaround: Ribbon | Start | View | Preferences | Links | General | Strict Connector Syntax | uncheck | Close

CaseId 18069108 – confirmed

Compartment Visibility – Attributes not shown

According documentation, attributes from a realized interface can be made visible on the class that realizes the interface by showing inherited attributes. However this does not work. The inherited attributes from the interface don’t show up.

Steps to Reproduce:
1. Create a new class diagram
2. Add an Interface to the class diagram
3. Add an attribute to the interface (type: int; scope: public)
4. Add a class to the class diagram
5. Connect class with interface using Realize relationship (source: class, target: interface)
6. Show inherited attributes on class by right clicking on the class > Compartment Visibility... > check Inherited Attributes under Show Element Compartments

Official answer from Sparx: We have confirmed that this is an issue and it should be fixed in a future release of EA

 

CaseId pending

Deployment on Execution Environment Instance not valid according to Package Validation

Details:
According to UML v2.5.1 section 19.2 Deployments artifacts can be deployed to execution environment instances.

However package validation emits an error stating that this type of deployment is not valid.

MVR050002 – error (<anonymous> (Deployment)): Deployment is not legal for Artifact Instance: Component Instance –> Instance Execution Environment: Execution Environment
MVR050002 – error (<anonymous> (Deployment)): Deployment is not legal for Artifact: Component –> Instance Execution Environment: Execution Environment

 

Steps to Reproduce:
1. Create a deployment diagram named “Deployment to Execution Environment”.
2. Create an execution environment named “Execution Environment” and drop it onto the diagram.
3. Create an instance of “Execution Environment” named “Instance Execution Environment” and drop it onto the diagram.
4. Create a Component named “Component” and drop it onto the diagram.
5. Create an instance of “Component” named “Component Instance” and drop it onto the diagram.
6. Create an artifact of “Component” named “Artifact” and drop it onto the diagram.
7. Create an artifact of “Component Instance” named “Artifact Instance” and drop it onto the diagram.
8. Create “Deployment Connectors” from the components and artifacts and connect them with both execution environments.
9. Run Package Validation and notice the errors that are generated.

 

Deployment to Execution Environment

Trackbacks

  1. […] further details see the corresponding section EA Version 14.0 Build 1421 does not allow to use Deployment Connector from Artifact to Execution Env… in my bug slayer […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: