Messages

1

General Board / Re: Multiple instances of the same element

« on: June 03, 2010, 04:38:58 am »

Andrew,

if you have a scenario where one use case is used by different "services", you would model these services as actors. Then you utilise the "use" association and link all actors to the same use case. That's the normal way of doing it, and you wouldn't need different instances of the same use case at all. If one of these actors uses some additional functionality not included in the original use case, you create a new use case denoting the extended functionality and associate it with the original use case using an <<extends>> relationship.

Cheers,

Till

2

General Board / Re: Multiple instances of the same element

« on: June 02, 2010, 05:59:11 am »

Yes, this is possible, although it is semantically different from adding the same "activity" multiple times.

An activity can only be defined once, however, you can add multiple "invocations" of that activity to the diagram.

To do this, hold the CTRL key while dragging the activity from the Project Browser to the diagram. In the dialog, select "as Invocation of an Activity (Action)" under "Paste Element into Diagram".

Cheers,

Till

3

General Board / Re: C# generator doesn't include namespace?

« on: June 02, 2010, 05:50:25 am »

Glad I could help.   Happy modelling!

Cheers,

Till

4

General Board / Re: C# generator doesn't include namespace?

« on: June 01, 2010, 10:07:29 pm »

Also ensure that the "Generate Namespaces" flag is set in the EA options.

(1) Go to "Tools" > "Options"
(2) Under "Source Code Engineering" select "C#"
(3) Set "Generate Namespaces" to "True" under "Options for the current user"

Moreover, make sure that the namespace root is set to the absolute root package, for example, if you have a package structure as follows

- C# Model
-- Logic
--- Ifc
--- Implementation

your namespace root should be set on "C# Model", yielding namespaces "Logic", "Logic.Ifc", and "Logic.Implementation", respectively.

Cheers,

Till

5

General Board / Re: How to create arrays of attributes?

« on: July 07, 2008, 02:13:13 am »

Hi,

whether you use a generic list really depends on your modelling approach. If you prefer to create a technical class model, you would use "List<double>" directly as a type for your attribute (without explicitly declaring the attribute a collection). You do not need to extend the data types of the programming language for this purpose since they should only contain primitive list types.
This of course results in a tight coupling between your model and the future implementation (C#, Java, etc.) since you use language-specific data types.

The other approach is to create a business domain model first. In this case you would model multi-valued dependencies by an association. You can then specify default collection types which are to be used for the implementation of such associations in the EA Options or in the properties of the association itself.

You kind of have a point there since you want to specify an attribute containing a set of "double" values, i.e. a set of primitive data type instances. In case you are developing a domain model, I would probably stick with an array. With regard to more complex data types, e.g. collections of user type instances, I would only use associations to model multi-valued dependencies.

Cheers,

Till

6

General Board / Re: How to create arrays of attributes?

« on: July 06, 2008, 08:31:08 pm »

Hello,

yes, there is a way of doing this. Open the properties of the corresponding attribute and go to the "Detail" tab. Tick the box "Attribute is a Collection" and put "[]" into the "Container Type" field, then click "Save" at the bottom.

Hope this helps.

Cheers,

Till

P.S.: Note that it is probably better to use a "real" collection type here as you can manipulate its content more dynamically than you could with an array. You could then still use a getter or property to return an array to the caller.