Hi all,
I have already submit a bug related to that question. It is number 2939...
<http://gforge.enseeiht.fr/tracker/?func=detail&aid=2939&group_id=52&atid=109>
This is really important in order to be able to provide standard
libraries to reuse. For instance, you could reused the definition of a
two-electrical-pins component.
@Raphaël, I think I will to talk to you about that this morning... ;-)
--
Regards,
Loïc Fejoz
Le 18/03/2010 17:25, [email protected] a écrit :
Hi Klaas,
this is indeed a very interesting question, not fully addressed today by
TOPCASED, and that raises a lot of questions.
In terms of faisability, it is possible to provide "inherited members"
section so that we can see ports/properties/operations/receptions
available from parent element. See Block2 example below.
Then we have several questions (and it is probably a good idea to create
a feature request where we can centralize the discussion about
specification):
1. can we modify inherited members in the outline view (name, type,
default value...)?
* I think that we should be able, and that it should lead to a
"refined" member.
2. can we drag and drop a member to a diagram ?
* It should be possible, but then we need to distinguish
inherited members and "local" members. We probably need to
identify too "refined" members.
3. what does mean linking an inherited property to a property from
another class/Block. As it can lead to change the definition of
the inherited property, we might refuse such an action..
* which are the rules concerning possible actions and
forbidden ones on inherited members? any ideas of formal rules?
4. Should we enforce rules on real time or by an OCL rule ?
Thanks for your answers and for creating a feature request about it,
best regards
raphaël
[email protected] a écrit :
Hi,
suppose I have a block Generic1, that has two flowPorts. If I now create a
Block Concrete1 that generalizes Generic1, would that imply that Concrete1 also
has the same two flowPorts?
I would have expected this, but at least, in topcased, it is not the case, but
I have to admit I can't find a clear statement about it in the spec either.
Unfortunately, this now means, that, fi. if I want to create 3 "Concrete"
blocks (what's in a name :-) that I have to add the ports each time again (and that I
would have to create an OCL rule that checks if the ports of a parent are the same/(a
more specific) type/name as those from their children?
Thoughts?
TIA,
Klaas
ps. The same goes for properties/operations/...
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
--
Image Signature IOC <http://www.atosorigin.fr/> *Raphaël FAUDOU*
*Responsable cellule Innovation / bureau méthodes *
*Head of Innovation & Method Definition *
*Embedded systems & critical systems *
Atos Origin
Tel : +33 (0)5 34 36 32 89
Tel : +33 (0)6 10 53 50 44
Mail : [email protected] <mailto:[email protected]>
Atos Origin
6, Impasse Alice Guy
BP 43045
31024 Toulouse Cedex 3, France
P Avant d'imprimer cet e-mail, pensez à l'environnement. Ce message et
les pièces jointes sont confidentiels et réservés à l'usage exclusif de
ses destinataires. Il peut également être protégé par le secret
professionnel. Si vous recevez ce message par erreur, merci d'en avertir
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne
pouvant être assurée sur Internet, la responsabilité du groupe Atos
Origin ne pourra être recherchée quant au contenu de ce message. Bien
que les meilleurs efforts soient faits pour maintenir cette transmission
exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard
et sa responsabilité ne saurait être recherchée pour tout dommage
résultant d'un virus transmis.
P Please consider your environmental responsibility before printing this
e-mail. This e-mail and the documents attached are confidential and
intended solely for the addressee; it may also be privileged. If you
receive this e-mail in error, please notify the sender immediately and
destroy it. As its integrity cannot be secured on the Internet, the Atos
Origin group liability cannot be triggered for the message content.
Although the sender endeavours to maintain a computer virus-free
network, the sender does not warrant that this transmission is
virus-free and will not be liable for any damages resulting from any
virus transmitted.
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
