if i understand correctly, the port cannot "provide" a service, rather it defines a point of interaction with the block.
the block must provide the service.
the block should inheret the same interface that is "provided" by the port, and should either include an implementation of the service, or an allocation to a sub-block.
hope this helps.
- daniel
From: dobre.dra...@gmail.com
To: sysmlforum@googlegroups.com
Subject: [SysML Forum] Interfaces usage
Date: Mon, 9 Nov 2009 15:55:34 +0100
Hello,
I have tried to understand the use of
Interfaces on standard ports and I even use them to provide or require
operations (as in Interfaces we define the operations). What I didn’t
understand is why in an Sequence Diagram it is not possible to use these
operations in order to describe the system’s behavior (communication
between ports is made by calling the Interfaces operations). I’m using
Artisan Studio Uno and when I want to call an operation from other block
(described by the Interface), within a sequence diagram, the operation must be
provided by the block (the operations from the Interface are not seen by the
block) and so I have to redefine the same operation defined in the Interface.
Can someone explain the use of Interfaces
(not only to show which block connects to which, but also the further use for
this connection and the declared operations).
Regards,
Dragos DOBRE
Doctorant - Nancy Université - Université Henri Poincaré
Centre de Recherche en Automatique de Nancy - CRAN
Faculté des Sciences, BP 70239
54506 Vandoeuvre-lès-Nancy
Tél: +33 (0) 3.83.68.40.00 P81450
Fax: +33 (0) 3.83.68.44.59
_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/
|
