23.5. Built In Stereotypes

UML 1.3 defines a large number of stereotypes which are all supported by ArgoUML.

[Caution]Caution

Not all stereotypes defined by UML 1.3 appear in ArgoUML due to limitations in the current implementation of some artifacts. The table below lists all stereotypes defined in UML 1.3 and if their base elements are supported in ArgoUML or not.

[Caution]Caution

The UML 1.3 standard also specifies many stereotypes in the chapters “Standard Profiles”: one for “Software Development” and one for “Business Modeling”. Due to the specialized nature of these profiles, implementation in ArgoUML is postponed until a yet undetermined moment.

Table 23.1. Stereotypes defined in UML 1.3 and ArgoUML

StereoType

Base Element

ArgoUML support

access

Permission

yes

association

AssociationEnd

yes

become

Flow

no

call

Usage

yes

copy

Flow

no

create

BehavioralFeature

yes

create

CallEvent

yes

create

Usage

yes

derive

Abstraction

yes

destroy

BehavioralFeature

yes

destroy

CallEvent

yes

document

Component

yes

executable

Component

yes

facade

Package

yes

file

Component

yes

framework

Package

yes

friend

Permission

yes

global

AssociationEnd

yes

implementation

Generalization

yes

implementationClass

Class

yes

implicit

Association

yes

import

Permission

yes

instantiate

Usage

yes

invariant

Constraint

no

library

Component

yes

local

AssociationEnd

yes

metaclass

Classifier

yes

metamodel

Package

yes

parameter

AssociationEnd

yes

postcondition

Constraint

no

powertype

Classifier

yes

precondition

Constraint

no

process

Classifier

yes

realize

Abstraction

yes

refine

Abstraction

yes

requirement

Comment

no

responsibility

Comment

no

self

AssociationEnd

yes

send

Usage

yes

signalflow

ObjectFlowState

no

stub

Package

yes

systemModel

Package

yes

table

Component

yes

thread

Classifier

yes

topLevel

Package

yes

trace

Abstraction

yes

type

Class

yes

utility

Classifier

yes