Re: [SysML Forum] Re: How design two interfaces in the same SysML model ?

[Stéphane Vayssier]

Hi Paolo,

Since you are using Artisan Studio ( a very nice tool  ) you can use its redefinition capabilites to design your system. This mechanism, although being very usefull, is still not included in the UML / SysML standard.

As explained earlier, you need to create an abstract Block (Connectic) and add the Generalization relationship between this block and your Ethernet and Can Blocks.

Then create a Block (your Equipment), create a Standard Port and set its type to Connectic.

Then, let's imagine that you have 2 Systems (System1 and System2) that are actually made of an Equipment.

Create System1 and System2 blocks, add a part typed by Equipment.

Create the IBD of System1, populate its parts, and populate the standard port of the part. If you change the type of the part's standard port (i do insist this must be done on the part typed by Equiment, not on the Block Equipment itself), you'll see that the Part standard port type has been change, without changing the Block's standard port type.

The redefinition mechanism allows you to "change" the type of Ports on a Part as long as the type you want to set is a subtype of the type of the Block's standard port.

If you are currently using Artisan Studio 7.4, i can send you the model I built

Stephane

2013/2/22 Stephan Roth <stephan....@googlemail.com>

Hi Paolo,

your basic approach is correct: you should create a block for your CAN bus, and another block for your Ethernet interface. Then you can describe the internal structure of those interfaces in their ibd's.

To introduce a kind of "varition point" it is common practice to introduce an abstract block, e.g. you can name it "CommunicationInterface", as a base type. Then you should use the generalization relationship to express that this new abstract block is the base element of your concrete CAN bus and Ethernet interface.

Now you will be able to define the type of your port with the help of this abstract block. I don't know Artisan good enough to explain it in detail, but the SysML 1.3 standard port can be typed with the help of a block, so that you will see the name and its type in the diagram, e.g.: "<<full>> ci : CommunicationInterface".

Hope that helps.

Regards,

Stephan

Am Donnerstag, 21. Februar 2013 15:14:08 UTC+1 schrieb Paolo Chiummo:

Hi all, I've a question about SysML formalism.
I’m designing (with Artisan Studio) the costructional view for a new equipment.The aim is to have an equipment which is able to support two type of interfaces (CAN bus OR Ethernet).Remember OR and not AND.
I would design the model to reduce the impact in SysML model.
Step 1) In IBD diagram of my equipment I introduced a generic flowPort (name is :ExternalInterfacePort)
Spep2) I created two new subsystem: one for CAN interface and second one for Ethernet interface.
Step3) For every new sybsystem I designed the BDD & IBD diagram and Blocks for subsystem and part subsytem
Step5) I created a link ( trace to) from my  generic flowPort (ExternalInterfacePort) to subsystem block
Step6) I used "human language" to describe  that the interface  are mutually exclusive.

Which is your opinion?
Thanks!!!

--
--
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.
 
 

[Robert Karban]

Hi,

I suggest also to redefine the port in the specialization in order
to know exactly which ports correspond as there might be more
ports in the specialization.

Robert