Messages

1

General Board / Re: Displaying attribute-level constraints

« on: January 22, 2013, 07:06:48 pm »

200% agree that xUml should be considered as a temporary work-around until Sparx provides a real uml-compliant solution.
Thanks guys for your supporting this.

2

General Board / Re: Displaying attribute-level constraints

« on: January 18, 2013, 09:19:48 pm »

Yep, this is top notch!

By the way I've just introduced a new feature request to have attribute- level constraints shown natively in the attribute compartment.

In the meantime, xUML will be heavily used!

3

General Board / Re: Displaying attribute-level constraints

« on: January 18, 2013, 07:41:25 pm »

Excellent! I'm just wondering where you catched this "hidden feature" from...  

4

General Board / Re: Displaying attribute-level constraints

« on: January 14, 2013, 06:50:23 pm »

Thanks for the tip.
Have a good day,
Bernard

5

General Board / Displaying attribute-level constraints

« on: January 10, 2013, 10:35:10 pm »

Hi,

In a class diagram, is there a way to display attribute-level constraints in the attribute compartment?

Thanks for your help!

Bernard

6

General Board / Re: Notes field size in attribute window

« on: August 29, 2012, 11:24:53 pm »

Thanks Geert! Your workaround is top-notch!

If some EA guys are reading this post : would it be possible to add a "splitter" between the notes field and the attribute list : increasing the height of the notes field would decrease the height of the attribute list?

Kr,
Bernard (from Belgium as well  )

7

General Board / Notes field size in attribute window

« on: August 29, 2012, 10:48:54 pm »

Hi,

Is there a way to configure (to increase) the notes field height in class attribute windows?

It's currently limited to 2 scrollable lines, which is not that convenient.

Thanks in advance for your help,

Bernard

8

General Board / Re: Link to artifact that is within another EAP

« on: August 14, 2012, 10:57:36 pm »

Of course the point is not to avoid hacking, but to make it less straightforward to change/delete artifacts one doesn't own or can't update because of package-level "security" configuration.
If you go directly to the database, even the current EA security model is useless since you can delete/update whatever you want.

9

General Board / Re: Link to artifact that is within another EAP

« on: August 14, 2012, 08:29:52 pm »

We also had the same requirement, but found not practical ways to implement it.
I still think that having one single centralized EA repository for all departements should be the way to go (for performance reasons, moving from EAP-based repository to DBMS-based repository is maybe inevitable). As far as we investigated, the major concern about this approach is security : how to insure that analysts from department A don't alter content produced by department B? The showstopper here is that EA doesn't provide package level security (yet ).
Regards,
Bernard

10

General Board / Re: how to model components and classes

« on: March 09, 2012, 02:41:11 am »

It's a question of taste... I like "simple" components :
- when I don't have to modelize the internals
- when I need to modelize required/provided interfaces (i.e. for a participation in a sequence diagram)
Bernard

11

General Board / Re: how to model components and classes

« on: March 08, 2012, 01:21:55 am »

Maybe you could try using Packaging Components (see Component Diagram).
Hope this helps,
Bernard

12

General Board / Re: Changing the icon displayed on a diagram! Help

« on: February 07, 2012, 07:22:47 pm »

Hi,
We are facing the same issue. Our idea was to apply a DDD-like approach by reusing robustness entities as aggregate roots into class diagrams. But... it is not possible within EA!!! We were obliged to create entitities and aggregate roots separately and link then together to keep traceability (dependency).

This "simple" limitation complicates everything and makes the traceability difficult to manage.

We don't want to start playing with shape scripts for a feature that should be built-in.

Kr,
Bernard

13

General Board / Re: Choosing stereotype appearance per diagram

« on: December 19, 2011, 08:02:58 pm »

Hmmm it's quite annoying... Is there any hope to see this feature natively included in a next release?

For example, in the "Feature Visibility" context menu, we could have the choice to display the stereotype shape or not.

Bernard

14

General Board / Choosing stereotype appearance per diagram

« on: December 17, 2011, 01:23:01 am »

Hi All,

Is there a way to choose the stereotype appearance of an element per diagram?

Here is our case : We have an "Entity" stereotyped class which has to be shown on a class and a sequence diagram.

On the class diagram we would like it to have a "class look"; on the sequence diagram we would like it to have a "robustness look"...

How do we do that?

Thank in advance,

Bernard

15

General Board / Re: connecting different projects

« on: December 06, 2011, 07:50:33 pm »

Oups, sorry by root package I meant root node (root model).