Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

This page provides guidance on the correct usage of IISOMI and ONAP stereotypes in the model. Not all stereotypes are described. For a full description of IISOMI stereotypes, please refer to the IISOMI Modeling Guidelines listed in the previous page.

Introduction

Stereotypes are the core extension mechanism of the UML. If you find that you need a modeling construct that isn't in the UML but is similar to something that is, you treat your construct as a stereotype of the UML construct. Stereotypes get "applied" to UML artifacts (like "Class", "Attribute (property)", "Interface", etc.) and are a means to supply additional relevant information to that artifact. Stereotypes are usually shown in text between guillemets, but you can also show them by defining an icon for the stereotype. 

Here is an example in Papyrus of stereotypes between guillemets. There are two stereotypes (OpenModelClass and OnapModelLifecycle) "applied" to the class Vnfd.

Stereotypes themselves are defined in "Profiles" that get applied to models. Currently in Papyrus we have two profiles that are applied to the ONAP model:

  • ONAP_Profile   (ONAP specific profile)
  • OpenModel_Profile  (IISOMI profile)

Stereotypes, like classes, may contain a set of attributes. Here is an example of how the IISOMI "OpenModelAttribute stereotype is defined. Note the icon with a little "s" to indicate that OpenModelAttribute is a stereotype. 

Note also that there is an attribute called "support". This particular attribute means what level of support is required over a management interface. It is further defined below

When defining the "Applied Stereotypes" in a wiki, it is important to note which stereotype is being applied (in this case OpenModelAttribute) and then the value given to a particular attribute, such as "support". Saying the "Applied Stereotypes" is "support=MANDATORY" is not exactly correct. One should say, for example "OpenModelAttribute.support = MANDATORY"

Some stereotypes, such as the IISOMI lifecycle stereotypes, don't have attributes. Here's an example of the "Deprecated" stereotype

This attribute implies that the UML artifact has been deprecated in the model. In the wiki it would not be correct to say "support=DEPRECATED", as DEPRECATED is not one of the values that the support qualifier can have. The correct way to define this in the "Applied Stereotypes" column on the wiki would be:

OpenModelAttribute.support = MANDATORY

Deprecated



  • No labels