Re: [SysML Forum] full ports in a block definition diagram

[Robert Karban]

You should consider a full port as a part which is literally moved to the border of a block. It's really
like a part.
You could also consider it as a kind of part with visibility public (if isEncapsulated=true)

On 14/05/2013 07:43, Torsten Gilz wrote:

Dear all,

I have problems with the understanding of full ports. In the example of the VPE-Robot I modelled the connection ports, which have a physical representation (the housing) and pins inside.

The pins and the sensor port are now parts of the building structure. In the picture I attached the composition relation between NXT Block and Sensor Port is explicit modelled. I'm not sure that this is conform to the SysML 1.3 spec.

The SysML specification says, that a full port is a part of the block. Does this mean, that there is an implicit composition relation, which is not shown?

I'm struggeling with the meaning and usage of the full port. How can the parts, which are represented by the full ports be shown in the bdd?

 

thanks

   Torsten

 

--
--
You received this message because you are subscribed to the Google
Groups "SysML Forum" group.
Public website: http://www.SysMLforum.com
To post to this group, send email to sysml...@googlegroups.com
To unsubscribe from this group, send email to
sysmlforum+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sysmlforum?hl=en_US?hl=en
 
---
You received this message because you are subscribed to the Google Groups "SysML Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sysmlforum+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[zhou, yi]

Hi,

I am developing a SysML tool.

In my SysML tool, a full port on the boundary of a block isn't shown in the part compartment of the block.

I attached the image.

Is this a bug?

If a full port should be considered as a part, it should be listed in the part compartment of a block.

Yi

2013/5/15 Stephan Roth <stephan....@googlemail.com>

Hi Torsten,

a full port is something like a part on the boundary of a block, and yes: it represents a part of the encapsulating block. Full ports are generally typed by a block, and they can handle incoming items, operations, and signals by themselves, furthermore they can send out items, etc.

In your diagram, the block "Sensor Port" is the type of your full ports 1...4 in your NXT brick. In an corresponding ibd you would have four ports on the boundary on the boundary of a part "Mikrocontroller:NXT Block". As far as I know, the block "Sensor Port" used to specifying the type of those four ports must not be a part of the NXT Block, because somewhere else in the system you might reuse it for specifying more ports.

Hope that helps,

Stephan

Am Dienstag, 14. Mai 2013 16:43:34 UTC+2 schrieb Torsten Gilz:

Dear all,

 

I have problems with the understanding of full ports. In the example of the VPE-Robot I modelled the connection ports, which have a physical representation (the housing) and pins inside.

The pins and the sensor port are now parts of the building structure. In the picture I attached the composition relation between NXT Block and Sensor Port is explicit modelled. I'm not sure that this is conform to the SysML 1.3 spec.

The SysML specification says, that a full port is a part of the block. Does this mean, that there is an implicit composition relation, which is not shown?

I'm struggeling with the meaning and usage of the full port. How can the parts, which are represented by the full ports be shown in the bdd?

 

thanks

   Torsten