Analysis diagram - objects/classes

[Paul W]

OK, Am I missing something.

I have defined a domain model using a class diagram and added Classes stereotyped as Entity.

I now want to create an Iconix Robustness diagram and introduce UI (<<Boundary>> Class) objects and Controller (<<Control>> class).

The process shows the use of the Analysis Diagram (UML->Extended) and the toolbox contains an number of relevant tools.

The problem is when I create a UI object using the Boundary tool it creates an Object element not a Class element stereotyped.

If I look at the Help for Activity diagram and then click on the toolbox items for Boundary/Control/Entity it takes me to a page that states they are Classes with stereotypes!!! But they're not

I want to be able to create a UI diagram with a storyboard using the UI elements as part of the UI object, but I can only do this if it is a Class element.

Am I missing a simple solution to this?

Is there a simple way of changing the behaviour of the toolbox to create a Class element and not an Object element?

[RoyC]

I can't comment on the Toolbox Boundary, Entity and Control elements at the moment, but to create these as stereotyped Classes, drag the Class element from the toolbox onto the diagram and, in the properties, set the stereotype to boundary, entity or control. You might have already done this for the Entity?

[KP]

To have them appear in the toolbox, create a UML Profile with three stereotypes («boundary», «control» and «entity») all extending "Class". The EA help file will explain how.

[RoyC]

OK, the Help was wrong.

As Paul found, the Analysis diagram Toolbox page creates Boundaries, Controls and Entities as stereotyped Objects. EA used to offer the choice of creating the elements as stereotyped Objects or stereotyped Classes, but now defaults to Objects.

As I mentioned earlier, you can easily create them as stereotyped Classes by creating a Class element and applying the appropriate stereotype. And as Neil mentioned, you can get the Toolbox elements to insert stereotyped Classes by defining them in a Profile.

Sorry about the confusion. I have corrected the Help - changes visible in the next release.