70 files changed, 553 insertions, 244 deletions

diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/.settings/org.eclipse.core.resources.prefs b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/.settings/org.eclipse.core.resources.prefs
index 61a8fc5c542..0b4b4e634a3 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/.settings/org.eclipse.core.resources.prefs
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/.settings/org.eclipse.core.resources.prefs
@@ -1,3 +1,11 @@
-eclipse.preferences.version=1

-encoding//resource/profile-toc.xml=utf-8

-encoding//resource/profile.html=utf-8

+eclipse.preferences.version=1
+encoding//resource/users/definingProfilesAndStereotypes-toc.xml=utf-8
+encoding//resource/users/definingProfilesAndStereotypes.html=utf-8
+encoding//resource/users/papyrusProfileArchitecture-toc.xml=utf-8
+encoding//resource/users/papyrusProfileArchitecture.html=utf-8
+encoding//resource/users/profile-toc.xml=utf-8
+encoding//resource/users/profile.html=utf-8
+encoding//resource/users/usingProfilesAndStereotypes-toc.xml=utf-8
+encoding//resource/users/usingProfilesAndStereotypes.html=utf-8
+encoding//resource/users/whatIsAUmlProfile-toc.xml=utf-8
+encoding//resource/users/whatIsAUmlProfile.html=utf-8
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/plugin.xml b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/plugin.xml
index 99f8f8789a1..649d2b81664 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/plugin.xml
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/plugin.xml
@@ -1,16 +1,32 @@
-<?xml version="1.0" encoding="UTF-8"?>

-<?eclipse version="3.4"?>

-<plugin>

-   <extension

-         point="org.eclipse.help.toc">

-      <toc

-            file="resource/profile-main-toc.xml"

-            primary="false">

-      </toc>

-      <toc

-            file="resource/profile-toc.xml"

-            primary="false">

-      </toc>

-   </extension>

-

-</plugin>

+<?xml version="1.0" encoding="UTF-8"?>
+<?eclipse version="3.4"?>
+<plugin>
+   <extension
+         point="org.eclipse.help.toc">
+      <toc
+            file="resource/users/profile-main-toc.xml"
+            primary="false">
+      </toc>
+      <toc
+            file="resource/users/profile-toc.xml"
+            primary="false">
+      </toc>
+      <toc
+            file="resource/users/whatIsAUmlProfile-toc.xml"
+            primary="false">
+      </toc>
+      <toc
+            file="resource/users/usingProfilesAndStereotypes-toc.xml"
+            primary="false">
+      </toc>
+      <toc
+            file="resource/users/definingProfilesAndStereotypes-toc.xml"
+            primary="false">
+      </toc>
+      <toc
+            file="resource/users/papyrusProfileArchitecture-toc.xml"
+            primary="false">
+      </toc>
+   </extension>
+
+</plugin>
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile-main-toc.xml b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile-main-toc.xml
deleted file mode 100644
index 1db2768f4e4..00000000000
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile-main-toc.xml
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>

-<toc label="Profiles" link_to="../org.eclipse.papyrus.infra.doc/toc.xml#PapyrusDocUser">

-   <topic href="resource/profile.html" label="Using Profiles">

-      <link toc="resource/profile-toc.xml"/>

-      <anchor id="profiles"/>

-   </topic>	

-</toc>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes-toc.xml b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes-toc.xml
new file mode 100644
index 00000000000..87638184611
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes-toc.xml
@@ -0,0 +1,13 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<toc topic="resource/users/definingProfilesAndStereotypes.html" label="definingProfilesAndStereotypes">
+	<topic href="resource/users/definingProfilesAndStereotypes.html" label="Defining Profiles and Stereotypes"></topic>
+	<topic href="resource/users/definingProfilesAndStereotypes.html#Creating_a_Profile_Resource" label="Creating a Profile Resource"></topic>
+	<topic href="resource/users/definingProfilesAndStereotypes.html#Defining_a_Stereotype" label="Defining a Stereotype">
+		<topic href="resource/users/definingProfilesAndStereotypes.html#Creating_a_Stereotype" label="Creating a Stereotype"></topic>
+		<topic href="resource/users/definingProfilesAndStereotypes.html#Importing_Metaclass" label="Importing Metaclass"></topic>
+		<topic href="resource/users/definingProfilesAndStereotypes.html#Linking_Stereotype_to_Metaclass_:_Extension_Creation" label="Linking Stereotype to Metaclass : Extension Creation"></topic>
+		<topic href="resource/users/definingProfilesAndStereotypes.html#Creating_a_Subprofile" label="Creating a Subprofile"></topic>
+		<topic href="resource/users/definingProfilesAndStereotypes.html#Generalizing_Stereotype" label="Generalizing Stereotype"></topic>
+	</topic>
+	<topic href="resource/users/definingProfilesAndStereotypes.html#Displaying_Stereotype_Options" label="Displaying Stereotype Options"></topic>
+</toc>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes.html b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes.html
new file mode 100644
index 00000000000..2f7f5edfd41
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes.html
@@ -0,0 +1,2 @@
+<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Defining_Profiles_and_Stereotypes">Defining Profiles and Stereotypes</h1><p>In UML, Stereotypes should be defined in a UML Profile. A UML Profile is a kind of uml::Package.</p><p>Papyrus allows to create Profiles and Sterotypes in any kind of models. But, if you want to define Profiles and Stereotypes in order to apply them to UML elements, <b>you need to define a Profile in a Papyrus profile resource (file)</b>.</p><p>Defining Stereotypes with Papyrus required the following:</p><ul><li>A <b>profile resource</b> - The resource (file) containing the profile (uml+di+notation files)</li><li>A <b>uml::Profile</b> - The uml element containing the Stereotypes</li><li>The <b>Stereotype</b> - The uml::Stereotype element defining the Stereotype</li></ul><h1 id="Creating_a_Profile_Resource">Creating a Profile Resource</h1><p>To create a new Profile, select File &gt; New &gt; Papyrus Project (Or Papyrus model, if you already have an opened project). When asked for a Diagram Language, Select "Profile":</p><p><img title="New Profile" alt="New Profile" border="0" src="images/newProfile.png"/><br/></p><p><img title="New Profile Diagram" alt="New Profile Diagram" border="0" src="images/newProfileDiagram.png"/><br/></p><p><img title="Profile Editor" alt="Profile Editor" border="0" src="images/profileEditor.png"/><br/></p><p>This creates a Resource containing a uml::Profile as root element.</p><h1 id="Defining_a_Stereotype">Defining a Stereotype</h1><p>Once a profile is created, it is now time to populate this latter with UML extensions, i.e. stereotypes, and their related concepts such as properties, extensions, and metaclasses.</p><h2 id="Creating_a_Stereotype">Creating a Stereotype</h2><p>A stereotype is created as any other UML model elements in Papyrus: select the related tool in the palette of the profile diagram editor, and then click in the place you want to create this element on the background of the diagram. If the palette is not open, just click on the small arrow on the upper right corner of the diagram editor. Papyrus will then ask you to provide a name. Once done, hit the return key and that all.</p><p><img title="Stereotype Palette" alt="Stereotype Palette" border="0" src="images/stereotypePalette.png"/><br/></p><p><img title="Stereotype Name" alt="Stereotype Name" border="0" src="images/stereotypeName.png"/><br/></p><h2 id="Importing_Metaclass">Importing Metaclass</h2><p>Once you have created a stereotype, you need to import the UML2 metaclasses you want to extend. First, you have to select the tool “Import Metaclass� within the palette of the profile diagram editor. Then, let’s click on the profile diagram where you want to drop the imported metaclass. A Papyrus dialog box is then opened in order to ask you to specify which metaclasses you want to import. Select the metaclasses in the left list and either drag and drop these latter in the right list or press the button with arrow directed from left to right and located between both aforementioned lists. Then, let’s press the button “ok� and it is done. The imported metaclasses are then shown in the diagram as illustrated.</p><p><img title="Import Metaclass" alt="Import Metaclass" border="0" src="images/importMetaclassDialog.png"/><br/></p><p><img title="Imported Metaclass" alt="Imported Metaclass" border="0" src="images/importedMetaclass.png"/><br/></p><p>Note: When you import UML2 metaclasses, Papyrus is creating ImportElement model element referent to the metaclasses of the UML2 metamodel itself. Those so-called specific model elements, the ImportElement, are indeed a kind of proxy to the model elements contained in another model, in the UML2 metamodel. If a metaclass has already be imported, you do not need to import it again to use it in another context. You can select the imported meta-class from the model browser and drag and drop this latter on the diagram you want to use it.</p><h2 id="Linking_Stereotype_to_Metaclass_:_Extension_Creation">Linking Stereotype to Metaclass : Extension Creation</h2><p>Once the stereotype is created and the meta-class is imported, you may then model the extension relation from the stereotype to the meta-class as shown in the following figure. The extension relationship is modeled using the extension tool in the profile diagram palette, <img title="Extension" alt="Extension" border="0" src="images/Extension.gif"/>. Within the diagram shown in next figure, both stereotypes «Requirement» and «Refinement» extend respectively both meta-classes Class and Dependency:</p><p><img title="Metaclass Extension" alt="Metaclass Extension" border="0" src="images/metaclassExtension.png"/><br/></p><h2 id="Creating_a_Subprofile">Creating a Subprofile</h2><p>Some profile may be complex due as for example to their scope that may be large. In order to cope with this complexity, it is then possible to decompose a profile into a hierarchy of subprofiles. A subprofile behaves such as a sub-package; it is a container of stereotypes.</p><p>To create a sub profile, select the profile tool in the profile diagram palette (<img title="Profile" alt="Profile" border="0" src="images/Profile.gif"/>) and then click on the profile diagram where you want to create your new profile.</p><p>In the example denoted below, we have created two sub-profiles of the SimplifiedReqML profile in order to gather in one hand the extensions that apply to node elements of the models and in the other hand the extension defined in the DSML for modeling relationships between those nodes:</p><p><img title="Sub Profiles" alt="Sub Profiles" border="0" src="images/subProfiles.png"/><br/></p><h2 id="Generalizing_Stereotype">Generalizing Stereotype</h2><p>When designing a profile, it is possible to reuse existing stereotypes defined in other existing profiles. Stereotypes can indeed be generalized enabling to create child stereotypes that inherit features of one or more generalized stereotype define either locally in the profile or externally other profiles.</p><p>To create a stereotype generalization using the profile diagram editor, let’s draw a generalization relationship using the tool <img title="Generalization" alt="Generalization" border="0" src="images/Generalization.gif"/> from the palette. As any relationship within Papyrus, you need to click first on the source and then on the target of the relationship you want to model.</p><p>In our example, there exists in the UML predefined profile a stereotype extending the dependency relationship in order to introduce the concept of refinement: «Refine». Consequently, we will redesign our sub-profile SRMLRelationship in order our stereotype «Refinement» to be a specialization of this UML stereotype instead of directly extending the UML dependency meta-class.</p><p>As previously mentioned, you may extend a stereotype defined in your profile or a stereotype defined in another external profile. In the latter case, the first thing to do is to import the profile where the stereotype has been defined, as denoted in the following example:</p><p><img title="Import Profile" alt="Import Profile" border="0" src="images/importProfile.png"/><br/></p><p><img title="Select Profile" alt="Select Profile" border="0" src="images/selectProfile.png"/><br/></p><p>Once the profile has been imported, you can select the stereotype you want to generalize from the imported profile (In the Model Explorer) and drop this latter in the diagram of profile description: </p><p><img title="Drop Stereotype" alt="Drop Stereotype" border="0" src="images/dropStereotype.png"/><br/></p><p>Now, let’s draw the generalization relationship from your stereotype (e.g., «Refinement» in the figure below) to the generalized stereotype (e.g., «Refine» in the figure below). </p><p><img title="Generalize Stereotype" alt="Generalize Stereotype" border="0" src="images/generalizeStereotype.png"/><br/></p><p>At this point, your diagram should look like something like the one shown here:</p><p><img title="Result Profile" alt="Result Profile" border="0" src="images/resultProfile.png"/><br/></p><h1 id="Displaying_Stereotype_Options">Displaying Stereotype Options</h1><p>When a stereotype application is shown in a diagram, the by-default way to show it within diagrams is using a string where the name of the stereotype is shown within a pair of French guillemets above or before the name of the model element. However, it is also possible to modify the graphical appearance of the annotated model element using icons. If the graphical representation of the model element is something like a box (including ellipse of the use cases), the icons can be displayed inside and on top of the figures, or it may replace this latter. In that latter case, the property of the element cannot be shown and the name of the model element appears within a label displayed near the icon. If the model element is graphically denoted by a line, the icon is shown in front of the name of the link.</p><p>In order to specify the icons you want to attach to a stereotype, select the stereotype and the tab UML of the property view. In the right-upper corner of the widget named “icons�, press the button <img title="Add" alt="Add" border="0" src="images/Add.gif"/> to add a new icon as shown in step 1. Once done, the dialog box shown at step 2 is open. Within this latter, let’s fill in a name and select an image file using the button <img title="Add" alt="Add" border="0" src="images/Add.gif"/> defining the content of the icon. Next, you have to define the kind value: icon or shape. Using this property, you can choose to associate the selected image either as an icon or as a shape.</p><p><img title="Step 1: Icons for Stereotypes" alt="Step 1: Icons for Stereotypes" border="0" src="images/iconsForStereotype.png"/><br/></p><p><img title="Step 2: Select Icon" alt="Step 2: Select Icon" border="0" src="images/selectIcon.png"/><br/></p><p>It is possible to associate only one shape to a stereotype, but you can associate different icons to a same stereotype. In that latter case, there is a description property that is used to select which one to display. By default, if no expression is defined, the first one is the list is chosen for displaying. The expression has to be on a property of the stereotype which type is an enumeration type.
+In our example, we can set different icons to the stereotype «Requirement» depending on the value of its importance property. This latter is indeed typed by the ImportanceLevel enumeration which values may be High, Medium of Low (figure shown below). For this example, we will then associate the three following images <img title="High" alt="High" border="0" src="images/high.png"/>, <img title="Medium" alt="Medium" border="0" src="images/medium.png"/>, and <img title="Low" alt="Low" border="0" src="images/low.png"/>, to the stereotype «Requirement» and their related expression will be respectively importance=High (e.g. figure shown below), importance=Medium and importance=Low.</p><p><img title="Many Stereotype Icons" alt="Many Stereotype Icons" border="0" src="images/manyStereotypeIcons.png"/><br/></p><p><img title="Icon Kind" alt="Icon Kind" border="0" src="images/iconKind.png"/><br/></p><p><img title="Icon Expressions" alt="Icon Expressions" border="0" src="images/iconExpressions.png"/><br/></p><p><img title="High Req. Icon" alt="High Req. Icon" border="0" src="images/highReqIcon.png"/><br/></p></body></html>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes.mediawiki b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes.mediawiki
new file mode 100644
index 00000000000..a417ad5fff1
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/definingProfilesAndStereotypes.mediawiki
@@ -0,0 +1,110 @@
+= Defining Profiles and Stereotypes =
+
+In UML, Stereotypes should be defined in a UML Profile. A UML Profile is a kind of uml::Package.
+
+Papyrus allows to create Profiles and Sterotypes in any kind of models. But, if you want to define Profiles and Stereotypes in order to apply them to UML elements, '''you need to define a Profile in a Papyrus profile resource (file)'''.
+
+Defining Stereotypes with Papyrus required the following:
+* A '''profile resource''' - The resource (file) containing the profile (uml+di+notation files)
+* A '''uml::Profile''' - The uml element containing the Stereotypes
+* The '''Stereotype''' - The uml::Stereotype element defining the Stereotype
+
+
+= Creating a Profile Resource =
+
+To create a new Profile, select File > New > Papyrus Project (Or Papyrus model, if you already have an opened project). When asked for a Diagram Language, Select "Profile":
+
+[[Image:images/newProfile.png|New Profile]]<br>
+
+[[Image:images/newProfileDiagram.png|New Profile Diagram]]<br>
+
+[[Image:images/profileEditor.png|Profile Editor]]<br>
+
+This creates a Resource containing a uml::Profile as root element.
+
+= Defining a Stereotype =
+
+Once a profile is created, it is now time to populate this latter with UML extensions, i.e. stereotypes, and their related concepts such as properties, extensions, and metaclasses.
+
+== Creating a Stereotype ==
+
+A stereotype is created as any other UML model elements in Papyrus: select the related tool in the palette of the profile diagram editor, and then click in the place you want to create this element on the background of the diagram. If the palette is not open, just click on the small arrow on the upper right corner of the diagram editor. Papyrus will then ask you to provide a name. Once done, hit the return key and that all.
+
+[[Image:images/stereotypePalette.png|Stereotype Palette]]<br>
+
+[[Image:images/stereotypeName.png|Stereotype Name]]<br>
+
+== Importing Metaclass ==
+
+Once you have created a stereotype, you need to import the UML2 metaclasses you want to extend. First, you have to select the tool “Import Metaclass� within the palette of the profile diagram editor. Then, let’s click on the profile diagram where you want to drop the imported metaclass. A Papyrus dialog box is then opened in order to ask you to specify which metaclasses you want to import. Select the metaclasses in the left list and either drag and drop these latter in the right list or press the button with arrow directed from left to right and located between both aforementioned lists. Then, let’s press the button “ok� and it is done. The imported metaclasses are then shown in the diagram as illustrated.
+
+[[Image:images/importMetaclassDialog.png|Import Metaclass]]<br>
+
+[[Image:images/importedMetaclass.png|Imported Metaclass]]<br>
+
+Note: When you import UML2 metaclasses, Papyrus is creating ImportElement model element referent to the metaclasses of the UML2 metamodel itself. Those so-called specific model elements, the ImportElement, are indeed a kind of proxy to the model elements contained in another model, in the UML2 metamodel. If a metaclass has already be imported, you do not need to import it again to use it in another context. You can select the imported meta-class from the model browser and drag and drop this latter on the diagram you want to use it.
+
+== Linking Stereotype to Metaclass : Extension Creation ==
+
+Once the stereotype is created and the meta-class is imported, you may then model the extension relation from the stereotype to the meta-class as shown in the following figure. The extension relationship is modeled using the extension tool in the profile diagram palette, [[Image:images/Extension.gif|Extension]]. Within the diagram shown in next figure, both stereotypes «Requirement» and «Refinement» extend respectively both meta-classes Class and Dependency:
+
+[[Image:images/metaclassExtension.png|Metaclass Extension]]<br>
+
+= Creating a Subprofile =
+
+Some profile may be complex due as for example to their scope that may be large. In order to cope with this complexity, it is then possible to decompose a profile into a hierarchy of subprofiles. A subprofile behaves such as a sub-package; it is a container of stereotypes.
+
+To create a sub profile, select the profile tool in the profile diagram palette ([[Image:images/Profile.gif|Profile]]) and then click on the profile diagram where you want to create your new profile.
+
+In the example denoted below, we have created two sub-profiles of the SimplifiedReqML profile in order to gather in one hand the extensions that apply to node elements of the models and in the other hand the extension defined in the DSML for modeling relationships between those nodes:
+
+[[Image:images/subProfiles.png|Sub Profiles]]<br>
+
+= Generalizing Stereotype  =
+
+When designing a profile, it is possible to reuse existing stereotypes defined in other existing profiles. Stereotypes can indeed be generalized enabling to create child stereotypes that inherit features of one or more generalized stereotype define either locally in the profile or externally other profiles.
+
+To create a stereotype generalization using the profile diagram editor, let’s draw a generalization relationship using the tool [[Image:images/Generalization.gif|Generalization]] from the palette. As any relationship within Papyrus, you need to click first on the source and then on the target of the relationship you want to model.
+
+In our example, there exists in the UML predefined profile a stereotype extending the dependency relationship in order to introduce the concept of refinement: «Refine». Consequently, we will redesign our sub-profile SRMLRelationship in order our stereotype «Refinement» to be a specialization of this UML stereotype instead of directly extending the UML dependency meta-class.
+
+As previously mentioned, you may extend a stereotype defined in your profile or a stereotype defined in another external profile. In the latter case, the first thing to do is to import the profile where the stereotype has been defined, as denoted in the following example:
+
+[[Image:images/importProfile.png|Import Profile]]<br>
+
+[[Image:images/selectProfile.png|Select Profile]]<br>
+
+Once the profile has been imported, you can select the stereotype you want to generalize from the imported profile (In the Model Explorer) and drop this latter in the diagram of profile description: 
+
+[[Image:images/dropStereotype.png|Drop Stereotype]]<br>
+
+Now, let’s draw the generalization relationship from your stereotype (e.g., «Refinement» in the figure below) to the generalized stereotype (e.g., «Refine» in the figure below). 
+
+[[Image:images/generalizeStereotype.png|Generalize Stereotype]]<br>
+
+At this point, your diagram should look like something like the one shown here:
+
+[[Image:images/resultProfile.png|Result Profile]]<br>
+
+= Displaying Stereotype Options =
+
+When a stereotype application is shown in a diagram, the by-default way to show it within diagrams is using a string where the name of the stereotype is shown within a pair of French guillemets above or before the name of the model element. However, it is also possible to modify the graphical appearance of the annotated model element using icons. If the graphical representation of the model element is something like a box (including ellipse of the use cases), the icons can be displayed inside and on top of the figures, or it may replace this latter. In that latter case, the property of the element cannot be shown and the name of the model element appears within a label displayed near the icon. If the model element is graphically denoted by a line, the icon is shown in front of the name of the link.
+
+In order to specify the icons you want to attach to a stereotype, select the stereotype and the tab UML of the property view. In the right-upper corner of the widget named “icons�, press the button [[Image:images/Add.gif|Add]] to add a new icon as shown in step 1. Once done, the dialog box shown at step 2 is open. Within this latter, let’s fill in a name and select an image file using the button [[Image:images/Add.gif|Add]] defining the content of the icon. Next, you have to define the kind value: icon or shape. Using this property, you can choose to associate the selected image either as an icon or as a shape.
+
+[[Image:images/iconsForStereotype.png|Step 1: Icons for Stereotypes]]<br>
+
+[[Image:images/selectIcon.png|Step 2: Select Icon]]<br>
+
+It is possible to associate only one shape to a stereotype, but you can associate different icons to a same stereotype. In that latter case, there is a description property that is used to select which one to display. By default, if no expression is defined, the first one is the list is chosen for displaying. The expression has to be on a property of the stereotype which type is an enumeration type.
+In our example, we can set different icons to the stereotype «Requirement» depending on the value of its importance property. This latter is indeed typed by the ImportanceLevel enumeration which values may be High, Medium of Low (figure shown below). For this example, we will then associate the three following images [[Image:images/high.png|High]], [[Image:images/medium.png|Medium]], and [[Image:images/low.png|Low]], to the stereotype «Requirement» and their related expression will be respectively importance=High (e.g. figure shown below), importance=Medium and importance=Low.
+
+[[Image:images/manyStereotypeIcons.png|Many Stereotype Icons]]<br>
+
+[[Image:images/iconKind.png|Icon Kind]]<br>
+
+[[Image:images/iconExpressions.png|Icon Expressions]]<br>
+
+[[Image:images/highReqIcon.png|High Req. Icon]]<br>
+
+
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Add.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Add.gif
index 189b46e5a5b..189b46e5a5b 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Add.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Add.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/ConsoleViewQN.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/ConsoleViewQN.gif
index 06b0699d543..06b0699d543 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/ConsoleViewQN.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/ConsoleViewQN.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Delete.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Delete.gif
index bd924a5e0fa..bd924a5e0fa 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Delete.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Delete.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Extension.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Extension.gif
index d6e7b151c61..d6e7b151c61 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Extension.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Extension.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Generalization.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Generalization.gif
index 20013dff017..20013dff017 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Generalization.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Generalization.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Profile.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Profile.gif
index 18eed1f5cb9..18eed1f5cb9 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/Profile.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/Profile.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/appliedProfiles.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/appliedProfiles.png
index 210a0992e06..210a0992e06 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/appliedProfiles.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/appliedProfiles.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/appliedStereotype.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/appliedStereotype.png
index e3f2787e2df..e3f2787e2df 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/appliedStereotype.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/appliedStereotype.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyProfile.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyProfile.png
index abaa8f4889c..abaa8f4889c 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyProfile.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyProfile.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyProfile2.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyProfile2.png
index f85311ce2d3..f85311ce2d3 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyProfile2.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyProfile2.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyProfile3.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyProfile3.png
index eff7c620de3..eff7c620de3 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyProfile3.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyProfile3.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype.png
index f8630fa1c79..f8630fa1c79 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype2.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype2.png
index 6197ac8e620..6197ac8e620 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype2.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype2.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype3.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype3.png
index bebfd407ad6..bebfd407ad6 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype3.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype3.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype4.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype4.png
index 82be9bba239..82be9bba239 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype4.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype4.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype5.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype5.png
index ab2f010b28a..ab2f010b28a 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/applyStereotype5.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/applyStereotype5.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/arrow_left.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/arrow_left.gif
index 4fb41501036..4fb41501036 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/arrow_left.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/arrow_left.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/arrow_right.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/arrow_right.gif
index 19567890aa8..19567890aa8 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/arrow_right.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/arrow_right.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/change_display.gif b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/change_display.gif
index a598f6082f6..a598f6082f6 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/change_display.gif
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/change_display.gif
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/dropStereotype.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/dropStereotype.png
index 70012cf5ce5..70012cf5ce5 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/dropStereotype.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/dropStereotype.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/generalizeStereotype.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/generalizeStereotype.png
index 77e120d3e1f..77e120d3e1f 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/generalizeStereotype.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/generalizeStereotype.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/high.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/high.png
index a7d39585713..a7d39585713 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/high.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/high.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/highReqIcon.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/highReqIcon.png
index 55370b81e91..55370b81e91 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/highReqIcon.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/highReqIcon.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/iconExpressions.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/iconExpressions.png
index f429fc9f4ed..f429fc9f4ed 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/iconExpressions.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/iconExpressions.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/iconKind.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/iconKind.png
index 736b5e56be8..736b5e56be8 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/iconKind.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/iconKind.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/iconsForStereotype.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/iconsForStereotype.png
index 3355e9bb51e..3355e9bb51e 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/iconsForStereotype.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/iconsForStereotype.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/importMetaclassDialog.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/importMetaclassDialog.png
index 09625e6124c..09625e6124c 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/importMetaclassDialog.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/importMetaclassDialog.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/importProfile.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/importProfile.png
index ab1e97f10cb..ab1e97f10cb 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/importProfile.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/importProfile.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/importedMetaclass.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/importedMetaclass.png
index 697b7ee96f6..697b7ee96f6 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/importedMetaclass.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/importedMetaclass.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/low.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/low.png
index 15ee9623ec9..15ee9623ec9 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/low.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/low.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/manyStereotypeIcons.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/manyStereotypeIcons.png
index 5afca3ea525..5afca3ea525 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/manyStereotypeIcons.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/manyStereotypeIcons.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/medium.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/medium.png
index e3f659a4b78..e3f659a4b78 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/medium.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/medium.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/metaclassExtension.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/metaclassExtension.png
index c679ac1b567..c679ac1b567 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/metaclassExtension.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/metaclassExtension.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/newProfile.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/newProfile.png
index 8879751e3e5..8879751e3e5 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/newProfile.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/newProfile.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/newProfileDiagram.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/newProfileDiagram.png
index 34f85df68ee..34f85df68ee 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/newProfileDiagram.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/newProfileDiagram.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/profileDefinition1.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/profileDefinition1.png
index c04de7449f7..c04de7449f7 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/profileDefinition1.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/profileDefinition1.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/profileDefinition2.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/profileDefinition2.png
index 0d820a35c9c..0d820a35c9c 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/profileDefinition2.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/profileDefinition2.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/profileDefinitionErrors.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/profileDefinitionErrors.png
index ee2378badc8..ee2378badc8 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/profileDefinitionErrors.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/profileDefinitionErrors.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/profileEditor.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/profileEditor.png
index 42463d165f3..42463d165f3 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/profileEditor.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/profileEditor.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/resultProfile.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/resultProfile.png
index e461d9f44a5..e461d9f44a5 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/resultProfile.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/resultProfile.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/selectIcon.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/selectIcon.png
index 91c1788d200..91c1788d200 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/selectIcon.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/selectIcon.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/selectProfile.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/selectProfile.png
index a7eec65915a..a7eec65915a 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/selectProfile.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/selectProfile.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/selectProfileModel.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/selectProfileModel.png
index ef77b809572..ef77b809572 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/selectProfileModel.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/selectProfileModel.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/selectProfiles.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/selectProfiles.png
index 3fd04081789..3fd04081789 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/selectProfiles.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/selectProfiles.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypeDisplayOptions.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypeDisplayOptions.png
index 27e2678c082..27e2678c082 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypeDisplayOptions.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypeDisplayOptions.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypeDisplays.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypeDisplays.png
index e4fc9c46f2e..e4fc9c46f2e 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypeDisplays.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypeDisplays.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypeName.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypeName.png
index 9ca2c8e2e53..9ca2c8e2e53 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypeName.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypeName.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypePalette.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypePalette.png
index 1cd40673b15..1cd40673b15 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypePalette.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypePalette.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypeProperties.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypeProperties.png
index 361f014db1e..361f014db1e 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypeProperties.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypeProperties.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypePropertyEdition.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypePropertyEdition.png
index 0d931e2d284..0d931e2d284 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/stereotypePropertyEdition.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/stereotypePropertyEdition.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/subProfiles.png b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/subProfiles.png
index 3314c05543b..3314c05543b 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/images/subProfiles.png
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/images/subProfiles.png
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture-toc.xml b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture-toc.xml
new file mode 100644
index 00000000000..139f6f393af
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture-toc.xml
@@ -0,0 +1,8 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<toc topic="resource/users/papyrusProfileArchitecture.html" label="papyrusProfileArchitecture">
+  <topic label="Papyrus Profile Architecture">
+	<topic href="resource/users/papyrusProfileArchitecture.html" label="Papyrus Profile Architecture"></topic>
+	<topic href="resource/users/papyrusProfileArchitecture.html#Profile_and_Stereotype_Definitions_Architecture" label="Profile and Stereotype Definitions Architecture"></topic>
+	<topic href="resource/users/papyrusProfileArchitecture.html#Profile_and_Stereotype_applications_Architecture" label="Profile and Stereotype applications Architecture"></topic>
+  </topic>
+</toc>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture.html b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture.html
new file mode 100644
index 00000000000..87fd4a0afba
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture.html
@@ -0,0 +1,2 @@
+<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Papyrus_Profile_Architecture">Papyrus Profile Architecture</h1><p>This section describes the architecture used to define uml Profiles in Papyrus. </p><p>Papyrus Profiles and Stereotypes implementation is made of two different parts:</p><ul><li>The Profile and Stereotype definitions - This part is used to handle the stereotype and profile definitions.</li><li>The Profile and Stereotype applications - This part is used to apply an existing stereotype or profile to an UML element.</li></ul><h1 id="Profile_and_Stereotype_Definitions_Architecture">Profile and Stereotype Definitions Architecture</h1><p>Papyrus allows to create Profiles and Sterotypes in any kind of models. But, if you want to define Profiles and Stereotypes in order to apply them to UML elements, <b>you need to define a Profile in a 'Papyrus profile resource</b>' (i.e. a file).</p><p>The definitions of Profiles and Stereoptypes is made of two parts: the UML definitions, and the corresponding dynamic model. User define profiles and stereotypes in UML. The corresponding dynamic model is computed by Papyrus when the resource is saved.</p><p>UML definition of profile follows UML standard: Stereotypes must be defined in a uml::Profile.</p><p>The dynamic model is defined by Papyrus using the EMF/UML framework. This dynamic model is associated to a version number. The version number is incremented each time the dynamic model is re-created, so each time the profile resource is saved.</p><h1 id="Profile_and_Stereotype_applications_Architecture">Profile and Stereotype applications Architecture</h1><p>When Profile or a Stereotype is applied to an UML element, this create a Application object referencing both the uml element, and the profile or stereotype definition. 
+Thus, an uml element is not directly linked to an Application object.</p><p>Application objects are normally stored in the resource file containing the uml element they reference. They are not stored inside the UML model. Rather, they are stored alongside of the uml model. </p></body></html>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture.mediawiki b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture.mediawiki
new file mode 100644
index 00000000000..052af4cb72a
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/papyrusProfileArchitecture.mediawiki
@@ -0,0 +1,28 @@
+
+= Papyrus Profile Architecture =
+
+This section describes the architecture used to define uml Profiles in Papyrus. 
+
+Papyrus Profiles and Stereotypes implementation is made of two different parts:
+* The Profile and Stereotype '''definitions''' - This part is used to handle the stereotype and profile definitions.
+* The Profile and Stereotype '''applications''' - This part is used to apply an existing stereotype or profile to an UML element.
+
+
+= Profile and Stereotype Definitions Architecture =
+
+Papyrus allows to create Profiles and Sterotypes in any kind of models. But, if you want to define Profiles and Stereotypes in order to apply them to UML elements, '''you need to define a Profile in a 'Papyrus profile resource'''' (i.e. a file).
+
+The definitions of Profiles and Stereoptypes is made of two parts: the UML definitions, and the corresponding dynamic model. User define profiles and stereotypes in UML. The corresponding dynamic model is computed by Papyrus when the resource is saved.
+
+UML definition of profile follows UML standard: Stereotypes must be defined in a uml::Profile.
+
+The dynamic model is defined by Papyrus using the EMF/UML framework. This dynamic model is associated to a version number. The version number is incremented each time the dynamic model is re-created, so each time the profile resource is saved.
+
+= Profile and Stereotype applications Architecture =
+
+When Profile or a Stereotype is applied to an UML element, this create a Application object referencing both the uml element, and the profile or stereotype definition. 
+Thus, an uml element is not directly linked to an Application object.
+
+Application objects are normally stored in the resource file containing the uml element they reference. They are not stored inside the UML model. Rather, they are stored alongside of the uml model. 
+
+
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile-main-toc.xml b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile-main-toc.xml
new file mode 100644
index 00000000000..4a24e9cb947
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile-main-toc.xml
@@ -0,0 +1,15 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<toc label="Papyrus Profiles" link_to="../org.eclipse.papyrus.infra.doc/toc.xml#PapyrusDocUser">
+   <topic label="Using UML Profiles">
+      <anchor id="profiles-start"/>
+      <link toc="resource/users/whatIsAUmlProfile-toc.xml"/>
+      <link toc="resource/users/papyrusProfileArchitecture-toc.xml" />
+      <topic label="Defining Profiles And Stereotypes">
+          <link toc="resource/users/definingProfilesAndStereotypes-toc.xml" />
+      </topic>
+      <topic label="Using Profiles And Stereotypes">
+          <link toc="resource/users/usingProfilesAndStereotypes-toc.xml" />
+      </topic>
+      <anchor id="profiles-end" />
+   </topic>
+</toc>
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile-toc.xml b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile-toc.xml
index e46a2c21144..e46a2c21144 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile-toc.xml
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile-toc.xml
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile.html b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile.html
index d20358f0f02..d20358f0f02 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile.html
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile.html
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile.mediawiki b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile.mediawiki
index 6c70e49457b..92fa35b2f74 100644
--- a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/profile.mediawiki
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/profile.mediawiki
@@ -1,218 +1,218 @@
-= Introduction =

-

-The purpose of this chapter is to provide the Papyrus users all the documentation needed in order to be able to use UML profiles. It includes the information for modeling and defining a profile using the Papyrus UML profile editor, but also the information for the usage of a profile within a user application model.

-

-The basic premise of profiles is that all domain-specific concepts are derived as extensions or refinements of existing UML concepts, called UML metaclasses. These extensions are called stereotypes. A stereotype definition must be consistent with the abstract syntax and semantics of standard UML meta-classes it extends. Consequently, a profile-based model can be created and manipulated by any tool that supports standard UML. Moreover, because the concepts underlying a profile are specializations of existing UML concepts, it is more easily learned by anyone with knowledge of UML.

-

-A stereotype is defined either as an extension of a UML base metaclass or as a specialization of an existing stereotype. The extension relationship of UML is not an association but a kind of association directed from the stereotype to the extended metaclass. Consequently, the metadata conveyed by the associated the attributes of the stereotype are associated to the extended metaclass in a transparent manner for the metaclass itself. This allows profiles owning the stereotypes to be applied and removed dynamically without modifying the underlying models — a fundamental feature of the profile mechanism.

-

-A stereotype may have attributes and may be associated with other stereotypes or existing UML metaclasses.

-

-Constraints, such as OCL constraints, can also be defined in a profile. They can apply to stereotypes defined in the profile or those imported by the profile. They can also be used to further constrain elements of the UML metamodel. For instance, one could define an OCL constraint that all instances of Class in a model are active, or that all instances of Class must have at least one Operation (regardless of whether the Class is extended by a stereotype or not). However, not all constraints can be written in OCL. In that case, it is common to denote those latter in natural language. The drawback is that such constraints are no more automatically interpretable and need to be first rewritten in some language the UML tool will understand. In the context of Papyrus, it is then usual to use Java.

-

-= Profile Creation and Modeling =

-

-== Profile Creation ==

-

-To create a new Profile, select File > New > Papyrus Project (Or Papyrus model, if you already have an opened project). When asked for a Diagram Language, Select "Profile":

-

-[[Image:images/newProfile.png|New Profile]]<br>

-

-[[Image:images/newProfileDiagram.png|New Profile Diagram]]<br>

-

-[[Image:images/profileEditor.png|Profile Editor]]<br>

-

-== Stereotype Definition ==

-

-Once a profile has been created, it is now time to populate this latter with UML extensions, i.e. stereotypes, and their related concepts such as properties, extensions, and metaclasses.

-

-=== Stereotype Creation ===

-

-A stereotype is created as any other UML model elements in Papyrus: select the related tool in the palette of the profile diagram editor, and then click in the place you want to create this element on the background of the diagram. If the palette is not open, just click on the small arrow on the upper right corner of the diagram editor. Papyrus will then ask you to provide a name. Once done, hit the return key and that all.

-

-[[Image:images/stereotypePalette.png|Stereotype Palette]]<br>

-

-[[Image:images/stereotypeName.png|Stereotype Name]]<br>

-

-=== Metaclass Import ===

-

-Once you have created a stereotype, you need to import the UML2 metaclasses you want to extend. First, you have to select the tool “Import Metaclass” within the palette of the profile diagram editor. Then, let’s click on the profile diagram where you want to drop the imported metaclass. A Papyrus dialog box is then opened in order to ask you to specify which metaclasses you want to import. Select the metaclasses in the left list and either drag and drop these latter in the right list or press the button with arrow directed from left to right and located between both aforementioned lists. Then, let’s press the button “ok” and it is done. The imported metaclasses are then shown in the diagram as illustrated.

-

-[[Image:images/importMetaclassDialog.png|Import Metaclass]]<br>

-

-[[Image:images/importedMetaclass.png|Imported Metaclass]]<br>

-

-Note: When you import UML2 metaclasses, Papyrus is creating ImportElement model element referent to the metaclasses of the UML2 metamodel itself. Those so-called specific model elements, the ImportElement, are indeed a kind of proxy to the model elements contained in another model, in the UML2 metamodel. If a metaclass has already be imported, you do not need to import it again to use it in another context. You can select the imported meta-class from the model browser and drag and drop this latter on the diagram you want to use it.

-

-=== Extension Creation ===

-

-Once the stereotype is created and the meta-class is imported, you may then model the extension relation from the stereotype to the meta-class as shown in the following figure. The extension relationship is modeled using the extension tool in the profile diagram palette, [[Image:images/Extension.gif|Extension]]. Within the diagram shown in next figure, both stereotypes «Requirement» and «Refinement» extend respectively both meta-classes Class and Dependency:

-

-[[Image:images/metaclassExtension.png|Metaclass Extension]]<br>

-

-=== Subprofile Creation ===

-

-Some profile may be complex due as for example to their scope that may be large. In order to cope with this complexity, it is then possible to decompose a profile into a hierarchy of subprofiles. A subprofile behaves such as a sub-package; it is a container of stereotypes.

-

-To create a sub profile, select the profile tool in the profile diagram palette ([[Image:images/Profile.gif|Profile]]) and then click on the profile diagram where you want to create your new profile.

-

-In the example denoted below, we have created two sub-profiles of the SimplifiedReqML profile in order to gather in one hand the extensions that apply to node elements of the models and in the other hand the extension defined in the DSML for modeling relationships between those nodes:

-

-[[Image:images/subProfiles.png|Sub Profiles]]<br>

-

-=== Stereotype Generalization ===

-

-When designing a profile, it is possible to reuse existing stereotypes defined in other existing profiles. Stereotypes can indeed be generalized enabling to create child stereotypes that inherit features of one or more generalized stereotype define either locally in the profile or externally other profiles.

-

-To create a stereotype generalization using the profile diagram editor, let’s draw a generalization relationship using the tool [[Image:images/Generalization.gif|Generalization]] from the palette. As any relationship within Papyrus, you need to click first on the source and then on the target of the relationship you want to model.

-

-In our example, there exists in the UML predefined profile a stereotype extending the dependency relationship in order to introduce the concept of refinement: «Refine». Consequently, we will redesign our sub-profile SRMLRelationship in order our stereotype «Refinement» to be a specialization of this UML stereotype instead of directly extending the UML dependency meta-class.

-

-As previously mentioned, you may extend a stereotype defined in your profile or a stereotype defined in another external profile. In the latter case, the first thing to do is to import the profile where the stereotype has been defined, as denoted in the following example:

-

-[[Image:images/importProfile.png|Import Profile]]<br>

-

-[[Image:images/selectProfile.png|Select Profile]]<br>

-

-Once the profile has been imported, you can select the stereotype you want to generalize from the imported profile (In the Model Explorer) and drop this latter in the diagram of profile description: 

-

-[[Image:images/dropStereotype.png|Drop Stereotype]]<br>

-

-Now, let’s draw the generalization relationship from your stereotype (e.g., «Refinement» in the figure below) to the generalized stereotype (e.g., «Refine» in the figure below). 

-

-[[Image:images/generalizeStereotype.png|Generalize Stereotype]]<br>

-

-At this point, your diagram should look like something like the one shown here:

-

-[[Image:images/resultProfile.png|Result Profile]]<br>

-

-== Stereotype display options ==

-

-When a stereotype application is shown in a diagram, the by-default way to show it within diagrams is using a string where the name of the stereotype is shown within a pair of French guillemets above or before the name of the model element. However, it is also possible to modify the graphical appearance of the annotated model element using icons. If the graphical representation of the model element is something like a box (including ellipse of the use cases), the icons can be displayed inside and on top of the figures, or it may replace this latter. In that latter case, the property of the element cannot be shown and the name of the model element appears within a label displayed near the icon. If the model element is graphically denoted by a line, the icon is shown in front of the name of the link.

-

-In order to specify the icons you want to attach to a stereotype, select the stereotype and the tab UML of the property view. In the right-upper corner of the widget named “icons”, press the button [[Image:images/Add.gif|Add]] to add a new icon as shown in step 1. Once done, the dialog box shown at step 2 is open. Within this latter, let’s fill in a name and select an image file using the button [[Image:images/Add.gif|Add]] defining the content of the icon. Next, you have to define the kind value: icon or shape. Using this property, you can choose to associate the selected image either as an icon or as a shape.

-

-[[Image:images/iconsForStereotype.png|Step 1: Icons for Stereotypes]]<br>

-

-[[Image:images/selectIcon.png|Step 2: Select Icon]]<br>

-

-It is possible to associate only one shape to a stereotype, but you can associate different icons to a same stereotype. In that latter case, there is a description property that is used to select which one to display. By default, if no expression is defined, the first one is the list is chosen for displaying. The expression has to be on a property of the stereotype which type is an enumeration type.

-In our example, we can set different icons to the stereotype «Requirement» depending on the value of its importance property. This latter is indeed typed by the ImportanceLevel enumeration which values may be High, Medium of Low (figure shown below). For this example, we will then associate the three following images [[Image:images/high.png|High]], [[Image:images/medium.png|Medium]], and [[Image:images/low.png|Low]], to the stereotype «Requirement» and their related expression will be respectively importance=High (e.g. figure shown below), importance=Medium and importance=Low.

-

-[[Image:images/manyStereotypeIcons.png|Many Stereotype Icons]]<br>

-

-[[Image:images/iconKind.png|Icon Kind]]<br>

-

-[[Image:images/iconExpressions.png|Icon Expressions]]<br>

-

-[[Image:images/highReqIcon.png|High Req. Icon]]<br>

-

-= Profile Definition and Export =

-

-Once a profile has been modeled, we need to define it before being able to apply it on user models. The definition of a profile consists in:

-

-''“When defining a dynamic profile representation, the contents of a profile are converted to an equivalent Ecore format that is stored as an annotation on the profile. Then, when a profile and its stereotypes are applied to a model and its elements, dynamic EMF (see the EMF book for details) is used to store property values for the stereotypes. For the most part, you can ignore this complexity, as long as you remember to define your profile before using it.”''

-

-(This definition has been extracted from [[http://wiki.eclipse.org/MDT/UML2/Introduction_to_UML2_Profiles]])

-

-''PS: The implementation of profile support in the UML2 component of MDT supports defining both dynamic and static profile representations. In this the document, we will focus on dynamic profiles.''

-

-To define a profile within Papyrus, you just need to save it doing as for example following actions: either through the menu bar action File > Save or using the key shortcut “CTRL S”.

-Let’s notice, that it is not mandatory to define a profile each time you save it. If you do not want to define your profile when saving it, just answer no to the related question asked by Papyrus when saving profile modifications. However, if you want to apply the modifications you have done on a given profile, this you have to define it again in order the modifications may be taken into account at the user model level.

-

-[[Image:images/profileDefinition1.png|Profile Definition]]<br>

-

-[[Image:images/profileDefinition2.png|Profile Definition]]<br>

-

-Note: If the profile contains errors (Such as an untyped Property or unnamed Stereotype), you won't be able to define it. However, it can still be saved. In such a case, a Diagnostic dialog displays all the validation errors preventing the profile from being defined.

-

-[[Image:images/profileDefinitionErrors.png|Profile Definition Errors]]<br>

-

-= Profile Application and Usage =

-

-Once a profile has been designed and defined as previously explained, it now times to use it. The first step to process is to apply the profile on your model or a part of the model. This is the purpose of the next section to explain this first step. Then, we will explain how to use the applied profile and mainly how to use its extensions, i.e. its stereotypes.

-

-== Applying a Profile ==

-

-To apply a profile, first you need to open your model.

-

-The first step consists in selecting the part of the model you want to apply the profile on. Profiles can be applied either on Models or Packages. Then to apply the profile on this part, let’s select the profile tab in the property view, and press the [[Image:images/Add.gif|Apply Profile]] button.

-

-[[Image:images/applyProfile.png|Select Package]]<br>

-

-[[Image:images/applyProfile2.png|Profile Tab]]<br>

-

-[[Image:images/applyProfile3.png|Apply Profile]]<br>

-

-Then, Papyrus will ask you firstly to choose the profile to apply from your workspace, and secondly to choose which part of the selected profile you want to apply. It is indeed possible that your profile may be composed of sub-profiles as explained in the previous chapter. It is then possible to apply partially a profile by applying one or more of its sub-profiles.

-

-[[Image:images/selectProfileModel.png|Select Profile]]<br>

-

-[[Image:images/selectProfiles.png|Select Profiles]]<br>

-

-Your model should now look like this:

-

-[[Image:images/appliedProfiles.png|Applied Profiles]]<br>

-

-== Using the Stereotypes of a Profile ==

-

-Once the profile is applied on you model, its extensions, i.e. stereotypes, are available in the modeling tool and can be used in your model to annotate it.

-

-=== Applying a Stereotype ===

-

-To annotate a model element, you first need to select it either through the model explorer or in one open diagram. Then, select the tab named “profile” in the properties view, and add your stereotype using the [[Image:images/Add.gif|Apply Profile]] button of the widget named “Applied stereotypes”

-

-[[Image:images/applyStereotype.png|Apply Stereotype]]<br>

-

-[[Image:images/applyStereotype2.png|Apply Stereotype]]<br>

-

-[[Image:images/applyStereotype3.png|Apply Stereotype]]<br>

-

-A dialog box enables you to select the stereotype(s) you want to apply (left part of the dialog box) and using the [[Image:images/arrow_right.gif|Add]] button located in the middle of the dialog box enables to define which stereotypes have to be applied. The list located on the right of the dialog box denotes the list of applied stereotype. If you want to unapply stereotypes, you can select those latter from the right list and use the [[Image:images/arrow_left.gif|Remove]] button to unapply them.

-

-[[Image:images/applyStereotype4.png|Apply Stereotype]]<br>

-

-[[Image:images/applyStereotype5.png|Apply Stereotype]]<br>

-

-At this point, your Papyrus should look like this:

-

-[[Image:images/appliedStereotype.png|Applied Stereotype]]<br>

-

-=== Assigning values to properties of stereotypes ===

-

-As already mentioned, Stereotypes may have properties. Consequently, when applying a stereotype to a model element, it may be necessary to set the values of those properties. For that, you will go to the profile tab of the properties view and then you can unfold the stereotype application as shown in following figure:

-

-[[Image:images/stereotypeProperties.png|Stereotype Properties]]<br>

-

-Once you have selected the property to edit, its value (if already set, as for example if there is a default value defined in the profile for the property) appear in the right part of the property view. If the property has not yet been valued, you can add a value by using the [[Image:images/add.gif|Add]] button located on the top right of the widget named “Properties values”. If there is a value, double-click on the value to edit this latter.

-

-[[Image:images/stereotypePropertyEdition.png|Edit Property]]<br>

-

-Ps: If you want to delete a value set to property, let’s use the [[Image:images/Delete.gif|Delete]] button located on the top right of the widget named “Properties values”.

-

-=== Display options of a stereotype application ===

-

-Stereotype applications may be graphically rendered under different forms, either textually, or using specific icons. Details to specify those icons associated to a stereotype are given in previous chapters (See [[#Stereotype display options]]).

-

-Let’s remind that in UML, you can apply several stereotypes on a same model element. In Papyrus, it is then possible to select the ones you want to show for each diagram. For showing or hiding a stereotype application, you have to select the tab “appearance” in the properties view. As shown in the next figure, there is one widget named “Applied stereotypes” that denotes the list of stereotypes applied on the current selected model element. On the example illustrated within this figure, you can see on the upper corner of the icon placed in front of the stereotype name “Requirement” an overlay denoting that this stereotype application is shown.

-

-[[Image:images/stereotypeDisplayOptions.png|Stereotype Display]]<br>

-

-''Warning: Let’s notice that the appearance tab of the property view is only visible if you select a model element from one of the open diagram. In other case, if you select the model element from the model explorer, the concept of graphical does not make sense because the information specified within this view are only related to graphical information.''

-

-''Consequently, the values set to the appearance properties of model element are valid only in the context of the diagram where the element is selected. It is then possible to show a stereotype on a diagram and hide it in another diagram depending on the concerns of the view realized by the diagram.''

-

-To hide or show stereotype applications, you have to select them from the list of applied stereotypes available within the appearance tab and then either press the [[Image:images/ConsoleViewQN.gif|Display qualified name]] button or [[Image:images/change_display.gif|Display]].

-

-The former is to be used if you want to display the stereotype application with its qualified name, and the latter is to be used if you want to show it without qualified name. Using one of both depends if you may have ambiguities or not on the origin of the stereotype when as for example applying several profiles defining similar stereotypes. As for example, both profiles, MARTE and SysML, define a stereotype named «FlowPort».

-

-In addition, there are three other widgets dedicated to configure the stereotype display options:

-

-* “Stereotype display” is an enumeration which values may be Text, Icon, Text and Icon or Shape. In UML, as explained previously, a stereotype may be denoted either as a string between a pair of French guillemets (e.g., «Requirement»), or as an icon embedded in the figure or as a shape with a label. In case of the shape option, it substitutes the normal graphical figure used to represent the element and its label denotes the name of the element.

-

-* “Text alignment” is an enumeration which values may be Horizontal or Vertical. When several applied stereotypes are shown, it is rendered as a list of string separated by a comma and enclosed between a pair of French guillemets. By default, this string is shown horizontally. But some times for aesthetic reasons, it may be useful to show it vertically, that is to say showing one stereotype per line.

-

-* “Display place” is an enumeration which values may be Compartment, Comment or With brace. This appearance property is used to set where to show the properties values of the applied stereotypes. In UML, those values can be shown either within a pair of braces located just near (above or on top) the name label of the model element (“With brace” option), or into a dedicated compartment, or in a text note associated with the annotated model element.

-

-''PS: if you display several stereotype applications, and if you select the options to display them with icon or with icon and text, this is the icon of the first stereotype application in the list which is chosen to be displayed.''

-

+= Introduction =
+
+The purpose of this chapter is to provide the Papyrus users all the documentation needed in order to be able to use UML profiles. It includes the information for modeling and defining a profile using the Papyrus UML profile editor, but also the information for the usage of a profile within a user application model.
+
+The basic premise of profiles is that all domain-specific concepts are derived as extensions or refinements of existing UML concepts, called UML metaclasses. These extensions are called stereotypes. A stereotype definition must be consistent with the abstract syntax and semantics of standard UML meta-classes it extends. Consequently, a profile-based model can be created and manipulated by any tool that supports standard UML. Moreover, because the concepts underlying a profile are specializations of existing UML concepts, it is more easily learned by anyone with knowledge of UML.
+
+A stereotype is defined either as an extension of a UML base metaclass or as a specialization of an existing stereotype. The extension relationship of UML is not an association but a kind of association directed from the stereotype to the extended metaclass. Consequently, the metadata conveyed by the associated the attributes of the stereotype are associated to the extended metaclass in a transparent manner for the metaclass itself. This allows profiles owning the stereotypes to be applied and removed dynamically without modifying the underlying models — a fundamental feature of the profile mechanism.
+
+A stereotype may have attributes and may be associated with other stereotypes or existing UML metaclasses.
+
+Constraints, such as OCL constraints, can also be defined in a profile. They can apply to stereotypes defined in the profile or those imported by the profile. They can also be used to further constrain elements of the UML metamodel. For instance, one could define an OCL constraint that all instances of Class in a model are active, or that all instances of Class must have at least one Operation (regardless of whether the Class is extended by a stereotype or not). However, not all constraints can be written in OCL. In that case, it is common to denote those latter in natural language. The drawback is that such constraints are no more automatically interpretable and need to be first rewritten in some language the UML tool will understand. In the context of Papyrus, it is then usual to use Java.
+
+= Profile Creation and Modeling =
+
+== Profile Creation ==
+
+To create a new Profile, select File > New > Papyrus Project (Or Papyrus model, if you already have an opened project). When asked for a Diagram Language, Select "Profile":
+
+[[Image:images/newProfile.png|New Profile]]<br>
+
+[[Image:images/newProfileDiagram.png|New Profile Diagram]]<br>
+
+[[Image:images/profileEditor.png|Profile Editor]]<br>
+
+== Stereotype Definition ==
+
+Once a profile has been created, it is now time to populate this latter with UML extensions, i.e. stereotypes, and their related concepts such as properties, extensions, and metaclasses.
+
+=== Stereotype Creation ===
+
+A stereotype is created as any other UML model elements in Papyrus: select the related tool in the palette of the profile diagram editor, and then click in the place you want to create this element on the background of the diagram. If the palette is not open, just click on the small arrow on the upper right corner of the diagram editor. Papyrus will then ask you to provide a name. Once done, hit the return key and that all.
+
+[[Image:images/stereotypePalette.png|Stereotype Palette]]<br>
+
+[[Image:images/stereotypeName.png|Stereotype Name]]<br>
+
+=== Metaclass Import ===
+
+Once you have created a stereotype, you need to import the UML2 metaclasses you want to extend. First, you have to select the tool “Import Metaclass” within the palette of the profile diagram editor. Then, let’s click on the profile diagram where you want to drop the imported metaclass. A Papyrus dialog box is then opened in order to ask you to specify which metaclasses you want to import. Select the metaclasses in the left list and either drag and drop these latter in the right list or press the button with arrow directed from left to right and located between both aforementioned lists. Then, let’s press the button “ok” and it is done. The imported metaclasses are then shown in the diagram as illustrated.
+
+[[Image:images/importMetaclassDialog.png|Import Metaclass]]<br>
+
+[[Image:images/importedMetaclass.png|Imported Metaclass]]<br>
+
+Note: When you import UML2 metaclasses, Papyrus is creating ImportElement model element referent to the metaclasses of the UML2 metamodel itself. Those so-called specific model elements, the ImportElement, are indeed a kind of proxy to the model elements contained in another model, in the UML2 metamodel. If a metaclass has already be imported, you do not need to import it again to use it in another context. You can select the imported meta-class from the model browser and drag and drop this latter on the diagram you want to use it.
+
+=== Extension Creation ===
+
+Once the stereotype is created and the meta-class is imported, you may then model the extension relation from the stereotype to the meta-class as shown in the following figure. The extension relationship is modeled using the extension tool in the profile diagram palette, [[Image:images/Extension.gif|Extension]]. Within the diagram shown in next figure, both stereotypes «Requirement» and «Refinement» extend respectively both meta-classes Class and Dependency:
+
+[[Image:images/metaclassExtension.png|Metaclass Extension]]<br>
+
+=== Subprofile Creation ===
+
+Some profile may be complex due as for example to their scope that may be large. In order to cope with this complexity, it is then possible to decompose a profile into a hierarchy of subprofiles. A subprofile behaves such as a sub-package; it is a container of stereotypes.
+
+To create a sub profile, select the profile tool in the profile diagram palette ([[Image:images/Profile.gif|Profile]]) and then click on the profile diagram where you want to create your new profile.
+
+In the example denoted below, we have created two sub-profiles of the SimplifiedReqML profile in order to gather in one hand the extensions that apply to node elements of the models and in the other hand the extension defined in the DSML for modeling relationships between those nodes:
+
+[[Image:images/subProfiles.png|Sub Profiles]]<br>
+
+=== Stereotype Generalization ===
+
+When designing a profile, it is possible to reuse existing stereotypes defined in other existing profiles. Stereotypes can indeed be generalized enabling to create child stereotypes that inherit features of one or more generalized stereotype define either locally in the profile or externally other profiles.
+
+To create a stereotype generalization using the profile diagram editor, let’s draw a generalization relationship using the tool [[Image:images/Generalization.gif|Generalization]] from the palette. As any relationship within Papyrus, you need to click first on the source and then on the target of the relationship you want to model.
+
+In our example, there exists in the UML predefined profile a stereotype extending the dependency relationship in order to introduce the concept of refinement: «Refine». Consequently, we will redesign our sub-profile SRMLRelationship in order our stereotype «Refinement» to be a specialization of this UML stereotype instead of directly extending the UML dependency meta-class.
+
+As previously mentioned, you may extend a stereotype defined in your profile or a stereotype defined in another external profile. In the latter case, the first thing to do is to import the profile where the stereotype has been defined, as denoted in the following example:
+
+[[Image:images/importProfile.png|Import Profile]]<br>
+
+[[Image:images/selectProfile.png|Select Profile]]<br>
+
+Once the profile has been imported, you can select the stereotype you want to generalize from the imported profile (In the Model Explorer) and drop this latter in the diagram of profile description: 
+
+[[Image:images/dropStereotype.png|Drop Stereotype]]<br>
+
+Now, let’s draw the generalization relationship from your stereotype (e.g., «Refinement» in the figure below) to the generalized stereotype (e.g., «Refine» in the figure below). 
+
+[[Image:images/generalizeStereotype.png|Generalize Stereotype]]<br>
+
+At this point, your diagram should look like something like the one shown here:
+
+[[Image:images/resultProfile.png|Result Profile]]<br>
+
+== Stereotype display options ==
+
+When a stereotype application is shown in a diagram, the by-default way to show it within diagrams is using a string where the name of the stereotype is shown within a pair of French guillemets above or before the name of the model element. However, it is also possible to modify the graphical appearance of the annotated model element using icons. If the graphical representation of the model element is something like a box (including ellipse of the use cases), the icons can be displayed inside and on top of the figures, or it may replace this latter. In that latter case, the property of the element cannot be shown and the name of the model element appears within a label displayed near the icon. If the model element is graphically denoted by a line, the icon is shown in front of the name of the link.
+
+In order to specify the icons you want to attach to a stereotype, select the stereotype and the tab UML of the property view. In the right-upper corner of the widget named “icons”, press the button [[Image:images/Add.gif|Add]] to add a new icon as shown in step 1. Once done, the dialog box shown at step 2 is open. Within this latter, let’s fill in a name and select an image file using the button [[Image:images/Add.gif|Add]] defining the content of the icon. Next, you have to define the kind value: icon or shape. Using this property, you can choose to associate the selected image either as an icon or as a shape.
+
+[[Image:images/iconsForStereotype.png|Step 1: Icons for Stereotypes]]<br>
+
+[[Image:images/selectIcon.png|Step 2: Select Icon]]<br>
+
+It is possible to associate only one shape to a stereotype, but you can associate different icons to a same stereotype. In that latter case, there is a description property that is used to select which one to display. By default, if no expression is defined, the first one is the list is chosen for displaying. The expression has to be on a property of the stereotype which type is an enumeration type.
+In our example, we can set different icons to the stereotype «Requirement» depending on the value of its importance property. This latter is indeed typed by the ImportanceLevel enumeration which values may be High, Medium of Low (figure shown below). For this example, we will then associate the three following images [[Image:images/high.png|High]], [[Image:images/medium.png|Medium]], and [[Image:images/low.png|Low]], to the stereotype «Requirement» and their related expression will be respectively importance=High (e.g. figure shown below), importance=Medium and importance=Low.
+
+[[Image:images/manyStereotypeIcons.png|Many Stereotype Icons]]<br>
+
+[[Image:images/iconKind.png|Icon Kind]]<br>
+
+[[Image:images/iconExpressions.png|Icon Expressions]]<br>
+
+[[Image:images/highReqIcon.png|High Req. Icon]]<br>
+
+= Profile Definition and Export =
+
+Once a profile has been modeled, we need to define it before being able to apply it on user models. The definition of a profile consists in:
+
+''“When defining a dynamic profile representation, the contents of a profile are converted to an equivalent Ecore format that is stored as an annotation on the profile. Then, when a profile and its stereotypes are applied to a model and its elements, dynamic EMF (see the EMF book for details) is used to store property values for the stereotypes. For the most part, you can ignore this complexity, as long as you remember to define your profile before using it.”''
+
+(This definition has been extracted from [[http://wiki.eclipse.org/MDT/UML2/Introduction_to_UML2_Profiles]])
+
+''PS: The implementation of profile support in the UML2 component of MDT supports defining both dynamic and static profile representations. In this the document, we will focus on dynamic profiles.''
+
+To define a profile within Papyrus, you just need to save it doing as for example following actions: either through the menu bar action File > Save or using the key shortcut “CTRL S”.
+Let’s notice, that it is not mandatory to define a profile each time you save it. If you do not want to define your profile when saving it, just answer no to the related question asked by Papyrus when saving profile modifications. However, if you want to apply the modifications you have done on a given profile, this you have to define it again in order the modifications may be taken into account at the user model level.
+
+[[Image:images/profileDefinition1.png|Profile Definition]]<br>
+
+[[Image:images/profileDefinition2.png|Profile Definition]]<br>
+
+Note: If the profile contains errors (Such as an untyped Property or unnamed Stereotype), you won't be able to define it. However, it can still be saved. In such a case, a Diagnostic dialog displays all the validation errors preventing the profile from being defined.
+
+[[Image:images/profileDefinitionErrors.png|Profile Definition Errors]]<br>
+
+= Profile Application and Usage =
+
+Once a profile has been designed and defined as previously explained, it now times to use it. The first step to process is to apply the profile on your model or a part of the model. This is the purpose of the next section to explain this first step. Then, we will explain how to use the applied profile and mainly how to use its extensions, i.e. its stereotypes.
+
+== Applying a Profile ==
+
+To apply a profile, first you need to open your model.
+
+The first step consists in selecting the part of the model you want to apply the profile on. Profiles can be applied either on Models or Packages. Then to apply the profile on this part, let’s select the profile tab in the property view, and press the [[Image:images/Add.gif|Apply Profile]] button.
+
+[[Image:images/applyProfile.png|Select Package]]<br>
+
+[[Image:images/applyProfile2.png|Profile Tab]]<br>
+
+[[Image:images/applyProfile3.png|Apply Profile]]<br>
+
+Then, Papyrus will ask you firstly to choose the profile to apply from your workspace, and secondly to choose which part of the selected profile you want to apply. It is indeed possible that your profile may be composed of sub-profiles as explained in the previous chapter. It is then possible to apply partially a profile by applying one or more of its sub-profiles.
+
+[[Image:images/selectProfileModel.png|Select Profile]]<br>
+
+[[Image:images/selectProfiles.png|Select Profiles]]<br>
+
+Your model should now look like this:
+
+[[Image:images/appliedProfiles.png|Applied Profiles]]<br>
+
+== Using the Stereotypes of a Profile ==
+
+Once the profile is applied on you model, its extensions, i.e. stereotypes, are available in the modeling tool and can be used in your model to annotate it.
+
+=== Applying a Stereotype ===
+
+To annotate a model element, you first need to select it either through the model explorer or in one open diagram. Then, select the tab named “profile” in the properties view, and add your stereotype using the [[Image:images/Add.gif|Apply Profile]] button of the widget named “Applied stereotypes”
+
+[[Image:images/applyStereotype.png|Apply Stereotype]]<br>
+
+[[Image:images/applyStereotype2.png|Apply Stereotype]]<br>
+
+[[Image:images/applyStereotype3.png|Apply Stereotype]]<br>
+
+A dialog box enables you to select the stereotype(s) you want to apply (left part of the dialog box) and using the [[Image:images/arrow_right.gif|Add]] button located in the middle of the dialog box enables to define which stereotypes have to be applied. The list located on the right of the dialog box denotes the list of applied stereotype. If you want to unapply stereotypes, you can select those latter from the right list and use the [[Image:images/arrow_left.gif|Remove]] button to unapply them.
+
+[[Image:images/applyStereotype4.png|Apply Stereotype]]<br>
+
+[[Image:images/applyStereotype5.png|Apply Stereotype]]<br>
+
+At this point, your Papyrus should look like this:
+
+[[Image:images/appliedStereotype.png|Applied Stereotype]]<br>
+
+=== Assigning values to properties of stereotypes ===
+
+As already mentioned, Stereotypes may have properties. Consequently, when applying a stereotype to a model element, it may be necessary to set the values of those properties. For that, you will go to the profile tab of the properties view and then you can unfold the stereotype application as shown in following figure:
+
+[[Image:images/stereotypeProperties.png|Stereotype Properties]]<br>
+
+Once you have selected the property to edit, its value (if already set, as for example if there is a default value defined in the profile for the property) appear in the right part of the property view. If the property has not yet been valued, you can add a value by using the [[Image:images/add.gif|Add]] button located on the top right of the widget named “Properties values”. If there is a value, double-click on the value to edit this latter.
+
+[[Image:images/stereotypePropertyEdition.png|Edit Property]]<br>
+
+Ps: If you want to delete a value set to property, let’s use the [[Image:images/Delete.gif|Delete]] button located on the top right of the widget named “Properties values”.
+
+=== Display options of a stereotype application ===
+
+Stereotype applications may be graphically rendered under different forms, either textually, or using specific icons. Details to specify those icons associated to a stereotype are given in previous chapters (See [[#Stereotype display options]]).
+
+Let’s remind that in UML, you can apply several stereotypes on a same model element. In Papyrus, it is then possible to select the ones you want to show for each diagram. For showing or hiding a stereotype application, you have to select the tab “appearance” in the properties view. As shown in the next figure, there is one widget named “Applied stereotypes” that denotes the list of stereotypes applied on the current selected model element. On the example illustrated within this figure, you can see on the upper corner of the icon placed in front of the stereotype name “Requirement” an overlay denoting that this stereotype application is shown.
+
+[[Image:images/stereotypeDisplayOptions.png|Stereotype Display]]<br>
+
+''Warning: Let’s notice that the appearance tab of the property view is only visible if you select a model element from one of the open diagram. In other case, if you select the model element from the model explorer, the concept of graphical does not make sense because the information specified within this view are only related to graphical information.''
+
+''Consequently, the values set to the appearance properties of model element are valid only in the context of the diagram where the element is selected. It is then possible to show a stereotype on a diagram and hide it in another diagram depending on the concerns of the view realized by the diagram.''
+
+To hide or show stereotype applications, you have to select them from the list of applied stereotypes available within the appearance tab and then either press the [[Image:images/ConsoleViewQN.gif|Display qualified name]] button or [[Image:images/change_display.gif|Display]].
+
+The former is to be used if you want to display the stereotype application with its qualified name, and the latter is to be used if you want to show it without qualified name. Using one of both depends if you may have ambiguities or not on the origin of the stereotype when as for example applying several profiles defining similar stereotypes. As for example, both profiles, MARTE and SysML, define a stereotype named «FlowPort».
+
+In addition, there are three other widgets dedicated to configure the stereotype display options:
+
+* “Stereotype display” is an enumeration which values may be Text, Icon, Text and Icon or Shape. In UML, as explained previously, a stereotype may be denoted either as a string between a pair of French guillemets (e.g., «Requirement»), or as an icon embedded in the figure or as a shape with a label. In case of the shape option, it substitutes the normal graphical figure used to represent the element and its label denotes the name of the element.
+
+* “Text alignment” is an enumeration which values may be Horizontal or Vertical. When several applied stereotypes are shown, it is rendered as a list of string separated by a comma and enclosed between a pair of French guillemets. By default, this string is shown horizontally. But some times for aesthetic reasons, it may be useful to show it vertically, that is to say showing one stereotype per line.
+
+* “Display place” is an enumeration which values may be Compartment, Comment or With brace. This appearance property is used to set where to show the properties values of the applied stereotypes. In UML, those values can be shown either within a pair of braces located just near (above or on top) the name label of the model element (“With brace” option), or into a dedicated compartment, or in a text note associated with the annotated model element.
+
+''PS: if you display several stereotype applications, and if you select the options to display them with icon or with icon and text, this is the icon of the first stereotype application in the list which is chosen to be displayed.''
+
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes-toc.xml b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes-toc.xml
new file mode 100644
index 00000000000..4654a82fb83
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes-toc.xml
@@ -0,0 +1,8 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<toc topic="resource/users/usingProfilesAndStereotypes.html" label="usingProfilesAndStereotypes">
+	<topic href="resource/users/usingProfilesAndStereotypes.html" label="Using Profiles and Stereotypes"></topic>
+	<topic href="resource/users/usingProfilesAndStereotypes.html#Applying_a_Profile" label="Applying a Profile"></topic>
+	<topic href="resource/users/usingProfilesAndStereotypes.html#Applying_a_Stereotype" label="Applying a Stereotype"></topic>
+	<topic href="resource/users/usingProfilesAndStereotypes.html#Setting_values_to_stereotype.27_properties" label="Setting values to stereotype' properties"></topic>
+	<topic href="resource/users/usingProfilesAndStereotypes.html#Display_options_of_a_stereotype_application" label="Display options of a stereotype application"></topic>
+</toc>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes.html b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes.html
new file mode 100644
index 00000000000..b6136eb4df4
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes.html
@@ -0,0 +1 @@
+<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="Using_Profiles_and_Stereotypes">Using Profiles and Stereotypes</h1><p>Once a profile has been designed and defined as previously explained, it now times to use it. The first step to process is to apply the profile on your model or a part of the model. This is the purpose of the next section to explain this first step. Then, we will explain how to use the applied profile and mainly how to use its extensions, i.e. its stereotypes.</p><h1 id="Applying_a_Profile">Applying a Profile</h1><p>To apply a profile, first you need to open your model.</p><p>The first step consists in selecting the part of the model you want to apply the profile on. Profiles can be applied either on Models or Packages. Then to apply the profile on this part, let’s select the profile tab in the property view, and press the <img title="Apply Profile" alt="Apply Profile" border="0" src="images/Add.gif"/> button.</p><p><img title="Select Package" alt="Select Package" border="0" src="images/applyProfile.png"/><br/></p><p><img title="Profile Tab" alt="Profile Tab" border="0" src="images/applyProfile2.png"/><br/></p><p><img title="Apply Profile" alt="Apply Profile" border="0" src="images/applyProfile3.png"/><br/></p><p>Then, Papyrus will ask you firstly to choose the profile to apply from your workspace, and secondly to choose which part of the selected profile you want to apply. It is indeed possible that your profile may be composed of sub-profiles as explained in the previous chapter. It is then possible to apply partially a profile by applying one or more of its sub-profiles.</p><p><img title="Select Profile" alt="Select Profile" border="0" src="images/selectProfileModel.png"/><br/></p><p><img title="Select Profiles" alt="Select Profiles" border="0" src="images/selectProfiles.png"/><br/></p><p>Your model should now look like this:</p><p><img title="Applied Profiles" alt="Applied Profiles" border="0" src="images/appliedProfiles.png"/><br/></p><h1 id="Applying_a_Stereotype">Applying a Stereotype</h1><p>Once the profile is applied on your model, its extensions, i.e. stereotypes, are available in the modeling tool and can be used in your model to annotate uml elements.</p><p>To annotate a model element, you first need to select it either through the model explorer or in one open diagram. Then, select the tab named “profile” in the properties view, and add your stereotype using the <img title="Apply Profile" alt="Apply Profile" border="0" src="images/Add.gif"/> button of the widget named “Applied stereotypes”</p><p><img title="Apply Stereotype" alt="Apply Stereotype" border="0" src="images/applyStereotype.png"/><br/></p><p><img title="Apply Stereotype" alt="Apply Stereotype" border="0" src="images/applyStereotype2.png"/><br/></p><p><img title="Apply Stereotype" alt="Apply Stereotype" border="0" src="images/applyStereotype3.png"/><br/></p><p>A dialog box enables you to select the stereotype(s) you want to apply (left part of the dialog box) and using the <img title="Add" alt="Add" border="0" src="images/arrow_right.gif"/> button located in the middle of the dialog box enables to define which stereotypes have to be applied. The list located on the right of the dialog box denotes the list of applied stereotype. If you want to unapply stereotypes, you can select those latter from the right list and use the <img title="Remove" alt="Remove" border="0" src="images/arrow_left.gif"/> button to unapply them.</p><p><img title="Apply Stereotype" alt="Apply Stereotype" border="0" src="images/applyStereotype4.png"/><br/></p><p><img title="Apply Stereotype" alt="Apply Stereotype" border="0" src="images/applyStereotype5.png"/><br/></p><p>At this point, your Papyrus should look like this:</p><p><img title="Applied Stereotype" alt="Applied Stereotype" border="0" src="images/appliedStereotype.png"/><br/></p><h1 id="Setting_values_to_stereotype.27_properties">Setting values to stereotype' properties</h1><p>As already mentioned, Stereotypes may have properties. Consequently, when applying a stereotype to a model element, it may be necessary to set the values of those properties. For that, you will go to the profile tab of the properties view and then you can unfold the stereotype application as shown in following figure:</p><p><img title="Stereotype Properties" alt="Stereotype Properties" border="0" src="images/stereotypeProperties.png"/><br/></p><p>Once you have selected the property to edit, its value (if already set, as for example if there is a default value defined in the profile for the property) appear in the right part of the property view. If the property has not yet been valued, you can add a value by using the <img title="Add" alt="Add" border="0" src="images/add.gif"/> button located on the top right of the widget named “Properties values”. If there is a value, double-click on the value to edit this latter.</p><p><img title="Edit Property" alt="Edit Property" border="0" src="images/stereotypePropertyEdition.png"/><br/></p><p>Ps: If you want to delete a value set to property, let’s use the <img title="Delete" alt="Delete" border="0" src="images/Delete.gif"/> button located on the top right of the widget named “Properties values”.</p><h1 id="Display_options_of_a_stereotype_application">Display options of a stereotype application</h1><p>Stereotype applications may be graphically rendered under different forms, either textually, or using specific icons. Details to specify those icons associated to a stereotype are given in previous chapters (See <a href="/wiki/definingProfilesAndStereotypes#Stereotype_display_options" title="definingProfilesAndStereotypes#Stereotype display options">definingProfilesAndStereotypes#Stereotype display options</a>).</p><p>Let’s remind that in UML, you can apply several stereotypes on a same model element. In Papyrus, it is then possible to select the ones you want to show for each diagram. For showing or hiding a stereotype application, you have to select the tab “appearance” in the properties view. As shown in the next figure, there is one widget named “Applied stereotypes” that denotes the list of stereotypes applied on the current selected model element. On the example illustrated within this figure, you can see on the upper corner of the icon placed in front of the stereotype name “Requirement” an overlay denoting that this stereotype application is shown.</p><p><img title="Stereotype Display" alt="Stereotype Display" border="0" src="images/stereotypeDisplayOptions.png"/><br/></p><p><i>Warning: Let’s notice that the appearance tab of the property view is only visible if you select a model element from one of the open diagram. In other case, if you select the model element from the model explorer, the concept of graphical does not make sense because the information specified within this view are only related to graphical information.</i></p><p><i>Consequently, the values set to the appearance properties of model element are valid only in the context of the diagram where the element is selected. It is then possible to show a stereotype on a diagram and hide it in another diagram depending on the concerns of the view realized by the diagram.</i></p><p>To hide or show stereotype applications, you have to select them from the list of applied stereotypes available within the appearance tab and then either press the <img title="Display qualified name" alt="Display qualified name" border="0" src="images/ConsoleViewQN.gif"/> button or <img title="Display" alt="Display" border="0" src="images/change_display.gif"/>.</p><p>The former is to be used if you want to display the stereotype application with its qualified name, and the latter is to be used if you want to show it without qualified name. Using one of both depends if you may have ambiguities or not on the origin of the stereotype when as for example applying several profiles defining similar stereotypes. As for example, both profiles, MARTE and SysML, define a stereotype named «FlowPort».</p><p>In addition, there are three other widgets dedicated to configure the stereotype display options:</p><ul><li>“Stereotype display” is an enumeration which values may be Text, Icon, Text and Icon or Shape. In UML, as explained previously, a stereotype may be denoted either as a string between a pair of French guillemets (e.g., «Requirement»), or as an icon embedded in the figure or as a shape with a label. In case of the shape option, it substitutes the normal graphical figure used to represent the element and its label denotes the name of the element.</li></ul><ul><li>“Text alignment” is an enumeration which values may be Horizontal or Vertical. When several applied stereotypes are shown, it is rendered as a list of string separated by a comma and enclosed between a pair of French guillemets. By default, this string is shown horizontally. But some times for aesthetic reasons, it may be useful to show it vertically, that is to say showing one stereotype per line.</li></ul><ul><li>“Display place” is an enumeration which values may be Compartment, Comment or With brace. This appearance property is used to set where to show the properties values of the applied stereotypes. In UML, those values can be shown either within a pair of braces located just near (above or on top) the name label of the model element (“With brace” option), or into a dedicated compartment, or in a text note associated with the annotated model element.</li></ul><p><i>PS: if you display several stereotype applications, and if you select the options to display them with icon or with icon and text, this is the icon of the first stereotype application in the list which is chosen to be displayed.</i></p></body></html>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes.mediawiki b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes.mediawiki
new file mode 100644
index 00000000000..825adb60bdf
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/usingProfilesAndStereotypes.mediawiki
@@ -0,0 +1,86 @@
+= Using Profiles and Stereotypes =
+
+Once a profile has been designed and defined as previously explained, it now times to use it. The first step to process is to apply the profile on your model or a part of the model. This is the purpose of the next section to explain this first step. Then, we will explain how to use the applied profile and mainly how to use its extensions, i.e. its stereotypes.
+
+= Applying a Profile =
+
+To apply a profile, first you need to open your model.
+
+The first step consists in selecting the part of the model you want to apply the profile on. Profiles can be applied either on Models or Packages. Then to apply the profile on this part, let’s select the profile tab in the property view, and press the [[Image:images/Add.gif|Apply Profile]] button.
+
+[[Image:images/applyProfile.png|Select Package]]<br>
+
+[[Image:images/applyProfile2.png|Profile Tab]]<br>
+
+[[Image:images/applyProfile3.png|Apply Profile]]<br>
+
+Then, Papyrus will ask you firstly to choose the profile to apply from your workspace, and secondly to choose which part of the selected profile you want to apply. It is indeed possible that your profile may be composed of sub-profiles as explained in the previous chapter. It is then possible to apply partially a profile by applying one or more of its sub-profiles.
+
+[[Image:images/selectProfileModel.png|Select Profile]]<br>
+
+[[Image:images/selectProfiles.png|Select Profiles]]<br>
+
+Your model should now look like this:
+
+[[Image:images/appliedProfiles.png|Applied Profiles]]<br>
+
+= Applying a Stereotype =
+
+Once the profile is applied on your model, its extensions, i.e. stereotypes, are available in the modeling tool and can be used in your model to annotate uml elements.
+
+To annotate a model element, you first need to select it either through the model explorer or in one open diagram. Then, select the tab named “profile” in the properties view, and add your stereotype using the [[Image:images/Add.gif|Apply Profile]] button of the widget named “Applied stereotypes”
+
+[[Image:images/applyStereotype.png|Apply Stereotype]]<br>
+
+[[Image:images/applyStereotype2.png|Apply Stereotype]]<br>
+
+[[Image:images/applyStereotype3.png|Apply Stereotype]]<br>
+
+A dialog box enables you to select the stereotype(s) you want to apply (left part of the dialog box) and using the [[Image:images/arrow_right.gif|Add]] button located in the middle of the dialog box enables to define which stereotypes have to be applied. The list located on the right of the dialog box denotes the list of applied stereotype. If you want to unapply stereotypes, you can select those latter from the right list and use the [[Image:images/arrow_left.gif|Remove]] button to unapply them.
+
+[[Image:images/applyStereotype4.png|Apply Stereotype]]<br>
+
+[[Image:images/applyStereotype5.png|Apply Stereotype]]<br>
+
+At this point, your Papyrus should look like this:
+
+[[Image:images/appliedStereotype.png|Applied Stereotype]]<br>
+
+= Setting values to stereotype' properties =
+
+As already mentioned, Stereotypes may have properties. Consequently, when applying a stereotype to a model element, it may be necessary to set the values of those properties. For that, you will go to the profile tab of the properties view and then you can unfold the stereotype application as shown in following figure:
+
+[[Image:images/stereotypeProperties.png|Stereotype Properties]]<br>
+
+Once you have selected the property to edit, its value (if already set, as for example if there is a default value defined in the profile for the property) appear in the right part of the property view. If the property has not yet been valued, you can add a value by using the [[Image:images/add.gif|Add]] button located on the top right of the widget named “Properties values”. If there is a value, double-click on the value to edit this latter.
+
+[[Image:images/stereotypePropertyEdition.png|Edit Property]]<br>
+
+Ps: If you want to delete a value set to property, let’s use the [[Image:images/Delete.gif|Delete]] button located on the top right of the widget named “Properties values”.
+
+= Display options of a stereotype application =
+
+Stereotype applications may be graphically rendered under different forms, either textually, or using specific icons. Details to specify those icons associated to a stereotype are given in previous chapters (See [[definingProfilesAndStereotypes#Stereotype display options]]).
+
+Let’s remind that in UML, you can apply several stereotypes on a same model element. In Papyrus, it is then possible to select the ones you want to show for each diagram. For showing or hiding a stereotype application, you have to select the tab “appearance” in the properties view. As shown in the next figure, there is one widget named “Applied stereotypes” that denotes the list of stereotypes applied on the current selected model element. On the example illustrated within this figure, you can see on the upper corner of the icon placed in front of the stereotype name “Requirement” an overlay denoting that this stereotype application is shown.
+
+[[Image:images/stereotypeDisplayOptions.png|Stereotype Display]]<br>
+
+''Warning: Let’s notice that the appearance tab of the property view is only visible if you select a model element from one of the open diagram. In other case, if you select the model element from the model explorer, the concept of graphical does not make sense because the information specified within this view are only related to graphical information.''
+
+''Consequently, the values set to the appearance properties of model element are valid only in the context of the diagram where the element is selected. It is then possible to show a stereotype on a diagram and hide it in another diagram depending on the concerns of the view realized by the diagram.''
+
+To hide or show stereotype applications, you have to select them from the list of applied stereotypes available within the appearance tab and then either press the [[Image:images/ConsoleViewQN.gif|Display qualified name]] button or [[Image:images/change_display.gif|Display]].
+
+The former is to be used if you want to display the stereotype application with its qualified name, and the latter is to be used if you want to show it without qualified name. Using one of both depends if you may have ambiguities or not on the origin of the stereotype when as for example applying several profiles defining similar stereotypes. As for example, both profiles, MARTE and SysML, define a stereotype named «FlowPort».
+
+In addition, there are three other widgets dedicated to configure the stereotype display options:
+
+* “Stereotype display” is an enumeration which values may be Text, Icon, Text and Icon or Shape. In UML, as explained previously, a stereotype may be denoted either as a string between a pair of French guillemets (e.g., «Requirement»), or as an icon embedded in the figure or as a shape with a label. In case of the shape option, it substitutes the normal graphical figure used to represent the element and its label denotes the name of the element.
+
+* “Text alignment” is an enumeration which values may be Horizontal or Vertical. When several applied stereotypes are shown, it is rendered as a list of string separated by a comma and enclosed between a pair of French guillemets. By default, this string is shown horizontally. But some times for aesthetic reasons, it may be useful to show it vertically, that is to say showing one stereotype per line.
+
+* “Display place” is an enumeration which values may be Compartment, Comment or With brace. This appearance property is used to set where to show the properties values of the applied stereotypes. In UML, those values can be shown either within a pair of braces located just near (above or on top) the name label of the model element (“With brace” option), or into a dedicated compartment, or in a text note associated with the annotated model element.
+
+''PS: if you display several stereotype applications, and if you select the options to display them with icon or with icon and text, this is the icon of the first stereotype application in the list which is chosen to be displayed.''
+
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile-toc.xml b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile-toc.xml
new file mode 100644
index 00000000000..69bd0f69944
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile-toc.xml
@@ -0,0 +1,4 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<toc topic="resource/users/whatIsAUmlProfile.html" label="whatIsAUmlProfile">
+	<topic href="resource/users/whatIsAUmlProfile.html" label="What Is A UML Profile"></topic>
+</toc>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile.html b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile.html
new file mode 100644
index 00000000000..48ce377bbd0
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile.html
@@ -0,0 +1 @@
+<?xml version='1.0' encoding='utf-8' ?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/></head><body><h1 id="What_Is_A_UML_Profile">What Is A UML Profile</h1><p>The purpose of this chapter is to provide the Papyrus users all the documentation needed in order to be able to use UML profiles. It includes the information for modeling and defining a profile using the Papyrus UML profile editor, but also the information for the usage of a profile within a user application model.</p><p>The basic premise of profiles is that all domain-specific concepts are derived as extensions or refinements of existing UML concepts, called UML metaclasses. These extensions are called stereotypes. A stereotype definition must be consistent with the abstract syntax and semantics of standard UML meta-classes it extends. Consequently, a profile-based model can be created and manipulated by any tool that supports standard UML. Moreover, because the concepts underlying a profile are specializations of existing UML concepts, it is more easily learned by anyone with knowledge of UML.</p><p>A stereotype is defined either as an extension of a UML base metaclass or as a specialization of an existing stereotype. The extension relationship of UML is not an association but a kind of association directed from the stereotype to the extended metaclass. Consequently, the metadata conveyed by the associated the attributes of the stereotype are associated to the extended metaclass in a transparent manner for the metaclass itself. This allows profiles owning the stereotypes to be applied and removed dynamically without modifying the underlying models — a fundamental feature of the profile mechanism.</p><p>A stereotype may have attributes and may be associated with other stereotypes or existing UML metaclasses.</p><p>Constraints, such as OCL constraints, can also be defined in a profile. They can apply to stereotypes defined in the profile or those imported by the profile. They can also be used to further constrain elements of the UML metamodel. For instance, one could define an OCL constraint that all instances of Class in a model are active, or that all instances of Class must have at least one Operation (regardless of whether the Class is extended by a stereotype or not). However, not all constraints can be written in OCL. In that case, it is common to denote those latter in natural language. The drawback is that such constraints are no more automatically interpretable and need to be first rewritten in some language the UML tool will understand. In the context of Papyrus, it is then usual to use Java.</p></body></html>
\ No newline at end of file
diff --git a/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile.mediawiki b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile.mediawiki
new file mode 100644
index 00000000000..7f4c93cda50
--- /dev/null
+++ b/plugins/doc/org.eclipse.papyrus.uml.diagram.profile.doc/resource/users/whatIsAUmlProfile.mediawiki
@@ -0,0 +1,14 @@
+= What is a UML Profile =
+
+The purpose of this chapter is to provide the Papyrus users all the documentation needed in order to be able to use UML profiles. It includes the information for modeling and defining a profile using the Papyrus UML profile editor, but also the information for the usage of a profile within a user application model.
+
+The basic premise of profiles is that all domain-specific concepts are derived as extensions or refinements of existing UML concepts, called UML metaclasses. These extensions are called stereotypes. A stereotype definition must be consistent with the abstract syntax and semantics of standard UML meta-classes it extends. Consequently, a profile-based model can be created and manipulated by any tool that supports standard UML. Moreover, because the concepts underlying a profile are specializations of existing UML concepts, it is more easily learned by anyone with knowledge of UML.
+
+A stereotype is defined either as an extension of a UML base metaclass or as a specialization of an existing stereotype. The extension relationship of UML is not an association but a kind of association directed from the stereotype to the extended metaclass. Consequently, the metadata conveyed by the associated the attributes of the stereotype are associated to the extended metaclass in a transparent manner for the metaclass itself. This allows profiles owning the stereotypes to be applied and removed dynamically without modifying the underlying models — a fundamental feature of the profile mechanism.
+
+A stereotype may have attributes and may be associated with other stereotypes or existing UML metaclasses.
+
+Constraints, such as OCL constraints, can also be defined in a profile. They can apply to stereotypes defined in the profile or those imported by the profile. They can also be used to further constrain elements of the UML metamodel. For instance, one could define an OCL constraint that all instances of Class in a model are active, or that all instances of Class must have at least one Operation (regardless of whether the Class is extended by a stereotype or not). However, not all constraints can be written in OCL. In that case, it is common to denote those latter in natural language. The drawback is that such constraints are no more automatically interpretable and need to be first rewritten in some language the UML tool will understand. In the context of Papyrus, it is then usual to use Java.
+
+
+