JOSIF Main Page | JOSIF Guidebook | Tooling | Information Model Tooling | TIP RSM Profile

Introduction

RSM uses a profile to define the stereotypes applicable to a project.

TIP has defined a unique TIP RSM Profile (TIPProfile.epx) that is applicable to the SID and the information model part of all interface projects.

This section explains the detailed contents of the TIP RSM Profile.

The information in this profile that are specific to JOSIF V1.1 are marked explicitely.

Stereotypes

TIP is using stereotypes to provide implementation-level decoration on the model that can be used in Tigerstripe by the generators.

The stereotypes applicable to the Information Model are defined as a profile in RSM.

The pattern used in TIP is to define 1 stereotype per type of object, named tipXxxx, where Xxxx is the type of object. This stereotype will contain a number of attributes where each attribute will contain a specific decoration. This is further explained in General_Patterns

The top level stereotypes defined in TIP,applicable to the Information Model are:

*tipClass for Entities
*tipDatatype for Datatypes
*tipAttribute for Attributes of Entitities and Association ends
*tipAssociationClass for Association Classes
*tipPackage for Packages

The stereotype doNotImplement is used to indicate objects that should not be implemented as part of interface development, like a package containing only examples or instances, or an association that is only present for illustrative purpose. It does not imply this object should not be used outside of interface development. This stereotype is applicable on most SID objects.

Note that the tipEntityXxx (like tipEntityCreate) stereotypes used to describe the common operations are not available in the TIP RSM Profile, even if they apply on the class. These stereotypes are only available in Tigerstripe.

tipClass

This stereotype provides the enhanced definitions for classes that are relevant for application in a TM Forum interface.

Browser not supported