Conference Paper

Stereotypical Encounters of the Third Kind.

DOI: 10.1007/3-540-45800-X_9 In proceeding of: UML 2002 - The Unified Modeling Language, 5th International Conference, Dresden, Germany, September 30 - October 4, 2002, Proceedings
Source: DBLP

ABSTRACT 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.

  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: An approach is presented to automatically determine a class's stereotype. The stereotype is based on the frequency and distribution of method stereotypes in the class. Method stereotypes are automatically determined using a defined taxonomy given in previous work. The stereotypes, boundary, control and entity are used as a basis but refined based on an empirical investigation of 21 systems. A number of heuristics, derived from empirical evidence, are used to determine a class's stereotype. For example, the prominence of certain types of methods can indicate a class's main role. The approach is applied to five open source systems and evaluated. The results show that 95% of the classes are stereotyped by the approach. Additionally, developers (via manual inspection) agreed with the approach's results.
    26th IEEE International Conference on Software Maintenance (ICSM 2010), September 12-18, 2010, Timisoara, Romania; 01/2010
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: VisualRDK is a high-level programming language for prototyping pervasive applications. Context is tightly integrated into the language itself, so developers can attach functionality to locations, persons, or situations instead of the device. Pervasive computing appliances range from consumer devices over embedded sensor boards to PCs and large-scale context servers. Because these devices vary tremendously in their capabilities, application developers must create different programming models for every class of device. This makes rapid prototyping infeasible as soon as more than one class of devices is involved. Rapid prototyping therefore requires a programming model that hides the environment's heterogeneity.
    IEEE Pervasive Computing 05/2007; 6(2):76-84. · 2.06 Impact Factor
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Much work has been done to clarify the notion of metamodelling and new ideas, such as strict metamodel- ling, distinction between ontological and linguistic instan- tiation, unified modelling elements and deep instantiation, have been introduced. However, many of these ideas have not yet been fully developed and integrated into modelling lan- guages with (concrete) syntax, rigorous semantics and tool support. Consequently, applying these ideas in practice and reasoning about their meaning is difficult, if not impossible. In this paper, we strive to add semantic rigour and conceptual clarity to metamodelling through the introduction of Nivel, a novel metamodelling language capable of expressing models spanning an arbitrary number of levels. Nivel is based on a core set of conceptual modelling concepts: class, generali- sation, instantiation, attribute, value and association. Nivel adheres to a form of strict metamodelling and supports deep instantiation of classes, associations and attributes. A for- mal semantics is given for Nivel by translation to weight constraint rule language (WCRL), which enables decidable, automated reasoning about Nivel. The modelling facilities of Nivel and the utility of the formalisation are demonstrated in a case study on feature modelling.
    Software and Systems Modeling 09/2009; 8(4):521-549. · 1.25 Impact Factor

Full-text (2 Sources)

Available from
May 20, 2014