Closed oalt closed 5 years ago
So far, I have used a property with title 'SpecIF:Stereotype' as follows:
Have a look at BPMN-Example
Does this help in your situation?
.. so with respect to your question: There are several resourceClasses, where Stereotypes make sense, e.g. FMC:Actor, FMC:State, FMC:Event, IREB:Requirement and SpecIF:Feature. I haven't thought about the others, yet. In case of resourceClass with title SpecIF:Diagram I have used a property SpecIF:Notation to distinguish different types, for example. So I do not see the need of a stereotype for all resources ...
The main criterion on whether a certain type/subtype becomes a resourceClass or just a stereotype of a more general resourceClass is:
@oalt : if you see the need for additional discussion or a change of the schema, please reopen this issue.
Makes it sense to apply the property 'PC-Stereotype' to each SpecIF resource class or is this restricted to a specific subset? Which practical experience is available using the stereotype property?