UML PROFILE FOR SAVECCM - Research

UML
In four layer metamodel hierarchy, user defined profile is at the same layer as
user model. Elements are instances of metaclass Class and Stereotype from
Profiles package.
4.6.2.1 Description of classes in Profiles package
Profiles package specifies several metaclasses in order to provide lightweight
extension mechanism to the UML standard. These classes are: Class,
Extension, ExtensionEnd, Image, Package, Profile,
ProfileApplication and Stereotype. Some of them are shortly described in
this section, for more details refer to [UMLs 07].
Package
In the Package metaclass, a package functionality is extended with an ability to
indicate the profiles applied to a package. A package can have one or more
ProfileApplications to indicate which profiles have been applied. Because a
profile is a package, it is possible to apply a profile not only to packages, but also
to profiles.
Profile
A Profile is a coherent set of extensions applicable to a given domain or
purpose. This metaclass inherits Package metaclass and is a restricted form of a
metamodel that must always be related to a reference metamodel, such as UML.
A Profile defines a limited capability to extend metaclasses of the reference
metamodel and it cannot be used without its reference metamodel.
Stereotype
Stereotype describes how an existing metaclass can be extended. It is a kind of
Class and extends Classes.
Each stereotype S must extend at least one metaclass C. The properties of S
encode the additional "semantics" of the instances of C stereotyped by S as
compared to those that are not. Stereotype must always be used in conjunction
with one of the metaclasses it extends.
Each stereotype may extend one or more classes through extensions as part of
a profile. Similarly, a class may be extended by one or more stereotypes.
Stereotype is the only kind of metaclass that cannot be extended by stereotypes.
A number of UML pre-defined stereotypes exist that apply to a component. For
example, «subsystem» to model large-scale components, and «specification» and
«realization» to model components with distinct specification and realization
definitions etc.
33