this gets a bit more complicated when you start using required and provided interfaces, but has the advantage that you neither lose information, nor add superfluous ports which may inhibit alternate designs in the future (and generally add mess on the higher levels.)
> Date: Fri, 6 Nov 2009 05:09:51 -0800
> Subject: [SysML Forum] Ports and (Internal) block diagrams
> From: frederic.fontan
...@gmail.com
> To: sysmlforum@googlegroups.com
> Hello,
> I am a little bit new on sysML, I hope you'll forgive me to query on a
> basic question.
> I try to modelize a system, allocated on several centres. Centre A and
> centre B.
> Centre A is divided into 2 parts : Part A1 and Part A2
> Centre B is divided into 2 parts : Part B1 and Part B2
> On a logical point of view, A1 communicates with B1 and A2
> communicates with B2., so A1 has a standard port p_B1 and A2 has a
> standard port p_B2
> When I draw the internal block diagram of the system, I draw my system
> with the two centres
> centre A has a standard port for communication with centre B : p_B,
> and B has a standard port for communication with centre A : p_A.
> but, when I draw the internal block diagram of the centre A, should I
> connect part A1 ports p_B1 and p_B2 to the port p_B ? If I do so, I
> loose the information of the destination/provenance of the interfaces
> exchanged with the parts. But if I create discriminated ports (one for
> B1 and one for B2) It means that the centre ibd will contain more
> ports, without signification at this level.
> Could you help me, please ?
|
