Building Web applications with UML
Building Web applications with UML
The Uml Profile for Framework Architectures
The Uml Profile for Framework Architectures
The Essence of Multilevel Metamodeling
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
UML-based Behavior Specification of Interactive Multimedia Applications
HCC '01 Proceedings of the IEEE 2001 Symposia on Human Centric Computing Languages and Environments (HCC'01)
UML'00 Proceedings of the 3rd international conference on The unified modeling language: advancing the standard
A classification of stereotypes for object-oriented modeling languages
UML'99 Proceedings of the 2nd international conference on The unified modeling language: beyond the standard
Evaluating UML using a generic quality framework
UML and the unified process
An empirical assessment of using stereotypes to improve reading techniques in software inspections
3-WoSQ Proceedings of the third workshop on Software quality
Journal of Systems and Software - Special issue: Quality software
Rapid Prototyping for Pervasive Applications
IEEE Pervasive Computing
Uses and abuses of the stereotype mechanism in UML 1.x and 2.0
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Properties of stereotypes from the perspective of their role in designs
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Extending profiles with stereotypes for composite concepts
MoDELS'05 Proceedings of the 8th international conference on Model Driven Engineering Languages and Systems
Hi-index | 0.00 |
As one of the UML's main extension mechanisms, stereotypes play a crucial role in the UML's ability to serve a wide and growing base of users. However, the precise meaning of stereotypes and their intended mode of use has never been entirely clear and has even generated much debate among experts. Two basic ways of using UML stereotypes have been observed in practice: one to support the classification of classes as a means of emulating metamodel extensions, the other to support the classification of objects as a means of assigning them certain properties. In this paper we analyze these two recognized stereotype usage scenarios and explain the rationale for explicitly identifying a third form of usage scenario. We propose some notational concepts which could be used to explicitly distinguish the three usage scenarios and provide heuristics as to when each should be used. Finally, we conclude by proposing enhancements to the UML which could support all three forms cleanly and concisely.