Overview of the UML Standard profile (UML Standard profile)
The UML Standard profile provides the following diagrams, items and relationships:
Package Diagram.
Profile Representation, Model Library and Model Representation items.
Access, Import, Profile Application, Package Merge, Realization, Refine and Trace relationships.
In addition to the preceding diagrams, items and relationships, the UML Standard profile predefined standard Stereotypes from the Standard Profile that is defined in the UML specification.
All of the Stereotypes have been linked with appropriate Modeler item types, which can be viewed through the Property Pages of the Stereotypes.
If you also add the SysML Profile to the model, you can create View and View Point items, and Conform relationships on a Package Diagram.
It is assumed that when the profile is imported into a model, it will be applied as appropriate to the requirements of that model.
The UML Profile package includes the following Stereotypes and Tag Definitions.
Stereotype
Can be applied to these item types
«access»
Dependency and Package
«artifact»
Role
«auxiliary»
Class, Instance, OCD::Instance and OSD::Instance
«boundary»
Class and Package
«buildComponent»
Class and Package
«call»
Association and Dependency
«component»
Attribute, Class and Role
«control»
Class
«create»
Association, Dependency, Operation and Role
«derive»
Dependency
«destroy»
Operation
«device»
Role
«document»
Class
«entity»
Class
«executable»
Class
«execution environment»
Role
«facade»
Package
«file»
Class
«focus»
Class, Instance, OCD::Instance and OSD::Instance
«framework»
Package
«friend»
Dependency and Package
«global»
Role
«implement»
Attribute, Class and Role
«implementationClass»
Class, Instance, OCD::Instance, OSD::Instance and Specialization
«implicit»
Association
«import»
Dependency and Package
«instantiate»
Association and Dependency
«invariant»
Constraint
«library»
Class
«local»
Role
«manifest»
Dependency
«metaclass»
Class
«metamodel»
Package and Model
«Model»
Package
«ModelLibrary»
Dependency and Package
«node»
Attribute and Role
«node type»
Class
«PackageDiagram»
Class Diagram
«PackageMerge»
Dependency
«parameter»
Role
«postcondition»
Constraint
«powertype»
Class
«precondition»
Constraint
«process»
Class, Instance, OCD::Instance, OSD::Instance and Task
«Profile»
Package
«ProfileApplication»
Package and Dependency
«realization»
Class, Data Type, Interface, Package and Signal
«realize»
Dependency
«Refine»
Dependency (the SysML Requirements Profile uses this Stereotype)
«responsibility»
Association and Dependency
«script»
Class
«self»
Role
«send»
Association and Dependency
«service»
Class
«source»
Class
«specification»
Class, Data Type, Interface, Package and Signal
«stub»
Package
«subsystem»
Class
«systemModel»
Package and Model
«table»
Table
«thread»
Class, Instance, OCD::Instance, OSD::Instance and Task
«Trace»
Dependency (the SysML Requirements Profile uses this Stereotype)
«type»
Class
«utility»
Class
Tag Definition
Applied by
Data Type
applicableSubset
«Profile»
Text
ip address
«device», «execution environment» and «node»
Text
isStrict
«ProfileApplication»
Boolean
port number
«artifact»
Text
* 
Do not make changes to the UML Standard profile. Any changes you make will be lost when the profile is updated.
Note that you can create Tag Definitions outside of the UML Standard profile, and link those Tag Definitions to Stereotypes in the UML Standard profile. When the UML Standard profile is updated, the links will not be broken.
Do not create copies of the UML Standard profile within a model, or create copies of the UML Standard profile through XMI Import/Export. The copies of the UML Standard profile will not work correctly and you will not be able to update the copies through the Update All Profiles command.