Uncaptured Functional Interfaces between call behavior actions.

Functional Architectures for Systems with SysML - Plugin for MagicDraw

Brought to you by: gfse, gmoe, ipek, j-lamm, and 3 others

#60 Uncaptured Functional Interfaces between call behavior actions.

Milestone: 1.0

Status: open

Owner: Abdallah Altalmas

Labels: None

Updated: 2019-10-11

Created: 2019-10-11

Creator: Abdallah Altalmas

Private: No

In the Activty diagram, if a "call behavior action1" that has an Interface/Interaction with another "call behavior action2" has an unmapped "activity1" to its corresponding functional group, then the Interface between both of the call behavior actions is not captured and not listed as a proposal during the creation of Interfaces.
Need to write a Warning Log to inform the user.

1 Attachments

ticket.PNG

Discussion

Description has changed:

Diff:

--- old
+++ new
@@ -1 +1,2 @@
 In the Activty diagram, if a &#34;call behavior action1&#34; that has an Interface/Interaction with another &#34;call behavior action2&#34; has an unmapped &#34;activity1&#34; to its corresponding functional group, then the Interface between both of the call behavior actions is not captured and not listed as a proposal during the creation of Interfaces.
+Need to write a **Warning Log** to inform the user.

Uncaptured Functional Interfaces between call behavior actions.

Functional Architectures for Systems with SysML - Plugin for MagicDraw

Milestone

Searches

Help

#60 Uncaptured Functional Interfaces between call behavior actions.

Discussion