|
Re: IBD item flow [message #1715391 is a reply to message #1715271] |
Mon, 23 November 2015 08:56 |
Klaas Gadeyne Messages: 165 Registered: July 2009 |
Senior Member |
|
|
Stephen Blackwell wrote on Fri, 20 November 2015 12:42Section 9.3.0.5 of the SysML1.4 spec describes the notation of an Item Flow as "...a black arrowhead on the connector or association.". Table 9.1 show several examples as solid black lines with a filled arrowheads in the middle of the line.
The Item Flow on the IBD diagram in Papyrus is a dashed line with an unfilled open arrowhead at the destination end of the flow.
Another bug?
Hi Stephen,
I can confirm it doesn't work AFAICT, this might rather be a complex issue. As you can see in Figure 9.5, SysML itemflow is a stereotype that extends the UML InformationFlow metaClass. Looking at the UML 2.5 specification, it looks as if UML 2.5 specifies 2 possible notations for InformationFlow. On the one hand, there's the dashed line with open arrowhead, on the other hand there's the 'add-on' notation that just 'adds' a closed arrowhead onto an existing connector or association.
I had a quick look, and (I might have missed something) it seems that the SysML specification adds an additional constraint (see 9.3.2.11, constraint [1]) that specifies that
Quote:
A Connector or an Association, or an inherited Association must exist between the source and the target of the InformationFlow.
This is probably the reason why the SysML specification only retains the second (add-on) notation.
So my guess is that this is not (only) a papyrus SysML 1.4 bug. I would assume that the proper way to fix this, is to provide the necessary support in papyrus UML for the add-on option, and then "forbid" the first notation in the SysML 1.4 plugins.
So, instead of 'another bug', I would say, some more enhancement requests Feel free to verify my thoughts, and create the necessary bugs and link them from within this thread!
HTH,
Klaas
|
|
|
|
|
Re: IBD item flow [message #1716090 is a reply to message #1716040] |
Tue, 01 December 2015 09:22 |
Camille Letavernier Messages: 952 Registered: February 2011 |
Senior Member |
|
|
Hi,
The Papyrus Diagrams do not support all the different notations of the InformationItem. However, the underlying framework is flexible enough to be able to represent most of them.
There is one exception however: we don't support the Fig. 20.5 or 20.6 notation (A Triangle on a Connector - or any other decoration)
So there are several bugs and/or limitations:
- Papyrus UML Diagrams do not properly allow all representations of the InformationItem: Fig. 20.2 is OK, 20.3 is OK, 20.4, 20.5 and 20.6 are not supported
- Papyrus Framework doesn't support custom decorators on Connectors: This prevents support for Fig. 20.5 and 20.6
So 20.4 could be supported with the current framework, whereas 20.5 and 20.6 would need additional customization capabilities in Papyrus
I think this requires at least two bug entries: One against the Class Diagram (And possibly other diagrams where InformationItem/Flow should be supported) for 20.4, and another one for the generic diagram framework to support decorators on connectors
Then, on top of that comes SysML 1.4 with either extra notations (New/different notations) or restricted notations (Only one notation among the many allowed by UML)
HTH,
Camille
Camille Letavernier
|
|
|
|
Powered by
FUDForum. Page generated in 0.01913 seconds