Activity Diagrams

Home Forums Executable UML and xtUML Methodology Activity Diagrams

This topic contains 3 replies, has 2 voices, and was last updated by  cort 3 weeks, 1 day ago.

Viewing 4 posts - 1 through 4 (of 4 total)
Author Posts
Author Posts
April 28, 2019 at 3:11 am #6221

Rob
Participant

I have not seen much in the tutorials about the activity diagrams but they are in the xtUML perspective. Are there ways to make the models executable utilizing the activity diagrams? Can the activity diagrams contain OAL? If not, what is the purpose of the activity diagram with xtUML? Do they just provide amplifying information?

April 29, 2019 at 12:38 am #6222

cort
Keymaster

Rob,

In the long-time past, BridgePoint supported only class diagrams, state machines and a bit of packaging. OAL was supported in the state machines and later in domain functions. This was the original base of Shlaer-Mellor modeling.

Enter UML. UML supports many diagrams. So these diagrams were added to BridgePoint. Use Case, Sequence, Activity and Communication diagrams were added. These are useful to define/describe individual scenarios of an application. They are not part of the solution but part of description of the solution.

The components, class diagrams and state machines represent the executable portion of the solution.

Note, there is a way to connect (“formalize”) the elements in the Use Case, Activity, et al to the executable elements. Let me know if you are interested.

Note, there is a way to configure the user interface of BridgePoint to support only the diagram and element types that you want to use in your work.

Regards,
Cort

April 29, 2019 at 11:04 pm #6223

Rob
Participant

Cort,

Yes, I am interested in the way to connect (“formalize”) the elements in the Use Case, Activity, et al to the executable elements.

Thanks,
Rob

April 30, 2019 at 12:40 am #6224

cort
Keymaster

When you have a class, component, message or other element in some informal (non-executable) diagram, you can right-click on the element and select ‘Formalize’ from the context menu. You can then select an element from the executable specification model. This presses you to treat elements in the informal diagrams more carefully. It causes you to consider carefully elements you may have in these diagrams that have no counterpart in the executable solution model.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.