Hi,
First, thanks for your answer, I understood it from
a theorical point of view.
But if look to SysML (V 1.3 june 2012) and if
I want to model to model requirements in my application named ProfileTeach
:
- I will create a classe diagram named
teach
- I will model a class
TeachRequirementManager
- I will model a class named
TeachRequirement
- I will add a composite link 0..* between
TeachRequirementManager and TeachRequirement
- I will apply stereotype
SysML::Requirements::Requirement to TeachRequirement and what should I do with
the stereotype properties text and id ?
What I understood from your answer is that all
TeachRequirement instances will have same values for text and id, if tihs is the
case the interest of these properties is meaningless because two different
instances of TeachRequirement should not have the same id. The uniqueness of id
is defined in SysML (16.3.2.3 p 148)
But how two different instances of TeachRequirement
could have different values for id, if id is not like a class properties
?
Of course, I am hardly/strongly (?)
interested by one answer ...
Bernard Granier 8 rue Michel de l'Hospital 95310 Saint Ouen
l'Aumone 01 30 37 27 84
----- Original Message -----
Sent: Tuesday, July 29, 2014 5:49
PM
Subject: Re: [polarsys-iwg] papyrus,
stereotypes and properties
Hi,
See below some answers.
Best
Sébastien.
------------------------------------------------------------------------------------------------------------------------------------------
Sébastien Gérard
Head of the LISE labs and leader of the Eclipse Papyrus project
(www.eclipse.org/papyrus).
+33 (0)1 69 08 58 24 / +33(0)6 88 20 00 47
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
DILS/Laboratoire
dIngénierie
dirigée par les modèles pour les Systèmes Embarqués (LISE),
Point
Courrier n°174
91 191
Gif sur Yvette CEDEX
De :
polarsys-iwg-bounces@xxxxxxxxxxx [mailto:polarsys-iwg-bounces@xxxxxxxxxxx]
De la part de bernard.granier Envoyé : lundi 28 juillet
2014 17:35 À : Polarsys IWG Objet :
[polarsys-iwg] papyrus, stereotypes and
properties
I defined a
stereotype with two properties : name of type String, and size of type
Real.
I create a class
diagram with one class MyClass, applied my stereotype to this class, I found
how to display stereotype attributes but without the attributes types. Is
there a way to display types of stereotype attributes in class diagram ? (not
a profil diagram but a class diagram)
[Seb> ] Stereotpypes and their propertiers are indeed
metainformation. When you applied a stereotype on a class as for example, it
is like creating an instance of kind of class, the stereotype, and to assign
value to its slots. So, it is not possible within a class diagram to display
the type of the properties of a stereotype: you can also display the property
which are indeed a kind of slot (in the sense of slot of an instance
specification in UML) and the value of the slot.
A more general
question about stereotype properties, are they like class properties ? I mean,
in my case, if I generate a java file MyClass.java, should name and size be
generated as properties of MyClass ?
[Seb> ] no, they are not. Properties of stereotype are more
similar to meta-properties of the Class, e.g. the isAbstract meta-properties
of the meta class Class.
Bernard
Granier 8 rue Michel de l'Hospital 95310 Saint Ouen l'Aumone 01 30 37
27 84
|
Ce
courrier électronique ne contient aucun virus ou logiciel malveillant
parce que la protection Antivirus
avast! est active. |
_______________________________________________ polarsys-iwg mailing
list polarsys-iwg@xxxxxxxxxxx To change your delivery options, retrieve
your password, or unsubscribe from this list,
visit https://dev.eclipse.org/mailman/listinfo/polarsys-iwg
|
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection Antivirus avast! est active.
|
|