Interfaces and Ports on a Block (BDD) and sequence diagrams

[Guillaume Finance]

Hi,

Using Sparx Enterprise Architect, I created a BDD to describe my Block with a number of ports, and for each of them the provided/required interfaces selected from a separate model that contains all interfaces.

This follows well SysML specs, but I face an issue as far as the tool is concerned when using sequence diagrams.
If I create an instance of the block on a sequence diagram, operations aren't available since they're defined in the interface provided by port.
I can display the embedded elements (Port + Interface) under the block's instance on the sequence diagram but  :
1. it doesn't render things properly (3 lifelines displayedunder the block),
2. I'd rather have all operations available from my block when drawing a message (list of available operations)

I currently realise each interface from my block which isn't ideal since this is only done so I can create my sequence diagrams.
Has anyone experienced this and could suggest a solution?

Thanks,
Guillaume

[Eran Peleg]

Hi Simon

Actually there is a formal and implementation (at least in IBM-Rhapsody) of the required connection:

Ports can have Interfaces (actually Standard-Ports) – provided and required interfaces; Interface can have Operations with or without parameters.

These operations with the internal parameters as Objects, are available as drop-down elements for selection in Sequence Diagrams (SD).  Two way of modeling ICD can connect Blocks and SDs:

1. Message oriented ICD – the messages are connected to Operation as their parameters; Operations are connected to Interface; Interface are connected to Ports; Ports are on Blocks; the Operations are available for SDs.
2. Block API is modeled as Ports-Interface-Operations-Parameters (of type Object).  Then the Interface of the Block or the Block can be a Life-Line in SD.

 

As you requested.

 

Regards

Eran

 

======================

Eran Peleg, CEO

Metaphor Vision Ltd.

Phone: +972545346060

Fax: 151545346060

eMail: epe...@metaphor.co.il

Skype: EranPelegMetaphor

======================

---

From: sysml...@googlegroups.com [mailto:sysml...@googlegroups.com] On Behalf Of Schwicht
Sent: Friday, September 07, 2012 11:17 PM
To: sysml...@googlegroups.com
Subject: [SysML Forum] Re: Interfaces and Ports on a Block (BDD) and sequence diagrams

 

Any updates on that?
I discovered similar problems in Eclipse Papyrus.
I do not find any sufficient statements in the SysML specification about modelling behaviour of blocks with ports. Furthermore, there are no sufficient informations about the connection between block diagrams and sequence diagrams, when ports are used for the communication.

I want to model sequence diagrams where the lifelines represent blocks but I want to use the operations or receptions from the ports for the messages.

Regards,
Simon

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

[Matthew Hause]

Artisan studio implements these as well. We also support the direct placement of the messages on the sequence diagram as well. At the time, it was not strictly SysML, but our customers demanded it. Otherwise, how could you show the flows from your IBD in a sequence? As UPDM supports these flows, we will need to make this feature official. We also support a feature that support the placement of flows between blocks that are received by the ports. Otherwise you have to model every single flow of the sequence which can get quite tiresome. Basically, we abstract the receipt of the flow to the ports up to the blocks.

[Eran Peleg]

Hi Matthew Hause and the forum

We are working a bit differently …

1. Blocks with or without Ports, are connected by Connectors; Connector represent a network.
2. A flow is attached to a connector;  actually more than one Flow may be attached to each connector
3. A flow is carrying Flow-Items (which are Class representing Messages; <<MessageSW>>Class)
4. An Interface attached to the Port
5. An operation with the name of the Message and a parameter of Type <<MessageSW>>Msg1 is created on the Interface
6. Now, the Connector-Flow-MessageSW representing the NW, Flow, Objects respectively and the Interface with its operations are making the Messages available on SD.
7. Message definition is unique within the model.  It can be placed on the static IBD diagram and on dynamic AD or SD as required.  It stays the same one-element message.

 

It is all implemented with Rhapsody.

 

Regards

Eran

 

======================

Eran Peleg, CEO

Metaphor Vision Ltd.

Phone: +972545346060

Fax: 151545346060

eMail: epe...@metaphor.co.il

Skype: EranPelegMetaphor

======================