Bug 482645 - [SysML 1.4][BDD/IBD] Support "Part notation" for SysML 1.4 ports (inclusive nested ports)
Summary: [SysML 1.4][BDD/IBD] Support "Part notation" for SysML 1.4 ports (inclusive n...
Status: NEW
Alias: None
Product: Papyrus
Classification: Modeling
Component: SysML (show other bugs)
Version: 0.8.0   Edit
Hardware: All All
: P3 normal with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 473722
Blocks:
  Show dependency tree
 
Reported: 2015-11-20 04:35 EST by Klaas Gadeyne CLA
Modified: 2016-04-22 09:06 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Klaas Gadeyne CLA 2015-11-20 04:35:05 EST
One _important_ asset for the representation of physical systems that was added in SysML 1.4 (actually most of it in SysML 1.3, see fi. http://www.pslm.gatech.edu/events/frontiers2011/1.3_Friedenthal.pdf) is a dedicated representation for parts which are on the physical boundary of other parts.

Currently, papyrus only allows to use the standard UML notation for ports, and displays the additional <<full>> or <<proxy>> stereotype.  However, other important parts are not yet supported:

- The ability to add Nested ports, see Section 9.1.2 and table 9.1 for the notation on the BDD, and table 9.2 for the notation on the IBD diagram
[quote]
Blocks with ports can type other ports (nested ports). 
[/quote]

- The ability to show the port using a part notation, i.e. including compartments
Spec Section 9.3.1.6 on page 79 and table 9.1 for the notation on the BDD, and table 9.2 for the notation on the IBD diagram.
[quote]
All ports and nested ports (i.e., proxy, full, and ports with no stereotype applied), and their type definitions (e.g., interface blocks, blocks) can include compartments with textual and graphical representations to display their features in the same way as other properties and types, including rectangles used to display properties in structure compartments.
[/quote]

I bundle these in one bug since I think they there is a single implementation that solves both of them: a port can either be visualized as a UML port, or as a part property which is locate _on_ the boundary of another block.