To aid in the efficiency in creating models the modeler may adapt SysML to their particular domain. This can be done using several possibilities allowed in SysML:

• Use of Profiles and Stereotype to extend the language (which is represented as meta-classes).
• Use of Model Libraries to have a library of standard elements that the modeler can draw from.

If language modeler wants to make the use of a particular profile mandatory then the relationship between the model and the profile shall be required.

• Profiles are a specialization of Packages.
• Profiles may contain sub-packages and/or sub-packages.
  • Advantages of sub-profiles is that the sub-profiles may be applied independently to other sub-profiles
  • If parent profile is applied then by default all stereotypes within sub-packages are applied
• Leaf nodes of a profile is its stereotypes
• Serves one of two purposes:
  • Profile defines a set of concepts that support a new domain
  • Profile defines a set of concepts that add value to a model in a domain that is already supported.

• Stereotypes are collected in Profiles (which is a specialization of Package).
• Stereotype extends metaclass (a construct of SysML, e.g. “Block”). This extension relationship is a specialization of the association relationship.

• Properties of stereotypes are different to properties of blocks. E.g. a block “Vehicle” may have a property called inspector which records which inspector did the inspector for an instance of Vehicle. However a stereotype “Vehicle” which extends the metaclass “Block” may also have a property called inspector. In this case the property is intended to capture which inspector checked the specification of Vehicle and nothing to do with any particular Vehicle instance.