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 - Uffe

Pages: [1] 2 3 ... 20
1
General Board / Choosing a tool
« on: Today at 06:54:23 pm »
Hi all,


This is a tangent from Ian's thread concerning EA vs Aris for process modelling.

I realize that 'it depends' is the most logical answer, but, like most clients, they haven't decided exactly how they are going to do their process modelling.
And I think this is a reasonable approach.
But before you scream 'that's no way to choose a modelling tool', given that they have realized they WILL need a tool, then surely the smart thing is to tailor their approach to (1) their own requirements, but also (2) the capabilities of a tool.

It seems like a solution -> Requirement approach, but don't we need some measure of this? No point crafting a wonderful modelling approach, then finding there is no tool to which can do it without huge modification. And when maybe a small change to the modelling approach would make it fit disproportionately better with one or other tool.

I couldn't agree more with this, and in general universally if you refuse to allow the chosen platform to drive requirements you will end up with a complete mess that combines weak least-common-denominator fulfillment of functional requirements with the massive bloat of "platform independence."

It doesn't matter if you're designing a system, devising a method or picking a tool, if you put those blinkers on (horizontal blinkers, I guess, preventing you from looking down) you'll end up spending an enormous effort on shoehorning which, ultimately, is non-productive work.

Understanding the platform (tool, middleware, operating system, programming language...) and its capabilities, and making sure your solution fits on top of it, is Right not Wrong.


/Uffe

2
Bugs and Issues / ActivityParameter _instanceType not honoured
« on: April 25, 2018, 07:12:11 pm »
Hi all,

If you create two stereotypes, one of ActivityParameter and one of ActionPin, and specify that the parameter stereotype should be instantiated to the pin stereotype using the _instanceType attribute in the ActivityParameter metaclass, that specification is not honoured when EA creates an action pin during instantiation of an activity with parameters.

AFAIK there is no other way to instantiate an activity parameter. You can't drag-and-drop one onto an empty diagram area, nor onto an action.

Reported.


/Uffe

3
Bugs and Issues / Language in activity parameters and action pins
« on: April 25, 2018, 06:58:30 pm »
Hi all,


When you create an activity parameter in a diagram, the parameter's Language property is set to the project's default regardless of the corresponding properties in the diagram and the activity.

If you create the parameter in the Structural Elements dialog, the behaviour is the same.

The behaviour is also the same for action pins in actions, both when created from the toolbox and in the Structural Elements dialog.

When an action pin is created as the result of instantiating an activity with paremeters, the pin is likewise given the project default Language.

When an activity parameter is created, its Language should be set to the same as its parent activity's.
When a pin is created manually, its Language should be set to the same as its parent action's.
When a pin is created as an instance of a parameter, its Language should be set to the same as the corresponding parameter's.

Reported.


/Uffe

4
Bugs and Issues / Actions in toolboxes
« on: April 24, 2018, 09:05:52 pm »
Hi all,


If you specify a toolbox which includes the following attribute definition

Name: UML::CallBehaviorAction
Initial Value: CB Action

... the resulting toolbox creates CallBehaviorActions correctly, but the icon is incorrect. Instead of the standard action icon, the stereotype icon (from the Profile toolbox) is displayed.

If instead you define the toolbox attribute as

Name: UML::CallBehaviorAction(UML::Action)
Initial Value: CB Action

... the correct icon is displayed.


Also, while the user guide page on elements used in toolboxes omits CallOperationAction (but includes CallBehaviorAction), you can in fact specify a CallOperationAction in your toolbox, and it works as expected.

Both reported.


/Uffe

5
Bugs and Issues / CallOperation actions, action pins and exceptions
« on: April 23, 2018, 09:34:26 pm »
Hi all,


If I create a CallOperation, regardless of whether I've assigned an operation to it, I can't create my own action pins for it. That's OK, the intent is that CallOperation actions should be linked to operations, and the "Synchronize with Parameters" function in the properties dialog (in the Call tab) allows me to create pins for the operation's parameters.

But what if I want to create a pin for an exception?

An operation's parameters cannot be exceptions. There's no exception property to select. What you can do is add "raised exceptions" to the operation in the properties dialog, Redefines tab.

An action pin, on the other hand, can be an exception. There's an "Exception" property on a pin, and selecting it causes the pin to be displayed differently in diagrams (with an added triangle).

See where I'm going?

I can't manually add pins to a CallOperation action.
The CallOperation action's "Synchronize with Parameters" only creates action pins for the operation's parameters, not for its raised exceptions.
Pins can be exceptions, but operation parameters can't.

So.

How do I represent visually the call to an operation which throws exceptions?


/Uffe

6
Hi all,

The default display of a CallOperation action looks a bit like this:
              ActionName
    InterfaceName::OperationName


Or, if the action's name is the same as the operation's (which it is by default):
        ActionAndOperationName
           InterfaceName::


I've been testing a bunch of parameters in a custom shape script, but I can't seem to get at the interface name: neither the classifier.* nor the  propertytype.* properties give me what I need. (Classifier shows the operation name, but only until I close the diagram; when I reopen it, it's blank.)

Is there a hidden property that contains the "classifier" operation's parent element?


/Uffe

7
Bugs and Issues / CallOperationActions in project browser
« on: April 20, 2018, 10:04:54 pm »
Hi all,


A CallBehaviourAction is displayed with its classifier in the project browser on the form action_name : classifier_name.
A CallOperationAction, on the other hand, doesn't display its operation.

Shouldn't it?

Something like action_name : element_name::operation_name, where element is the interface, class, component or whatever that holds the operation?


/Uffe

8
If you create a stereotype for Action and assign it a shape script which prints the Classifier or Classifier.Name property, the expected behaviour for a CallOperationAction is that the name of the operation (when set) is printed. It is not.

When you set the action's operation, the name of that operation is printed -- but only until the diagram is closed. When next it is opened, nothing is printed although you can still Find the operation from the action.

It appears that classifiers defined by the GUID string and not the integer ID aren't handled correctly by the shape script engine.

/Uffe

9
If you create a stereotype for CallOperationAction on the fly, then assign it a shape script in Configure -- UML Types, and then create a CallOperationAction in an activity diagram and give it that stereotype, the shape script is not executed.

If you modify the stereotype to apply to Action, it is executed correctly on the same CallOperationAction.


/Uffe

10
Bugs and Issues / Time-aware models: revert clone
« on: April 19, 2018, 10:14:14 pm »
Hi boys & girls,

I can't find a function to revert a cloned element in a diagram, in other words destroy the cloned element and replace it in the diagram with the original.

Isn't there one?


/Uffe

11
Bugs and Issues / Import/export of time-aware models
« on: April 19, 2018, 09:41:36 pm »
Hellu,


If I clone a package structure to a new version, and then export the new version as XMI, will the exported XMI include the non-cloned elements from the original version?

Similarly, if I do a CSV export will the non-cloned elements be included?


/Uffe

12
Bugs and Issues / Time-aware MDG Technology models
« on: April 19, 2018, 09:39:55 pm »
Hi all,


So I'm thinking about trying time-aware models in my MDG Technology project, where I've got a couple of different technologies.

Let's say I've got a model that I've generated an MDG Technology from, and I clone that model.

If I now generate a profile from a package in my cloned model, going from the project browser and not the diagram, will the generated profile include the non-cloned elements?

Will the generated profile have the same "<Documentation id" attribute as the original?


/Uffe

13
Hi all,


I'm fiddling around with time-aware models to see if they're of any use.

First thing I tried was to set up a simple package structure as version 1.0.
- Parent package
  - Package diagram (showing child package)
  - Child package
    - Component diagram (showing component)
    - Component


Then I went ahead and cloned the whole structure to a new version 1.1. Here's what I got:
- Parent package [cloned]
  - Package diagram (showing original child package)
  - Child package [cloned]
    - Component diagram (showing original component)


This can't be right, can it? Since the child package is cloned, surely the diagram it's in should show the clone and not the original?
The way this is implemented, if I navigate between diagrams by double-clicking the child package, I go from the 1.1 version of the package diagram into the 1.0 version of the component diagram, even though the child package exists as a clone in 1.1 and has a cloned component diagram.

Am I missing something?


/Uffe

14
Bugs and Issues / Downgrading from 13.5
« on: April 18, 2018, 01:33:44 am »
Hi all,


After our recent upgrade from 11.1 to 13.5, we've noticed multiple issues with document generation and database modelling, where things that worked in the older version no longer do in the new. We're getting nothing back from Sparx support, so we're going to have to look at downgrading.

We've upgraded all our databases (SQL Server) to the 1220 version of the schema. This means downgrading to 12.1 should be OK, but I'm thinking about what we'll need to do if it turns out the bugs that are causing our problems were already present in 12.1, meaning we'll have do go even further back to either 12.0 or 11.1, where we know things work.

Does anyone have experience of downgrading past a schema change?

Or is it possible to run 11.1/12.0 on a 1220 schema?

Thanks,


/Uffe

15
Bugs and Issues / No API documentation for Repository.ImportRASAsset()
« on: April 13, 2018, 06:34:55 pm »
Hi all,

There is no documentation in the user guide for the automation function Repository.ImportRASAsset(), which was introduced in 1308.

According to EA's VBScript IntelliSense it takes eight string parameters, which takes a bit more effort to work out through trial and error than I would like to spend.

Reported.


/Uffe

Pages: [1] 2 3 ... 20