This commit was manufactured by cvs2svn to create tag
'before_importing_DSDM_plug-in'.
diff --git a/Scrum French/.cvsignore b/Scrum French/.cvsignore
deleted file mode 100644
index b30de62..0000000
--- a/Scrum French/.cvsignore
+++ /dev/null
@@ -1,2 +0,0 @@
-.lock
-.project
diff --git a/Scrum French/Scrum/about.html b/Scrum French/Scrum/about.html
deleted file mode 100644
index 6040025..0000000
--- a/Scrum French/Scrum/about.html
+++ /dev/null
@@ -1,9 +0,0 @@
-
-<span style="font-weight: bold; font-family: Arial Narrow;">Claude Aubry</span><br/>
-<span style="font-weight: bold; color: rgb(255, 102, 0); font-family: Arial Narrow;">Consultant M&eacute;thodes Agiles</span><span style="font-family: Arial Narrow;">
-</span>
-<br/><small style="font-family: Arial Narrow;">
-<span style="color: rgb(102, 102, 102);">Mobile : 06 60 646 946</span>
-<br/>
-<a href="http://scrum.aubryconseil.com">Blog</a> -&nbsp;
-<a href="http://www.aubryconseil.com/">Web</a>
\ No newline at end of file
diff --git a/Scrum French/Scrum/customcategories/Intro.xmi b/Scrum French/Scrum/customcategories/Intro.xmi
deleted file mode 100644
index aa49ac4..0000000
--- a/Scrum French/Scrum/customcategories/Intro.xmi
+++ /dev/null
@@ -1,4 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-juIDa_fXi2K1BE5NTblPow" name="new_custom_category,_s8y1UABREdu3o4yroaI-tA" guid="-juIDa_fXi2K1BE5NTblPow" changeDate="2006-12-04T21:46:12.515+0100">
-  <mainDescription>Ce site décrit l'utilisation de Scrum</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/customcategories/Scrum Elements.xmi b/Scrum French/Scrum/customcategories/Scrum Elements.xmi
deleted file mode 100644
index 35e8dc5..0000000
--- a/Scrum French/Scrum/customcategories/Scrum Elements.xmi
+++ /dev/null
@@ -1,2 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmi:id="-zS9h38tmK4L-U9kbgkpGKQ" name="Eléments de Scrum,_nF6fgALYEduFv7wnrO7SvQ" guid="-zS9h38tmK4L-U9kbgkpGKQ" changeDate="2006-07-16T15:44:25.338+0200"/>
diff --git a/Scrum French/Scrum/deliveryprocesses/Scrum/content.xmi b/Scrum French/Scrum/deliveryprocesses/Scrum/content.xmi
deleted file mode 100644
index c97db24..0000000
--- a/Scrum French/Scrum/deliveryprocesses/Scrum/content.xmi
+++ /dev/null
@@ -1,83 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0">
-  <org.eclipse.epf.uma:DeliveryProcessDescription xmi:id="-16dzhVoCex78V2iCDZVx0w" name="Scrum,_9llsAQAvEdubGMceRDupFQ" guid="-16dzhVoCex78V2iCDZVx0w">
-    <mainDescription>La production d’une version du logiciel (&lt;a class=&quot;elementLink&quot;
-href=&quot;./../../Scrum/guidances/termdefinitions/Release,_AIB9gIHrEduFs9jH8xc4xw.html&quot;
-guid=&quot;_AIB9gIHrEduFs9jH8xc4xw&quot;&gt;Release&lt;/a&gt;) se fait en général en quelques mois. Les fonctionnalités demandées pour la
-release sont collectées dans le backlog de produit et classées par priorité. Le directeur de produit est responsable de
-l’insertion des changements dans ce backlog.&amp;nbsp; &lt;br /&gt;
-La release est produite par une série d’itérations de 2 à 4 semaines appelées des &lt;a class=&quot;elementLink&quot;
-href=&quot;./../../Scrum/guidances/termdefinitions/Sprint,_kftWoIHqEduFs9jH8xc4xw.html&quot;
-guid=&quot;_kftWoIHqEduFs9jH8xc4xw&quot;&gt;Sprint&lt;/a&gt;s. Le contenu d’un Sprint est défini par l’équipe avec le propriétaire de produit,
-en tenant compte des priorités et de la capacité de l’équipe. L’équipe définit les tâches nécessaires pour réaliser les
-fonctionnalités sélectionnées pour le Sprint.&amp;nbsp; &lt;br /&gt;
-Pendant un sprint, des points de contrôle sur l’avancement sont effectués lors des mêlées quotidiennes. Cela permet au
-ScrumMaster de déterminer l’avancement par rapport aux engagements du Sprint et de conseiller des ajustements pour assurer
-le succès du Sprint.&amp;nbsp; &lt;br /&gt;
-A la fin de chaque Sprint, l’équipe produit un &lt;a class=&quot;elementLink&quot;
-href=&quot;./../../Scrum/workproducts/Product increment,_tCmYEP-xEdqLnajTSLeAsA.html&quot; guid=&quot;_tCmYEP-xEdqLnajTSLeAsA&quot;&gt;Incrément
-de produit&lt;/a&gt;&amp;nbsp;potentiellement utilisable, dont l’évaluation permet d’ajuster le backlog pour le Sprint suivant.</mainDescription>
-    <keyConsiderations>&lt;p&gt;
-    Scrum contribue à renforcer l’esprit d’équipe dans les projets,&amp;nbsp; avec une collection de pratiques proches de
-    celles que l’on trouve dans des sports collectifs en particulier le rugby.
-&lt;/p&gt;
-&lt;br /&gt;
-&lt;br /&gt;</keyConsiderations>
-    <purpose>.</purpose>
-    <howtoStaff>Une équipe Scrum est composée de 3 à 10 personnes.</howtoStaff>
-    <scope>Scrum ne décrit pas toutes les disciplines du développement de logiciel (analyse, conception, codage, test) et doit être
-considéré, plutôt qu’un processus complet, comme un pattern de processus qui est à utiliser pour la gestion de projet et la
-gestion des exigences. &lt;br /&gt;
-Scrum ne fournit pas d’aide pour la réalisation des activités techniques du développement.</scope>
-    <estimatingTechnique>&lt;p&gt;
-    Il est conseillé de pratiquer une estimation basée sur les points (story points), associés aux éléments du backlog.
-&lt;/p&gt;</estimatingTechnique>
-  </org.eclipse.epf.uma:DeliveryProcessDescription>
-  <org.eclipse.epf.uma:ActivityDescription xmi:id="-WiMYK8iwLeOO-sSBRBjbNQ" name="Phase de préparation,_37TdkAL_EduOAKqB9I73uw" guid="-WiMYK8iwLeOO-sSBRBjbNQ">
-    <mainDescription>&lt;p&gt;
-    Scrum ne prend pas en compte tous les aspects de préparation d'un projet. Seules sont présentées les taches spécifiques
-    de Scrum plus une qui regroupe tous les travaux pouvant etre réalisés
-&lt;/p&gt;</mainDescription>
-  </org.eclipse.epf.uma:ActivityDescription>
-  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-EpBaHVCIYCqqGX_wv7dlYA" name="Travaux quotidiens,_nXmKUANlEduYd-55D-Aiqg" guid="-EpBaHVCIYCqqGX_wv7dlYA">
-    <refinedDescription>Scrum ne propose rien pour la réalisation de ces tâches techniques de conception, codage et test mais se conjugue bien avec
-l’utilisation des techniques XP (binômage, développement dirigé par les tests…). &lt;br /&gt;
-Les tâches ne sont pas assignées par le ScrumMaster mais choisies par les membres de l’équipe au fur et à mesure. &lt;br /&gt;
-L’équipe met à jour, chaque fois que c’est nécessaire, l’estimation du reste à faire sur les tâches du &lt;br /&gt;
-backlog du sprint.</refinedDescription>
-  </org.eclipse.epf.uma:DescriptorDescription>
-  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-EOwIzNPjfNIjzJ3TRAgeWQ" name="Sprint de release,_zbM2QIGBEduKE9hnyImx1Q" guid="-EOwIzNPjfNIjzJ3TRAgeWQ">
-    <keyConsiderations>Essayer de ne pas modifier de code lors du dernier sprint, c'est trop tard et risqué.</keyConsiderations>
-    <usageGuidance>Il est optionnel. Cela dépend de la façon dont le produit est mis à disposition de ses utilisateurs finals. On en devrait
-dérouler ce sprint optionnel que des travaux qu'il est impossible de faire avant, dans les sprints &quot;normaux&quot;.</usageGuidance>
-    <refinedDescription>&lt;p&gt;
-    Les tâches effectuées pendant ce sprint dépendent fortement du type de déploiement du logiciel.
-&lt;/p&gt;
-&lt;p&gt;
-    On peut y trouver des travaux portant sur :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        mise en production à chaud,
-    &lt;/li&gt;
-    &lt;li&gt;
-        packaging du produit,
-    &lt;/li&gt;
-    &lt;li&gt;
-        mise à disposition par téléchargement en ligne,
-    &lt;/li&gt;
-    &lt;li&gt;
-        documentation technique,
-    &lt;/li&gt;
-    &lt;li&gt;
-        formation des utilisateurs,
-    &lt;/li&gt;
-    &lt;li&gt;
-        marketing du produit.
-    &lt;/li&gt;
-&lt;/ul&gt;</refinedDescription>
-  </org.eclipse.epf.uma:DescriptorDescription>
-  <org.eclipse.epf.uma:DescriptorDescription xmi:id="-MupkaQeHNEmiF7Lnl3VirQ" name="Sprint backlog,_glbG2wMAEduOAKqB9I73uw" guid="-MupkaQeHNEmiF7Lnl3VirQ">
-    <usageGuidance>Un par sprint</usageGuidance>
-  </org.eclipse.epf.uma:DescriptorDescription>
-</xmi:XMI>
diff --git a/Scrum French/Scrum/deliveryprocesses/Scrum/model.xmi b/Scrum French/Scrum/deliveryprocesses/Scrum/model.xmi
deleted file mode 100644
index eafcf7c..0000000
--- a/Scrum French/Scrum/deliveryprocesses/Scrum/model.xmi
+++ /dev/null
@@ -1,982 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore" epf:version="1.0.0">
-  <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_9m1CIAAvEdubGMceRDupFQ" guid="_9m1CIAAvEdubGMceRDupFQ">
-    <resourceDescriptors xmi:id="_9m1CIQAvEdubGMceRDupFQ" id="-16dzhVoCex78V2iCDZVx0w" uri="content.xmi"/>
-    <resourceDescriptors xmi:id="_-d2LQQMEEduOAKqB9I73uw" id="-WiMYK8iwLeOO-sSBRBjbNQ" uri="content.xmi"/>
-    <resourceDescriptors xmi:id="_8N5DwANlEduYd-55D-Aiqg" id="-EpBaHVCIYCqqGX_wv7dlYA" uri="content.xmi"/>
-    <resourceDescriptors xmi:id="_iCOP4IGPEduKE9hnyImx1Q" id="-EOwIzNPjfNIjzJ3TRAgeWQ" uri="content.xmi"/>
-    <resourceDescriptors xmi:id="_tObbkLPBEduk5O8SjA21Fg" id="-MupkaQeHNEmiF7Lnl3VirQ" uri="content.xmi"/>
-  </org.eclipse.epf.uma.resourcemanager:ResourceManager>
-  <org.eclipse.epf.uma:ProcessComponent xmi:id="_9llsAAAvEdubGMceRDupFQ" name="Scrum" guid="_9llsAAAvEdubGMceRDupFQ">
-    <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_37NW8AL_EduOAKqB9I73uw" name="Preparation Phase" guid="_37NW8AL_EduOAKqB9I73uw">
-      <processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_37TdkAL_EduOAKqB9I73uw" name="Preparation Phase" guid="_37TdkAL_EduOAKqB9I73uw" briefDescription="Cette phase initiale permet de préparer tout ce qui est nécessaire avant de commencer la série des sprints" presentationName="Phase de préparation" isOptional="true" superActivities="_9llsAQAvEdubGMceRDupFQ" breakdownElements="_zYT-EQMAEduOAKqB9I73uw _zYaEsAMAEduOAKqB9I73uw _zYaEsgMAEduOAKqB9I73uw _zYaEswMAEduOAKqB9I73uw _zYaEtAMAEduOAKqB9I73uw _7FGsMANkEduYd-55D-Aiqg _7FGsMQNkEduYd-55D-Aiqg _O6XmcANlEduYd-55D-Aiqg">
-        <presentation xmi:id="-WiMYK8iwLeOO-sSBRBjbNQ" href="uma://-16dzhVoCex78V2iCDZVx0w#-WiMYK8iwLeOO-sSBRBjbNQ"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_zYT-EQMAEduOAKqB9I73uw" name="Plan release" guid="_zYT-EQMAEduOAKqB9I73uw" presentationName="Planifier la release" superActivities="_37TdkAL_EduOAKqB9I73uw" linkToPredecessor="_2vOSsAMEEduOAKqB9I73uw _MEJPgAPOEdubhrgDuRb4fA _MEPWIAPOEdubhrgDuRb4fA" additionallyPerformedBy="_zYaEswMAEduOAKqB9I73uw _zYaEsgMAEduOAKqB9I73uw" mandatoryInput="_zYaEtAMAEduOAKqB9I73uw" output="_zYaEtAMAEduOAKqB9I73uw" performedPrimarilyBy="_zYaEsAMAEduOAKqB9I73uw">
-        <Task href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_ho-aIP_BEdqtbrr0B1TG-A"/>
-        <selectedSteps href="uma://-3f4axrWBKHGv74oKN2x-gQ#_8qN08APJEdubhrgDuRb4fA"/>
-        <selectedSteps href="uma://-3f4axrWBKHGv74oKN2x-gQ#_BuXEQAPKEdubhrgDuRb4fA"/>
-        <selectedSteps href="uma://-3f4axrWBKHGv74oKN2x-gQ#_EaLKQAPKEdubhrgDuRb4fA"/>
-        <selectedSteps href="uma://-3f4axrWBKHGv74oKN2x-gQ#_HDZ2UAPKEdubhrgDuRb4fA"/>
-        <selectedSteps href="uma://-3f4axrWBKHGv74oKN2x-gQ#_I71XkAPKEdubhrgDuRb4fA"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_zYaEsAMAEduOAKqB9I73uw" name="Product Owner" guid="_zYaEsAMAEduOAKqB9I73uw" presentationName="Directeur Produit" superActivities="_37TdkAL_EduOAKqB9I73uw" responsibleFor="_zYaEtAMAEduOAKqB9I73uw">
-        <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_ICJyYPpaEdqsc-f87sBK8A"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_zYaEsgMAEduOAKqB9I73uw" name="Team" guid="_zYaEsgMAEduOAKqB9I73uw" presentationName="Equipe Scrum" hasMultipleOccurrences="true" superActivities="_37TdkAL_EduOAKqB9I73uw">
-        <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_9apLsPpaEdqsc-f87sBK8A"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_zYaEswMAEduOAKqB9I73uw" name="ScrumMaster" guid="_zYaEswMAEduOAKqB9I73uw" presentationName="ScrumMaster" superActivities="_37TdkAL_EduOAKqB9I73uw">
-        <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_t1K9kPpYEdqsc-f87sBK8A"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_zYaEtAMAEduOAKqB9I73uw" name="Product Backlog" guid="_zYaEtAMAEduOAKqB9I73uw" presentationName="Backlog de produit" superActivities="_37TdkAL_EduOAKqB9I73uw">
-        <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_5ABscPpYEdqsc-f87sBK8A"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_2vOSsAMEEduOAKqB9I73uw" guid="_2vOSsAMEEduOAKqB9I73uw" linkType="finishToFinish"/>
-      <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_7FGsMANkEduYd-55D-Aiqg" name="Initiate Product Backlog" guid="_7FGsMANkEduYd-55D-Aiqg" presentationName="Produire le backlog de produit initial" superActivities="_37TdkAL_EduOAKqB9I73uw" additionallyPerformedBy="_7FGsMQNkEduYd-55D-Aiqg _zYaEsgMAEduOAKqB9I73uw" output="_zYaEtAMAEduOAKqB9I73uw" performedPrimarilyBy="_zYaEsAMAEduOAKqB9I73uw">
-        <Task href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_BGFMoANkEduYd-55D-Aiqg"/>
-        <selectedSteps href="uma://-mi1O4H7RRm0YqlUNyp8TJg#_pWL_gAPJEdubhrgDuRb4fA"/>
-        <selectedSteps href="uma://-mi1O4H7RRm0YqlUNyp8TJg#_u0Z7sAPJEdubhrgDuRb4fA"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_7FGsMQNkEduYd-55D-Aiqg" name="StakeHolder" guid="_7FGsMQNkEduYd-55D-Aiqg" presentationName="Intervenant" isPlanned="false" hasMultipleOccurrences="true" superActivities="_37TdkAL_EduOAKqB9I73uw">
-        <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_Qqmp8P_AEdqtbrr0B1TG-A"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_O6XmcANlEduYd-55D-Aiqg" name="Preparation work" guid="_O6XmcANlEduYd-55D-Aiqg" presentationName="Travaux de préparation" isPlanned="true" hasMultipleOccurrences="true" superActivities="_37TdkAL_EduOAKqB9I73uw" performedPrimarilyBy="_zYaEsgMAEduOAKqB9I73uw"/>
-      <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_MEJPgAPOEdubhrgDuRb4fA" guid="_MEJPgAPOEdubhrgDuRb4fA" linkType="finishToFinish" pred="_7FGsMANkEduYd-55D-Aiqg"/>
-      <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_MEPWIAPOEdubhrgDuRb4fA" guid="_MEPWIAPOEdubhrgDuRb4fA" linkType="finishToFinish" pred="_O6XmcANlEduYd-55D-Aiqg"/>
-      <diagrams xmi:id="_y9sh0AMEEduOAKqB9I73uw" guid="_y9sh0AMEEduOAKqB9I73uw">
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_y9yocAMEEduOAKqB9I73uw" guid="_y9yocAMEEduOAKqB9I73uw">
-          <position xmi:id="_y9yocQMEEduOAKqB9I73uw" x="84.0" y="34.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_2vIMEQMEEduOAKqB9I73uw" guid="_2vIMEQMEEduOAKqB9I73uw" anchor="_2vIMEAMEEduOAKqB9I73uw _2vIMEgMEEduOAKqB9I73uw">
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vOSsQMEEduOAKqB9I73uw" guid="_2vOSsQMEEduOAKqB9I73uw"/>
-          </contained>
-          <anchorage xmi:id="_2QAAEgMEEduOAKqB9I73uw" guid="_2QAAEgMEEduOAKqB9I73uw" graphEdge="_2QAAEQMEEduOAKqB9I73uw"/>
-          <anchorage xmi:id="_2vIMEAMEEduOAKqB9I73uw" guid="_2vIMEAMEEduOAKqB9I73uw" graphEdge="_2vIMEQMEEduOAKqB9I73uw">
-            <position xmi:id="_2vIMEwMEEduOAKqB9I73uw" x="155.0" y="50.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_y9yocgMEEduOAKqB9I73uw" guid="_y9yocgMEEduOAKqB9I73uw"/>
-          <size xmi:id="_y9yocwMEEduOAKqB9I73uw" width="130.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_y9yodAMEEduOAKqB9I73uw" guid="_y9yodAMEEduOAKqB9I73uw">
-          <position xmi:id="_y9yodQMEEduOAKqB9I73uw" x="158.0" y="214.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_nqi5YYGGEduKE9hnyImx1Q" guid="_nqi5YYGGEduKE9hnyImx1Q" anchor="_nqi5YIGGEduKE9hnyImx1Q _nqi5YoGGEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_2vIMEgMEEduOAKqB9I73uw" guid="_2vIMEgMEEduOAKqB9I73uw" graphEdge="_2vIMEQMEEduOAKqB9I73uw"/>
-          <anchorage xmi:id="_MEDI4gPOEdubhrgDuRb4fA" guid="_MEDI4gPOEdubhrgDuRb4fA" graphEdge="_MEDI4QPOEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_nqi5YIGGEduKE9hnyImx1Q" guid="_nqi5YIGGEduKE9hnyImx1Q" graphEdge="_nqi5YYGGEduKE9hnyImx1Q">
-            <position xmi:id="_nqi5Y4GGEduKE9hnyImx1Q" x="171.0" y="228.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_y9yodgMEEduOAKqB9I73uw" guid="_y9yodgMEEduOAKqB9I73uw" element="_zYT-EQMAEduOAKqB9I73uw"/>
-          <size xmi:id="_y9yodwMEEduOAKqB9I73uw" width="88.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_03XZMAMEEduOAKqB9I73uw" guid="_03XZMAMEEduOAKqB9I73uw">
-          <position xmi:id="_03XZMQMEEduOAKqB9I73uw" x="187.0" y="-6.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_2QAAEQMEEduOAKqB9I73uw" guid="_2QAAEQMEEduOAKqB9I73uw" anchor="_2QAAEAMEEduOAKqB9I73uw _2QAAEgMEEduOAKqB9I73uw"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_-h0qsQNkEduYd-55D-Aiqg" guid="_-h0qsQNkEduYd-55D-Aiqg" anchor="_-h0qsANkEduYd-55D-Aiqg _-h0qsgNkEduYd-55D-Aiqg"/>
-          <anchorage xmi:id="_2QAAEAMEEduOAKqB9I73uw" guid="_2QAAEAMEEduOAKqB9I73uw" graphEdge="_2QAAEQMEEduOAKqB9I73uw">
-            <position xmi:id="_2QAAEwMEEduOAKqB9I73uw" x="58.0" y="51.0"/>
-          </anchorage>
-          <anchorage xmi:id="_-h0qsANkEduYd-55D-Aiqg" guid="_-h0qsANkEduYd-55D-Aiqg" graphEdge="_-h0qsQNkEduYd-55D-Aiqg">
-            <position xmi:id="_-h6xUANkEduYd-55D-Aiqg" x="62.0" y="51.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_03XZMgMEEduOAKqB9I73uw" guid="_03XZMgMEEduOAKqB9I73uw" typeInfo="start node"/>
-          <size xmi:id="_03XZMwMEEduOAKqB9I73uw" width="20.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_8cZ2UANkEduYd-55D-Aiqg" guid="_8cZ2UANkEduYd-55D-Aiqg">
-          <position xmi:id="_8cZ2UQNkEduYd-55D-Aiqg" x="14.0" y="94.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_LDfDwQPOEdubhrgDuRb4fA" guid="_LDfDwQPOEdubhrgDuRb4fA" anchor="_LDfDwAPOEdubhrgDuRb4fA _LDfDwgPOEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_4JEBIgPNEdubhrgDuRb4fA" guid="_4JEBIgPNEdubhrgDuRb4fA" graphEdge="_4JEBIQPNEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_LDfDwAPOEdubhrgDuRb4fA" guid="_LDfDwAPOEdubhrgDuRb4fA" graphEdge="_LDfDwQPOEdubhrgDuRb4fA">
-            <position xmi:id="_LDfDwwPOEdubhrgDuRb4fA" x="114.0" y="145.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_8cZ2UgNkEduYd-55D-Aiqg" guid="_8cZ2UgNkEduYd-55D-Aiqg" element="_7FGsMANkEduYd-55D-Aiqg"/>
-          <size xmi:id="_8cZ2UwNkEduYd-55D-Aiqg" width="168.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_n_DhAANnEduYd-55D-Aiqg" guid="_n_DhAANnEduYd-55D-Aiqg">
-          <position xmi:id="_n_DhAQNnEduYd-55D-Aiqg" x="255.0" y="90.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_LgIjgQPOEdubhrgDuRb4fA" guid="_LgIjgQPOEdubhrgDuRb4fA" anchor="_LgIjgAPOEdubhrgDuRb4fA _LgIjggPOEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_114dkgPNEdubhrgDuRb4fA" guid="_114dkgPNEdubhrgDuRb4fA" graphEdge="_114dkQPNEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_LgIjgAPOEdubhrgDuRb4fA" guid="_LgIjgAPOEdubhrgDuRb4fA" graphEdge="_LgIjgQPOEdubhrgDuRb4fA">
-            <position xmi:id="_LgIjgwPOEdubhrgDuRb4fA" x="282.0" y="140.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_n_DhAgNnEduYd-55D-Aiqg" guid="_n_DhAgNnEduYd-55D-Aiqg" element="_O6XmcANlEduYd-55D-Aiqg"/>
-          <size xmi:id="_n_DhAwNnEduYd-55D-Aiqg" width="113.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_nITO0APNEdubhrgDuRb4fA" guid="_nITO0APNEdubhrgDuRb4fA">
-          <position xmi:id="_nITO0QPNEdubhrgDuRb4fA" x="162.0" y="55.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_114dkQPNEdubhrgDuRb4fA" guid="_114dkQPNEdubhrgDuRb4fA" anchor="_114dkAPNEdubhrgDuRb4fA _114dkgPNEdubhrgDuRb4fA"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_4JEBIQPNEdubhrgDuRb4fA" guid="_4JEBIQPNEdubhrgDuRb4fA" anchor="_4JEBIAPNEdubhrgDuRb4fA _4JEBIgPNEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_-h0qsgNkEduYd-55D-Aiqg" guid="_-h0qsgNkEduYd-55D-Aiqg" graphEdge="_-h0qsQNkEduYd-55D-Aiqg">
-            <position xmi:id="_Ip2OIFGGEduRlKB2-_Ejlg" x="36.0" y="5.0"/>
-          </anchorage>
-          <anchorage xmi:id="_114dkAPNEdubhrgDuRb4fA" guid="_114dkAPNEdubhrgDuRb4fA" graphEdge="_114dkQPNEdubhrgDuRb4fA">
-            <position xmi:id="_114dkwPNEdubhrgDuRb4fA" x="67.0" y="0.0"/>
-          </anchorage>
-          <anchorage xmi:id="_4JEBIAPNEdubhrgDuRb4fA" guid="_4JEBIAPNEdubhrgDuRb4fA" graphEdge="_4JEBIQPNEdubhrgDuRb4fA">
-            <position xmi:id="_HPd_kAPOEdubhrgDuRb4fA" x="17.0" y="0.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_nITO0gPNEdubhrgDuRb4fA" guid="_nITO0gPNEdubhrgDuRb4fA" typeInfo="synchnonization bar"/>
-          <size xmi:id="_nITO0wPNEdubhrgDuRb4fA" width="81.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_J5FtMAPOEdubhrgDuRb4fA" guid="_J5FtMAPOEdubhrgDuRb4fA">
-          <position xmi:id="_J5FtMQPOEdubhrgDuRb4fA" x="152.0" y="171.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_MEDI4QPOEdubhrgDuRb4fA" guid="_MEDI4QPOEdubhrgDuRb4fA" anchor="_MEDI4APOEdubhrgDuRb4fA _MEDI4gPOEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_LDfDwgPOEdubhrgDuRb4fA" guid="_LDfDwgPOEdubhrgDuRb4fA" graphEdge="_LDfDwQPOEdubhrgDuRb4fA">
-            <position xmi:id="_LDfDxAPOEdubhrgDuRb4fA" x="42.0" y="0.0"/>
-          </anchorage>
-          <anchorage xmi:id="_LgIjggPOEdubhrgDuRb4fA" guid="_LgIjggPOEdubhrgDuRb4fA" graphEdge="_LgIjgQPOEdubhrgDuRb4fA">
-            <position xmi:id="_LgIjhAPOEdubhrgDuRb4fA" x="54.0" y="0.0"/>
-          </anchorage>
-          <anchorage xmi:id="_MEDI4APOEdubhrgDuRb4fA" guid="_MEDI4APOEdubhrgDuRb4fA" graphEdge="_MEDI4QPOEdubhrgDuRb4fA">
-            <position xmi:id="_MJgy8FGGEduRlKB2-_Ejlg" x="49.0" y="0.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_J5FtMgPOEdubhrgDuRb4fA" guid="_J5FtMgPOEdubhrgDuRb4fA" typeInfo="synchnonization bar"/>
-          <size xmi:id="_J5FtMwPOEdubhrgDuRb4fA" width="100.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_mMXrMIGGEduKE9hnyImx1Q" guid="_mMXrMIGGEduKE9hnyImx1Q">
-          <position xmi:id="_mMXrMYGGEduKE9hnyImx1Q" x="190.0" y="282.0"/>
-          <anchorage xmi:id="_nqi5YoGGEduKE9hnyImx1Q" guid="_nqi5YoGGEduKE9hnyImx1Q" graphEdge="_nqi5YYGGEduKE9hnyImx1Q"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_mMXrMoGGEduKE9hnyImx1Q" guid="_mMXrMoGGEduKE9hnyImx1Q" typeInfo="end node"/>
-          <size xmi:id="_mMXrM4GGEduKE9hnyImx1Q" width="24.0" height="-1.0"/>
-        </contained>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_y9sh0QMEEduOAKqB9I73uw" guid="_y9sh0QMEEduOAKqB9I73uw" presentation="Workflow" element="_37TdkAL_EduOAKqB9I73uw"/>
-      </diagrams>
-      <diagrams xmi:id="_jcymYAPNEdubhrgDuRb4fA" guid="_jcymYAPNEdubhrgDuRb4fA">
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jcymYQPNEdubhrgDuRb4fA" guid="_jcymYQPNEdubhrgDuRb4fA">
-          <position xmi:id="_jcymYgPNEdubhrgDuRb4fA" x="-1.0" y="-1.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5oznBIGMEduKE9hnyImx1Q" guid="_5oznBIGMEduKE9hnyImx1Q" anchor="_5oznA4GMEduKE9hnyImx1Q _5oznBYGMEduKE9hnyImx1Q"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5uBeNIGMEduKE9hnyImx1Q" guid="_5uBeNIGMEduKE9hnyImx1Q" anchor="_5uBeM4GMEduKE9hnyImx1Q _5uBeNYGMEduKE9hnyImx1Q"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_03qQxLKjEdudsfcMCYa15A" guid="_03qQxLKjEdudsfcMCYa15A" anchor="_03qQw7KjEdudsfcMCYa15A _03qQxbKjEdudsfcMCYa15A"/>
-          <anchorage xmi:id="_5oznAoGMEduKE9hnyImx1Q" guid="_5oznAoGMEduKE9hnyImx1Q" graphEdge="_5oznAYGMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_5oznA4GMEduKE9hnyImx1Q" guid="_5oznA4GMEduKE9hnyImx1Q" graphEdge="_5oznBIGMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_5uBeMoGMEduKE9hnyImx1Q" guid="_5uBeMoGMEduKE9hnyImx1Q" graphEdge="_5uBeMYGMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_5uBeM4GMEduKE9hnyImx1Q" guid="_5uBeM4GMEduKE9hnyImx1Q" graphEdge="_5uBeNIGMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_03qQwrKjEdudsfcMCYa15A" guid="_03qQwrKjEdudsfcMCYa15A" graphEdge="_03qQwbKjEdudsfcMCYa15A"/>
-          <anchorage xmi:id="_03qQw7KjEdudsfcMCYa15A" guid="_03qQw7KjEdudsfcMCYa15A" graphEdge="_03qQxLKjEdudsfcMCYa15A"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymYwPNEdubhrgDuRb4fA" guid="_jcymYwPNEdubhrgDuRb4fA" element="_zYT-EQMAEduOAKqB9I73uw"/>
-          <size xmi:id="_jcymZAPNEdubhrgDuRb4fA" width="-1.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jcymZQPNEdubhrgDuRb4fA" guid="_jcymZQPNEdubhrgDuRb4fA">
-          <position xmi:id="_jcymZgPNEdubhrgDuRb4fA" x="30.0" y="88.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymZwPNEdubhrgDuRb4fA" guid="_jcymZwPNEdubhrgDuRb4fA" element="_zYaEsAMAEduOAKqB9I73uw"/>
-          <size xmi:id="_jcymaAPNEdubhrgDuRb4fA" width="316.0" height="67.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jcymaQPNEdubhrgDuRb4fA" guid="_jcymaQPNEdubhrgDuRb4fA">
-          <position xmi:id="_jcymagPNEdubhrgDuRb4fA" x="30.0" y="283.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymawPNEdubhrgDuRb4fA" guid="_jcymawPNEdubhrgDuRb4fA" element="_zYaEsgMAEduOAKqB9I73uw"/>
-          <size xmi:id="_jcymbAPNEdubhrgDuRb4fA" width="239.0" height="53.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jcymbQPNEdubhrgDuRb4fA" guid="_jcymbQPNEdubhrgDuRb4fA">
-          <position xmi:id="_jcymbgPNEdubhrgDuRb4fA" x="-1.0" y="-1.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymbwPNEdubhrgDuRb4fA" guid="_jcymbwPNEdubhrgDuRb4fA" element="_zYaEswMAEduOAKqB9I73uw"/>
-          <size xmi:id="_jcymcAPNEdubhrgDuRb4fA" width="-1.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jcymcQPNEdubhrgDuRb4fA" guid="_jcymcQPNEdubhrgDuRb4fA">
-          <position xmi:id="_jcymcgPNEdubhrgDuRb4fA" x="-1.0" y="-1.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymcwPNEdubhrgDuRb4fA" guid="_jcymcwPNEdubhrgDuRb4fA" element="_zYaEtAMAEduOAKqB9I73uw"/>
-          <size xmi:id="_jcymdAPNEdubhrgDuRb4fA" width="-1.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jcymdQPNEdubhrgDuRb4fA" guid="_jcymdQPNEdubhrgDuRb4fA">
-          <position xmi:id="_jcymdgPNEdubhrgDuRb4fA" x="-1.0" y="-1.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5oznB4GMEduKE9hnyImx1Q" guid="_5oznB4GMEduKE9hnyImx1Q" anchor="_5oznBoGMEduKE9hnyImx1Q _5oznCIGMEduKE9hnyImx1Q"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5uBeN4GMEduKE9hnyImx1Q" guid="_5uBeN4GMEduKE9hnyImx1Q" anchor="_5uBeNoGMEduKE9hnyImx1Q _5uBeOIGMEduKE9hnyImx1Q"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_03qQx7KjEdudsfcMCYa15A" guid="_03qQx7KjEdudsfcMCYa15A" anchor="_03qQxrKjEdudsfcMCYa15A _03qQyLKjEdudsfcMCYa15A"/>
-          <anchorage xmi:id="_5oznBoGMEduKE9hnyImx1Q" guid="_5oznBoGMEduKE9hnyImx1Q" graphEdge="_5oznB4GMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_5uBeNoGMEduKE9hnyImx1Q" guid="_5uBeNoGMEduKE9hnyImx1Q" graphEdge="_5uBeN4GMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_03qQxrKjEdudsfcMCYa15A" guid="_03qQxrKjEdudsfcMCYa15A" graphEdge="_03qQx7KjEdudsfcMCYa15A"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymdwPNEdubhrgDuRb4fA" guid="_jcymdwPNEdubhrgDuRb4fA" element="_7FGsMANkEduYd-55D-Aiqg"/>
-          <size xmi:id="_jcymeAPNEdubhrgDuRb4fA" width="-1.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jcymeQPNEdubhrgDuRb4fA" guid="_jcymeQPNEdubhrgDuRb4fA">
-          <position xmi:id="_jcymegPNEdubhrgDuRb4fA" x="-1.0" y="-1.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymewPNEdubhrgDuRb4fA" guid="_jcymewPNEdubhrgDuRb4fA" element="_7FGsMQNkEduYd-55D-Aiqg"/>
-          <size xmi:id="_jcymfAPNEdubhrgDuRb4fA" width="-1.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jcymfQPNEdubhrgDuRb4fA" guid="_jcymfQPNEdubhrgDuRb4fA">
-          <position xmi:id="_jcymfgPNEdubhrgDuRb4fA" x="-1.0" y="-1.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymfwPNEdubhrgDuRb4fA" guid="_jcymfwPNEdubhrgDuRb4fA" element="_O6XmcANlEduYd-55D-Aiqg"/>
-          <size xmi:id="_jcymgAPNEdubhrgDuRb4fA" width="-1.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jdE6QAPNEdubhrgDuRb4fA" guid="_jdE6QAPNEdubhrgDuRb4fA">
-          <property xmi:id="_jdE6QQPNEdubhrgDuRb4fA" guid="_jdE6QQPNEdubhrgDuRb4fA" key="wpCompositeType" value="1"/>
-          <position xmi:id="_jdE6QgPNEdubhrgDuRb4fA" x="127.0" y="1.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_jdRHgQPNEdubhrgDuRb4fA" guid="_jdRHgQPNEdubhrgDuRb4fA" anchor="_jdRHgAPNEdubhrgDuRb4fA"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_8P1cgRTUEduFIr9xNbwGyQ" guid="_8P1cgRTUEduFIr9xNbwGyQ" anchor="_8P1cgBTUEduFIr9xNbwGyQ"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5oznAYGMEduKE9hnyImx1Q" guid="_5oznAYGMEduKE9hnyImx1Q" anchor="_5oznAIGMEduKE9hnyImx1Q _5oznAoGMEduKE9hnyImx1Q"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5uBeMYGMEduKE9hnyImx1Q" guid="_5uBeMYGMEduKE9hnyImx1Q" anchor="_5uBeMIGMEduKE9hnyImx1Q _5uBeMoGMEduKE9hnyImx1Q"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_03qQwbKjEdudsfcMCYa15A" guid="_03qQwbKjEdudsfcMCYa15A" anchor="_03qQwLKjEdudsfcMCYa15A _03qQwrKjEdudsfcMCYa15A"/>
-          <anchorage xmi:id="_jdRHgAPNEdubhrgDuRb4fA" guid="_jdRHgAPNEdubhrgDuRb4fA" graphEdge="_jdRHgQPNEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_8P1cgBTUEduFIr9xNbwGyQ" guid="_8P1cgBTUEduFIr9xNbwGyQ" graphEdge="_8P1cgRTUEduFIr9xNbwGyQ"/>
-          <anchorage xmi:id="_5oznAIGMEduKE9hnyImx1Q" guid="_5oznAIGMEduKE9hnyImx1Q" graphEdge="_5oznAYGMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_5uBeMIGMEduKE9hnyImx1Q" guid="_5uBeMIGMEduKE9hnyImx1Q" graphEdge="_5uBeMYGMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_03qQwLKjEdudsfcMCYa15A" guid="_03qQwLKjEdudsfcMCYa15A" graphEdge="_03qQwbKjEdudsfcMCYa15A"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jdE6QwPNEdubhrgDuRb4fA" guid="_jdE6QwPNEdubhrgDuRb4fA" element="_zYT-EQMAEduOAKqB9I73uw"/>
-          <size xmi:id="_jdE6RAPNEdubhrgDuRb4fA" width="78.0" height="67.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jdE6RQPNEdubhrgDuRb4fA" guid="_jdE6RQPNEdubhrgDuRb4fA">
-          <property xmi:id="_jdE6RgPNEdubhrgDuRb4fA" guid="_jdE6RgPNEdubhrgDuRb4fA" key="wpCompositeType" value="2"/>
-          <position xmi:id="_jdE6RwPNEdubhrgDuRb4fA" x="127.0" y="175.0"/>
-          <anchorage xmi:id="_jdRHggPNEdubhrgDuRb4fA" guid="_jdRHggPNEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_8P1cghTUEduFIr9xNbwGyQ" guid="_8P1cghTUEduFIr9xNbwGyQ"/>
-          <anchorage xmi:id="_5oznBYGMEduKE9hnyImx1Q" guid="_5oznBYGMEduKE9hnyImx1Q" graphEdge="_5oznBIGMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_5uBeNYGMEduKE9hnyImx1Q" guid="_5uBeNYGMEduKE9hnyImx1Q" graphEdge="_5uBeNIGMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_03qQxbKjEdudsfcMCYa15A" guid="_03qQxbKjEdudsfcMCYa15A" graphEdge="_03qQxLKjEdudsfcMCYa15A"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jdE6SAPNEdubhrgDuRb4fA" guid="_jdE6SAPNEdubhrgDuRb4fA" element="_zYT-EQMAEduOAKqB9I73uw"/>
-          <size xmi:id="_jdE6SQPNEdubhrgDuRb4fA" width="78.0" height="67.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_jdLA4APNEdubhrgDuRb4fA" guid="_jdLA4APNEdubhrgDuRb4fA">
-          <property xmi:id="_jdLA4QPNEdubhrgDuRb4fA" guid="_jdLA4QPNEdubhrgDuRb4fA" key="wpCompositeType" value="2"/>
-          <position xmi:id="_jdLA4gPNEdubhrgDuRb4fA" x="220.0" y="175.0"/>
-          <anchorage xmi:id="_jdRHgwPNEdubhrgDuRb4fA" guid="_jdRHgwPNEdubhrgDuRb4fA"/>
-          <anchorage xmi:id="_8P1cgxTUEduFIr9xNbwGyQ" guid="_8P1cgxTUEduFIr9xNbwGyQ"/>
-          <anchorage xmi:id="_5oznCIGMEduKE9hnyImx1Q" guid="_5oznCIGMEduKE9hnyImx1Q" graphEdge="_5oznB4GMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_5uBeOIGMEduKE9hnyImx1Q" guid="_5uBeOIGMEduKE9hnyImx1Q" graphEdge="_5uBeN4GMEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_03qQyLKjEdudsfcMCYa15A" guid="_03qQyLKjEdudsfcMCYa15A" graphEdge="_03qQx7KjEdudsfcMCYa15A"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jdLA4wPNEdubhrgDuRb4fA" guid="_jdLA4wPNEdubhrgDuRb4fA" element="_7FGsMANkEduYd-55D-Aiqg"/>
-          <size xmi:id="_jdLA5APNEdubhrgDuRb4fA" width="78.0" height="67.0"/>
-        </contained>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_jcymgQPNEdubhrgDuRb4fA" guid="_jcymgQPNEdubhrgDuRb4fA" presentation="Activity Detail" element="_37TdkAL_EduOAKqB9I73uw"/>
-      </diagrams>
-    </childPackages>
-    <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_NSW6sAMAEduOAKqB9I73uw" name="Sprint Phase" guid="_NSW6sAMAEduOAKqB9I73uw">
-      <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_SoXWEAMAEduOAKqB9I73uw" name="Sprint (n)" guid="_SoXWEAMAEduOAKqB9I73uw">
-        <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_SoXWEQMAEduOAKqB9I73uw" name="Sprint (n)" guid="_SoXWEQMAEduOAKqB9I73uw" briefDescription="Déroulement d'un sprint (itération)" presentationName="Sprint" isPlanned="false" superActivities="_NSW6sQMAEduOAKqB9I73uw" isRepeatable="true" breakdownElements="_glbG0AMAEduOAKqB9I73uw _glbG0QMAEduOAKqB9I73uw _glbG0wMAEduOAKqB9I73uw _glbG1AMAEduOAKqB9I73uw _glbG1QMAEduOAKqB9I73uw _glbG1gMAEduOAKqB9I73uw _glbG1wMAEduOAKqB9I73uw _glbG2AMAEduOAKqB9I73uw _glbG2QMAEduOAKqB9I73uw _glbG2gMAEduOAKqB9I73uw _glbG2wMAEduOAKqB9I73uw _glbG3AMAEduOAKqB9I73uw _glbG3QMAEduOAKqB9I73uw _nXmKUANlEduYd-55D-Aiqg"/>
-        <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_glbG0AMAEduOAKqB9I73uw" name="Manage problems" guid="_glbG0AMAEduOAKqB9I73uw" presentationName="Gérer les problèmes" superActivities="_SoXWEQMAEduOAKqB9I73uw" isOngoing="true" optionalInput="_glbG2wMAEduOAKqB9I73uw" output="_glbG2wMAEduOAKqB9I73uw" performedPrimarilyBy="_glbG1wMAEduOAKqB9I73uw">
-          <Task href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_Xpd5gP_AEdqtbrr0B1TG-A"/>
-          <selectedSteps href="uma://-mZfAV7RcWJlp5idlHzeEcA#_LCxqQAB6EduSVaTQTBfIHA"/>
-          <selectedSteps href="uma://-mZfAV7RcWJlp5idlHzeEcA#_PIKyUAB6EduSVaTQTBfIHA"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_glbG0QMAEduOAKqB9I73uw" name="Update product backlog" guid="_glbG0QMAEduOAKqB9I73uw" presentationName="Mettre à jour le backlog de produit" superActivities="_SoXWEQMAEduOAKqB9I73uw" isOngoing="true" additionallyPerformedBy="_glbG2QMAEduOAKqB9I73uw _glbG2gMAEduOAKqB9I73uw" mandatoryInput="_glbG3AMAEduOAKqB9I73uw" output="_glbG3AMAEduOAKqB9I73uw" performedPrimarilyBy="_glbG2AMAEduOAKqB9I73uw">
-          <Task href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_STkWYP_BEdqtbrr0B1TG-A"/>
-          <selectedSteps href="uma://-XdgedeazfFRGDxMY3Fnh5g#_c3HaQAPKEdubhrgDuRb4fA"/>
-          <selectedSteps href="uma://-XdgedeazfFRGDxMY3Fnh5g#_fkXDoAPKEdubhrgDuRb4fA"/>
-          <selectedSteps href="uma://-XdgedeazfFRGDxMY3Fnh5g#_k-kCgAPKEdubhrgDuRb4fA"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_glbG0wMAEduOAKqB9I73uw" name="Plan sprint" guid="_glbG0wMAEduOAKqB9I73uw" presentationName="Planifier le sprint" superActivities="_SoXWEQMAEduOAKqB9I73uw" additionallyPerformedBy="_glbG2AMAEduOAKqB9I73uw" mandatoryInput="_glbG3AMAEduOAKqB9I73uw" output="_glbG2wMAEduOAKqB9I73uw" performedPrimarilyBy="_glbG2gMAEduOAKqB9I73uw">
-          <Task href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_4LOggPpaEdqsc-f87sBK8A"/>
-          <selectedSteps href="uma://-NRwwk6YGAtu25V3Lc04G6w#_TJNsUP--Edqtbrr0B1TG-A"/>
-          <selectedSteps href="uma://-NRwwk6YGAtu25V3Lc04G6w#_p4C0sP--Edqtbrr0B1TG-A"/>
-          <selectedSteps href="uma://-NRwwk6YGAtu25V3Lc04G6w#_worbAP--Edqtbrr0B1TG-A"/>
-          <selectedSteps href="uma://-NRwwk6YGAtu25V3Lc04G6w#_xvy5UAPKEdubhrgDuRb4fA"/>
-          <selectedSteps href="uma://-NRwwk6YGAtu25V3Lc04G6w#_DxNQUAPLEdubhrgDuRb4fA"/>
-          <selectedSteps href="uma://-NRwwk6YGAtu25V3Lc04G6w#_Iq14wAPLEdubhrgDuRb4fA"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_glbG1AMAEduOAKqB9I73uw" name="Retrospective" guid="_glbG1AMAEduOAKqB9I73uw" presentationName="Rétrospective" superActivities="_SoXWEQMAEduOAKqB9I73uw" linkToPredecessor="_O0710AMCEduOAKqB9I73uw" additionallyPerformedBy="_glbG2AMAEduOAKqB9I73uw _glbG1wMAEduOAKqB9I73uw _glbG2QMAEduOAKqB9I73uw" output="_glbG3AMAEduOAKqB9I73uw" performedPrimarilyBy="_glbG2gMAEduOAKqB9I73uw">
-          <Task href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_J_sRIP_AEdqtbrr0B1TG-A"/>
-          <selectedSteps href="uma://-S4qXwp40l_8eCcyyI7o-3A#_lwzeABGPEduHloEV5-Zv-w"/>
-          <selectedSteps href="uma://-S4qXwp40l_8eCcyyI7o-3A#_noL2YBGPEduHloEV5-Zv-w"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_glbG1QMAEduOAKqB9I73uw" name="Review sprint" guid="_glbG1QMAEduOAKqB9I73uw" presentationName="Faire la revue du sprint" superActivities="_SoXWEQMAEduOAKqB9I73uw" isEventDriven="true" additionallyPerformedBy="_glbG2AMAEduOAKqB9I73uw _glbG1wMAEduOAKqB9I73uw _glbG2QMAEduOAKqB9I73uw" mandatoryInput="_glbG3QMAEduOAKqB9I73uw" output="_glbG3AMAEduOAKqB9I73uw" performedPrimarilyBy="_glbG2gMAEduOAKqB9I73uw">
-          <Task href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_MRrRYPpbEdqsc-f87sBK8A"/>
-          <selectedSteps href="uma://-zoJryMCuHfxWP7Q5Er195Q#_XL6VgAPLEdubhrgDuRb4fA"/>
-          <selectedSteps href="uma://-zoJryMCuHfxWP7Q5Er195Q#_ZgJB8APLEdubhrgDuRb4fA"/>
-          <selectedSteps href="uma://-zoJryMCuHfxWP7Q5Er195Q#_cBouUAPLEdubhrgDuRb4fA"/>
-          <selectedSteps href="uma://-zoJryMCuHfxWP7Q5Er195Q#_hrswoHoYEduJVrY6eKG_mw"/>
-          <selectedSteps href="uma://-zoJryMCuHfxWP7Q5Er195Q#_d776UHoYEduJVrY6eKG_mw"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_glbG1gMAEduOAKqB9I73uw" name="Scrum daily meeting" guid="_glbG1gMAEduOAKqB9I73uw" presentationName="Mêlée quotidienne" superActivities="_SoXWEQMAEduOAKqB9I73uw" isRepeatable="true" isEventDriven="true" linkToPredecessor="_34UPdAzNEduDObTFE5q79g _34UPdQzNEduDObTFE5q79g _34UPdgzNEduDObTFE5q79g" additionallyPerformedBy="_glbG2gMAEduOAKqB9I73uw _glbG2AMAEduOAKqB9I73uw" mandatoryInput="_glbG2wMAEduOAKqB9I73uw" output="_glbG2wMAEduOAKqB9I73uw" performedPrimarilyBy="_glbG1wMAEduOAKqB9I73uw">
-          <Task href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_d09LYP_AEdqtbrr0B1TG-A"/>
-          <selectedSteps href="uma://-vDOuVl_xPKipKd90HQNZng#_oUrlcBGOEduHloEV5-Zv-w"/>
-          <selectedSteps href="uma://-vDOuVl_xPKipKd90HQNZng#_r0KkEBGOEduHloEV5-Zv-w"/>
-          <selectedSteps href="uma://-vDOuVl_xPKipKd90HQNZng#_vZkkgBGOEduHloEV5-Zv-w"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_glbG1wMAEduOAKqB9I73uw" name="ScrumMaster" guid="_glbG1wMAEduOAKqB9I73uw" presentationName="ScrumMaster" superActivities="_SoXWEQMAEduOAKqB9I73uw" responsibleFor="_glbG2wMAEduOAKqB9I73uw">
-          <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_t1K9kPpYEdqsc-f87sBK8A"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_glbG2AMAEduOAKqB9I73uw" name="Product Owner" guid="_glbG2AMAEduOAKqB9I73uw" presentationName="Directeur Produit" superActivities="_SoXWEQMAEduOAKqB9I73uw" responsibleFor="_glbG3AMAEduOAKqB9I73uw">
-          <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_ICJyYPpaEdqsc-f87sBK8A"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_glbG2QMAEduOAKqB9I73uw" name="StakeHolder" guid="_glbG2QMAEduOAKqB9I73uw" presentationName="Intervenant" isPlanned="false" hasMultipleOccurrences="true" superActivities="_SoXWEQMAEduOAKqB9I73uw">
-          <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_Qqmp8P_AEdqtbrr0B1TG-A"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_glbG2gMAEduOAKqB9I73uw" name="Team" guid="_glbG2gMAEduOAKqB9I73uw" presentationName="Equipe Scrum" hasMultipleOccurrences="true" superActivities="_SoXWEQMAEduOAKqB9I73uw">
-          <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_9apLsPpaEdqsc-f87sBK8A"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_glbG2wMAEduOAKqB9I73uw" name="Sprint backlog" guid="_glbG2wMAEduOAKqB9I73uw" presentationName="Backlog du sprint" superActivities="_SoXWEQMAEduOAKqB9I73uw">
-          <presentation xmi:id="-MupkaQeHNEmiF7Lnl3VirQ" href="uma://-16dzhVoCex78V2iCDZVx0w#-MupkaQeHNEmiF7Lnl3VirQ"/>
-          <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_Dzw70PpZEdqsc-f87sBK8A"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_glbG3AMAEduOAKqB9I73uw" name="Product Backlog" guid="_glbG3AMAEduOAKqB9I73uw" presentationName="Backlog de produit" superActivities="_SoXWEQMAEduOAKqB9I73uw" activityEntryState="courant" activityExitState="mis à jour">
-          <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_5ABscPpYEdqsc-f87sBK8A"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_glbG3QMAEduOAKqB9I73uw" name="Product" guid="_glbG3QMAEduOAKqB9I73uw" presentationName="Incrément de produit" superActivities="_SoXWEQMAEduOAKqB9I73uw">
-          <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_tCmYEP-xEdqLnajTSLeAsA"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_O0710AMCEduOAKqB9I73uw" guid="_O0710AMCEduOAKqB9I73uw" linkType="finishToFinish" pred="_glbG1QMAEduOAKqB9I73uw"/>
-        <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_nXmKUANlEduYd-55D-Aiqg" name="Daily work" guid="_nXmKUANlEduYd-55D-Aiqg" briefDescription="L'équipe réalise les taches du backlog pour arriver au but du sprint" presentationName="Travaux quotidiens" isPlanned="true" hasMultipleOccurrences="true" superActivities="_SoXWEQMAEduOAKqB9I73uw" mandatoryInput="_glbG2wMAEduOAKqB9I73uw" output="_glbG3QMAEduOAKqB9I73uw">
-          <presentation xmi:id="-EpBaHVCIYCqqGX_wv7dlYA" href="uma://-16dzhVoCex78V2iCDZVx0w#-EpBaHVCIYCqqGX_wv7dlYA"/>
-        </processElements>
-        <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_34UPdAzNEduDObTFE5q79g" guid="_34UPdAzNEduDObTFE5q79g" linkType="finishToFinish" pred="_glbG0QMAEduOAKqB9I73uw"/>
-        <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_34UPdQzNEduDObTFE5q79g" guid="_34UPdQzNEduDObTFE5q79g" linkType="finishToFinish" pred="_nXmKUANlEduYd-55D-Aiqg"/>
-        <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_34UPdgzNEduDObTFE5q79g" guid="_34UPdgzNEduDObTFE5q79g" linkType="finishToFinish" pred="_glbG0AMAEduOAKqB9I73uw"/>
-        <diagrams xmi:id="_2vZZMAMBEduOAKqB9I73uw" guid="_2vZZMAMBEduOAKqB9I73uw">
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_2vZZMQMBEduOAKqB9I73uw" guid="_2vZZMQMBEduOAKqB9I73uw">
-            <position xmi:id="_2vZZMgMBEduOAKqB9I73uw" x="199.0" y="174.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_LnUDQQMCEduOAKqB9I73uw" guid="_LnUDQQMCEduOAKqB9I73uw" anchor="_LnUDQAMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_LSlwcgMCEduOAKqB9I73uw" guid="_LSlwcgMCEduOAKqB9I73uw" graphEdge="_LSlwcQMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_LnUDQAMCEduOAKqB9I73uw" guid="_LnUDQAMCEduOAKqB9I73uw" graphEdge="_LnUDQQMCEduOAKqB9I73uw">
-              <position xmi:id="_LnUDQwMCEduOAKqB9I73uw" x="316.0" y="187.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vZZMwMBEduOAKqB9I73uw" guid="_2vZZMwMBEduOAKqB9I73uw"/>
-            <size xmi:id="_2vZZNAMBEduOAKqB9I73uw" width="143.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_2vff0AMBEduOAKqB9I73uw" guid="_2vff0AMBEduOAKqB9I73uw">
-            <position xmi:id="_2vff0QMBEduOAKqB9I73uw" x="322.0" y="134.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_swPHwQzNEduDObTFE5q79g" guid="_swPHwQzNEduDObTFE5q79g" anchor="_swPHwAzNEduDObTFE5q79g _swPHwgzNEduDObTFE5q79g"/>
-            <anchorage xmi:id="_L-ChMgMCEduOAKqB9I73uw" guid="_L-ChMgMCEduOAKqB9I73uw" graphEdge="_L-ChMQMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_swPHwAzNEduDObTFE5q79g" guid="_swPHwAzNEduDObTFE5q79g" graphEdge="_swPHwQzNEduDObTFE5q79g">
-              <position xmi:id="_swPHwwzNEduDObTFE5q79g" x="394.0" y="241.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vff0gMBEduOAKqB9I73uw" guid="_2vff0gMBEduOAKqB9I73uw" element="_glbG0AMAEduOAKqB9I73uw"/>
-            <size xmi:id="_2vff0wMBEduOAKqB9I73uw" width="98.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_2vff1AMBEduOAKqB9I73uw" guid="_2vff1AMBEduOAKqB9I73uw">
-            <position xmi:id="_2vff1QMBEduOAKqB9I73uw" x="19.0" y="127.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_r27hMQzNEduDObTFE5q79g" guid="_r27hMQzNEduDObTFE5q79g" anchor="_r27hMAzNEduDObTFE5q79g _r27hMgzNEduDObTFE5q79g"/>
-            <anchorage xmi:id="_KNcGQgMCEduOAKqB9I73uw" guid="_KNcGQgMCEduOAKqB9I73uw" graphEdge="_KNcGQQMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_r27hMAzNEduDObTFE5q79g" guid="_r27hMAzNEduDObTFE5q79g" graphEdge="_r27hMQzNEduDObTFE5q79g">
-              <position xmi:id="_r27hMwzNEduDObTFE5q79g" x="123.0" y="239.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vff1gMBEduOAKqB9I73uw" guid="_2vff1gMBEduOAKqB9I73uw" element="_glbG0QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_2vff1wMBEduOAKqB9I73uw" width="130.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_2vff2AMBEduOAKqB9I73uw" guid="_2vff2AMBEduOAKqB9I73uw">
-            <position xmi:id="_2vff2QMBEduOAKqB9I73uw" x="76.0" y="269.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vff2gMBEduOAKqB9I73uw" guid="_2vff2gMBEduOAKqB9I73uw"/>
-            <size xmi:id="_2vff2wMBEduOAKqB9I73uw" width="88.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_2vff3AMBEduOAKqB9I73uw" guid="_2vff3AMBEduOAKqB9I73uw">
-            <position xmi:id="_2vff3QMBEduOAKqB9I73uw" x="190.0" y="3.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_-mYC4QzNEduDObTFE5q79g" guid="_-mYC4QzNEduDObTFE5q79g" anchor="_-mYC4AzNEduDObTFE5q79g _-mYC4gzNEduDObTFE5q79g"/>
-            <anchorage xmi:id="_I2DckgMCEduOAKqB9I73uw" guid="_I2DckgMCEduOAKqB9I73uw" graphEdge="_I2DckQMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_-mYC4AzNEduDObTFE5q79g" guid="_-mYC4AzNEduDObTFE5q79g" graphEdge="_-mYC4QzNEduDObTFE5q79g">
-              <position xmi:id="_-mYC4wzNEduDObTFE5q79g" x="264.0" y="88.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vff3gMBEduOAKqB9I73uw" guid="_2vff3gMBEduOAKqB9I73uw" element="_glbG0wMAEduOAKqB9I73uw"/>
-            <size xmi:id="_2vff3wMBEduOAKqB9I73uw" width="79.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_2vff4AMBEduOAKqB9I73uw" guid="_2vff4AMBEduOAKqB9I73uw">
-            <position xmi:id="_2vff4QMBEduOAKqB9I73uw" x="346.0" y="332.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_PENn8QMCEduOAKqB9I73uw" guid="_PENn8QMCEduOAKqB9I73uw" anchor="_PENn8AMCEduOAKqB9I73uw _PENn8gMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_O0vokgMCEduOAKqB9I73uw" guid="_O0vokgMCEduOAKqB9I73uw" graphEdge="_O0vokQMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_PENn8AMCEduOAKqB9I73uw" guid="_PENn8AMCEduOAKqB9I73uw" graphEdge="_PENn8QMCEduOAKqB9I73uw">
-              <position xmi:id="_PENn8wMCEduOAKqB9I73uw" x="327.0" y="377.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vff4gMBEduOAKqB9I73uw" guid="_2vff4gMBEduOAKqB9I73uw" element="_glbG1AMAEduOAKqB9I73uw"/>
-            <size xmi:id="_2vff4wMBEduOAKqB9I73uw" width="67.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_2vff5AMBEduOAKqB9I73uw" guid="_2vff5AMBEduOAKqB9I73uw">
-            <position xmi:id="_2vff5QMBEduOAKqB9I73uw" x="175.0" y="332.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_O0vokQMCEduOAKqB9I73uw" guid="_O0vokQMCEduOAKqB9I73uw" anchor="_O0vokAMCEduOAKqB9I73uw _O0vokgMCEduOAKqB9I73uw">
-              <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O0710QMCEduOAKqB9I73uw" guid="_O0710QMCEduOAKqB9I73uw"/>
-            </contained>
-            <anchorage xmi:id="_Ok5OsgMCEduOAKqB9I73uw" guid="_Ok5OsgMCEduOAKqB9I73uw" graphEdge="_Ok5OsQMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_O0vokAMCEduOAKqB9I73uw" guid="_O0vokAMCEduOAKqB9I73uw" graphEdge="_O0vokQMCEduOAKqB9I73uw">
-              <position xmi:id="_O0vokwMCEduOAKqB9I73uw" x="324.0" y="328.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vff5gMBEduOAKqB9I73uw" guid="_2vff5gMBEduOAKqB9I73uw" element="_glbG1QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_2vff5wMBEduOAKqB9I73uw" width="111.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_2vff6AMBEduOAKqB9I73uw" guid="_2vff6AMBEduOAKqB9I73uw">
-            <position xmi:id="_2vff6QMBEduOAKqB9I73uw" x="187.0" y="217.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_63CqYQzNEduDObTFE5q79g" guid="_63CqYQzNEduDObTFE5q79g" anchor="_63CqYAzNEduDObTFE5q79g _63CqYgzNEduDObTFE5q79g"/>
-            <anchorage xmi:id="_34UPcgzNEduDObTFE5q79g" guid="_34UPcgzNEduDObTFE5q79g" graphEdge="_34UPcQzNEduDObTFE5q79g"/>
-            <anchorage xmi:id="_63CqYAzNEduDObTFE5q79g" guid="_63CqYAzNEduDObTFE5q79g" graphEdge="_63CqYQzNEduDObTFE5q79g">
-              <position xmi:id="_63CqYwzNEduDObTFE5q79g" x="268.0" y="326.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vff6gMBEduOAKqB9I73uw" guid="_2vff6gMBEduOAKqB9I73uw" element="_glbG1gMAEduOAKqB9I73uw"/>
-            <size xmi:id="_2vff6wMBEduOAKqB9I73uw" width="86.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_DtnjIAMCEduOAKqB9I73uw" guid="_DtnjIAMCEduOAKqB9I73uw">
-            <position xmi:id="_DtnjIQMCEduOAKqB9I73uw" x="9.0" y="15.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_I2DckQMCEduOAKqB9I73uw" guid="_I2DckQMCEduOAKqB9I73uw" anchor="_I2DckAMCEduOAKqB9I73uw _I2DckgMCEduOAKqB9I73uw"/>
-            <anchorage xmi:id="_I2DckAMCEduOAKqB9I73uw" guid="_I2DckAMCEduOAKqB9I73uw" graphEdge="_I2DckQMCEduOAKqB9I73uw">
-              <position xmi:id="_I2DckwMCEduOAKqB9I73uw" x="318.0" y="32.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_DtnjIgMCEduOAKqB9I73uw" guid="_DtnjIgMCEduOAKqB9I73uw" typeInfo="start node"/>
-            <size xmi:id="_DtnjIwMCEduOAKqB9I73uw" width="20.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_EQ85sAMCEduOAKqB9I73uw" guid="_EQ85sAMCEduOAKqB9I73uw">
-            <position xmi:id="_EQ85sQMCEduOAKqB9I73uw" x="531.0" y="342.0"/>
-            <anchorage xmi:id="_PENn8gMCEduOAKqB9I73uw" guid="_PENn8gMCEduOAKqB9I73uw" graphEdge="_PENn8QMCEduOAKqB9I73uw"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_EQ85sgMCEduOAKqB9I73uw" guid="_EQ85sgMCEduOAKqB9I73uw" typeInfo="end node"/>
-            <size xmi:id="_EQ85swMCEduOAKqB9I73uw" width="24.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_FLsDoAMCEduOAKqB9I73uw" guid="_FLsDoAMCEduOAKqB9I73uw">
-            <position xmi:id="_FLsDoQMCEduOAKqB9I73uw" x="206.0" y="274.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_Ok5OsQMCEduOAKqB9I73uw" guid="_Ok5OsQMCEduOAKqB9I73uw" anchor="_Ok5OsAMCEduOAKqB9I73uw _Ok5OsgMCEduOAKqB9I73uw"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_ADBAAQzOEduDObTFE5q79g" guid="_ADBAAQzOEduDObTFE5q79g" anchor="_ADBAAAzOEduDObTFE5q79g _ADBAAgzOEduDObTFE5q79g">
-              <waypoints xmi:id="_0PYkcAzOEduDObTFE5q79g" x="491.0" y="285.0"/>
-              <waypoints xmi:id="_0PYkcQzOEduDObTFE5q79g" x="492.0" y="76.0"/>
-            </contained>
-            <anchorage xmi:id="_Ok5OsAMCEduOAKqB9I73uw" guid="_Ok5OsAMCEduOAKqB9I73uw" graphEdge="_Ok5OsQMCEduOAKqB9I73uw">
-              <position xmi:id="_cyxCoAMCEduOAKqB9I73uw" x="23.0" y="23.0"/>
-            </anchorage>
-            <anchorage xmi:id="_63CqYgzNEduDObTFE5q79g" guid="_63CqYgzNEduDObTFE5q79g" graphEdge="_63CqYQzNEduDObTFE5q79g">
-              <position xmi:id="_63CqZAzNEduDObTFE5q79g" x="23.0" y="0.0"/>
-            </anchorage>
-            <anchorage xmi:id="_ADBAAAzOEduDObTFE5q79g" guid="_ADBAAAzOEduDObTFE5q79g" graphEdge="_ADBAAQzOEduDObTFE5q79g">
-              <position xmi:id="_ADBAAwzOEduDObTFE5q79g" x="47.0" y="11.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_FLsDogMCEduOAKqB9I73uw" guid="_FLsDogMCEduOAKqB9I73uw" typeInfo="decision node"/>
-            <size xmi:id="_FLsDowMCEduOAKqB9I73uw" width="48.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_HEmGAAMCEduOAKqB9I73uw" guid="_HEmGAAMCEduOAKqB9I73uw">
-            <position xmi:id="_HEmGAQMCEduOAKqB9I73uw" x="180.0" y="106.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_KNcGQQMCEduOAKqB9I73uw" guid="_KNcGQQMCEduOAKqB9I73uw" anchor="_KNcGQAMCEduOAKqB9I73uw _KNcGQgMCEduOAKqB9I73uw"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_LSlwcQMCEduOAKqB9I73uw" guid="_LSlwcQMCEduOAKqB9I73uw" anchor="_LSlwcAMCEduOAKqB9I73uw _LSlwcgMCEduOAKqB9I73uw"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_L-ChMQMCEduOAKqB9I73uw" guid="_L-ChMQMCEduOAKqB9I73uw" anchor="_L-ChMAMCEduOAKqB9I73uw _L-ChMgMCEduOAKqB9I73uw"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_haut0QNmEduYd-55D-Aiqg" guid="_haut0QNmEduYd-55D-Aiqg" anchor="_haut0ANmEduYd-55D-Aiqg _haut0gNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_KNcGQAMCEduOAKqB9I73uw" guid="_KNcGQAMCEduOAKqB9I73uw" graphEdge="_KNcGQQMCEduOAKqB9I73uw">
-              <position xmi:id="_KNcGQwMCEduOAKqB9I73uw" x="47.0" y="5.0"/>
-            </anchorage>
-            <anchorage xmi:id="_LSlwcAMCEduOAKqB9I73uw" guid="_LSlwcAMCEduOAKqB9I73uw" graphEdge="_LSlwcQMCEduOAKqB9I73uw">
-              <position xmi:id="_LSlwcwMCEduOAKqB9I73uw" x="49.0" y="0.0"/>
-            </anchorage>
-            <anchorage xmi:id="_L-ChMAMCEduOAKqB9I73uw" guid="_L-ChMAMCEduOAKqB9I73uw" graphEdge="_L-ChMQMCEduOAKqB9I73uw">
-              <position xmi:id="_L-In0AMCEduOAKqB9I73uw" x="50.0" y="5.0"/>
-            </anchorage>
-            <anchorage xmi:id="_haut0ANmEduYd-55D-Aiqg" guid="_haut0ANmEduYd-55D-Aiqg" graphEdge="_haut0QNmEduYd-55D-Aiqg">
-              <position xmi:id="_8NQZYIGPEduKE9hnyImx1Q" x="50.0" y="5.0"/>
-            </anchorage>
-            <anchorage xmi:id="__S4jkgzNEduDObTFE5q79g" guid="__S4jkgzNEduDObTFE5q79g" graphEdge="__S4jkQzNEduDObTFE5q79g">
-              <position xmi:id="__S4jlAzNEduDObTFE5q79g" x="46.0" y="0.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_HEmGAgMCEduOAKqB9I73uw" guid="_HEmGAgMCEduOAKqB9I73uw" typeInfo="synchnonization bar"/>
-            <size xmi:id="_HEmGAwMCEduOAKqB9I73uw" width="100.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_XP3cUANmEduYd-55D-Aiqg" guid="_XP3cUANmEduYd-55D-Aiqg">
-            <position xmi:id="_XP3cUQNmEduYd-55D-Aiqg" x="184.0" y="134.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_sOOm4QzNEduDObTFE5q79g" guid="_sOOm4QzNEduDObTFE5q79g" anchor="_sOOm4AzNEduDObTFE5q79g _sOOm4gzNEduDObTFE5q79g"/>
-            <anchorage xmi:id="_haut0gNmEduYd-55D-Aiqg" guid="_haut0gNmEduYd-55D-Aiqg" graphEdge="_haut0QNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_sOOm4AzNEduDObTFE5q79g" guid="_sOOm4AzNEduDObTFE5q79g" graphEdge="_sOOm4QzNEduDObTFE5q79g">
-              <position xmi:id="_sOOm4wzNEduDObTFE5q79g" x="263.0" y="237.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_XP3cUgNmEduYd-55D-Aiqg" guid="_XP3cUgNmEduYd-55D-Aiqg" element="_nXmKUANlEduYd-55D-Aiqg"/>
-            <size xmi:id="_XP3cUwNmEduYd-55D-Aiqg" width="92.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_4Fi44ANmEduYd-55D-Aiqg" name="Add Free Text" guid="_4Fi44ANmEduYd-55D-Aiqg">
-            <property xmi:id="_4Fi44QNmEduYd-55D-Aiqg" guid="_4Fi44QNmEduYd-55D-Aiqg" key="free text" value="date de fin de sprint atteinte"/>
-            <position xmi:id="_4Fi44gNmEduYd-55D-Aiqg" x="154.0" y="297.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_4Fi44wNmEduYd-55D-Aiqg" guid="_4Fi44wNmEduYd-55D-Aiqg" typeInfo="free text"/>
-            <size xmi:id="_4Fi45ANmEduYd-55D-Aiqg" width="69.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_S90SkAzNEduDObTFE5q79g" guid="_S90SkAzNEduDObTFE5q79g">
-            <position xmi:id="_S90SkQzNEduDObTFE5q79g" x="206.0" y="66.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="__S4jkQzNEduDObTFE5q79g" guid="__S4jkQzNEduDObTFE5q79g" anchor="__S4jkAzNEduDObTFE5q79g __S4jkgzNEduDObTFE5q79g"/>
-            <anchorage xmi:id="_-mYC4gzNEduDObTFE5q79g" guid="_-mYC4gzNEduDObTFE5q79g" graphEdge="_-mYC4QzNEduDObTFE5q79g">
-              <position xmi:id="_-mYC5AzNEduDObTFE5q79g" x="23.0" y="0.0"/>
-            </anchorage>
-            <anchorage xmi:id="__S4jkAzNEduDObTFE5q79g" guid="__S4jkAzNEduDObTFE5q79g" graphEdge="__S4jkQzNEduDObTFE5q79g">
-              <position xmi:id="__S4jkwzNEduDObTFE5q79g" x="23.0" y="23.0"/>
-            </anchorage>
-            <anchorage xmi:id="_ADBAAgzOEduDObTFE5q79g" guid="_ADBAAgzOEduDObTFE5q79g" graphEdge="_ADBAAQzOEduDObTFE5q79g">
-              <position xmi:id="_ADBABAzOEduDObTFE5q79g" x="47.0" y="11.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_S90SkgzNEduDObTFE5q79g" guid="_S90SkgzNEduDObTFE5q79g" typeInfo="decision node"/>
-            <size xmi:id="_S90SkwzNEduDObTFE5q79g" width="48.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_qmzWEAzNEduDObTFE5q79g" guid="_qmzWEAzNEduDObTFE5q79g">
-            <position xmi:id="_qmzWEQzNEduDObTFE5q79g" x="180.0" y="198.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_34UPcQzNEduDObTFE5q79g" guid="_34UPcQzNEduDObTFE5q79g" anchor="_34UPcAzNEduDObTFE5q79g _34UPcgzNEduDObTFE5q79g"/>
-            <anchorage xmi:id="_r27hMgzNEduDObTFE5q79g" guid="_r27hMgzNEduDObTFE5q79g" graphEdge="_r27hMQzNEduDObTFE5q79g">
-              <position xmi:id="_r27hNAzNEduDObTFE5q79g" x="38.0" y="0.0"/>
-            </anchorage>
-            <anchorage xmi:id="_sOOm4gzNEduDObTFE5q79g" guid="_sOOm4gzNEduDObTFE5q79g" graphEdge="_sOOm4QzNEduDObTFE5q79g">
-              <position xmi:id="_8NQZYYGPEduKE9hnyImx1Q" x="50.0" y="0.0"/>
-            </anchorage>
-            <anchorage xmi:id="_swPHwgzNEduDObTFE5q79g" guid="_swPHwgzNEduDObTFE5q79g" graphEdge="_swPHwQzNEduDObTFE5q79g">
-              <position xmi:id="_swPHxAzNEduDObTFE5q79g" x="48.0" y="0.0"/>
-            </anchorage>
-            <anchorage xmi:id="_34UPcAzNEduDObTFE5q79g" guid="_34UPcAzNEduDObTFE5q79g" graphEdge="_34UPcQzNEduDObTFE5q79g">
-              <position xmi:id="_34UPcwzNEduDObTFE5q79g" x="44.0" y="0.0"/>
-            </anchorage>
-            <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_qmzWEgzNEduDObTFE5q79g" guid="_qmzWEgzNEduDObTFE5q79g" typeInfo="synchnonization bar"/>
-            <size xmi:id="_qmzWEwzNEduDObTFE5q79g" width="100.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_f5j60AzOEduDObTFE5q79g" name="Add Free Text" guid="_f5j60AzOEduDObTFE5q79g">
-            <property xmi:id="_f5j60QzOEduDObTFE5q79g" guid="_f5j60QzOEduDObTFE5q79g" key="free text" value="encore des jours dans le sprint"/>
-            <position xmi:id="_f5j60gzOEduDObTFE5q79g" x="289.0" y="266.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_f5j60wzOEduDObTFE5q79g" guid="_f5j60wzOEduDObTFE5q79g" typeInfo="free text"/>
-            <size xmi:id="_f5j61AzOEduDObTFE5q79g" width="165.0" height="-1.0"/>
-          </contained>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_2vZZNQMBEduOAKqB9I73uw" guid="_2vZZNQMBEduOAKqB9I73uw" presentation="Workflow" element="_SoXWEQMAEduOAKqB9I73uw"/>
-        </diagrams>
-        <diagrams xmi:id="_O8kwcANmEduYd-55D-Aiqg" guid="_O8kwcANmEduYd-55D-Aiqg">
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8kwcQNmEduYd-55D-Aiqg" guid="_O8kwcQNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8kwcgNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5RsYGMEduKE9hnyImx1Q" guid="_5q5RsYGMEduKE9hnyImx1Q" anchor="_5q5RsIGMEduKE9hnyImx1Q _5q5RsoGMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeEYGMEduKE9hnyImx1Q" guid="_51BeEYGMEduKE9hnyImx1Q" anchor="_51BeEIGMEduKE9hnyImx1Q _51BeEoGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5RsIGMEduKE9hnyImx1Q" guid="_5q5RsIGMEduKE9hnyImx1Q" graphEdge="_5q5RsYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeEIGMEduKE9hnyImx1Q" guid="_51BeEIGMEduKE9hnyImx1Q" graphEdge="_51BeEYGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8kwcwNmEduYd-55D-Aiqg" guid="_O8kwcwNmEduYd-55D-Aiqg" element="_glbG0AMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8kwdANmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8kwdQNmEduYd-55D-Aiqg" guid="_O8kwdQNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8kwdgNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5Rt4GMEduKE9hnyImx1Q" guid="_5q5Rt4GMEduKE9hnyImx1Q" anchor="_5q5RtoGMEduKE9hnyImx1Q _5q5RuIGMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeF4GMEduKE9hnyImx1Q" guid="_51BeF4GMEduKE9hnyImx1Q" anchor="_51BeFoGMEduKE9hnyImx1Q _51BeGIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5RtYGMEduKE9hnyImx1Q" guid="_5q5RtYGMEduKE9hnyImx1Q" graphEdge="_5q5RtIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5RtoGMEduKE9hnyImx1Q" guid="_5q5RtoGMEduKE9hnyImx1Q" graphEdge="_5q5Rt4GMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeFYGMEduKE9hnyImx1Q" guid="_51BeFYGMEduKE9hnyImx1Q" graphEdge="_51BeFIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeFoGMEduKE9hnyImx1Q" guid="_51BeFoGMEduKE9hnyImx1Q" graphEdge="_51BeF4GMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8kwdwNmEduYd-55D-Aiqg" guid="_O8kwdwNmEduYd-55D-Aiqg" element="_glbG0QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8kweANmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8kweQNmEduYd-55D-Aiqg" guid="_O8kweQNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8kwegNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5RvYGMEduKE9hnyImx1Q" guid="_5q5RvYGMEduKE9hnyImx1Q" anchor="_5q5RvIGMEduKE9hnyImx1Q _5q5RvoGMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeHYGMEduKE9hnyImx1Q" guid="_51BeHYGMEduKE9hnyImx1Q" anchor="_51BeHIGMEduKE9hnyImx1Q _51BeHoGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5Ru4GMEduKE9hnyImx1Q" guid="_5q5Ru4GMEduKE9hnyImx1Q" graphEdge="_5q5RuoGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5RvIGMEduKE9hnyImx1Q" guid="_5q5RvIGMEduKE9hnyImx1Q" graphEdge="_5q5RvYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeG4GMEduKE9hnyImx1Q" guid="_51BeG4GMEduKE9hnyImx1Q" graphEdge="_51BeGoGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeHIGMEduKE9hnyImx1Q" guid="_51BeHIGMEduKE9hnyImx1Q" graphEdge="_51BeHYGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8kwewNmEduYd-55D-Aiqg" guid="_O8kwewNmEduYd-55D-Aiqg" element="_glbG0wMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8kwfANmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8kwfQNmEduYd-55D-Aiqg" guid="_O8kwfQNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8kwfgNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5RwIGMEduKE9hnyImx1Q" guid="_5q5RwIGMEduKE9hnyImx1Q" anchor="_5q5Rv4GMEduKE9hnyImx1Q _5q5RwYGMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeIIGMEduKE9hnyImx1Q" guid="_51BeIIGMEduKE9hnyImx1Q" anchor="_51BeH4GMEduKE9hnyImx1Q _51BeIYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5Rv4GMEduKE9hnyImx1Q" guid="_5q5Rv4GMEduKE9hnyImx1Q" graphEdge="_5q5RwIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeH4GMEduKE9hnyImx1Q" guid="_51BeH4GMEduKE9hnyImx1Q" graphEdge="_51BeIIGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3EANmEduYd-55D-Aiqg" guid="_O8q3EANmEduYd-55D-Aiqg" element="_glbG1AMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3EQNmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3EgNmEduYd-55D-Aiqg" guid="_O8q3EgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3EwNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5RxoGMEduKE9hnyImx1Q" guid="_5q5RxoGMEduKE9hnyImx1Q" anchor="_5q5RxYGMEduKE9hnyImx1Q _5q5Rx4GMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeJoGMEduKE9hnyImx1Q" guid="_51BeJoGMEduKE9hnyImx1Q" anchor="_51BeJYGMEduKE9hnyImx1Q _51BeJ4GMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5RxIGMEduKE9hnyImx1Q" guid="_5q5RxIGMEduKE9hnyImx1Q" graphEdge="_5q5Rw4GMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5RxYGMEduKE9hnyImx1Q" guid="_5q5RxYGMEduKE9hnyImx1Q" graphEdge="_5q5RxoGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeJIGMEduKE9hnyImx1Q" guid="_51BeJIGMEduKE9hnyImx1Q" graphEdge="_51BeI4GMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeJYGMEduKE9hnyImx1Q" guid="_51BeJYGMEduKE9hnyImx1Q" graphEdge="_51BeJoGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3FANmEduYd-55D-Aiqg" guid="_O8q3FANmEduYd-55D-Aiqg" element="_glbG1QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3FQNmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3FgNmEduYd-55D-Aiqg" guid="_O8q3FgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3FwNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5RzIGMEduKE9hnyImx1Q" guid="_5q5RzIGMEduKE9hnyImx1Q" anchor="_5q5Ry4GMEduKE9hnyImx1Q _5q5RzYGMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeLIGMEduKE9hnyImx1Q" guid="_51BeLIGMEduKE9hnyImx1Q" anchor="_51BeK4GMEduKE9hnyImx1Q _51BeLYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5RyoGMEduKE9hnyImx1Q" guid="_5q5RyoGMEduKE9hnyImx1Q" graphEdge="_5q5RyYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_5q5Ry4GMEduKE9hnyImx1Q" guid="_5q5Ry4GMEduKE9hnyImx1Q" graphEdge="_5q5RzIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeKoGMEduKE9hnyImx1Q" guid="_51BeKoGMEduKE9hnyImx1Q" graphEdge="_51BeKYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeK4GMEduKE9hnyImx1Q" guid="_51BeK4GMEduKE9hnyImx1Q" graphEdge="_51BeLIGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3GANmEduYd-55D-Aiqg" guid="_O8q3GANmEduYd-55D-Aiqg" element="_glbG1gMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3GQNmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3GgNmEduYd-55D-Aiqg" guid="_O8q3GgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3GwNmEduYd-55D-Aiqg" x="30.0" y="88.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3HANmEduYd-55D-Aiqg" guid="_O8q3HANmEduYd-55D-Aiqg" element="_glbG1wMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3HQNmEduYd-55D-Aiqg" width="338.0" height="53.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3HgNmEduYd-55D-Aiqg" guid="_O8q3HgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3HwNmEduYd-55D-Aiqg" x="30.0" y="356.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3IANmEduYd-55D-Aiqg" guid="_O8q3IANmEduYd-55D-Aiqg" element="_glbG2AMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3IQNmEduYd-55D-Aiqg" width="222.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3IgNmEduYd-55D-Aiqg" guid="_O8q3IgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3IwNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3JANmEduYd-55D-Aiqg" guid="_O8q3JANmEduYd-55D-Aiqg" element="_glbG2QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3JQNmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3JgNmEduYd-55D-Aiqg" guid="_O8q3JgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3JwNmEduYd-55D-Aiqg" x="30.0" y="638.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3KANmEduYd-55D-Aiqg" guid="_O8q3KANmEduYd-55D-Aiqg" element="_glbG2gMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3KQNmEduYd-55D-Aiqg" width="374.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3KgNmEduYd-55D-Aiqg" guid="_O8q3KgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3KwNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3LANmEduYd-55D-Aiqg" guid="_O8q3LANmEduYd-55D-Aiqg" element="_glbG2wMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3LQNmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3LgNmEduYd-55D-Aiqg" guid="_O8q3LgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3LwNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3MANmEduYd-55D-Aiqg" guid="_O8q3MANmEduYd-55D-Aiqg" element="_glbG3AMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3MQNmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3MgNmEduYd-55D-Aiqg" guid="_O8q3MgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3MwNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3NANmEduYd-55D-Aiqg" guid="_O8q3NANmEduYd-55D-Aiqg" element="_glbG3QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O8q3NQNmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O8q3NgNmEduYd-55D-Aiqg" guid="_O8q3NgNmEduYd-55D-Aiqg">
-            <position xmi:id="_O8q3NwNmEduYd-55D-Aiqg" x="-1.0" y="-1.0"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3OANmEduYd-55D-Aiqg" guid="_O8q3OANmEduYd-55D-Aiqg" element="_nXmKUANlEduYd-55D-Aiqg"/>
-            <size xmi:id="_O8q3OQNmEduYd-55D-Aiqg" width="-1.0" height="-1.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O9bsEANmEduYd-55D-Aiqg" guid="_O9bsEANmEduYd-55D-Aiqg">
-            <property xmi:id="_O9bsEQNmEduYd-55D-Aiqg" guid="_O9bsEQNmEduYd-55D-Aiqg" key="wpCompositeType" value="2"/>
-            <position xmi:id="_O9bsEgNmEduYd-55D-Aiqg" x="137.0" y="161.0"/>
-            <anchorage xmi:id="_O-9WFQNmEduYd-55D-Aiqg" guid="_O-9WFQNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVsANnEduYd-55D-Aiqg" guid="_oHjVsANnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPMAO8EdubhrgDuRb4fA" guid="_D6EPMAO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTMAPMEdubhrgDuRb4fA" guid="_-EfTMAPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTcBTUEduFIr9xNbwGyQ" guid="_8ZSTcBTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5RsoGMEduKE9hnyImx1Q" guid="_5q5RsoGMEduKE9hnyImx1Q" graphEdge="_5q5RsYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeEoGMEduKE9hnyImx1Q" guid="_51BeEoGMEduKE9hnyImx1Q" graphEdge="_51BeEYGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O9bsEwNmEduYd-55D-Aiqg" guid="_O9bsEwNmEduYd-55D-Aiqg" element="_glbG0AMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O9bsFANmEduYd-55D-Aiqg" width="72.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O9t_8ANmEduYd-55D-Aiqg" guid="_O9t_8ANmEduYd-55D-Aiqg">
-            <property xmi:id="_O9t_8QNmEduYd-55D-Aiqg" guid="_O9t_8QNmEduYd-55D-Aiqg" key="wpCompositeType" value="1"/>
-            <position xmi:id="_O9t_8gNmEduYd-55D-Aiqg" x="142.0" y="269.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_O-9WFwNmEduYd-55D-Aiqg" guid="_O-9WFwNmEduYd-55D-Aiqg" anchor="_O-9WFgNmEduYd-55D-Aiqg"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_oHjVsgNnEduYd-55D-Aiqg" guid="_oHjVsgNnEduYd-55D-Aiqg" anchor="_oHjVsQNnEduYd-55D-Aiqg"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_D6EPMgO8EdubhrgDuRb4fA" guid="_D6EPMgO8EdubhrgDuRb4fA" anchor="_D6EPMQO8EdubhrgDuRb4fA"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_-EfTMgPMEdubhrgDuRb4fA" guid="_-EfTMgPMEdubhrgDuRb4fA" anchor="_-EfTMQPMEdubhrgDuRb4fA"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_8ZSTchTUEduFIr9xNbwGyQ" guid="_8ZSTchTUEduFIr9xNbwGyQ" anchor="_8ZSTcRTUEduFIr9xNbwGyQ"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5RtIGMEduKE9hnyImx1Q" guid="_5q5RtIGMEduKE9hnyImx1Q" anchor="_5q5Rs4GMEduKE9hnyImx1Q _5q5RtYGMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeFIGMEduKE9hnyImx1Q" guid="_51BeFIGMEduKE9hnyImx1Q" anchor="_51BeE4GMEduKE9hnyImx1Q _51BeFYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_O-9WFgNmEduYd-55D-Aiqg" guid="_O-9WFgNmEduYd-55D-Aiqg" graphEdge="_O-9WFwNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVsQNnEduYd-55D-Aiqg" guid="_oHjVsQNnEduYd-55D-Aiqg" graphEdge="_oHjVsgNnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPMQO8EdubhrgDuRb4fA" guid="_D6EPMQO8EdubhrgDuRb4fA" graphEdge="_D6EPMgO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTMQPMEdubhrgDuRb4fA" guid="_-EfTMQPMEdubhrgDuRb4fA" graphEdge="_-EfTMgPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTcRTUEduFIr9xNbwGyQ" guid="_8ZSTcRTUEduFIr9xNbwGyQ" graphEdge="_8ZSTchTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5Rs4GMEduKE9hnyImx1Q" guid="_5q5Rs4GMEduKE9hnyImx1Q" graphEdge="_5q5RtIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeE4GMEduKE9hnyImx1Q" guid="_51BeE4GMEduKE9hnyImx1Q" graphEdge="_51BeFIGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O9t_8wNmEduYd-55D-Aiqg" guid="_O9t_8wNmEduYd-55D-Aiqg" element="_glbG0QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O9t_9ANmEduYd-55D-Aiqg" width="78.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O96NMANmEduYd-55D-Aiqg" guid="_O96NMANmEduYd-55D-Aiqg">
-            <property xmi:id="_O96NMQNmEduYd-55D-Aiqg" guid="_O96NMQNmEduYd-55D-Aiqg" key="wpCompositeType" value="2"/>
-            <position xmi:id="_O96NMgNmEduYd-55D-Aiqg" x="142.0" y="443.0"/>
-            <anchorage xmi:id="_O-9WGANmEduYd-55D-Aiqg" guid="_O-9WGANmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVswNnEduYd-55D-Aiqg" guid="_oHjVswNnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPMwO8EdubhrgDuRb4fA" guid="_D6EPMwO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTMwPMEdubhrgDuRb4fA" guid="_-EfTMwPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTcxTUEduFIr9xNbwGyQ" guid="_8ZSTcxTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5RuIGMEduKE9hnyImx1Q" guid="_5q5RuIGMEduKE9hnyImx1Q" graphEdge="_5q5Rt4GMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeGIGMEduKE9hnyImx1Q" guid="_51BeGIGMEduKE9hnyImx1Q" graphEdge="_51BeF4GMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O96NMwNmEduYd-55D-Aiqg" guid="_O96NMwNmEduYd-55D-Aiqg" element="_glbG0QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O96NNANmEduYd-55D-Aiqg" width="78.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O-GacANmEduYd-55D-Aiqg" guid="_O-GacANmEduYd-55D-Aiqg">
-            <property xmi:id="_O-GacQNmEduYd-55D-Aiqg" guid="_O-GacQNmEduYd-55D-Aiqg" key="wpCompositeType" value="1"/>
-            <position xmi:id="_O-GacgNmEduYd-55D-Aiqg" x="289.0" y="551.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_O-9WGgNmEduYd-55D-Aiqg" guid="_O-9WGgNmEduYd-55D-Aiqg" anchor="_O-9WGQNmEduYd-55D-Aiqg"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_oHjVtQNnEduYd-55D-Aiqg" guid="_oHjVtQNnEduYd-55D-Aiqg" anchor="_oHjVtANnEduYd-55D-Aiqg"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_D6EPNQO8EdubhrgDuRb4fA" guid="_D6EPNQO8EdubhrgDuRb4fA" anchor="_D6EPNAO8EdubhrgDuRb4fA"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_-EfTNQPMEdubhrgDuRb4fA" guid="_-EfTNQPMEdubhrgDuRb4fA" anchor="_-EfTNAPMEdubhrgDuRb4fA"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_8ZSTdRTUEduFIr9xNbwGyQ" guid="_8ZSTdRTUEduFIr9xNbwGyQ" anchor="_8ZSTdBTUEduFIr9xNbwGyQ"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5RuoGMEduKE9hnyImx1Q" guid="_5q5RuoGMEduKE9hnyImx1Q" anchor="_5q5RuYGMEduKE9hnyImx1Q _5q5Ru4GMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeGoGMEduKE9hnyImx1Q" guid="_51BeGoGMEduKE9hnyImx1Q" anchor="_51BeGYGMEduKE9hnyImx1Q _51BeG4GMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_O-9WGQNmEduYd-55D-Aiqg" guid="_O-9WGQNmEduYd-55D-Aiqg" graphEdge="_O-9WGgNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVtANnEduYd-55D-Aiqg" guid="_oHjVtANnEduYd-55D-Aiqg" graphEdge="_oHjVtQNnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPNAO8EdubhrgDuRb4fA" guid="_D6EPNAO8EdubhrgDuRb4fA" graphEdge="_D6EPNQO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTNAPMEdubhrgDuRb4fA" guid="_-EfTNAPMEdubhrgDuRb4fA" graphEdge="_-EfTNQPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTdBTUEduFIr9xNbwGyQ" guid="_8ZSTdBTUEduFIr9xNbwGyQ" graphEdge="_8ZSTdRTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5RuYGMEduKE9hnyImx1Q" guid="_5q5RuYGMEduKE9hnyImx1Q" graphEdge="_5q5RuoGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeGYGMEduKE9hnyImx1Q" guid="_51BeGYGMEduKE9hnyImx1Q" graphEdge="_51BeGoGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O-GacwNmEduYd-55D-Aiqg" guid="_O-GacwNmEduYd-55D-Aiqg" element="_glbG0wMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O-GadANmEduYd-55D-Aiqg" width="78.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O-MhEANmEduYd-55D-Aiqg" guid="_O-MhEANmEduYd-55D-Aiqg">
-            <property xmi:id="_O-MhEQNmEduYd-55D-Aiqg" guid="_O-MhEQNmEduYd-55D-Aiqg" key="wpCompositeType" value="2"/>
-            <position xmi:id="_O-MhEgNmEduYd-55D-Aiqg" x="292.0" y="725.0"/>
-            <anchorage xmi:id="_O-9WGwNmEduYd-55D-Aiqg" guid="_O-9WGwNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVtgNnEduYd-55D-Aiqg" guid="_oHjVtgNnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPNgO8EdubhrgDuRb4fA" guid="_D6EPNgO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTNgPMEdubhrgDuRb4fA" guid="_-EfTNgPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTdhTUEduFIr9xNbwGyQ" guid="_8ZSTdhTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5RvoGMEduKE9hnyImx1Q" guid="_5q5RvoGMEduKE9hnyImx1Q" graphEdge="_5q5RvYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeHoGMEduKE9hnyImx1Q" guid="_51BeHoGMEduKE9hnyImx1Q" graphEdge="_51BeHYGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O-MhEwNmEduYd-55D-Aiqg" guid="_O-MhEwNmEduYd-55D-Aiqg" element="_glbG0wMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O-MhFANmEduYd-55D-Aiqg" width="72.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O-YuUANmEduYd-55D-Aiqg" guid="_O-YuUANmEduYd-55D-Aiqg">
-            <property xmi:id="_O-YuUQNmEduYd-55D-Aiqg" guid="_O-YuUQNmEduYd-55D-Aiqg" key="wpCompositeType" value="2"/>
-            <position xmi:id="_O-YuUgNmEduYd-55D-Aiqg" x="121.0" y="725.0"/>
-            <anchorage xmi:id="_O-9WHANmEduYd-55D-Aiqg" guid="_O-9WHANmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVtwNnEduYd-55D-Aiqg" guid="_oHjVtwNnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPNwO8EdubhrgDuRb4fA" guid="_D6EPNwO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTNwPMEdubhrgDuRb4fA" guid="_-EfTNwPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTdxTUEduFIr9xNbwGyQ" guid="_8ZSTdxTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5RwYGMEduKE9hnyImx1Q" guid="_5q5RwYGMEduKE9hnyImx1Q" graphEdge="_5q5RwIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeIYGMEduKE9hnyImx1Q" guid="_51BeIYGMEduKE9hnyImx1Q" graphEdge="_51BeIIGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O-YuUwNmEduYd-55D-Aiqg" guid="_O-YuUwNmEduYd-55D-Aiqg" element="_glbG1AMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O-YuVANmEduYd-55D-Aiqg" width="78.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O-k7kANmEduYd-55D-Aiqg" guid="_O-k7kANmEduYd-55D-Aiqg">
-            <property xmi:id="_O-k7kQNmEduYd-55D-Aiqg" guid="_O-k7kQNmEduYd-55D-Aiqg" key="wpCompositeType" value="1"/>
-            <position xmi:id="_O-k7kgNmEduYd-55D-Aiqg" x="216.0" y="565.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_O-9WHgNmEduYd-55D-Aiqg" guid="_O-9WHgNmEduYd-55D-Aiqg" anchor="_O-9WHQNmEduYd-55D-Aiqg"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_oHjVuQNnEduYd-55D-Aiqg" guid="_oHjVuQNnEduYd-55D-Aiqg" anchor="_oHjVuANnEduYd-55D-Aiqg"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_D6EPOQO8EdubhrgDuRb4fA" guid="_D6EPOQO8EdubhrgDuRb4fA" anchor="_D6EPOAO8EdubhrgDuRb4fA"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_-EfTOQPMEdubhrgDuRb4fA" guid="_-EfTOQPMEdubhrgDuRb4fA" anchor="_-EfTOAPMEdubhrgDuRb4fA"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_8ZSTeRTUEduFIr9xNbwGyQ" guid="_8ZSTeRTUEduFIr9xNbwGyQ" anchor="_8ZSTeBTUEduFIr9xNbwGyQ"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5Rw4GMEduKE9hnyImx1Q" guid="_5q5Rw4GMEduKE9hnyImx1Q" anchor="_5q5RwoGMEduKE9hnyImx1Q _5q5RxIGMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeI4GMEduKE9hnyImx1Q" guid="_51BeI4GMEduKE9hnyImx1Q" anchor="_51BeIoGMEduKE9hnyImx1Q _51BeJIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_O-9WHQNmEduYd-55D-Aiqg" guid="_O-9WHQNmEduYd-55D-Aiqg" graphEdge="_O-9WHgNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVuANnEduYd-55D-Aiqg" guid="_oHjVuANnEduYd-55D-Aiqg" graphEdge="_oHjVuQNnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPOAO8EdubhrgDuRb4fA" guid="_D6EPOAO8EdubhrgDuRb4fA" graphEdge="_D6EPOQO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTOAPMEdubhrgDuRb4fA" guid="_-EfTOAPMEdubhrgDuRb4fA" graphEdge="_-EfTOQPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTeBTUEduFIr9xNbwGyQ" guid="_8ZSTeBTUEduFIr9xNbwGyQ" graphEdge="_8ZSTeRTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5RwoGMEduKE9hnyImx1Q" guid="_5q5RwoGMEduKE9hnyImx1Q" graphEdge="_5q5Rw4GMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeIoGMEduKE9hnyImx1Q" guid="_51BeIoGMEduKE9hnyImx1Q" graphEdge="_51BeI4GMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O-k7kwNmEduYd-55D-Aiqg" guid="_O-k7kwNmEduYd-55D-Aiqg" element="_glbG1QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O-k7lANmEduYd-55D-Aiqg" width="63.0" height="53.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O-rCMANmEduYd-55D-Aiqg" guid="_O-rCMANmEduYd-55D-Aiqg">
-            <property xmi:id="_O-rCMQNmEduYd-55D-Aiqg" guid="_O-rCMQNmEduYd-55D-Aiqg" key="wpCompositeType" value="2"/>
-            <position xmi:id="_O-rCMgNmEduYd-55D-Aiqg" x="209.0" y="725.0"/>
-            <anchorage xmi:id="_O-9WHwNmEduYd-55D-Aiqg" guid="_O-9WHwNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVugNnEduYd-55D-Aiqg" guid="_oHjVugNnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPOgO8EdubhrgDuRb4fA" guid="_D6EPOgO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTOgPMEdubhrgDuRb4fA" guid="_-EfTOgPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTehTUEduFIr9xNbwGyQ" guid="_8ZSTehTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5Rx4GMEduKE9hnyImx1Q" guid="_5q5Rx4GMEduKE9hnyImx1Q" graphEdge="_5q5RxoGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeJ4GMEduKE9hnyImx1Q" guid="_51BeJ4GMEduKE9hnyImx1Q" graphEdge="_51BeJoGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O-rCMwNmEduYd-55D-Aiqg" guid="_O-rCMwNmEduYd-55D-Aiqg" element="_glbG1QMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O-rCNANmEduYd-55D-Aiqg" width="78.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O-xI0ANmEduYd-55D-Aiqg" guid="_O-xI0ANmEduYd-55D-Aiqg">
-            <property xmi:id="_O-xI0QNmEduYd-55D-Aiqg" guid="_O-xI0QNmEduYd-55D-Aiqg" key="wpCompositeType" value="1"/>
-            <position xmi:id="_O-xI0gNmEduYd-55D-Aiqg" x="249.0" y="1.0"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_O-9WIQNmEduYd-55D-Aiqg" guid="_O-9WIQNmEduYd-55D-Aiqg" anchor="_O-9WIANmEduYd-55D-Aiqg"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_oHjVvANnEduYd-55D-Aiqg" guid="_oHjVvANnEduYd-55D-Aiqg" anchor="_oHjVuwNnEduYd-55D-Aiqg"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_D6EPPAO8EdubhrgDuRb4fA" guid="_D6EPPAO8EdubhrgDuRb4fA" anchor="_D6EPOwO8EdubhrgDuRb4fA"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_-EfTPAPMEdubhrgDuRb4fA" guid="_-EfTPAPMEdubhrgDuRb4fA" anchor="_-EfTOwPMEdubhrgDuRb4fA"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_8ZSTfBTUEduFIr9xNbwGyQ" guid="_8ZSTfBTUEduFIr9xNbwGyQ" anchor="_8ZSTexTUEduFIr9xNbwGyQ"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_5q5RyYGMEduKE9hnyImx1Q" guid="_5q5RyYGMEduKE9hnyImx1Q" anchor="_5q5RyIGMEduKE9hnyImx1Q _5q5RyoGMEduKE9hnyImx1Q"/>
-            <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_51BeKYGMEduKE9hnyImx1Q" guid="_51BeKYGMEduKE9hnyImx1Q" anchor="_51BeKIGMEduKE9hnyImx1Q _51BeKoGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_O-9WIANmEduYd-55D-Aiqg" guid="_O-9WIANmEduYd-55D-Aiqg" graphEdge="_O-9WIQNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVuwNnEduYd-55D-Aiqg" guid="_oHjVuwNnEduYd-55D-Aiqg" graphEdge="_oHjVvANnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPOwO8EdubhrgDuRb4fA" guid="_D6EPOwO8EdubhrgDuRb4fA" graphEdge="_D6EPPAO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTOwPMEdubhrgDuRb4fA" guid="_-EfTOwPMEdubhrgDuRb4fA" graphEdge="_-EfTPAPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTexTUEduFIr9xNbwGyQ" guid="_8ZSTexTUEduFIr9xNbwGyQ" graphEdge="_8ZSTfBTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5RyIGMEduKE9hnyImx1Q" guid="_5q5RyIGMEduKE9hnyImx1Q" graphEdge="_5q5RyYGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeKIGMEduKE9hnyImx1Q" guid="_51BeKIGMEduKE9hnyImx1Q" graphEdge="_51BeKYGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O-xI0wNmEduYd-55D-Aiqg" guid="_O-xI0wNmEduYd-55D-Aiqg" element="_glbG1gMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O-xI1ANmEduYd-55D-Aiqg" width="72.0" height="67.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O-9WEANmEduYd-55D-Aiqg" guid="_O-9WEANmEduYd-55D-Aiqg">
-            <property xmi:id="_O-9WEQNmEduYd-55D-Aiqg" guid="_O-9WEQNmEduYd-55D-Aiqg" key="wpCompositeType" value="2"/>
-            <position xmi:id="_O-9WEgNmEduYd-55D-Aiqg" x="249.0" y="161.0"/>
-            <anchorage xmi:id="_O-9WIgNmEduYd-55D-Aiqg" guid="_O-9WIgNmEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_oHjVvQNnEduYd-55D-Aiqg" guid="_oHjVvQNnEduYd-55D-Aiqg"/>
-            <anchorage xmi:id="_D6EPPQO8EdubhrgDuRb4fA" guid="_D6EPPQO8EdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_-EfTPQPMEdubhrgDuRb4fA" guid="_-EfTPQPMEdubhrgDuRb4fA"/>
-            <anchorage xmi:id="_8ZSTfRTUEduFIr9xNbwGyQ" guid="_8ZSTfRTUEduFIr9xNbwGyQ"/>
-            <anchorage xmi:id="_5q5RzYGMEduKE9hnyImx1Q" guid="_5q5RzYGMEduKE9hnyImx1Q" graphEdge="_5q5RzIGMEduKE9hnyImx1Q"/>
-            <anchorage xmi:id="_51BeLYGMEduKE9hnyImx1Q" guid="_51BeLYGMEduKE9hnyImx1Q" graphEdge="_51BeLIGMEduKE9hnyImx1Q"/>
-            <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O-9WEwNmEduYd-55D-Aiqg" guid="_O-9WEwNmEduYd-55D-Aiqg" element="_glbG1gMAEduOAKqB9I73uw"/>
-            <size xmi:id="_O-9WFANmEduYd-55D-Aiqg" width="72.0" height="67.0"/>
-          </contained>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_O8q3OgNmEduYd-55D-Aiqg" guid="_O8q3OgNmEduYd-55D-Aiqg" presentation="Activity Detail" element="_SoXWEQMAEduOAKqB9I73uw"/>
-        </diagrams>
-      </childPackages>
-      <processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_NSW6sQMAEduOAKqB9I73uw" name="Sprint Phase" guid="_NSW6sQMAEduOAKqB9I73uw" briefDescription="Cette phase consiste à dérouler les sprints les uns après les autres " presentationName="Phase des sprints" isPlanned="false" superActivities="_9llsAQAvEdubGMceRDupFQ" linkToPredecessor="_9MP9UAMAEduOAKqB9I73uw" breakdownElements="_SoXWEQMAEduOAKqB9I73uw _zbM2QIGBEduKE9hnyImx1Q _MpXRYIGOEduKE9hnyImx1Q _RHd0YIGOEduKE9hnyImx1Q"/>
-      <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_9MP9UAMAEduOAKqB9I73uw" guid="_9MP9UAMAEduOAKqB9I73uw" linkType="finishToFinish" pred="_37TdkAL_EduOAKqB9I73uw"/>
-      <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_zbM2QIGBEduKE9hnyImx1Q" name="Sprint de release" guid="_zbM2QIGBEduKE9hnyImx1Q" briefDescription="Ce dernier sprint permet de préparer la livraison du produit." presentationName="Travaux de livraison" isPlanned="true" isOptional="true" superActivities="_NSW6sQMAEduOAKqB9I73uw" isRepeatable="true" mandatoryInput="_RHd0YIGOEduKE9hnyImx1Q" output="_RHd0YIGOEduKE9hnyImx1Q" performedPrimarilyBy="_MpXRYIGOEduKE9hnyImx1Q">
-        <presentation xmi:id="-EOwIzNPjfNIjzJ3TRAgeWQ" href="uma://-16dzhVoCex78V2iCDZVx0w#-EOwIzNPjfNIjzJ3TRAgeWQ"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_MpXRYIGOEduKE9hnyImx1Q" name="Team" guid="_MpXRYIGOEduKE9hnyImx1Q" presentationName="Equipe Scrum" hasMultipleOccurrences="true" superActivities="_NSW6sQMAEduOAKqB9I73uw">
-        <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_9apLsPpaEdqsc-f87sBK8A"/>
-      </processElements>
-      <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_RHd0YIGOEduKE9hnyImx1Q" name="Product increment" guid="_RHd0YIGOEduKE9hnyImx1Q" presentationName="Incrément de produit" superActivities="_NSW6sQMAEduOAKqB9I73uw">
-        <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_tCmYEP-xEdqLnajTSLeAsA"/>
-      </processElements>
-      <diagrams xmi:id="_N15QIAMBEduOAKqB9I73uw" guid="_N15QIAMBEduOAKqB9I73uw">
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_N15QIQMBEduOAKqB9I73uw" guid="_N15QIQMBEduOAKqB9I73uw">
-          <position xmi:id="_N15QIgMBEduOAKqB9I73uw" x="204.0" y="49.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_APACQWaOEduYmqfjmBwflA" guid="_APACQWaOEduYmqfjmBwflA" anchor="_APACQGaOEduYmqfjmBwflA _APACQmaOEduYmqfjmBwflA"/>
-          <anchorage xmi:id="__iwAQmaNEduYmqfjmBwflA" guid="__iwAQmaNEduYmqfjmBwflA" graphEdge="__iwAQWaNEduYmqfjmBwflA"/>
-          <anchorage xmi:id="_APACQGaOEduYmqfjmBwflA" guid="_APACQGaOEduYmqfjmBwflA" graphEdge="_APACQWaOEduYmqfjmBwflA">
-            <position xmi:id="_APACQ2aOEduYmqfjmBwflA" x="212.0" y="44.0"/>
-          </anchorage>
-          <anchorage xmi:id="_K_vA8maOEduYmqfjmBwflA" guid="_K_vA8maOEduYmqfjmBwflA" graphEdge="_K_vA8WaOEduYmqfjmBwflA"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_N15QIwMBEduOAKqB9I73uw" guid="_N15QIwMBEduOAKqB9I73uw" element="_SoXWEQMAEduOAKqB9I73uw"/>
-          <size xmi:id="_N15QJAMBEduOAKqB9I73uw" width="40.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_8BvXoGaNEduYmqfjmBwflA" guid="_8BvXoGaNEduYmqfjmBwflA">
-          <position xmi:id="_8BvXoWaNEduYmqfjmBwflA" x="94.0" y="62.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="__iwAQWaNEduYmqfjmBwflA" guid="__iwAQWaNEduYmqfjmBwflA" anchor="__iwAQGaNEduYmqfjmBwflA __iwAQmaNEduYmqfjmBwflA"/>
-          <anchorage xmi:id="__iwAQGaNEduYmqfjmBwflA" guid="__iwAQGaNEduYmqfjmBwflA" graphEdge="__iwAQWaNEduYmqfjmBwflA">
-            <position xmi:id="__iwAQ2aNEduYmqfjmBwflA" x="94.0" y="51.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_8BvXomaNEduYmqfjmBwflA" guid="_8BvXomaNEduYmqfjmBwflA" typeInfo="start node"/>
-          <size xmi:id="_8BvXo2aNEduYmqfjmBwflA" width="19.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_8oyJgGaNEduYmqfjmBwflA" guid="_8oyJgGaNEduYmqfjmBwflA">
-          <position xmi:id="_8oyJgWaNEduYmqfjmBwflA" x="613.0" y="60.0"/>
-          <anchorage xmi:id="_7lIDYoGEEduKE9hnyImx1Q" guid="_7lIDYoGEEduKE9hnyImx1Q" graphEdge="_7lIDYYGEEduKE9hnyImx1Q"/>
-          <anchorage xmi:id="_hKUjEoGFEduKE9hnyImx1Q" guid="_hKUjEoGFEduKE9hnyImx1Q" graphEdge="_hKUjEYGFEduKE9hnyImx1Q"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_8oyJgmaNEduYmqfjmBwflA" guid="_8oyJgmaNEduYmqfjmBwflA" typeInfo="end node"/>
-          <size xmi:id="_8oyJg2aNEduYmqfjmBwflA" width="26.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_9kPFIGaNEduYmqfjmBwflA" guid="_9kPFIGaNEduYmqfjmBwflA">
-          <position xmi:id="_9kPFIWaNEduYmqfjmBwflA" x="343.0" y="60.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_K_vA8WaOEduYmqfjmBwflA" guid="_K_vA8WaOEduYmqfjmBwflA" anchor="_K_vA8GaOEduYmqfjmBwflA _K_vA8maOEduYmqfjmBwflA">
-            <waypoints xmi:id="_R-7AoGaOEduYmqfjmBwflA" x="363.0" y="17.0"/>
-            <waypoints xmi:id="_QXWl4GaOEduYmqfjmBwflA" x="222.0" y="17.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_a2plkYGFEduKE9hnyImx1Q" guid="_a2plkYGFEduKE9hnyImx1Q" anchor="_a2plkIGFEduKE9hnyImx1Q _a2plkoGFEduKE9hnyImx1Q">
-            <waypoints xmi:id="_DyIEkIGGEduKE9hnyImx1Q" x="363.0" y="133.0"/>
-          </contained>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_hKUjEYGFEduKE9hnyImx1Q" guid="_hKUjEYGFEduKE9hnyImx1Q" anchor="_hKUjEIGFEduKE9hnyImx1Q _hKUjEoGFEduKE9hnyImx1Q">
-            <waypoints xmi:id="_9g1ssIGFEduKE9hnyImx1Q" x="575.0" y="71.0"/>
-          </contained>
-          <anchorage xmi:id="_APACQmaOEduYmqfjmBwflA" guid="_APACQmaOEduYmqfjmBwflA" graphEdge="_APACQWaOEduYmqfjmBwflA">
-            <position xmi:id="_APACRGaOEduYmqfjmBwflA" x="0.0" y="11.0"/>
-          </anchorage>
-          <anchorage xmi:id="_K_vA8GaOEduYmqfjmBwflA" guid="_K_vA8GaOEduYmqfjmBwflA" graphEdge="_K_vA8WaOEduYmqfjmBwflA">
-            <position xmi:id="_K_vA82aOEduYmqfjmBwflA" x="21.0" y="0.0"/>
-          </anchorage>
-          <anchorage xmi:id="_a2plkIGFEduKE9hnyImx1Q" guid="_a2plkIGFEduKE9hnyImx1Q" graphEdge="_a2plkYGFEduKE9hnyImx1Q">
-            <position xmi:id="_Ais7MIGGEduKE9hnyImx1Q" x="21.0" y="23.0"/>
-          </anchorage>
-          <anchorage xmi:id="_hKUjEIGFEduKE9hnyImx1Q" guid="_hKUjEIGFEduKE9hnyImx1Q" graphEdge="_hKUjEYGFEduKE9hnyImx1Q">
-            <position xmi:id="_9C4lYIGFEduKE9hnyImx1Q" x="42.0" y="11.0"/>
-          </anchorage>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_9kPFImaNEduYmqfjmBwflA" guid="_9kPFImaNEduYmqfjmBwflA" typeInfo="decision node"/>
-          <size xmi:id="_9kPFI2aNEduYmqfjmBwflA" width="43.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_-UpVwHoSEduJVrY6eKG_mw" name="Add Free Text" guid="_-UpVwHoSEduJVrY6eKG_mw">
-          <property xmi:id="_-UpVwXoSEduJVrY6eKG_mw" guid="_-UpVwXoSEduJVrY6eKG_mw" key="free text" value="livraison à préparer"/>
-          <position xmi:id="_-UpVwnoSEduJVrY6eKG_mw" x="377.0" y="102.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_-UpVw3oSEduJVrY6eKG_mw" guid="_-UpVw3oSEduJVrY6eKG_mw" typeInfo="free text"/>
-          <size xmi:id="_-UpVxHoSEduJVrY6eKG_mw" width="69.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_O1l_kHoTEduJVrY6eKG_mw" name="Add Free Text" guid="_O1l_kHoTEduJVrY6eKG_mw">
-          <property xmi:id="_O1l_kXoTEduJVrY6eKG_mw" guid="_O1l_kXoTEduJVrY6eKG_mw" key="free text" value="encore un sprint"/>
-          <position xmi:id="_O1l_knoTEduJVrY6eKG_mw" x="237.0" y="0.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_O1l_k3oTEduJVrY6eKG_mw" guid="_O1l_k3oTEduJVrY6eKG_mw" typeInfo="free text"/>
-          <size xmi:id="_O1l_lHoTEduJVrY6eKG_mw" width="79.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_4SofQIGBEduKE9hnyImx1Q" guid="_4SofQIGBEduKE9hnyImx1Q">
-          <position xmi:id="_4SofQYGBEduKE9hnyImx1Q" x="457.0" y="104.0"/>
-          <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_7lIDYYGEEduKE9hnyImx1Q" guid="_7lIDYYGEEduKE9hnyImx1Q" anchor="_7lIDYIGEEduKE9hnyImx1Q _7lIDYoGEEduKE9hnyImx1Q">
-            <waypoints xmi:id="_FGeBUIGGEduKE9hnyImx1Q" x="626.0" y="133.0"/>
-          </contained>
-          <anchorage xmi:id="_7lIDYIGEEduKE9hnyImx1Q" guid="_7lIDYIGEEduKE9hnyImx1Q" graphEdge="_7lIDYYGEEduKE9hnyImx1Q">
-            <position xmi:id="_7lIDY4GEEduKE9hnyImx1Q" x="509.0" y="67.0"/>
-          </anchorage>
-          <anchorage xmi:id="_a2plkoGFEduKE9hnyImx1Q" guid="_a2plkoGFEduKE9hnyImx1Q" graphEdge="_a2plkYGFEduKE9hnyImx1Q"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_4SofQoGBEduKE9hnyImx1Q" guid="_4SofQoGBEduKE9hnyImx1Q" element="_zbM2QIGBEduKE9hnyImx1Q"/>
-          <size xmi:id="_4SofQ4GBEduKE9hnyImx1Q" width="82.0" height="-1.0"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_JYpoMIGGEduKE9hnyImx1Q" name="Add Free Text" guid="_JYpoMIGGEduKE9hnyImx1Q">
-          <property xmi:id="_JYpoMYGGEduKE9hnyImx1Q" guid="_JYpoMYGGEduKE9hnyImx1Q" key="free text" value="fin de release"/>
-          <position xmi:id="_JYpoMoGGEduKE9hnyImx1Q" x="457.0" y="54.0"/>
-          <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_JYpoM4GGEduKE9hnyImx1Q" guid="_JYpoM4GGEduKE9hnyImx1Q" typeInfo="free text"/>
-          <size xmi:id="_JYpoNIGGEduKE9hnyImx1Q" width="66.0" height="-1.0"/>
-        </contained>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_N15QJQMBEduOAKqB9I73uw" guid="_N15QJQMBEduOAKqB9I73uw" presentation="Workflow" element="_NSW6sQMAEduOAKqB9I73uw"/>
-      </diagrams>
-    </childPackages>
-    <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_E1ptMIF9EduKE9hnyImx1Q" guid="_E1ptMIF9EduKE9hnyImx1Q" linkType="finishToFinish" pred="_NSW6sQMAEduOAKqB9I73uw"/>
-    <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_XJr8krPCEduk5O8SjA21Fg" name="Product Owner" guid="_XJr8krPCEduk5O8SjA21Fg" suppressed="true" presentationName="Directeur Produit" superActivities="_9llsAQAvEdubGMceRDupFQ">
-      <Role href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_ICJyYPpaEdqsc-f87sBK8A"/>
-    </processElements>
-    <diagrams xmi:id="_kZvAwAChEduhO59Otqg2rw" guid="_kZvAwAChEduhO59Otqg2rw">
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_kZvAwQChEduhO59Otqg2rw" guid="_kZvAwQChEduhO59Otqg2rw">
-        <position xmi:id="_kZvAwgChEduhO59Otqg2rw" x="124.0" y="57.0"/>
-        <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_mj1g0QChEduhO59Otqg2rw" guid="_mj1g0QChEduhO59Otqg2rw" anchor="_mj1g0AChEduhO59Otqg2rw _mj1g0gChEduhO59Otqg2rw">
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_mkBuEQChEduhO59Otqg2rw" guid="_mkBuEQChEduhO59Otqg2rw"/>
-        </contained>
-        <anchorage xmi:id="_mj1g0AChEduhO59Otqg2rw" guid="_mj1g0AChEduhO59Otqg2rw" graphEdge="_mj1g0QChEduhO59Otqg2rw">
-          <position xmi:id="_mj1g0wChEduhO59Otqg2rw" x="158.0" y="73.0"/>
-        </anchorage>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_kZvAwwChEduhO59Otqg2rw" guid="_kZvAwwChEduhO59Otqg2rw"/>
-        <size xmi:id="_kZvAxAChEduhO59Otqg2rw" width="55.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_kZvAxQChEduhO59Otqg2rw" guid="_kZvAxQChEduhO59Otqg2rw">
-        <position xmi:id="_kZvAxgChEduhO59Otqg2rw" x="340.0" y="57.0"/>
-        <anchorage xmi:id="_mj1g0gChEduhO59Otqg2rw" guid="_mj1g0gChEduhO59Otqg2rw" graphEdge="_mj1g0QChEduhO59Otqg2rw"/>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_kZvAxwChEduhO59Otqg2rw" guid="_kZvAxwChEduhO59Otqg2rw"/>
-        <size xmi:id="_kZvAyAChEduhO59Otqg2rw" width="62.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_Ew8_sACiEduhO59Otqg2rw" name="Add Free Text" guid="_Ew8_sACiEduhO59Otqg2rw">
-        <property xmi:id="_Ew8_sQCiEduhO59Otqg2rw" guid="_Ew8_sQCiEduhO59Otqg2rw" key="free text" value="les sprints successifs qui constituent la release"/>
-        <position xmi:id="_Ew8_sgCiEduhO59Otqg2rw" x="299.0" y="87.0"/>
-        <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_Ew8_swCiEduhO59Otqg2rw" guid="_Ew8_swCiEduhO59Otqg2rw" typeInfo="free text"/>
-        <size xmi:id="_Ew8_tACiEduhO59Otqg2rw" width="86.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_Nk0CAACiEduhO59Otqg2rw" name="Add Free Text" guid="_Nk0CAACiEduhO59Otqg2rw">
-        <property xmi:id="_Nk6IoACiEduhO59Otqg2rw" guid="_Nk6IoACiEduhO59Otqg2rw" key="free text" value="Phase initiale avant le premier sprint"/>
-        <position xmi:id="_Nk6IoQCiEduhO59Otqg2rw" x="134.0" y="89.0"/>
-        <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_Nk6IogCiEduhO59Otqg2rw" guid="_Nk6IogCiEduhO59Otqg2rw" typeInfo="free text"/>
-        <size xmi:id="_Nk6IowCiEduhO59Otqg2rw" width="72.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_G5YwkAEKEduzRosbOajx7w" guid="_G5YwkAEKEduzRosbOajx7w">
-        <position xmi:id="_G5e3MAEKEduzRosbOajx7w" x="109.0" y="43.0"/>
-        <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_Ivhy0QEKEduzRosbOajx7w" guid="_Ivhy0QEKEduzRosbOajx7w" anchor="_Ivhy0AEKEduzRosbOajx7w _Ivhy0gEKEduzRosbOajx7w">
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_Iv0GsQEKEduzRosbOajx7w" guid="_Iv0GsQEKEduzRosbOajx7w"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_ZSAOMQEsEduzRosbOajx7w" guid="_ZSAOMQEsEduzRosbOajx7w" anchor="_ZSAOMAEsEduzRosbOajx7w _ZSAOMgEsEduzRosbOajx7w">
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_ZSSiEQEsEduzRosbOajx7w" guid="_ZSSiEQEsEduzRosbOajx7w"/>
-        </contained>
-        <anchorage xmi:id="_Ivhy0AEKEduzRosbOajx7w" guid="_Ivhy0AEKEduzRosbOajx7w" graphEdge="_Ivhy0QEKEduzRosbOajx7w">
-          <position xmi:id="_Ivhy0wEKEduzRosbOajx7w" x="152.0" y="58.0"/>
-        </anchorage>
-        <anchorage xmi:id="_ZSAOMAEsEduzRosbOajx7w" guid="_ZSAOMAEsEduzRosbOajx7w" graphEdge="_ZSAOMQEsEduzRosbOajx7w">
-          <position xmi:id="_ZSAOMwEsEduzRosbOajx7w" x="135.0" y="60.0"/>
-        </anchorage>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_G5e3MQEKEduzRosbOajx7w" guid="_G5e3MQEKEduzRosbOajx7w"/>
-        <size xmi:id="_G5e3MgEKEduzRosbOajx7w" width="55.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_G5e3MwEKEduzRosbOajx7w" guid="_G5e3MwEKEduzRosbOajx7w">
-        <position xmi:id="_G5e3NAEKEduzRosbOajx7w" x="337.0" y="41.0"/>
-        <anchorage xmi:id="_Ivhy0gEKEduzRosbOajx7w" guid="_Ivhy0gEKEduzRosbOajx7w" graphEdge="_Ivhy0QEKEduzRosbOajx7w"/>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_G5e3NQEKEduzRosbOajx7w" guid="_G5e3NQEKEduzRosbOajx7w"/>
-        <size xmi:id="_G5e3NgEKEduzRosbOajx7w" width="83.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_GOyb8AEsEduzRosbOajx7w" guid="_GOyb8AEsEduzRosbOajx7w">
-        <position xmi:id="_GOyb8QEsEduzRosbOajx7w" x="359.0" y="43.0"/>
-        <anchorage xmi:id="_ZSAOMgEsEduzRosbOajx7w" guid="_ZSAOMgEsEduzRosbOajx7w" graphEdge="_ZSAOMQEsEduzRosbOajx7w"/>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_GOyb8gEsEduzRosbOajx7w" guid="_GOyb8gEsEduzRosbOajx7w"/>
-        <size xmi:id="_GOyb8wEsEduzRosbOajx7w" width="32.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_6wY-4AMAEduOAKqB9I73uw" guid="_6wY-4AMAEduOAKqB9I73uw">
-        <position xmi:id="_6wY-4QMAEduOAKqB9I73uw" x="112.0" y="25.0"/>
-        <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_9LxcMQMAEduOAKqB9I73uw" guid="_9LxcMQMAEduOAKqB9I73uw" anchor="_9LxcMAMAEduOAKqB9I73uw _9LxcMgMAEduOAKqB9I73uw">
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_9MP9UQMAEduOAKqB9I73uw" guid="_9MP9UQMAEduOAKqB9I73uw"/>
-        </contained>
-        <anchorage xmi:id="_9LxcMAMAEduOAKqB9I73uw" guid="_9LxcMAMAEduOAKqB9I73uw" graphEdge="_9LxcMQMAEduOAKqB9I73uw">
-          <position xmi:id="_9LxcMwMAEduOAKqB9I73uw" x="151.0" y="42.0"/>
-        </anchorage>
-        <anchorage xmi:id="_D3KWIgMBEduOAKqB9I73uw" guid="_D3KWIgMBEduOAKqB9I73uw" graphEdge="_D3KWIQMBEduOAKqB9I73uw"/>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_6wY-4gMAEduOAKqB9I73uw" guid="_6wY-4gMAEduOAKqB9I73uw" element="_37TdkAL_EduOAKqB9I73uw"/>
-        <size xmi:id="_6wY-4wMAEduOAKqB9I73uw" width="103.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_6wY-5AMAEduOAKqB9I73uw" guid="_6wY-5AMAEduOAKqB9I73uw">
-        <position xmi:id="_6wY-5QMAEduOAKqB9I73uw" x="295.0" y="25.0"/>
-        <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_EPaeEQMBEduOAKqB9I73uw" guid="_EPaeEQMBEduOAKqB9I73uw" anchor="_EPaeEAMBEduOAKqB9I73uw">
-          <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_E1ptMYF9EduKE9hnyImx1Q" guid="_E1ptMYF9EduKE9hnyImx1Q"/>
-        </contained>
-        <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_DVQF4YGHEduKE9hnyImx1Q" guid="_DVQF4YGHEduKE9hnyImx1Q" anchor="_DVQF4IGHEduKE9hnyImx1Q _DVQF4oGHEduKE9hnyImx1Q"/>
-        <anchorage xmi:id="_9LxcMgMAEduOAKqB9I73uw" guid="_9LxcMgMAEduOAKqB9I73uw" graphEdge="_9LxcMQMAEduOAKqB9I73uw"/>
-        <anchorage xmi:id="_EPaeEAMBEduOAKqB9I73uw" guid="_EPaeEAMBEduOAKqB9I73uw" graphEdge="_EPaeEQMBEduOAKqB9I73uw">
-          <position xmi:id="_EPaeEwMBEduOAKqB9I73uw" x="340.0" y="44.0"/>
-        </anchorage>
-        <anchorage xmi:id="_DVQF4IGHEduKE9hnyImx1Q" guid="_DVQF4IGHEduKE9hnyImx1Q" graphEdge="_DVQF4YGHEduKE9hnyImx1Q">
-          <position xmi:id="_ENbrEIGHEduKE9hnyImx1Q" x="343.0" y="41.0"/>
-        </anchorage>
-        <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_6wY-5gMAEduOAKqB9I73uw" guid="_6wY-5gMAEduOAKqB9I73uw" element="_NSW6sQMAEduOAKqB9I73uw"/>
-        <size xmi:id="_6wY-5wMAEduOAKqB9I73uw" width="87.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_CL_00AMBEduOAKqB9I73uw" guid="_CL_00AMBEduOAKqB9I73uw">
-        <position xmi:id="_CL_00QMBEduOAKqB9I73uw" x="39.0" y="38.0"/>
-        <contained xsi:type="org.eclipse.epf.uma:GraphEdge" xmi:id="_D3KWIQMBEduOAKqB9I73uw" guid="_D3KWIQMBEduOAKqB9I73uw" anchor="_D3KWIAMBEduOAKqB9I73uw _D3KWIgMBEduOAKqB9I73uw"/>
-        <anchorage xmi:id="_D3KWIAMBEduOAKqB9I73uw" guid="_D3KWIAMBEduOAKqB9I73uw" graphEdge="_D3KWIQMBEduOAKqB9I73uw">
-          <position xmi:id="_D3KWIwMBEduOAKqB9I73uw" x="46.0" y="44.0"/>
-        </anchorage>
-        <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_CL_00gMBEduOAKqB9I73uw" guid="_CL_00gMBEduOAKqB9I73uw" typeInfo="start node"/>
-        <size xmi:id="_CL_00wMBEduOAKqB9I73uw" width="20.0" height="-1.0"/>
-      </contained>
-      <contained xsi:type="org.eclipse.epf.uma:GraphNode" xmi:id="_DDxxYAMBEduOAKqB9I73uw" guid="_DDxxYAMBEduOAKqB9I73uw">
-        <position xmi:id="_DD34AAMBEduOAKqB9I73uw" x="456.0" y="36.0"/>
-        <anchorage xmi:id="_DVQF4oGHEduKE9hnyImx1Q" guid="_DVQF4oGHEduKE9hnyImx1Q" graphEdge="_DVQF4YGHEduKE9hnyImx1Q"/>
-        <semanticModel xsi:type="org.eclipse.epf.uma:SimpleSemanticModelElement" xmi:id="_DD34AQMBEduOAKqB9I73uw" guid="_DD34AQMBEduOAKqB9I73uw" typeInfo="end node"/>
-        <size xmi:id="_DD34AgMBEduOAKqB9I73uw" width="24.0" height="-1.0"/>
-      </contained>
-      <semanticModel xsi:type="org.eclipse.epf.uma:UMASemanticModelBridge" xmi:id="_kZvAyQChEduhO59Otqg2rw" guid="_kZvAyQChEduhO59Otqg2rw" presentation="Workflow" element="_9llsAQAvEdubGMceRDupFQ"/>
-    </diagrams>
-    <process xsi:type="org.eclipse.epf.uma:DeliveryProcess" xmi:id="_9llsAQAvEdubGMceRDupFQ" name="Scrum" guid="_9llsAQAvEdubGMceRDupFQ" briefDescription="Les phases, les sprints et les tâches à dérouler lors de la production d'une release." presentationName="Release" isRepeatable="true" breakdownElements="_37TdkAL_EduOAKqB9I73uw _NSW6sQMAEduOAKqB9I73uw _XJr8krPCEduk5O8SjA21Fg">
-      <presentation xmi:id="-16dzhVoCex78V2iCDZVx0w" href="uma://-16dzhVoCex78V2iCDZVx0w#-16dzhVoCex78V2iCDZVx0w"/>
-      <concepts href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_XtRuYP-zEdqLnajTSLeAsA"/>
-      <defaultContext href="uma://_hDRYYPpYEdqsc-f87sBK8A#_IqDLgP_OEdqtbrr0B1TG-A"/>
-      <validContext href="uma://_hDRYYPpYEdqsc-f87sBK8A#_IqDLgP_OEdqtbrr0B1TG-A"/>
-    </process>
-  </org.eclipse.epf.uma:ProcessComponent>
-</xmi:XMI>
diff --git a/Scrum French/Scrum/deliveryprocesses/resources/csm.jpg b/Scrum French/Scrum/deliveryprocesses/resources/csm.jpg
deleted file mode 100644
index 18cd417..0000000
--- a/Scrum French/Scrum/deliveryprocesses/resources/csm.jpg
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.gif b/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.gif
deleted file mode 100644
index e7d73b3..0000000
--- a/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.gif
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.jpg b/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.jpg
deleted file mode 100644
index bc69128..0000000
--- a/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.jpg
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.png b/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.png
deleted file mode 100644
index a91525c..0000000
--- a/Scrum French/Scrum/deliveryprocesses/resources/icescrum_simple.png
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/disciplines/Scrum activities.xmi b/Scrum French/Scrum/disciplines/Scrum activities.xmi
deleted file mode 100644
index 48a8e24..0000000
--- a/Scrum French/Scrum/disciplines/Scrum activities.xmi
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-4wqJQ0qXLYZ8kCnpDu--tA" name="Scrum activities,_6sdMAAL-EduOAKqB9I73uw" guid="-4wqJQ0qXLYZ8kCnpDu--tA" changeDate="2006-12-03T10:43:16.000+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    L'application de Scrum concerne essentiellement&amp;nbsp;les disciplines habituelles de gestion de projet et de gestion des
-    exigences.
-&lt;/p&gt;</mainDescription>
-  <keyConsiderations>Une bonne partie de ces activités est effectuée collectivement,&amp;nbsp;en équipe.</keyConsiderations>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/concepts/Presentation Scrum.xmi b/Scrum French/Scrum/guidances/concepts/Presentation Scrum.xmi
deleted file mode 100644
index b707be0..0000000
--- a/Scrum French/Scrum/guidances/concepts/Presentation Scrum.xmi
+++ /dev/null
@@ -1,81 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-MSO8KF-0IlKZJGnSwwTNZA" name="new_concept,_3WivIBTQEduFIr9xNbwGyQ" guid="-MSO8KF-0IlKZJGnSwwTNZA" changeDate="2006-12-03T08:21:54.843+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Scrum est un processus léger et itératif de gestion de projets, qui fait partie de la famille des &lt;a
-    title=&quot;Méthode agile&quot; href=&quot;http://fr.wikipedia.org/wiki/Méthode_agile&quot;&gt;méthodes agiles&lt;/a&gt;, qui partage les valeurs
-    définies dans le Manifeste Agile et qui en reprend les principes fondamentaux.
-&lt;/p&gt;
-&lt;h5&gt;
-    Résumé
-&lt;/h5&gt;
-&lt;p&gt;
-    Scrum peut se résumer ainsi :
-&lt;/p&gt;
-&lt;p class=&quot;quote&quot;&gt;
-    Scrum conduit à montrer souvent et régulièrement (toutes les 2 à 4 semaines, selon la durée du &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../../Scrum/guidances/termdefinitions/Sprint,_kftWoIHqEduFs9jH8xc4xw.html&quot;
-    guid=&quot;_kftWoIHqEduFs9jH8xc4xw&quot;&gt;Sprint&lt;/a&gt;) un produit (partiel) qui fonctionne. Le métier identifie les exigences et
-    définit leur priorité. L'équipe s'organise elle-même pour déterminer la meilleure façon de produire les exigences les
-    plus prioritaires. A chaque fin de sprint, tout le monde peut voir fonctionner le produit actuel et contribuer à
-    prendre une décision sur ce qu'on fait&amp;nbsp;: soit le livrer dans l'état, soit continuer à l'améliorer pendant&amp;nbsp;un
-    sprint&amp;nbsp;supplémentaire avant de se reposer la question.
-&lt;/p&gt;
-&lt;h5&gt;
-    Origine
-&lt;/h5&gt;
-&lt;p&gt;
-    Le terme Scrum est emprunté au rugby et signifie mêlée. Ce processus s'articule en effet autour d'une équipe soudée,
-    qui cherche à atteindre un but, comme c'est le cas au rugby quand le pack déploie sa force collective pour avancer avec
-    le ballon pendant une mêlée.
-&lt;/p&gt;
-&lt;p&gt;
-    Scrum insiste particulièrement sur l’aspect social et collectif du développement. Le but de Scrum est d'améliorer la
-    qualité et la productivité, avec une approche empirique, en s'appuyant sur l'autonomie de l'équipe.
-&lt;/p&gt;
-&lt;h5&gt;
-    Empirisme
-&lt;/h5&gt;
-&lt;p&gt;
-    Un processus empirique, donc basé sur l'expérience, nécessite une bonne visibilité, des inspections fréquentes et des
-    adaptations aux plans. Cela se décline dans Scrum par les 2 cycles de régulation&amp;nbsp;:
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        lors de mêlées quotidiennes, on tient compte de l'expérience du jour passé pour adapter le planning des jours
-        restant dans le sprint.
-    &lt;/li&gt;
-    &lt;li&gt;
-        lors des revues de sprint, on tient compte de l'expérience du sprint passé pour adapter le planning de la release,
-        portant sur les sprints à venir.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    Les tâches d'un sprint ne sont pas définies de façon très précise : pas de date de début, pas de date de fin, pas de
-    dépendance. Scrum considère que ce n'est pas prévisible. L'empirisme de Scrum consiste à s'appuyer continuellement sur
-    l'analyse de l'état courant du projet pour contrôler le processus et réduire les risques.
-&lt;/p&gt;
-&lt;h5&gt;
-    Portée
-&lt;/h5&gt;
-&lt;p&gt;
-    Scrum ne décrit pas toutes les disciplines du développement (analyse, conception, codage, test) et doit être considéré,
-    plutôt qu’un processus complet, comme un pattern de processus qui est&amp;nbsp;concerne la gestion de projet et la gestion
-    des exigences. Scrum ne fournit pas d’aide pour la réalisation des activités techniques du développement. C'est à
-    l'équipe de définir elle-même ce qu'elle à faire.
-&lt;/p&gt;
-&lt;h5&gt;
-    Diffusion
-&lt;/h5&gt;
-&lt;p&gt;
-    Scrum existe depuis les années 90 et connaît une popularité croissante depuis quelques années. Il a été utilisé sur des
-    centaines de projets dans le monde, mais est pour l’instant peu introduit en France. Depuis 3 ans, un processus de
-    certification a été mis en place. En novembre 2006, plus de 7000 personnes avaient obtenu la certification ScrumMaster.
-&lt;/p&gt;
-&lt;p&gt;
-    &amp;nbsp;&lt;img height=&quot;56&quot; alt=&quot;ScrumMaster&quot; src=&quot;./resources/csm.jpg&quot; width=&quot;179&quot; /&gt;
-&lt;/p&gt;
-&lt;p&gt;
-    Pour plus d'informations sur Scrum, voir &lt;a href=&quot;http://fr.wikipedia.org/wiki/Scrum&quot;
-    target=&quot;_blank&quot;&gt;http://fr.wikipedia.org/wiki/Scrum&lt;/a&gt;
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/concepts/Produit, release et sprint.xmi b/Scrum French/Scrum/guidances/concepts/Produit, release et sprint.xmi
deleted file mode 100644
index 6d73875..0000000
--- a/Scrum French/Scrum/guidances/concepts/Produit, release et sprint.xmi
+++ /dev/null
@@ -1,37 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-BPz1k8sC6CCyJ2yZCc1p2Q" name="Produit, release et sprint,_XtRuYP-zEdqLnajTSLeAsA" guid="-BPz1k8sC6CCyJ2yZCc1p2Q" changeDate="2006-12-02T00:54:40.221+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Une &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/guidances/termdefinitions/Release,_AIB9gIHrEduFs9jH8xc4xw.html&quot;
-    guid=&quot;_AIB9gIHrEduFs9jH8xc4xw&quot;&gt;Release&lt;/a&gt;&amp;nbsp;est constituée d'une série de &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../../Scrum/guidances/termdefinitions/Sprint,_kftWoIHqEduFs9jH8xc4xw.html&quot;
-    guid=&quot;_kftWoIHqEduFs9jH8xc4xw&quot;&gt;Sprint&lt;/a&gt;s et dure en général quelques mois. Pendant la vie d'un produit, on déroule
-    plusieurs releases.
-&lt;/p&gt;
-&lt;p&gt;
-    &lt;img height=&quot;115&quot; alt=&quot;release et sprints&quot; src=&quot;./resources/release.jpg&quot; width=&quot;600&quot; /&gt;
-&lt;/p&gt;
-&lt;p&gt;
-    Une release a les attributs suivants :
-&lt;/p&gt;
-&lt;ul class=&quot;noindent&quot;&gt;
-    &lt;li&gt;
-        le but
-    &lt;/li&gt;
-    &lt;li&gt;
-        le type, à choisir entre &quot;à date fixée&quot; et &quot;sans date fixée&quot;(par défaut). Dans le cas où on choisit à date fixée,
-        la date est fournie.
-    &lt;/li&gt;
-    &lt;li&gt;
-        la durée, en nombre de jours, définie pour les sprints
-    &lt;/li&gt;
-    &lt;li&gt;
-        le nombre de sprints&amp;nbsp;prévus
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    Le &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/guidances/reports/Release Planning,_Z2NzkIGWEduKE9hnyImx1Q.html&quot;
-    guid=&quot;_Z2NzkIGWEduKE9hnyImx1Q&quot;&gt;Planning de la release&lt;/a&gt;&amp;nbsp;constitue un niveau de planification du projet : il
-    montre de façon &quot;grosses mailles&quot; les items qu'il est prévu de réaliser au cours des sprints de cette release.&lt;br /&gt;
-    &lt;br /&gt;
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/concepts/Travail collaboratif.xmi b/Scrum French/Scrum/guidances/concepts/Travail collaboratif.xmi
deleted file mode 100644
index 55eac7a..0000000
--- a/Scrum French/Scrum/guidances/concepts/Travail collaboratif.xmi
+++ /dev/null
@@ -1,134 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-dU_t9olFRQIyOBZQvMndKg" name="new_concept,_OUjj0AEZEduzRosbOajx7w" guid="-dU_t9olFRQIyOBZQvMndKg" changeDate="2006-12-04T21:17:26.750+0100">
-  <mainDescription>&lt;p&gt;
-    Le collectif prend forme à travers des réunions. Scrum impose 5 types de réunions :&amp;nbsp;
-&lt;/p&gt;
-&lt;ol&gt;
-    &lt;li&gt;
-        Réunion pour &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/tasks/Plan sprint,_4LOggPpaEdqsc-f87sBK8A.html&quot;
-        guid=&quot;_4LOggPpaEdqsc-f87sBK8A&quot;&gt;Planifier le sprint&lt;/a&gt;&amp;nbsp;(1ème partie, sélection du sous-ensemble du backlog))
-    &lt;/li&gt;
-    &lt;li&gt;
-        Réunion pour &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/tasks/Plan sprint,_4LOggPpaEdqsc-f87sBK8A.html&quot;
-        guid=&quot;_4LOggPpaEdqsc-f87sBK8A&quot;&gt;Planifier le sprint&lt;/a&gt;nt (2ème&amp;nbsp;partie, planification du sprint)
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/tasks/Scrum daily meeting,_d09LYP_AEdqtbrr0B1TG-A.html&quot;
-        guid=&quot;_d09LYP_AEdqtbrr0B1TG-A&quot;&gt;Mêlée quotidienne&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        Réunion pour &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/tasks/Review sprint,_MRrRYPpbEdqsc-f87sBK8A.html&quot;
-        guid=&quot;_MRrRYPpbEdqsc-f87sBK8A&quot;&gt;Faire la revue du sprint&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/tasks/Retrospective,_J_sRIP_AEdqtbrr0B1TG-A.html&quot;
-        guid=&quot;_J_sRIP_AEdqtbrr0B1TG-A&quot;&gt;Rétrospective&lt;/a&gt;&lt;br /&gt;
-    &lt;/li&gt;
-&lt;/ol&gt;
-&lt;p&gt;
-    Le tableau ci-dessous montre la participation des rôles Scrum à ces réunions :&lt;br /&gt;
-&lt;/p&gt;
-&lt;table cellspacing=&quot;2&quot; cellpadding=&quot;2&quot; width=&quot;180&quot; border=&quot;1&quot;&gt;
-    &lt;tbody&gt;
-        &lt;tr&gt;
-            &lt;th scope=&quot;col&quot;&gt;
-            &lt;/th&gt;
-            &lt;th scope=&quot;col&quot;&gt;
-                1
-            &lt;/th&gt;
-            &lt;th scope=&quot;col&quot;&gt;
-                2
-            &lt;/th&gt;
-            &lt;th scope=&quot;col&quot;&gt;
-                3
-            &lt;/th&gt;
-            &lt;th scope=&quot;col&quot;&gt;
-                4
-            &lt;/th&gt;
-            &lt;th scope=&quot;col&quot;&gt;
-                5
-            &lt;/th&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;th scope=&quot;row&quot;&gt;
-                &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/roles/ScrumMaster,_t1K9kPpYEdqsc-f87sBK8A.html&quot;
-                guid=&quot;_t1K9kPpYEdqsc-f87sBK8A&quot;&gt;ScrumMaster&lt;/a&gt; 
-            &lt;/th&gt;
-            &lt;td&gt;
-                Obligatoire
-            &lt;/td&gt;
-            &lt;td&gt;
-                Animation
-            &lt;/td&gt;
-            &lt;td&gt;
-                Animation
-            &lt;/td&gt;
-            &lt;td&gt;
-                Obligatoire
-            &lt;/td&gt;
-            &lt;td&gt;
-                Animation
-            &lt;/td&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;th scope=&quot;row&quot;&gt;
-                &lt;a class=&quot;elementLink&quot; href=&quot;./../../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot;
-                guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Directeur Produit&lt;/a&gt; 
-            &lt;/th&gt;
-            &lt;td&gt;
-                Animation
-            &lt;/td&gt;
-            &lt;td&gt;
-                Souhaitée
-            &lt;/td&gt;
-            &lt;td&gt;
-                Souhaitée
-            &lt;/td&gt;
-            &lt;td&gt;
-                Obligatoire
-            &lt;/td&gt;
-            &lt;td&gt;
-                Souhaitée
-            &lt;/td&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;th scope=&quot;row&quot;&gt;
-                Equipe
-            &lt;/th&gt;
-            &lt;td&gt;
-                Obligatoire
-            &lt;/td&gt;
-            &lt;td&gt;
-                Obligatoire
-            &lt;/td&gt;
-            &lt;td&gt;
-                Obligatoire
-            &lt;/td&gt;
-            &lt;td&gt;
-                Animation
-            &lt;/td&gt;
-            &lt;td&gt;
-                Obligatoire
-            &lt;/td&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;th scope=&quot;row&quot;&gt;
-                Intervenant
-            &lt;/th&gt;
-            &lt;td&gt;
-            &lt;/td&gt;
-            &lt;td&gt;
-            &lt;/td&gt;
-            &lt;td&gt;
-                Possible
-            &lt;/td&gt;
-            &lt;td&gt;
-                Souhaitée
-            &lt;/td&gt;
-            &lt;td&gt;
-            &lt;/td&gt;
-        &lt;/tr&gt;
-    &lt;/tbody&gt;
-&lt;/table&gt;
-&lt;br /&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/concepts/resources/clip_image001.png b/Scrum French/Scrum/guidances/concepts/resources/clip_image001.png
deleted file mode 100644
index 32678ac..0000000
--- a/Scrum French/Scrum/guidances/concepts/resources/clip_image001.png
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/guidances/concepts/resources/clip_image002.gif b/Scrum French/Scrum/guidances/concepts/resources/clip_image002.gif
deleted file mode 100644
index aa6b057..0000000
--- a/Scrum French/Scrum/guidances/concepts/resources/clip_image002.gif
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/guidances/concepts/resources/csm.jpg b/Scrum French/Scrum/guidances/concepts/resources/csm.jpg
deleted file mode 100644
index 18cd417..0000000
--- a/Scrum French/Scrum/guidances/concepts/resources/csm.jpg
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/guidances/concepts/resources/release.jpg b/Scrum French/Scrum/guidances/concepts/resources/release.jpg
deleted file mode 100644
index a270cd4..0000000
--- a/Scrum French/Scrum/guidances/concepts/resources/release.jpg
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/guidances/examples/resources/demo_banque_2.JPG b/Scrum French/Scrum/guidances/examples/resources/demo_banque_2.JPG
deleted file mode 100644
index 046308b..0000000
--- a/Scrum French/Scrum/guidances/examples/resources/demo_banque_2.JPG
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/guidances/reports/Release Burndown Chart.xmi b/Scrum French/Scrum/guidances/reports/Release Burndown Chart.xmi
deleted file mode 100644
index 434f1c4..0000000
--- a/Scrum French/Scrum/guidances/reports/Release Burndown Chart.xmi
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-pJuF9iKbSQx7TIwHNBVTgg" name="Release Burndown Chart,_vKqe8PpaEdqsc-f87sBK8A" guid="-pJuF9iKbSQx7TIwHNBVTgg" changeDate="2006-12-03T15:16:09.515+0100">
-  <mainDescription>&lt;p&gt;
-    C'est un &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../../Scrum/guidances/termdefinitions/Burndown Chart,_X5rREILYEduLd8CaF_IcMA.html&quot;
-    guid=&quot;_X5rREILYEduLd8CaF_IcMA&quot;&gt;Graphe de tendance&lt;/a&gt;&amp;nbsp;pour une release :&amp;nbsp;il montre la tendance dans
-    l'avancement de la release par une présentation graphique du reste à faire à la fin de chaque sprint passé.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/reports/Release Planning.xmi b/Scrum French/Scrum/guidances/reports/Release Planning.xmi
deleted file mode 100644
index 9360ab0..0000000
--- a/Scrum French/Scrum/guidances/reports/Release Planning.xmi
+++ /dev/null
@@ -1,7 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-EmLqiNX2WnmsfEtxNiuyTQ" name="new_report,_Z2NzkIGWEduKE9hnyImx1Q" guid="-EmLqiNX2WnmsfEtxNiuyTQ" changeDate="2006-12-02T00:51:59.549+0100">
-  <mainDescription>&lt;p&gt;
-    Il est dérivé du backlog de produit : c'est un sous-ensemble contenant uniquement les éléments prévus dans la release
-    et associés aux sprints prévus dans la release.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/reports/Sprint Burndown Chart.xmi b/Scrum French/Scrum/guidances/reports/Sprint Burndown Chart.xmi
deleted file mode 100644
index 10e80bb..0000000
--- a/Scrum French/Scrum/guidances/reports/Sprint Burndown Chart.xmi
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-qVeT6_sAspmZjCYQLOrhbg" name="Sprint Burndown Chart,_jC4NwPpaEdqsc-f87sBK8A" guid="-qVeT6_sAspmZjCYQLOrhbg" changeDate="2006-12-03T15:17:51.046+0100">
-  <mainDescription>&lt;p&gt;
-    C'est un &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../../Scrum/guidances/termdefinitions/Burndown Chart,_X5rREILYEduLd8CaF_IcMA.html&quot;
-    guid=&quot;_X5rREILYEduLd8CaF_IcMA&quot;&gt;Graphe de tendance&lt;/a&gt;&amp;nbsp;pour un sprint :&amp;nbsp;il montre la tendance dans
-    l'avancement du sprint par une présentation graphique du reste à faire à la fin de chaque jour passé.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/roadmaps/Application.xmi b/Scrum French/Scrum/guidances/roadmaps/Application.xmi
deleted file mode 100644
index 5ade8ce..0000000
--- a/Scrum French/Scrum/guidances/roadmaps/Application.xmi
+++ /dev/null
@@ -1,33 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-IPxNSDzXKWa-H_kJ2PMtYA" name="new_roadmap,_6Jox0IRuEduo75chJsIcXg" guid="-IPxNSDzXKWa-H_kJ2PMtYA" changeDate="2006-12-05T16:29:34.781+0100">
-  <mainDescription>&lt;p&gt;
-    Le&amp;nbsp;Manifeste Agile proclame que &quot;les outils et les processus sont utiles, mais que&amp;nbsp;les personnes et les
-    interactions qu'elles ont entre elles sont plus importantes&quot; pour la réussite du projet. Il faut garder ce principe à
-    l'esprit lors de l'application de Scrum. Il convient également de respecter les&amp;nbsp;caractéristiques de Scrum comme :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        l'approche empirique basée sur la régulation,
-    &lt;/li&gt;
-    &lt;li&gt;
-        la planification adaptative plutôt que prédictive,
-    &lt;/li&gt;
-    &lt;li&gt;
-        l'auto-gestion de l'équipe pour faire ce qu'elle a à faire.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    De plus, Scrum ne décrit pas les activités d'ingénierie nécessaires à la réalisation du produit.
-&lt;/p&gt;
-&lt;p&gt;
-    L'application de Scrum décrite ci-dessous&amp;nbsp;doit être lue et utilisée&amp;nbsp;à l'aune de ces principes agiles. Elle
-    montre comment les éléments de Scrum sont utilisés lors du déroulement d'une période de temps,&amp;nbsp;ou cycle de vie.
-&lt;/p&gt;
-&lt;p&gt;
-    Ce cycle de vie ne représente pas toute la vie d'un produit, mais porte uniquement sur la production d'une &lt;a
-    class=&quot;elementLink&quot; href=&quot;./../../../Scrum/guidances/termdefinitions/Release,_AIB9gIHrEduFs9jH8xc4xw.html&quot;
-    guid=&quot;_AIB9gIHrEduFs9jH8xc4xw&quot;&gt;Release&lt;/a&gt;. Le guide &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../../Scrum/guidances/concepts/Produit, release et sprint,_XtRuYP-zEdqLnajTSLeAsA.html&quot;
-    guid=&quot;_XtRuYP-zEdqLnajTSLeAsA&quot;&gt;Produit, release et sprint&lt;/a&gt;&amp;nbsp;replace cette période dans un contexte plus large.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/supportingmaterials/Copyright.xmi b/Scrum French/Scrum/guidances/supportingmaterials/Copyright.xmi
deleted file mode 100644
index 09ba739..0000000
--- a/Scrum French/Scrum/guidances/supportingmaterials/Copyright.xmi
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-03XtfjRMEs23qIdCSSQiNQ" name="new_supporting_material,_N8zs0AEGEduzRosbOajx7w" guid="-03XtfjRMEs23qIdCSSQiNQ" changeDate="2007-02-03T11:40:46.906-0800" version="1.0.0">
-  <mainDescription>Ce programme et le matériel qui l'accompagne sont mis à disposition selon les termes de la licence &quot;&lt;a
-href=&quot;http://www.eclipse.org/org/documents/epl-v10.php&quot; target=&quot;_blank&quot;&gt;Eclipse Public License v1.0&lt;/a&gt;&quot; qui régit cette
-distribution.</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/supportingmaterials/Introduction.xmi b/Scrum French/Scrum/guidances/supportingmaterials/Introduction.xmi
deleted file mode 100644
index 8254917..0000000
--- a/Scrum French/Scrum/guidances/supportingmaterials/Introduction.xmi
+++ /dev/null
@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-WfzsSn3X35gSHQZ2kqtoVw" name="Introduction,_wz30kABREdu3o4yroaI-tA" guid="-WfzsSn3X35gSHQZ2kqtoVw" changeDate="2006-12-04T21:23:34.453+0100">
-  <mainDescription>&lt;p&gt;
-    Ce plugin, réalisé&amp;nbsp;avec&amp;nbsp;&lt;a href=&quot;http://www.eclipse.org/epf/&quot; target=&quot;_blank&quot;&gt;EPF&lt;/a&gt; (Eclipse&amp;nbsp;Process
-    Framework)&amp;nbsp;présente :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        une introduction à &lt;a class=&quot;elementLink&quot;
-        href=&quot;./../../../Scrum/guidances/concepts/Presentation Scrum,_3WivIBTQEduFIr9xNbwGyQ.html&quot;
-        guid=&quot;_3WivIBTQEduFIr9xNbwGyQ&quot;&gt;Scrum&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        les notions principales de Scrum (&lt;a class=&quot;elementLink&quot;
-        href=&quot;./../../../Scrum/customcategories/Scrum Elements,_nF6fgALYEduFv7wnrO7SvQ.html&quot;
-        guid=&quot;_nF6fgALYEduFv7wnrO7SvQ&quot;&gt;Eléments Scrum&lt;/a&gt;),
-    &lt;/li&gt;
-    &lt;li&gt;
-        une façon de les appliquer (&lt;a class=&quot;elementLink&quot;
-        href=&quot;./../../../Scrum/customcategories/Cycle de vie Scrum,_7BSBkABCEduYUKPFgCzFuA.html&quot;
-        guid=&quot;_7BSBkABCEduYUKPFgCzFuA&quot;&gt;Cycle de vie&lt;/a&gt;) qui est à adapter à chaque projet.
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/supportingmaterials/Scrum references.xmi b/Scrum French/Scrum/guidances/supportingmaterials/Scrum references.xmi
deleted file mode 100644
index a1f2561..0000000
--- a/Scrum French/Scrum/guidances/supportingmaterials/Scrum references.xmi
+++ /dev/null
@@ -1,14 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-cfa6bdUgQuboNpJRKaCLAw" name="Scrum referencesl,_PTGe4IRvEduo75chJsIcXg" guid="-cfa6bdUgQuboNpJRKaCLAw" changeDate="2006-12-05T15:45:31.406+0100">
-  <mainDescription>&lt;ul&gt;
-    &lt;li&gt;
-        Ken Schwaber&amp;nbsp;: &lt;a href=&quot;http://softpro.stores.yahoo.net/0-7356-1993-x.html&quot; target=&quot;_blank&quot;&gt;Agile Project
-        Management with Scrum.&lt;/a&gt;&amp;nbsp;
-    &lt;/li&gt;
-    &lt;li&gt;
-        Mike Cohn&amp;nbsp;: &lt;a
-        href=&quot;http://www.amazon.fr/exec/obidos/ASIN/0131479415/sr=8-1/qid=1152998855/ref=sr_1_1/402-4433368-7461703?_encoding=UTF8&amp;amp;s=gateway&amp;amp;v=glance&quot;
-         target=&quot;_blank&quot;&gt;Agile Estimating and Planning&lt;/a&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/termdefinitions/Burndown Chart.xmi b/Scrum French/Scrum/guidances/termdefinitions/Burndown Chart.xmi
deleted file mode 100644
index 63ce6f7..0000000
--- a/Scrum French/Scrum/guidances/termdefinitions/Burndown Chart.xmi
+++ /dev/null
@@ -1,4 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-KQ4Jzjy6YgAr_2NXa4J67g" name="new_term_definition,_X5rREILYEduLd8CaF_IcMA" guid="-KQ4Jzjy6YgAr_2NXa4J67g">
-  <mainDescription>Représentation graphique du reste à faire dans une période, actualisée aussi souvent que possible.</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/termdefinitions/Release.xmi b/Scrum French/Scrum/guidances/termdefinitions/Release.xmi
deleted file mode 100644
index 46444c0..0000000
--- a/Scrum French/Scrum/guidances/termdefinitions/Release.xmi
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-XPyPmZTAVbnvJVuOLvYpXw" name="Release,_AIB9gIHrEduFs9jH8xc4xw" guid="-XPyPmZTAVbnvJVuOLvYpXw" changeDate="2006-12-02T10:53:51.187+0100" version="1.0.0">
-  <mainDescription>Une release correspond à la livraison d'une version. Par habitude, on parle de release pour considérer la période de temps
-qui va du début du travail sur cette version jusqu'à sa livraison et qui passe par une série de sprints successifs.</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/termdefinitions/Sprint.xmi b/Scrum French/Scrum/guidances/termdefinitions/Sprint.xmi
deleted file mode 100644
index 0af2272..0000000
--- a/Scrum French/Scrum/guidances/termdefinitions/Sprint.xmi
+++ /dev/null
@@ -1,5 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-fcoz1Nm_QnX6xtLg5YWdVg" name="new_term_definition,_kftWoIHqEduFs9jH8xc4xw" guid="-fcoz1Nm_QnX6xtLg5YWdVg" changeDate="2006-12-02T10:51:49.500+0100">
-  <mainDescription>Un sprint est un bloc de temps aboutissant à créer un incrément du produit. C'est le terme utilisé dans Scrum pour
-itération.</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/termdefinitions/Theme.xmi b/Scrum French/Scrum/guidances/termdefinitions/Theme.xmi
deleted file mode 100644
index 2814df0..0000000
--- a/Scrum French/Scrum/guidances/termdefinitions/Theme.xmi
+++ /dev/null
@@ -1,4 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-GKfSarwQLoaHhoT71FQI8Q" name="new_term_definition,_aeYKoIKlEduQgtHqedKdMA" guid="-GKfSarwQLoaHhoT71FQI8Q" changeDate="2006-12-03T09:09:30.312+0100">
-  <mainDescription>Un thème constitue un regroupement fonctionnel d'exigences.</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/termdefinitions/Timebox.xmi b/Scrum French/Scrum/guidances/termdefinitions/Timebox.xmi
deleted file mode 100644
index 0d19473..0000000
--- a/Scrum French/Scrum/guidances/termdefinitions/Timebox.xmi
+++ /dev/null
@@ -1,4 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-tHVOELWOQDI7i0M2rlMufQ" name="new_term_definition,_3qdXkILXEduLd8CaF_IcMA" guid="-tHVOELWOQDI7i0M2rlMufQ" changeDate="2006-12-03T15:11:12.609+0100">
-  <mainDescription>Une période de temps à échéance fixée et intangible même si tous les objectifs ne sont pas atteints.</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/guidances/termdefinitions/Velocity.xmi b/Scrum French/Scrum/guidances/termdefinitions/Velocity.xmi
deleted file mode 100644
index ac28bb4..0000000
--- a/Scrum French/Scrum/guidances/termdefinitions/Velocity.xmi
+++ /dev/null
@@ -1,4 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-PeP4fADValHXs2Z2Z8zJ1w" name="new_term_definition,_HQEP8ILXEduLd8CaF_IcMA" guid="-PeP4fADValHXs2Z2Z8zJ1w" changeDate="2007-01-29T09:14:31.140+0100" version="1.0.0">
-  <mainDescription>La vélocité est la mesure de la capacité de l'équipe pendant un sprint.</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/plugin.xmi b/Scrum French/Scrum/plugin.xmi
deleted file mode 100644
index 1789c5d..0000000
--- a/Scrum French/Scrum/plugin.xmi
+++ /dev/null
@@ -1,197 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore" epf:version="1.0.0">
-  <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_5AUAUPpYEdqsc-f87sBK8A" guid="_5AUAUPpYEdqsc-f87sBK8A">
-    <subManagers xmi:id="_9m1CIAAvEdubGMceRDupFQ" href="uma://_9llsAAAvEdubGMceRDupFQ#_9m1CIAAvEdubGMceRDupFQ"/>
-    <resourceDescriptors xmi:id="_5AUAUfpYEdqsc-f87sBK8A" id="-Y3SFEe-A-lRF8TaEn9vKNQ" uri="roles/ScrumMaster.xmi"/>
-    <resourceDescriptors xmi:id="_N_XCIf-0EdqLnajTSLeAsA" id="-CgLjZ6Bwc0EyYyQCjzlw7g" uri="rolesets/Scrum%20Roles.xmi"/>
-    <resourceDescriptors xmi:id="_aziTsP--Edqtbrr0B1TG-A" id="-NRwwk6YGAtu25V3Lc04G6w" uri="tasks/Plan%20sprint%202.xmi"/>
-    <resourceDescriptors xmi:id="_9lx5QAAvEdubGMceRDupFQ" id="_9llsAAAvEdubGMceRDupFQ" uri="deliveryprocesses/Scrum/model.xmi"/>
-    <resourceDescriptors xmi:id="_qJ7PoABSEdu3o4yroaI-tA" id="-juIDa_fXi2K1BE5NTblPow" uri="customcategories/Intro.xmi"/>
-    <resourceDescriptors xmi:id="_OY10sABaEdu3o4yroaI-tA" id="-WfzsSn3X35gSHQZ2kqtoVw" uri="guidances/supportingmaterials/Introduction.xmi"/>
-    <resourceDescriptors xmi:id="_hhv8QAB7EduSVaTQTBfIHA" id="-35iKPqDM2F2PjKWQLCW4tA" uri="roles/Product%20Owner.xmi"/>
-    <resourceDescriptors xmi:id="_hh2C4AB7EduSVaTQTBfIHA" id="-mZfAV7RcWJlp5idlHzeEcA" uri="tasks/Manage%20problems.xmi"/>
-    <resourceDescriptors xmi:id="_rosG4AEGEduzRosbOajx7w" id="-03XtfjRMEs23qIdCSSQiNQ" uri="guidances/supportingmaterials/Copyright.xmi"/>
-    <resourceDescriptors xmi:id="_kTIcUAELEduzRosbOajx7w" id="-eSc2tcV1h17HBw_s8ROEVw" uri="workproducttypes/Backlogs.xmi"/>
-    <resourceDescriptors xmi:id="_K5MbwAEPEduzRosbOajx7w" id="-Of1SdnAQ9nmsL5DFvD2Uug" uri="workproducts/Product%20Backlog.xmi"/>
-    <resourceDescriptors xmi:id="_K5MbwQEPEduzRosbOajx7w" id="-LVZG5zK2YjEGXO3SwDmqug" uri="roles/Team.xmi"/>
-    <resourceDescriptors xmi:id="_K5YpAAEPEduzRosbOajx7w" id="-u0-b4PNo9XzOh1-dv_aaKA" uri="roles/StakeHolder.xmi"/>
-    <resourceDescriptors xmi:id="_AaX3AAEQEduzRosbOajx7w" id="-8V2DOvzUhvtqwWvTOHMB5g" uri="workproducts/Sprint%20backlog.xmi"/>
-    <resourceDescriptors xmi:id="_A0kNwQESEduzRosbOajx7w" id="-zoJryMCuHfxWP7Q5Er195Q" uri="tasks/Review%20sprint.xmi"/>
-    <resourceDescriptors xmi:id="_A0qUYAESEduzRosbOajx7w" id="-vDOuVl_xPKipKd90HQNZng" uri="tasks/Scrum%20daily%20meeting.xmi"/>
-    <resourceDescriptors xmi:id="_A0qUYQESEduzRosbOajx7w" id="-XdgedeazfFRGDxMY3Fnh5g" uri="tasks/Update%20product%20backlog.xmi"/>
-    <resourceDescriptors xmi:id="_wj_I8AEWEduzRosbOajx7w" id="-S4qXwp40l_8eCcyyI7o-3A" uri="tasks/Retrospective.xmi"/>
-    <resourceDescriptors xmi:id="_WYwq0QEZEduzRosbOajx7w" id="-dU_t9olFRQIyOBZQvMndKg" uri="guidances/concepts/Travail%20collaboratif.xmi"/>
-    <resourceDescriptors xmi:id="_pWgXYAL_EduOAKqB9I73uw" id="-4wqJQ0qXLYZ8kCnpDu--tA" uri="disciplines/Scrum%20activities.xmi"/>
-    <resourceDescriptors xmi:id="_PitjwQOwEduJnc8byNAQ9Q" id="-zS9h38tmK4L-U9kbgkpGKQ" uri="customcategories/Scrum%20Elements.xmi"/>
-    <resourceDescriptors xmi:id="_XQS7sAPKEdubhrgDuRb4fA" id="-3f4axrWBKHGv74oKN2x-gQ" uri="tasks/Plan%20release.xmi"/>
-    <resourceDescriptors xmi:id="_XQZCUAPKEdubhrgDuRb4fA" id="-mi1O4H7RRm0YqlUNyp8TJg" uri="tasks/Initiate%20Product%20Backlog.xmi"/>
-    <resourceDescriptors xmi:id="_E6ZVsBTREduFIr9xNbwGyQ" id="-MSO8KF-0IlKZJGnSwwTNZA" uri="guidances/concepts/Presentation%20Scrum.xmi"/>
-    <resourceDescriptors xmi:id="_ZllqMDwUEdun48PxFCzHCw" id="-BPz1k8sC6CCyJ2yZCc1p2Q" uri="guidances/concepts/Produit,%20release%20et%20sprint.xmi"/>
-    <resourceDescriptors xmi:id="_tO6jEHpCEdug1NkGFo_hTg" id="-6aCUL_kawJFNBtfH_sRXkw" uri="workproducts/Product%20increment.xmi"/>
-    <resourceDescriptors xmi:id="_5nqe4IGJEduKE9hnyImx1Q" id="-KC1R73i9f6P7ZT4pgBOLzA" uri="workproducts/Product%20Backlog%20Item.xmi"/>
-    <resourceDescriptors xmi:id="_74nh8YGWEduKE9hnyImx1Q" id="-EmLqiNX2WnmsfEtxNiuyTQ" uri="guidances/reports/Release%20Planning.xmi"/>
-    <resourceDescriptors xmi:id="_U_2y4IHpEdu3SZQ-Dp1OAA" id="-6UJtuFO3WFBFpJOFeV1QMQ" uri="workproducts/Sprint%20Backlog%20Item.xmi"/>
-    <resourceDescriptors xmi:id="_1MHpkIHqEduFs9jH8xc4xw" id="-fcoz1Nm_QnX6xtLg5YWdVg" uri="guidances/termdefinitions/Sprint.xmi"/>
-    <resourceDescriptors xmi:id="_DD7t8IHrEduFs9jH8xc4xw" id="-XPyPmZTAVbnvJVuOLvYpXw" uri="guidances/termdefinitions/Release.xmi"/>
-    <resourceDescriptors xmi:id="_mmlSkIKlEduQgtHqedKdMA" id="-GKfSarwQLoaHhoT71FQI8Q" uri="guidances/termdefinitions/Theme.xmi"/>
-    <resourceDescriptors xmi:id="_P8d_YILXEduLd8CaF_IcMA" id="-PeP4fADValHXs2Z2Z8zJ1w" uri="guidances/termdefinitions/Velocity.xmi"/>
-    <resourceDescriptors xmi:id="_IbymwILYEduLd8CaF_IcMA" id="-tHVOELWOQDI7i0M2rlMufQ" uri="guidances/termdefinitions/Timebox.xmi"/>
-    <resourceDescriptors xmi:id="_tOn1YILYEduLd8CaF_IcMA" id="-KQ4Jzjy6YgAr_2NXa4J67g" uri="guidances/termdefinitions/Burndown%20Chart.xmi"/>
-    <resourceDescriptors xmi:id="_-wFhAILYEduLd8CaF_IcMA" id="-pJuF9iKbSQx7TIwHNBVTgg" uri="guidances/reports/Release%20Burndown%20Chart.xmi"/>
-    <resourceDescriptors xmi:id="_LCa1UILZEduLd8CaF_IcMA" id="-qVeT6_sAspmZjCYQLOrhbg" uri="guidances/reports/Sprint%20Burndown%20Chart.xmi"/>
-    <resourceDescriptors xmi:id="_egmj0IRvEduo75chJsIcXg" id="-cfa6bdUgQuboNpJRKaCLAw" uri="guidances/supportingmaterials/Scrum%20references.xmi"/>
-    <resourceDescriptors xmi:id="_cpeaYYSAEduo75chJsIcXg" id="-IPxNSDzXKWa-H_kJ2PMtYA" uri="guidances/roadmaps/Application.xmi"/>
-  </org.eclipse.epf.uma.resourcemanager:ResourceManager>
-  <org.eclipse.epf.uma:MethodPlugin xmi:id="_mQ3eoPpYEdqsc-f87sBK8A" name="Scrum" guid="_mQ3eoPpYEdqsc-f87sBK8A" briefDescription="Ce plugin porte sur l'utilisation de Scrum." authors="Claude Aubry" changeDate="2006-12-05T18:52:42.109+0100" version="1.0" copyrightStatement="_N8zs0AEGEduzRosbOajx7w">
-    <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3eofpYEdqsc-f87sBK8A" name="Content" guid="_mQ3eofpYEdqsc-f87sBK8A">
-      <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3eovpYEdqsc-f87sBK8A" name="Categories" guid="_mQ3eovpYEdqsc-f87sBK8A">
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3eo_pYEdqsc-f87sBK8A" name="Domains" guid="_mQ3eo_pYEdqsc-f87sBK8A">
-          <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_AcwmAANoEduYd-55D-Aiqg" name="Scrum Artefacts" guid="_AcwmAANoEduYd-55D-Aiqg" presentationName="Produits Scrum" workProducts="_tCmYEP-xEdqLnajTSLeAsA _5ABscPpYEdqsc-f87sBK8A _Dzw70PpZEdqsc-f87sBK8A"/>
-        </childPackages>
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3epPpYEdqsc-f87sBK8A" name="Disciplines" guid="_mQ3epPpYEdqsc-f87sBK8A">
-          <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_6sdMAAL-EduOAKqB9I73uw" name="Scrum activities" guid="_6sdMAAL-EduOAKqB9I73uw" briefDescription="Les activités spécifiques induites par l'application de Scrum." presentationName="Activités Scrum" conceptsAndPapers="_OUjj0AEZEduzRosbOajx7w" tasks="_Xpd5gP_AEdqtbrr0B1TG-A _STkWYP_BEdqtbrr0B1TG-A _ho-aIP_BEdqtbrr0B1TG-A _4LOggPpaEdqsc-f87sBK8A _J_sRIP_AEdqtbrr0B1TG-A _MRrRYPpbEdqsc-f87sBK8A _d09LYP_AEdqtbrr0B1TG-A _BGFMoANkEduYd-55D-Aiqg">
-            <presentation xmi:id="-4wqJQ0qXLYZ8kCnpDu--tA" href="uma://-4wqJQ0qXLYZ8kCnpDu--tA#-4wqJQ0qXLYZ8kCnpDu--tA"/>
-          </contentElements>
-        </childPackages>
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3epfpYEdqsc-f87sBK8A" name="RoleSets" guid="_mQ3epfpYEdqsc-f87sBK8A">
-          <contentElements xsi:type="org.eclipse.epf.uma:RoleSet" xmi:id="_3qmmoP-zEdqLnajTSLeAsA" name="Scrum Roles" guid="_3qmmoP-zEdqLnajTSLeAsA" briefDescription="Les rôles dans un projet qui applique Scrum." presentationName="Rôles Scrum" conceptsAndPapers="_OUjj0AEZEduzRosbOajx7w" roles="_ICJyYPpaEdqsc-f87sBK8A _t1K9kPpYEdqsc-f87sBK8A _9apLsPpaEdqsc-f87sBK8A _Qqmp8P_AEdqtbrr0B1TG-A">
-            <presentation xmi:id="-CgLjZ6Bwc0EyYyQCjzlw7g" href="uma://-CgLjZ6Bwc0EyYyQCjzlw7g#-CgLjZ6Bwc0EyYyQCjzlw7g"/>
-          </contentElements>
-        </childPackages>
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3epvpYEdqsc-f87sBK8A" name="WP Types" guid="_mQ3epvpYEdqsc-f87sBK8A">
-          <contentElements xsi:type="org.eclipse.epf.uma:WorkProductType" xmi:id="_d-yk8ABREdu3o4yroaI-tA" name="Backlogs" guid="_d-yk8ABREdu3o4yroaI-tA" briefDescription="Scrum utilise un nombre très restreint de produits de travail, essentiellement 2 listes appelées backlogs." presentationName="Backlogs" workProducts="_5ABscPpYEdqsc-f87sBK8A _Dzw70PpZEdqsc-f87sBK8A">
-            <presentation xmi:id="-eSc2tcV1h17HBw_s8ROEVw" href="uma://-eSc2tcV1h17HBw_s8ROEVw#-eSc2tcV1h17HBw_s8ROEVw"/>
-          </contentElements>
-        </childPackages>
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3ep_pYEdqsc-f87sBK8A" name="Tools" guid="_mQ3ep_pYEdqsc-f87sBK8A"/>
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3eqPpYEdqsc-f87sBK8A" name="StandardCategories" guid="_mQ3eqPpYEdqsc-f87sBK8A"/>
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3eqfpYEdqsc-f87sBK8A" name="CustomCategories" guid="_mQ3eqfpYEdqsc-f87sBK8A">
-          <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3eqvpYEdqsc-f87sBK8A" name="Hidden" guid="_mQ3eqvpYEdqsc-f87sBK8A">
-            <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_mQ3eq_pYEdqsc-f87sBK8A" name="Catégories personnalisées" guid="_mQ3eq_pYEdqsc-f87sBK8A" categorizedElements="_7BSBkABCEduYUKPFgCzFuA _s8y1UABREdu3o4yroaI-tA _nF6fgALYEduFv7wnrO7SvQ"/>
-          </childPackages>
-          <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_7BSBkABCEduYUKPFgCzFuA" name="Cycle de vie Scrum" guid="_7BSBkABCEduYUKPFgCzFuA" presentationName="Cycle de vie">
-            <categorizedElements xsi:type="org.eclipse.epf.uma:Roadmap" href="#_6Jox0IRuEduo75chJsIcXg"/>
-            <categorizedElements xsi:type="org.eclipse.epf.uma:DeliveryProcess" href="uma://_9llsAAAvEdubGMceRDupFQ#_9llsAQAvEdubGMceRDupFQ"/>
-            <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="#_XtRuYP-zEdqLnajTSLeAsA"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_s8y1UABREdu3o4yroaI-tA" name="Intro" guid="_s8y1UABREdu3o4yroaI-tA" presentationName="Intro" categorizedElements="_wz30kABREdu3o4yroaI-tA _3WivIBTQEduFIr9xNbwGyQ _PTGe4IRvEduo75chJsIcXg">
-            <presentation xmi:id="-juIDa_fXi2K1BE5NTblPow" href="uma://-juIDa_fXi2K1BE5NTblPow#-juIDa_fXi2K1BE5NTblPow"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_nF6fgALYEduFv7wnrO7SvQ" name="Scrum Elements" guid="_nF6fgALYEduFv7wnrO7SvQ" briefDescription="Description des éléments de Scrum : rôles, réunions et backlogs, ainsi que des guides dans leur utilisation." presentationName="Eléments" categorizedElements="_3qmmoP-zEdqLnajTSLeAsA _d-yk8ABREdu3o4yroaI-tA _6sdMAAL-EduOAKqB9I73uw">
-            <presentation xmi:id="-zS9h38tmK4L-U9kbgkpGKQ" href="uma://-zS9h38tmK4L-U9kbgkpGKQ#-zS9h38tmK4L-U9kbgkpGKQ"/>
-          </contentElements>
-        </childPackages>
-      </childPackages>
-      <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mQ3erPpYEdqsc-f87sBK8A" name="CoreContent" guid="_mQ3erPpYEdqsc-f87sBK8A">
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_rkSgEPpYEdqsc-f87sBK8A" name="Eléments de Scrum" guid="_rkSgEPpYEdqsc-f87sBK8A" briefDescription="Scrum signifie mêlée au rugby. Scrum utilise les valeurs et l'esprit du rugby et les adapte aux projets de développement. Comme le pack lors d'un ballon porté au rugby, l'équipe chargée du développement travaille de façon collective, soudée vers un objectif précis. Comme un demi de mêlée, le ScrumMaster aiguillonne les membres de l'équipe, les repositionne dans la bonne direction et donne le tempo pour assurer la réussite du projet.  Au delà de cet accent mis sur la puissance du collectif, Scrum est un processus agile qui attaque la complexité par une approche empirique. Scrum est facile à apprendre, Scrum est indépendant des méthodes et technologies utilisées : son adoption présente peu de risques. ">
-          <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_t1K9kPpYEdqsc-f87sBK8A" name="ScrumMaster" guid="_t1K9kPpYEdqsc-f87sBK8A" briefDescription="C' est l'animateur d'une équipe Scrum." presentationName="ScrumMaster" responsibleFor="_Dzw70PpZEdqsc-f87sBK8A">
-            <presentation xmi:id="-Y3SFEe-A-lRF8TaEn9vKNQ" href="uma://-Y3SFEe-A-lRF8TaEn9vKNQ#-Y3SFEe-A-lRF8TaEn9vKNQ"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_5ABscPpYEdqsc-f87sBK8A" name="Product Backlog" guid="_5ABscPpYEdqsc-f87sBK8A" briefDescription="Contient les exigences d'un produit" presentationName="Backlog de produit" conceptsAndPapers="_XtRuYP-zEdqLnajTSLeAsA" reports="_vKqe8PpaEdqsc-f87sBK8A _Z2NzkIGWEduKE9hnyImx1Q">
-            <presentation xmi:id="-Of1SdnAQ9nmsL5DFvD2Uug" href="uma://-Of1SdnAQ9nmsL5DFvD2Uug#-Of1SdnAQ9nmsL5DFvD2Uug"/>
-            <containedArtifacts xmi:id="_-D85cIGIEduKE9hnyImx1Q" name="Product Backlog Item" guid="_-D85cIGIEduKE9hnyImx1Q" briefDescription="Chose à faire qui apporte de la valeur. Appelé PBI (Product Backlog Item)" presentationName="Elément de backlog de produit">
-              <presentation xmi:id="-KC1R73i9f6P7ZT4pgBOLzA" href="uma://-KC1R73i9f6P7ZT4pgBOLzA#-KC1R73i9f6P7ZT4pgBOLzA"/>
-            </containedArtifacts>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_Dzw70PpZEdqsc-f87sBK8A" name="Sprint backlog" guid="_Dzw70PpZEdqsc-f87sBK8A" briefDescription="Liste des choses à faire du point de vue de l'équipe de développement." presentationName="Backlog du sprint" reports="_jC4NwPpaEdqsc-f87sBK8A">
-            <presentation xmi:id="-8V2DOvzUhvtqwWvTOHMB5g" href="uma://-8V2DOvzUhvtqwWvTOHMB5g#-8V2DOvzUhvtqwWvTOHMB5g"/>
-            <containedArtifacts xmi:id="_9C78MIHnEdu3SZQ-Dp1OAA" name="Sprint Backlog Item" guid="_9C78MIHnEdu3SZQ-Dp1OAA" briefDescription="C'est une tâche, un travail élémentaire à réaliser pendant le sprint." presentationName="Elément de Backlog de Sprint">
-              <presentation xmi:id="-6UJtuFO3WFBFpJOFeV1QMQ" href="uma://-6UJtuFO3WFBFpJOFeV1QMQ#-6UJtuFO3WFBFpJOFeV1QMQ"/>
-            </containedArtifacts>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_ICJyYPpaEdqsc-f87sBK8A" name="Product Owner" guid="_ICJyYPpaEdqsc-f87sBK8A" briefDescription="C’est le représentant du &quot;métier&quot; dans le projet. " presentationName="Directeur Produit" responsibleFor="_5ABscPpYEdqsc-f87sBK8A">
-            <presentation xmi:id="-35iKPqDM2F2PjKWQLCW4tA" href="uma://-35iKPqDM2F2PjKWQLCW4tA#-35iKPqDM2F2PjKWQLCW4tA"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Report" xmi:id="_jC4NwPpaEdqsc-f87sBK8A" name="Sprint Burndown Chart" guid="_jC4NwPpaEdqsc-f87sBK8A" briefDescription="Présentation de l'avancement du sprint courant." presentationName="Sprint Burndown Chart" conceptsAndPapers="_XtRuYP-zEdqLnajTSLeAsA">
-            <presentation xmi:id="-qVeT6_sAspmZjCYQLOrhbg" href="uma://-qVeT6_sAspmZjCYQLOrhbg#-qVeT6_sAspmZjCYQLOrhbg"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Report" xmi:id="_vKqe8PpaEdqsc-f87sBK8A" name="Release Burndown Chart" guid="_vKqe8PpaEdqsc-f87sBK8A" briefDescription="Présentation de l'avancement de la release." presentationName="Release Burndown Chart" conceptsAndPapers="_XtRuYP-zEdqLnajTSLeAsA">
-            <presentation xmi:id="-pJuF9iKbSQx7TIwHNBVTgg" href="uma://-pJuF9iKbSQx7TIwHNBVTgg#-pJuF9iKbSQx7TIwHNBVTgg"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_4LOggPpaEdqsc-f87sBK8A" name="Plan sprint" guid="_4LOggPpaEdqsc-f87sBK8A" briefDescription="Planification du court terme" presentationName="Planifier le sprint" performedBy="_9apLsPpaEdqsc-f87sBK8A" mandatoryInput="_5ABscPpYEdqsc-f87sBK8A" output="_Dzw70PpZEdqsc-f87sBK8A" additionallyPerformedBy="_ICJyYPpaEdqsc-f87sBK8A">
-            <presentation xmi:id="-NRwwk6YGAtu25V3Lc04G6w" href="uma://-NRwwk6YGAtu25V3Lc04G6w#-NRwwk6YGAtu25V3Lc04G6w"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_9apLsPpaEdqsc-f87sBK8A" name="Team" guid="_9apLsPpaEdqsc-f87sBK8A" briefDescription="Il s'agit d'un rôle collectif. Tous les membres de l'équipe participent au travail, sans qu'on disitingue des fonctions particulières pour chacun." presentationName="Equipe Scrum" responsibleFor="_tCmYEP-xEdqLnajTSLeAsA">
-            <presentation xmi:id="-LVZG5zK2YjEGXO3SwDmqug" href="uma://-LVZG5zK2YjEGXO3SwDmqug#-LVZG5zK2YjEGXO3SwDmqug"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_MRrRYPpbEdqsc-f87sBK8A" name="Review sprint" guid="_MRrRYPpbEdqsc-f87sBK8A" briefDescription="Montrer ce qui a été réalisé et fonctionne. En tirer les conséquences." presentationName="Faire la revue du sprint" performedBy="_9apLsPpaEdqsc-f87sBK8A" mandatoryInput="_tCmYEP-xEdqLnajTSLeAsA" output="_5ABscPpYEdqsc-f87sBK8A" additionallyPerformedBy="_ICJyYPpaEdqsc-f87sBK8A _t1K9kPpYEdqsc-f87sBK8A _Qqmp8P_AEdqtbrr0B1TG-A">
-            <presentation xmi:id="-zoJryMCuHfxWP7Q5Er195Q" href="uma://-zoJryMCuHfxWP7Q5Er195Q#-zoJryMCuHfxWP7Q5Er195Q"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_tCmYEP-xEdqLnajTSLeAsA" name="Product increment" guid="_tCmYEP-xEdqLnajTSLeAsA" briefDescription="Le produit partiel obtenu à la fin de chaque sprint." presentationName="Incrément de produit">
-            <presentation xmi:id="-6aCUL_kawJFNBtfH_sRXkw" href="uma://-6aCUL_kawJFNBtfH_sRXkw#-6aCUL_kawJFNBtfH_sRXkw"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_J_sRIP_AEdqtbrr0B1TG-A" name="Retrospective" guid="_J_sRIP_AEdqtbrr0B1TG-A" briefDescription="Faire un bilan du sprint qui se termine" presentationName="Rétrospective" performedBy="_9apLsPpaEdqsc-f87sBK8A" output="_5ABscPpYEdqsc-f87sBK8A" additionallyPerformedBy="_ICJyYPpaEdqsc-f87sBK8A _t1K9kPpYEdqsc-f87sBK8A _Qqmp8P_AEdqtbrr0B1TG-A">
-            <presentation xmi:id="-S4qXwp40l_8eCcyyI7o-3A" href="uma://-S4qXwp40l_8eCcyyI7o-3A#-S4qXwp40l_8eCcyyI7o-3A"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_Qqmp8P_AEdqtbrr0B1TG-A" name="StakeHolder" guid="_Qqmp8P_AEdqtbrr0B1TG-A" briefDescription="Personne ne participant pas directement au projet mais ayant une influence sur celui-ci." presentationName="Intervenant">
-            <presentation xmi:id="-u0-b4PNo9XzOh1-dv_aaKA" href="uma://-u0-b4PNo9XzOh1-dv_aaKA#-u0-b4PNo9XzOh1-dv_aaKA"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_Xpd5gP_AEdqtbrr0B1TG-A" name="Manage problems" guid="_Xpd5gP_AEdqtbrr0B1TG-A" briefDescription="Prendre en compte les événements qui surviennent à tout moment sur un projet et tenter de les régler." presentationName="Gérer les problèmes" performedBy="_t1K9kPpYEdqsc-f87sBK8A" output="_Dzw70PpZEdqsc-f87sBK8A" optionalInput="_Dzw70PpZEdqsc-f87sBK8A">
-            <presentation xmi:id="-mZfAV7RcWJlp5idlHzeEcA" href="uma://-mZfAV7RcWJlp5idlHzeEcA#-mZfAV7RcWJlp5idlHzeEcA"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_d09LYP_AEdqtbrr0B1TG-A" name="Scrum daily meeting" guid="_d09LYP_AEdqtbrr0B1TG-A" briefDescription="La régulation des activités de développement et de test se fait à travers les mêlées quotidiennes." presentationName="Mêlée quotidienne" performedBy="_t1K9kPpYEdqsc-f87sBK8A" mandatoryInput="_Dzw70PpZEdqsc-f87sBK8A" output="_Dzw70PpZEdqsc-f87sBK8A" additionallyPerformedBy="_9apLsPpaEdqsc-f87sBK8A _ICJyYPpaEdqsc-f87sBK8A">
-            <presentation xmi:id="-vDOuVl_xPKipKd90HQNZng" href="uma://-vDOuVl_xPKipKd90HQNZng#-vDOuVl_xPKipKd90HQNZng"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_STkWYP_BEdqtbrr0B1TG-A" name="Update product backlog" guid="_STkWYP_BEdqtbrr0B1TG-A" briefDescription="Prise en compte des changements de périmètre en vue de préparer les sprints suivants." presentationName="Mettre à jour le backlog de produit" performedBy="_ICJyYPpaEdqsc-f87sBK8A" mandatoryInput="_5ABscPpYEdqsc-f87sBK8A" output="_5ABscPpYEdqsc-f87sBK8A" additionallyPerformedBy="_Qqmp8P_AEdqtbrr0B1TG-A _9apLsPpaEdqsc-f87sBK8A">
-            <presentation xmi:id="-XdgedeazfFRGDxMY3Fnh5g" href="uma://-XdgedeazfFRGDxMY3Fnh5g#-XdgedeazfFRGDxMY3Fnh5g"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_ho-aIP_BEdqtbrr0B1TG-A" name="Plan release" guid="_ho-aIP_BEdqtbrr0B1TG-A" briefDescription="Planification à moyen terme" presentationName="Planifier la release" performedBy="_ICJyYPpaEdqsc-f87sBK8A" mandatoryInput="_5ABscPpYEdqsc-f87sBK8A" output="_5ABscPpYEdqsc-f87sBK8A" additionallyPerformedBy="_t1K9kPpYEdqsc-f87sBK8A _9apLsPpaEdqsc-f87sBK8A">
-            <presentation xmi:id="-3f4axrWBKHGv74oKN2x-gQ" href="uma://-3f4axrWBKHGv74oKN2x-gQ#-3f4axrWBKHGv74oKN2x-gQ"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_OUjj0AEZEduzRosbOajx7w" name="Travail collaboratif" guid="_OUjj0AEZEduzRosbOajx7w" presentationName="Travail collaboratif">
-            <presentation xmi:id="-dU_t9olFRQIyOBZQvMndKg" href="uma://-dU_t9olFRQIyOBZQvMndKg#-dU_t9olFRQIyOBZQvMndKg"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_XtRuYP-zEdqLnajTSLeAsA" name="Produit, release et sprint" guid="_XtRuYP-zEdqLnajTSLeAsA" presentationName="Produit, release et sprint">
-            <presentation xmi:id="-BPz1k8sC6CCyJ2yZCc1p2Q" href="uma://-BPz1k8sC6CCyJ2yZCc1p2Q#-BPz1k8sC6CCyJ2yZCc1p2Q"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_BGFMoANkEduYd-55D-Aiqg" name="Initiate Product Backlog" guid="_BGFMoANkEduYd-55D-Aiqg" briefDescription="Identifier une liste d'items, les inclure dans le backlog et les classer par priorité." presentationName="Elaborer le backlog de produit initial" performedBy="_ICJyYPpaEdqsc-f87sBK8A" output="_5ABscPpYEdqsc-f87sBK8A" additionallyPerformedBy="_Qqmp8P_AEdqtbrr0B1TG-A _9apLsPpaEdqsc-f87sBK8A">
-            <presentation xmi:id="-mi1O4H7RRm0YqlUNyp8TJg" href="uma://-mi1O4H7RRm0YqlUNyp8TJg#-mi1O4H7RRm0YqlUNyp8TJg"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_3WivIBTQEduFIr9xNbwGyQ" name="Presentation Scrum" guid="_3WivIBTQEduFIr9xNbwGyQ" briefDescription="Scrum repose sur une technique de gestion de projets qui conduit à obtenir un produit avec la plus grande valeur &quot;métier&quot; possible dans la durée la plus réduite." presentationName="Scrum">
-            <presentation xmi:id="-MSO8KF-0IlKZJGnSwwTNZA" href="uma://-MSO8KF-0IlKZJGnSwwTNZA#-MSO8KF-0IlKZJGnSwwTNZA"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Report" xmi:id="_Z2NzkIGWEduKE9hnyImx1Q" name="Release Planning" guid="_Z2NzkIGWEduKE9hnyImx1Q" briefDescription="Plan montrant les sprints et les éléments du backlog associés à ces sprints" presentationName="Planning de la release" conceptsAndPapers="_XtRuYP-zEdqLnajTSLeAsA">
-            <presentation xmi:id="-EmLqiNX2WnmsfEtxNiuyTQ" href="uma://-EmLqiNX2WnmsfEtxNiuyTQ#-EmLqiNX2WnmsfEtxNiuyTQ"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_kftWoIHqEduFs9jH8xc4xw" name="Sprint" guid="_kftWoIHqEduFs9jH8xc4xw" presentationName="Sprint">
-            <presentation xmi:id="-fcoz1Nm_QnX6xtLg5YWdVg" href="uma://-fcoz1Nm_QnX6xtLg5YWdVg#-fcoz1Nm_QnX6xtLg5YWdVg"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_AIB9gIHrEduFs9jH8xc4xw" name="Release" guid="_AIB9gIHrEduFs9jH8xc4xw" presentationName="Release">
-            <presentation xmi:id="-XPyPmZTAVbnvJVuOLvYpXw" href="uma://-XPyPmZTAVbnvJVuOLvYpXw#-XPyPmZTAVbnvJVuOLvYpXw"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_aeYKoIKlEduQgtHqedKdMA" name="Theme" guid="_aeYKoIKlEduQgtHqedKdMA" presentationName="Thème">
-            <presentation xmi:id="-GKfSarwQLoaHhoT71FQI8Q" href="uma://-GKfSarwQLoaHhoT71FQI8Q#-GKfSarwQLoaHhoT71FQI8Q"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_HQEP8ILXEduLd8CaF_IcMA" name="Velocity" guid="_HQEP8ILXEduLd8CaF_IcMA" presentationName="Vélocité">
-            <presentation xmi:id="-PeP4fADValHXs2Z2Z8zJ1w" href="uma://-PeP4fADValHXs2Z2Z8zJ1w#-PeP4fADValHXs2Z2Z8zJ1w"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_3qdXkILXEduLd8CaF_IcMA" name="Timebox" guid="_3qdXkILXEduLd8CaF_IcMA" presentationName="Bloc de temps">
-            <presentation xmi:id="-tHVOELWOQDI7i0M2rlMufQ" href="uma://-tHVOELWOQDI7i0M2rlMufQ#-tHVOELWOQDI7i0M2rlMufQ"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_X5rREILYEduLd8CaF_IcMA" name="Burndown Chart" guid="_X5rREILYEduLd8CaF_IcMA" presentationName="Graphe de tendance">
-            <presentation xmi:id="-KQ4Jzjy6YgAr_2NXa4J67g" href="uma://-KQ4Jzjy6YgAr_2NXa4J67g#-KQ4Jzjy6YgAr_2NXa4J67g"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_6Jox0IRuEduo75chJsIcXg" name="Application" guid="_6Jox0IRuEduo75chJsIcXg" briefDescription="Appliquer Scrum sans oublier les principes" presentationName="Appliquer Scrum">
-            <presentation xmi:id="-IPxNSDzXKWa-H_kJ2PMtYA" href="uma://-IPxNSDzXKWa-H_kJ2PMtYA#-IPxNSDzXKWa-H_kJ2PMtYA"/>
-          </contentElements>
-        </childPackages>
-        <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_SqGkoABREdu3o4yroaI-tA" name="Général" guid="_SqGkoABREdu3o4yroaI-tA">
-          <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_wz30kABREdu3o4yroaI-tA" name="Introduction" guid="_wz30kABREdu3o4yroaI-tA" briefDescription="Bienvenue dans Scrum !" presentationName="Introduction">
-            <presentation xmi:id="-WfzsSn3X35gSHQZ2kqtoVw" href="uma://-WfzsSn3X35gSHQZ2kqtoVw#-WfzsSn3X35gSHQZ2kqtoVw"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_N8zs0AEGEduzRosbOajx7w" name="Copyright" guid="_N8zs0AEGEduzRosbOajx7w" presentationName="Copyright">
-            <presentation xmi:id="-03XtfjRMEs23qIdCSSQiNQ" href="uma://-03XtfjRMEs23qIdCSSQiNQ#-03XtfjRMEs23qIdCSSQiNQ"/>
-          </contentElements>
-          <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_PTGe4IRvEduo75chJsIcXg" name="Scrum references" guid="_PTGe4IRvEduo75chJsIcXg" presentationName="Références">
-            <presentation xmi:id="-cfa6bdUgQuboNpJRKaCLAw" href="uma://-cfa6bdUgQuboNpJRKaCLAw#-cfa6bdUgQuboNpJRKaCLAw"/>
-          </contentElements>
-        </childPackages>
-      </childPackages>
-      <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_mQ3erfpYEdqsc-f87sBK8A" name="CapabilityPatterns" guid="_mQ3erfpYEdqsc-f87sBK8A"/>
-    </methodPackages>
-    <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_mQ3ervpYEdqsc-f87sBK8A" name="DeliveryProcesses" guid="_mQ3ervpYEdqsc-f87sBK8A">
-      <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_9llsAAAvEdubGMceRDupFQ" href="uma://_9llsAAAvEdubGMceRDupFQ#_9llsAAAvEdubGMceRDupFQ"/>
-    </methodPackages>
-    <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_mQ3er_pYEdqsc-f87sBK8A" name="ProcessContributions" guid="_mQ3er_pYEdqsc-f87sBK8A"/>
-  </org.eclipse.epf.uma:MethodPlugin>
-</xmi:XMI>
diff --git a/Scrum French/Scrum/roles/Product Owner.xmi b/Scrum French/Scrum/roles/Product Owner.xmi
deleted file mode 100644
index 8a24545..0000000
--- a/Scrum French/Scrum/roles/Product Owner.xmi
+++ /dev/null
@@ -1,70 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:RoleDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-35iKPqDM2F2PjKWQLCW4tA" name="Product Owner,_ICJyYPpaEdqsc-f87sBK8A" guid="-35iKPqDM2F2PjKWQLCW4tA" authors="Claude Aubry" changeDate="2006-12-06T09:55:24.078+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Le Directeur de produit (&lt;i&gt;Product Owner&lt;/i&gt;) est le représentant des clients et utilisateurs dans l'équipe.
-&lt;/p&gt;
-&lt;p&gt;
-    A ce titre, il est responsable de définir les caractéristiques du produit développé par l'équipe en termes de :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        &lt;strong&gt;fonctionnalités&lt;/strong&gt; offertes. Plus précisément il identifie chaque exigence que doit&amp;nbsp;satisfaire
-        le produit comme un&amp;nbsp;&lt;a class=&quot;elementLink&quot;
-        href=&quot;./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html&quot;
-        guid=&quot;_-D85cIGIEduKE9hnyImx1Q&quot;&gt;Elément de backlog de produit&lt;/a&gt;&amp;nbsp;(ou item). Il fournit les détails sur ces
-        exigences quand c'est nécessaire pour l'équipe. Il est souhaitable qu'il spécifie&amp;nbsp;les tests d'acceptation
-        (acceptance tests) de chaque exigence.
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;strong&gt;priorité&lt;/strong&gt;. C'est lui qui définit l'ordre dans lequel ces éléments seront développés en fonction de
-        la valeur qu'ils apportent aux clients et utilisateurs. Cela permet d'alimenter l'équipe avec un &lt;a
-        class=&quot;elementLink&quot; href=&quot;./../../Scrum/workproducts/Product Backlog,_5ABscPpYEdqsc-f87sBK8A.html&quot;
-        guid=&quot;_5ABscPpYEdqsc-f87sBK8A&quot;&gt;Backlog de produit&lt;/a&gt;&amp;nbsp;prêt pour la planification des sprints,
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;strong&gt;but&lt;/strong&gt;. C'est lui définit l'objectif d'une release et qui prend les décisions concernant le &lt;a
-        class=&quot;elementLink&quot; href=&quot;./../../Scrum/guidances/reports/Release Planning,_Z2NzkIGWEduKE9hnyImx1Q.html&quot;
-        guid=&quot;_Z2NzkIGWEduKE9hnyImx1Q&quot;&gt;Planning de la release&lt;/a&gt;.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;br /&gt;</mainDescription>
-  <keyConsiderations>&lt;p&gt;
-    Son implication est capitale pour assurer le succès du projet. En définissant sa vision sur le produit, il&amp;nbsp;donne
-    l'impulsion à l'équipe. En promouvant à l'extérieur le résultat de chaque sprint, il fournit à l'équipe une
-    reconnaissance qui la motive.
-&lt;/p&gt;</keyConsiderations>
-  <skills>&lt;p&gt;
-    Une personne qui joue ce rôle devrait posséder les compétences suivantes :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        bonne connaissance du domaine métier,
-    &lt;/li&gt;
-    &lt;li&gt;
-        capacité à avoir une position respectée par tous les intervenants extérieurs (clients et utilisateurs),
-    &lt;/li&gt;
-    &lt;li&gt;
-        capacité à prendre une décision au bon moment (pas trop tôt ni trop tard),
-    &lt;/li&gt;
-    &lt;li&gt;
-        esprit ouvert au changement,
-    &lt;/li&gt;
-    &lt;li&gt;
-        facilité à communiquer avec l'équipe.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    Quelqu'un qui a été Analyste Métier (Business Analyst) est un bon candidat pour ce rôle.
-&lt;/p&gt;</skills>
-  <assignmentApproaches>&lt;p&gt;
-    Il n'y a qu'une seule personne qui joue ce rôle. Cette personne doit être affectée au projet (le Directeur de produit
-    fait partie de l'équipe étendue et participe aux réunions). Le travail nécessite une affectation à plein temps ou
-    presque.
-&lt;/p&gt;
-&lt;p&gt;
-    Il est&amp;nbsp;important qu'il soit très disponible pour répondre aux questions de l'équipe, pour définir les tests
-    fonctionnels et&amp;nbsp;donner son avis sur divers aspects du produit (l'interface homme machine d'un logiciel, par
-    exemple).
-&lt;/p&gt;</assignmentApproaches>
-  <synonyms>Propriétaire de produit (product owner en anglais),&amp;nbsp;Client (dans XP)</synonyms>
-</org.eclipse.epf.uma:RoleDescription>
diff --git a/Scrum French/Scrum/roles/ScrumMaster.xmi b/Scrum French/Scrum/roles/ScrumMaster.xmi
deleted file mode 100644
index 84b2974..0000000
--- a/Scrum French/Scrum/roles/ScrumMaster.xmi
+++ /dev/null
@@ -1,122 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:RoleDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-Y3SFEe-A-lRF8TaEn9vKNQ" name="new_role,_t1K9kPpYEdqsc-f87sBK8A" guid="-Y3SFEe-A-lRF8TaEn9vKNQ" authors="Claude Aubry" changeDate="2007-01-08T17:37:05.421+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Il a pour responsabilité, dans le cadre du développement d'un produit, d'aider l'équipe à travailler de façon autonome
-    et à s'améliorer constamment.
-&lt;/p&gt;
-&lt;p&gt;
-    Pour cela, il effectue les travaux suivants :&amp;nbsp;
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        tâches périodiques,&amp;nbsp;dont l'objectif est de mettre en application Scrum en organisant et animant le&amp;nbsp;&lt;a
-        class=&quot;elementLink&quot; href=&quot;./../../Scrum/guidances/concepts/Travail collaboratif,_OUjj0AEZEduzRosbOajx7w.html&quot;
-        guid=&quot;_OUjj0AEZEduzRosbOajx7w&quot;&gt;Travail collaboratif&lt;/a&gt;&amp;nbsp;(réunions)&amp;nbsp;: 
-        &lt;ul&gt;
-            &lt;li&gt;
-                Mêlée quotidienne.
-            &lt;/li&gt;
-            &lt;li&gt;
-                Planification du sprint
-            &lt;/li&gt;
-            &lt;li&gt;
-                Revue du sprint
-            &lt;/li&gt;
-            &lt;li&gt;
-                Rétrospective
-            &lt;/li&gt;
-        &lt;/ul&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        tâches sur évènement 
-        &lt;ul&gt;
-            &lt;li&gt;
-                éliminer les obstacles&amp;nbsp;: prendre en compte les évènements qui surviennent à tout moment sur un projet
-                pour les régler au plus vite, tout en protégeant l’équipe des interférences extérieures
-            &lt;/li&gt;
-        &lt;/ul&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        tâche de fond 
-        &lt;ul&gt;
-            &lt;li&gt;
-                faire en sorte que l’équipe reste concentrée sur le véritable objectif du projet, qui est de réaliser les
-                éléments du Backlog en collaboration étroite avec le Directeur Produit, et soit productive .
-            &lt;/li&gt;
-        &lt;/ul&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    Analogies
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Le terme Scrum vient du rugby. Le poste de demi de mêlée est celui qui se rapproche le plus de l'idée de
-        ScrumMaster.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Ken Schwaber compare le ScrumMaster à un chien de berger.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;br /&gt;</mainDescription>
-  <keyConsiderations>&lt;ul&gt;
-    &lt;li&gt;
-        Ce n'est pas un chef de projet&amp;nbsp;: il ne dirige pas, il n'impose pas, il ne contraint pas.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Il fait partie de l'équipe&amp;nbsp;: il s'engage avec les autres.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Il doit régulièrement rencontrer physiquement les autres membres de l'équipe.
-    &lt;/li&gt;
-&lt;/ul&gt;</keyConsiderations>
-  <skills>&lt;p&gt;
-    Les compétences et l'expérience souhaitées dépendent de la taille, de la complexité technique et de management. Il est
-    préférable de posséder les compétences suivantes pour jouer&amp;nbsp;ce rôle :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        bien connaître Scrum,
-    &lt;/li&gt;
-    &lt;li&gt;
-        avoir des facilités de présentation, de communication et de négociation,
-    &lt;/li&gt;
-    &lt;li&gt;
-        guider sans imposer,
-    &lt;/li&gt;
-    &lt;li&gt;
-        faire preuve de qualité de meneur d'hommes et savoir motiver une équipe,
-    &lt;/li&gt;
-    &lt;li&gt;
-        savoir résoudre les conflits et les problèmes,
-    &lt;/li&gt;
-    &lt;li&gt;
-        communiquer honnêtement sur le degré d'avancement,
-    &lt;/li&gt;
-    &lt;li&gt;
-        garder le respect de l'objectif essentiel, qui est de livrer un produit qui remplit&amp;nbsp;ses exigences.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    En revanche il n'est pas nécessaire de :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        avoir de l'expérience du domaine de l'application (pas indispensable, mais ça peut aider),
-    &lt;/li&gt;
-    &lt;li&gt;
-        avoir des compétences techniques sur le développement.
-    &lt;/li&gt;
-&lt;/ul&gt;</skills>
-  <assignmentApproaches>&lt;p&gt;
-    Pour une équipe Scrum typique (de 6 à 10 personnes) , une seule personne joue ce rôle sur un projet.
-&lt;/p&gt;
-&lt;p&gt;
-    Celui qui le joue peut, éventuellement, participer aux travaux du sprint avec les autres membres de l'équipe, mais cela
-    doit rester limité.
-&lt;/p&gt;</assignmentApproaches>
-  <synonyms>&lt;p&gt;
-    Facilitateur de processus. On désigne parfois le ScrumMaster comme une déclinaison agile du chef de projet, mais cela
-    ne favorise pas la compréhension du rôle.
-&lt;/p&gt;</synonyms>
-</org.eclipse.epf.uma:RoleDescription>
diff --git a/Scrum French/Scrum/roles/StakeHolder.xmi b/Scrum French/Scrum/roles/StakeHolder.xmi
deleted file mode 100644
index a1ded05..0000000
--- a/Scrum French/Scrum/roles/StakeHolder.xmi
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:RoleDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-u0-b4PNo9XzOh1-dv_aaKA" name="StakeHolder,_Qqmp8P_AEdqtbrr0B1TG-A" guid="-u0-b4PNo9XzOh1-dv_aaKA" authors="Claude Aubry" changeDate="2006-12-03T09:39:26.078+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Un intervenant ne fait pas partie de l'équipe, mais il est intéressé par le produit réalisé. Il peut avoir une
-    influence sur le déroulement du projet. Il participe à des réunions Scrum : voir sa contribution au &lt;a
-    class=&quot;elementLink&quot; href=&quot;./../../Scrum/guidances/concepts/Travail collaboratif,_OUjj0AEZEduzRosbOajx7w.html&quot;
-    guid=&quot;_OUjj0AEZEduzRosbOajx7w&quot;&gt;Travail collaboratif&lt;/a&gt;.
-&lt;/p&gt;
-&lt;p&gt;
-    Dans son jargon, Scrum appelle&amp;nbsp;les personnes jouant ce rôle&amp;nbsp;des poules (chicken) et conseille de protéger
-    l’équipe, constituée des cochons (pigs), de leur influence directe sur le projet pendant un sprint. Cela signifie que
-    les intervenants ont des fenêtres d'intervention qui sont strictement définies afin de ne pas perturber le travail de
-    l'équipe.
-&lt;/p&gt;</mainDescription>
-  <synonyms>&lt;p&gt;
-    Partie-prenante (Stakeholder en anglais)
-&lt;/p&gt;</synonyms>
-</org.eclipse.epf.uma:RoleDescription>
diff --git a/Scrum French/Scrum/roles/Team.xmi b/Scrum French/Scrum/roles/Team.xmi
deleted file mode 100644
index 91e38f6..0000000
--- a/Scrum French/Scrum/roles/Team.xmi
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:RoleDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-LVZG5zK2YjEGXO3SwDmqug" name="Team,_9apLsPpaEdqsc-f87sBK8A" guid="-LVZG5zK2YjEGXO3SwDmqug" authors="Claude Aubry" changeDate="2006-12-03T09:36:21.984+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Une équipe regroupe des membres qui forment un tout soudé capable de réaliser les différentes tâches sur
-    lesquelles&amp;nbsp;elle s’engage collectivement lors de chaque sprint.
-&lt;/p&gt;
-&lt;p&gt;
-    Elle possède la latitude voulue pour déterminer ce qui doit être fait afin d’atteindre le but fixé du sprint. Elle
-    s’organise de façon autonome et planifie ses propres travaux, sans se les faire imposer.
-&lt;/p&gt;</mainDescription>
-  <keyConsiderations>Par son approche centrée sur le collectif,&amp;nbsp;l'agilité contribue à améliorer la camaraderie dans l’équipe.</keyConsiderations>
-  <skills>L’équipe doit être capable de réaliser les différentes tâches sur lesquelles elle s'engage lors de la planification du
-sprint. Cela signifie qu'elle doit être multi-fonctionnelle (cross-functional) pour couvrir les travaux d'analyse, de
-conception, de codage, de test et autres.</skills>
-  <assignmentApproaches>Une équipe Scrum comprend généralement de&amp;nbsp;3 à 10 personnes.</assignmentApproaches>
-</org.eclipse.epf.uma:RoleDescription>
diff --git a/Scrum French/Scrum/roles/resources/148-le-role-de-scrummaster.html b/Scrum French/Scrum/roles/resources/148-le-role-de-scrummaster.html
deleted file mode 100644
index 83644c8..0000000
--- a/Scrum French/Scrum/roles/resources/148-le-role-de-scrummaster.html
+++ /dev/null
@@ -1,296 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
-<html lang="fr" xmlns="http://www.w3.org/1999/xhtml" xml:lang="fr">
-<head>
-
-
-<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-
-
-
-
-	
-	<meta name="MSSmartTagsPreventParsing" content="TRUE">
-	<link rel="previous" href="http://www.aubryconseil.com/dotclear/index.php/2007/01/05/146-inscription-technorati" title="Inscription Technorati">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/Mes-projets" title="Mes projets">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/Evenements" title="Mes événements">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/Mes-conseils" title="Mes conseils">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/Mes-cours" title="Mes cours">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/L-agilite-en-france" title="L'agilité en France">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/L-agilite-dans-le-monde" title="L'agilité dans le monde">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/L-agilite-en-dehors-du-logiciel" title="L'agilité en dehors du logiciel">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/Mon-butinage" title="Mon butinage">
-<link rel="section" href="http://www.aubryconseil.com/dotclear/index.php/Mon-blog" title="Mon blog">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2007/01" title="janvier 2007">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/12" title="décembre 2006">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/11" title="novembre 2006">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/10" title="octobre 2006">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/09" title="septembre 2006">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/08" title="août 2006">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/07" title="juillet 2006">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/06" title="juin 2006">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/05" title="mai 2006">
-<link rel="archive" href="http://www.aubryconseil.com/dotclear/index.php/2006/04" title="avril 2006">
-	<link rel="alternate" type="application/rss+xml" title="RSS" href="http://www.aubryconseil.com/dotclear/rss.php">
-	<link rel="alternate" type="application/xml" title="Atom" href="http://www.aubryconseil.com/dotclear/atom.php">
-	<meta name="DC.title" content="Scrum - Méthodes agiles"><title>Le rôle de ScrumMaster - Scrum - Méthodes agiles</title><!--
-<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
-  xmlns:dc="http://purl.org/dc/elements/1.1/"
-  xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
-<rdf:Description
-  rdf:about="http://www.aubryconseil.com/dotclear/index.php/2007/01/07/148-le-role-de-scrummaster"
-  dc:identifier="http://www.aubryconseil.com/dotclear/index.php/2007/01/07/148-le-role-de-scrummaster"
-  dc:title="Le rôle de ScrumMaster"
-  trackback:ping="http://www.aubryconseil.com/dotclear/tb.php?id=148" />
-</rdf:RDF>
--->
-	
-	
-	
-<link rel="stylesheet" type="text/css" href="148-le-role-de-scrummaster.css" media="all"></head><body>
-
-<div id="page">
-
-<div id="top">
-	<h1><a indepth="true" href="index.html">Scrum - Méthodes agiles</a></h1>
-</div>
-
-<p id="prelude"><a href="#main">Aller au contenu</a> |
-<a href="#sidebar">Aller au menu</a> |
-<a href="#search">Aller à la recherche</a></p>
-
-<div id="main">
-	<div id="content">
-			
-<div class="post">
-	<h2 class="post-title">Le rôle de ScrumMaster</h2>
-	<p class="post-info">
-<!-- 
-claude aubry,
--->
-	dimanche  7 janvier 2007 à 16:08	<span>::</span> <a indepth="true" href="mes-conseils.html">Mes conseils</a>
-	<span>::</span> <a indepth="true" href="148-le-role-de-scrummaster.html" title="Lien permanent vers : Le rôle de ScrumMaster">#148</a>
-	<span>::</span> <a href="http://www.aubryconseil.com/dotclear/rss.php?type=co&amp;post=148" title="fil RSS des commentaires de : Le rôle de ScrumMaster">rss</a>
-	</p>
-	
-	<div class="post-chapo"><p>Un résumé du rôle de ScrumMaster, l'animateur d'une équipe qui applique Scrum.</p></div>	<div class="post-content"><h5>Synonymes</h5>
-<ul>
-<li>Facilitateur de processus.</li>
-<li>On désigne parfois le ScrumMaster comme une déclinaison agile du chef de projet, mais cela ne favorise pas la compréhension du rôle <sup>[<a href="#pnote-148-1" id="rev-pnote-148-1">1</a>]</sup>.</li>
-</ul>
-<h5>Analogies</h5>
-<ul>
-<li>Le terme Scrum vient du rugby. Le poste de demi de mêlée est celui qui se rapproche le plus de l'idée de ScrumMaster.</li>
-<li>Ken Schwaber compare le ScrumMaster à un chien de berger.</li>
-</ul>
-<h5>Responsabilité</h5>
-
-<p>Il a pour responsabilité, dans le cadre du développement d'un produit, d'aider l'équipe à travailler de façon autonome et à s'améliorer constamment.</p>
-
-
-<h5>Tâches</h5>
-<ul>
-<li>tâches périodiques&nbsp;: mettre en application Scrum en organisant et animant les réunions&nbsp;:
-<ul>
-<li>Mêlée quotidienne.</li>
-<li>Planification du sprint</li>
-<li>Revue du sprint</li>
-<li>Rétrospective</li>
-</ul></li>
-<li>tâches sur évènement
-<ul>
-<li>éliminer les obstacles&nbsp;: prendre en compte les évènements qui surviennent à tout moment sur un projet pour les régler au plus vite, tout en protégeant l’équipe des interférences extérieures</li>
-</ul></li>
-<li>tâche de fond
-<ul>
-<li>faire en sorte que l’équipe reste concentrée sur le véritable objectif du projet, qui est de réaliser les éléments du Backlog en collaboration étroite avec le Directeur Produit, et soit productive .</li>
-</ul></li>
-</ul>
-
-<h5>Compétences</h5>
-
-<p>Les compétences et l'expérience souhaitées dépendent de la taille, de la complexité technique et de management. Il est préférable de posséder les compétences suivantes pour jouer ce rôle&nbsp;:</p>
-<ul>
-<li>bien connaitre Scrum,</li>
-<li>avoir des facilités de présentation, de communication et de négociation,</li>
-<li>guider sans imposer,</li>
-<li>faire preuve de qualité de meneur d'hommes et savoir motiver une équipe,</li>
-<li>savoir résoudre les conflits et les problèmes,</li>
-<li>communiquer honnêtement sur le degré d'avancement,</li>
-<li>garder le respect de l'objectif essentiel, qui est de livrer un produit qui apporte de la valeur avec une utilisation optimale des ressources.</li>
-</ul>
-
-<p>En revanche il n'est pas nécessaire de&nbsp;:</p>
-<ul>
-<li>avoir de l'expérience du domaine de l'application <sup>[<a href="#pnote-148-2" id="rev-pnote-148-2">2</a>]</sup>,</li>
-<li>avoir des compétences techniques sur le développement logiciel.</li>
-</ul>
-
-<h5>Affectation</h5>
-
-
-<p>Pour une équipe Scrum typique <sup>[<a href="#pnote-148-3" id="rev-pnote-148-3">3</a>]</sup>, une seule personne joue ce rôle sur un projet.</p>
-
-
-<p>Celui qui le joue peut, éventuellement, participer aux travaux du sprint avec les autres membres de l'équipe, mais cela doit rester limité.</p>
-
-<h5>Points clés</h5>
-<ul>
-<li>Ce n'est pas un chef de projet&nbsp;: il ne dirige pas, il n'impose pas, il ne contraint pas.</li>
-<li>Il fait partie de l'équipe&nbsp;: il s'engage avec les autres.</li>
-<li>Il doit régulièrement rencontrer physiquement les autres membres de l'équipe.</li>
-</ul>
-<div class="footnotes"><h4>Notes</h4>
-<p>[<a href="#rev-pnote-148-1" id="pnote-148-1">1</a>] voir sur ce sujet <a href="http://agilitateur.azeau.com/index.php?itemid=61" hreflang="fr">le billet de l'Agilitateur</a></p>
-<p>[<a href="#rev-pnote-148-2" id="pnote-148-2">2</a>] ce n'est pas indispensable, mais ça peut aider</p>
-<p>[<a href="#rev-pnote-148-3" id="pnote-148-3">3</a>] de 6 à 10 personnes</p></div></div>
-	
-	
-</div>
-
-<div id="trackbacks">
-	<h3 id="tb">Rétroliens</h3>
-			<p>Aucun rétrolien.</p>
-		
-		
-	
-				<p>Pour faire un rétrolien sur ce billet&nbsp;:
-		http://www.aubryconseil.com/dotclear/tb.php?id=148</p>
-	</div>
-	
-<div id="comments">
-	<h3 id="co">Commentaires</h3>
-			<p>Aucun commentaire pour le moment.</p>
-		
-		
-	
-	<h3>Ajouter un commentaire</h3>
-						<form action="http://www.aubryconseil.com/dotclear/index.php/2007/01/07/148-le-role-de-scrummaster" method="post" id="comment-form">
-<fieldset>
-			<p class="field"><label for="c_nom">Nom ou pseudo&nbsp;:</label>
-	<input name="c_nom" id="c_nom" size="30" maxlength="255" value="" type="text">
-	</p>
-
-	<p class="field"><label for="c_mail">Email (facultatif)&nbsp;:</label>
-	<input name="c_mail" id="c_mail" size="30" maxlength="255" value="" type="text">
-	</p>
-
-	<p class="field"><label for="c_site">Site Web (facultatif)&nbsp;:</label>
-	<input name="c_site" id="c_site" size="30" maxlength="255" value="http://" type="text">
-	</p>
-	
-	<p class="field"><label for="c_content">Commentaire&nbsp;:</label>
-	<textarea name="c_content" id="c_content" cols="35" rows="7"></textarea>
-	</p>
-</fieldset>
-
-<p class="form-help">Le code HTML dans le commentaire sera affiché comme du texte,
-les adresses internet seront converties automatiquement.</p>
-
-<fieldset>	
-	<p><input id="c_remember" name="c_remember" type="checkbox">
-	<label for="c_remember">Se souvenir de mes informations</label>
-	</p>
-	<p><input class="preview" name="preview" value="prévisualiser" type="submit">
-	<input class="submit" value="envoyer" type="submit">
-	<input name="redir" value="http://www.aubryconseil.com/dotclear/index.php/2007/01/07/148-le-role-de-scrummaster" type="hidden"></p>
-</fieldset>
-
-</form>
-			</div>		
-	</div>
-</div>
-	
-	<div id="sidebar">
-
-
-	<div id="presentation"><h2></h2><p>Dans ce blog ma contribution à la diffusion de Scrum à travers mes expériences en tant que <a href="http://www.aubryconseil.com/">consultant</a> et comme enseignant à l'<a href="http://www.iup-ups.ups-tlse.fr/isi/" hreflang="fr">IUP ISI</a> <br>
-Claude Aubry</p>
-	<a indepth="true" href="contact.html">Page contact</a>
-	</div>
-	
-	<div id="connexes">
-		<h2>Scrum</h2>
-		
-		<ul><li><a indepth="true" href="scrum_001.html">Introduction à Scrum</a>
-</li><li><a indepth="true" href="mon-offre-scrum.html">Essayer Scrum</a>
-</li><li><a indepth="true" href="icescrum.html">IceScrum</a>
-</li><li><a indepth="true" href="liens-scrum.html">Plus d'infos sur Scrum</a>
-</li></ul>   </div>
-   
-   
-	
-	<div id="tags">
-		<h2>Tags</h2>
-
-		<ul id="tagcloud"><li class="level-2"><a indepth="true" href="agilite.html">agilité</a> </li><li class="level-1"><a indepth="true" href="backlog.html">backlog</a> </li><li class="level-1"><a indepth="true" href="blog.html">blog</a> </li><li class="level-1"><a indepth="true" href="conference.html">conférence</a> </li><li class="level-1"><a indepth="true" href="contrat.html">contrat</a> </li><li class="level-1"><a indepth="true" href="dotclear.html">dotclear</a> </li><li class="level-1"><a indepth="true" href="epf.html">EPF</a> </li><li class="level-1"><a indepth="true" href="equipe.html">equipe</a> </li><li class="level-2"><a indepth="true" href="estimation.html">estimation</a> </li><li class="level-1"><a indepth="true" href="fac.html">fac</a> </li><li class="level-1"><a indepth="true" href="formation.html">formation</a> </li><li class="level-1"><a indepth="true" href="humour.html">humour</a> </li><li class="level-2"><a indepth="true" href="icescrum_001.html">icescrum</a> </li><li class="level-1"><a indepth="true" href="mesures.html">mesures</a> </li><li class="level-1"><a indepth="true" href="moi.html">moi</a> </li><li class="level-1"><a indepth="true" href="musique.html">musique</a> </li><li class="level-1"><a indepth="true" href="openup.html">OpenUP</a> </li><li class="level-1"><a indepth="true" href="outils.html">outils</a> </li><li class="level-2"><a indepth="true" href="planification.html">planification</a> </li><li class="level-2"><a indepth="true" href="processus.html">processus</a> </li><li class="level-1"><a indepth="true" href="presentation.html">présentation</a> </li><li class="level-1"><a indepth="true" href="release.html">release</a> </li><li class="level-1"><a indepth="true" href="rugby.html">rugby</a> </li><li class="level-1"><a indepth="true" href="retrospective.html">rétrospective</a> </li><li class="level-1"><a indepth="true" href="roles.html">rôles</a> </li><li class="level-5"><a indepth="true" href="scrum.html">scrum</a> </li><li class="level-1"><a indepth="true" href="sigmat.html">sigmat</a> </li><li class="level-1"><a indepth="true" href="tdd.html">tdd</a> </li><li class="level-1"><a indepth="true" href="techno.html">techno</a> </li><li class="level-2"><a indepth="true" href="tendances.html">tendances</a> </li><li class="level-1"><a indepth="true" href="traduction.html">traduction</a> </li><li class="level-1"><a indepth="true" href="uml.html">UML</a> </li><li class="level-2"><a indepth="true" href="user-stories.html">user stories</a> </li><li class="level-1"><a indepth="true" href="vision.html">vision</a> </li><li class="level-1"><a indepth="true" href="xp.html">xp</a> </li></ul>	</div>
-	
-	<div id="syndicate">
-   	<h2>Syndication</h2>
-	<a href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.aubryconseil.com%2Fdotclear"><img src="add2netvibes.gif" alt="Add to Netvibes" height="17" width="91"></a>
-	<ul>
-		<li><a href="http://www.aubryconseil.com/dotclear/rss.php">fil rss</a></li>
-		<li><a href="http://www.aubryconseil.com/dotclear/rss.php?type=co">fil rss commentaires</a></li>
-		<li><a href="http://www.aubryconseil.com/dotclear/atom.php">fil atom</a></li>
-		<li><a href="http://www.aubryconseil.com/dotclear/atom.php?type=co">fil atom commentaires</a></li>
-	</ul>
-	</div>
-	
-	<div id="calendar">
-		<h2>Calendrier</h2>
-		<table summary="Calendrier">
-<caption><a indepth="true" href="12.html" title="décembre 2006">«</a> janvier 2007</caption><thead><tr><th scope="col"><abbr title="lundi">lun</abbr></th><th scope="col"><abbr title="mardi">mar</abbr></th><th scope="col"><abbr title="mercredi">mer</abbr></th><th scope="col"><abbr title="jeudi">jeu</abbr></th><th scope="col"><abbr title="vendredi">ven</abbr></th><th scope="col"><abbr title="samedi">sam</abbr></th><th scope="col"><abbr title="dimanche">dim</abbr></th></tr></thead>
-<tbody><tr><td><a indepth="true" href="01.html">1</a></td><td><a indepth="true" href="02.html">2</a></td><td>3</td><td><a indepth="true" href="04.html">4</a></td><td><a indepth="true" href="05.html">5</a></td><td>6</td><td class="active"><a indepth="true" href="07.html">7</a></td></tr>
-<tr><td>8</td><td>9</td><td>10</td><td>11</td><td>12</td><td>13</td><td>14</td></tr>
-<tr><td>15</td><td>16</td><td>17</td><td>18</td><td>19</td><td>20</td><td>21</td></tr>
-<tr><td>22</td><td>23</td><td>24</td><td>25</td><td>26</td><td>27</td><td>28</td></tr>
-<tr><td>29</td><td>30</td><td>31</td><td> </td><td> </td><td> </td><td> </td></tr>
-</tbody>
-</table>	</div>
-	
-	<div id="search">
-		<form action="http://www.aubryconseil.com/dotclear/index.php/" method="get">
-		
-			<h2><label for="q">Rechercher</label></h2>
-			<p class="field"><input name="q" id="q" size="10" value="" accesskey="4" type="text">
-			<input class="submit" value="ok" type="submit"></p>
-		
-		</form>
-	</div>
-	
-		<div id="selection"><h2>À retenir</h2><ul><li><a indepth="true" href="148-le-role-de-scrummaster.html">Le rôle de ScrumMaster</a></li><li><a indepth="true" href="132-le-role-de-directeur-de-produit.html">Le rôle de directeur de produit</a></li><li><a indepth="true" href="125-scrum-en-bref.html">Scrum en bref</a></li><li><a indepth="true" href="115-backlog-priorise.html">Backlog : critères pour établir les priorités</a></li><li><a indepth="true" href="99-discipline-et-agilite.html">Discipline et agilité</a></li><li><a indepth="true" href="87-duree-fixe-des-iterations.html">Durée fixe des itérations</a></li><li><a indepth="true" href="67-la-minute-ideale-du-randonneur.html">La minute idéale du randonneur</a></li><li><a indepth="true" href="58-agilite-pour-un-contrat-au-forfait.html">Agilité pour un contrat au forfait</a></li><li><a indepth="true" href="36-avant-la-premiere-iteration.html">Avant la première itération</a></li><li><a indepth="true" href="29-duree-d-une-iteration.html">Durée d'une itération</a></li></ul></div>	
-		
-	<div id="toclink">
-<h2><a indepth="true" href="toc.html">Table des matières</a></h2>
-</div>
-
-   
-
-	<div id="archives">
-		<h2>Archives</h2>
-		<ul><li><strong><a indepth="true" href="01_001.html">janvier 2007</a></strong></li><li><a indepth="true" href="12.html">décembre 2006</a></li><li><a indepth="true" href="11.html">novembre 2006</a></li><li><a indepth="true" href="10.html">octobre 2006</a></li><li><a indepth="true" href="09.html">septembre 2006</a></li><li><a indepth="true" href="08.html">août 2006</a></li><li><a indepth="true" href="07_001.html">juillet 2006</a></li><li><a indepth="true" href="06.html">juin 2006</a></li><li><a indepth="true" href="05_001.html">mai 2006</a></li><li><a indepth="true" href="04_001.html">avril 2006</a></li></ul>	</div>
-	
-	<div id="links">
-		<h2>Blogs lus régulièrement</h2>
-		<h3>Agile</h3><ul><li><a href="http://agilitateur.azeau.com/" hreflang="fr">L'Agilitateur</a></li><li><a href="http://kanemar.wordpress.com/" hreflang="EN">Kane Mar</a></li><li><a href="http://silkandspinach.net/" hreflang="EN">Silk and Spinach</a></li><li><a href="http://www.testing.com/cgi-bin/blog" hreflang="en">Exploration Through Example</a></li><li><a href="http://www.agileadvice.com/" hreflang="EN">Agile Advice</a></li><li><a href="http://theagileblog.net/" hreflang="en">On Be(come)ing Agile</a></li><li><a href="http://bossavit.com/thoughts/" hreflang="EN" rel="co-worker">Laurent Bossavit</a></li><li><a href="http://prog13.free.fr/" hreflang="fr">Avangel</a></li><li><a href="http://tcros.blogspot.com/" hreflang="fr">Thierry Cros</a></li></ul><h3>Techno</h3><ul><li><a href="http://www.dotnetguru2.org/proques/" hreflang="fr" title="Le blog de Pascal Roques">UML Guru</a></li><li><a href="http://www.inherence.fr/dotclear/" hreflang="fr">Parlons ISO 20000</a></li><li><a href="http://nauges.typepad.com/my_weblog/" hreflang="fr">Louis Naugès</a></li><li><a href="http://standblog.org/blog/" hreflang="fr">StandBlog</a></li></ul>	</div>
-	
-	<div id="categories">
-		<h2>Catégories</h2>
-		<ul><li><a indepth="true" href="mes-projets.html">Mes projets</a></li><li><a indepth="true" href="evenements.html">Mes événements</a></li><li><a indepth="true" href="mes-conseils.html">Mes conseils</a></li><li><a indepth="true" href="mes-cours.html">Mes cours</a></li><li><a indepth="true" href="l-agilite-en-france.html">L'agilité en France</a></li><li><a indepth="true" href="l-agilite-dans-le-monde.html">L'agilité dans le monde</a></li><li><a indepth="true" href="l-agilite-en-dehors-du-logiciel.html">L'agilité en dehors du logiciel</a></li><li><a indepth="true" href="mon-butinage.html">Mon butinage</a></li><li><a indepth="true" href="mon-blog.html">Mon blog</a></li></ul>	</div>
-	
-	
-	
-	
-</div><p id="footer">Le blog de Claude  Aubry est <a href="http://www.dotclear.net/">
-propulsé par DotClear</a></p>
-
-</div> 
-<!-- end #page -->
-
-<!-- Blocs en plus pour ajouter des images en tout genre si besoin -->
-<div id="block1"><span></span></div><div id="block2"><span></span></div>
-<div id="block3"><span></span></div><div id="block4"><span></span></div>
-<div id="block5"><span></span></div><div id="block6"><span></span></div>
-
-
-
-</body></html>
diff --git a/Scrum French/Scrum/rolesets/Scrum Roles.xmi b/Scrum French/Scrum/rolesets/Scrum Roles.xmi
deleted file mode 100644
index 8542e8b..0000000
--- a/Scrum French/Scrum/rolesets/Scrum Roles.xmi
+++ /dev/null
@@ -1,13 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-CgLjZ6Bwc0EyYyQCjzlw7g" name="new_role_set,_3qmmoP-zEdqLnajTSLeAsA" guid="-CgLjZ6Bwc0EyYyQCjzlw7g" changeDate="2006-12-03T08:51:09.000+0100">
-  <mainDescription>&lt;p&gt;
-    Scrum définit uniquement 3 rôles pour les personnes qui participent aux travaux de développement. A la différence
-    d’autres processus, il n’existe pas d’architecte, de programmeur, de testeur, d’analyste, de rédacteur. L’équipe
-    regroupe les compétences sans distinction du rôle de chacun a priori.
-&lt;/p&gt;
-&lt;p&gt;
-    Toutes les personnes ayant une influence sur&amp;nbsp;le projet sans y participer directement sont représentées par le rôle
-    &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/StakeHolder,_Qqmp8P_AEdqtbrr0B1TG-A.html&quot;
-    guid=&quot;_Qqmp8P_AEdqtbrr0B1TG-A&quot;&gt;Intervenant&lt;/a&gt;.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/Scrum/scrum.jpg b/Scrum French/Scrum/scrum.jpg
deleted file mode 100644
index 5fe67e3..0000000
--- a/Scrum French/Scrum/scrum.jpg
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/tasks/Initiate Product Backlog.xmi b/Scrum French/Scrum/tasks/Initiate Product Backlog.xmi
deleted file mode 100644
index 3563196..0000000
--- a/Scrum French/Scrum/tasks/Initiate Product Backlog.xmi
+++ /dev/null
@@ -1,45 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-mi1O4H7RRm0YqlUNyp8TJg" name="Initiate Product Backlog,_BGFMoANkEduYd-55D-Aiqg" guid="-mi1O4H7RRm0YqlUNyp8TJg" authors="Claude Aubry" changeDate="2006-12-03T09:00:53.343+0100" version="1.0.0">
-  <keyConsiderations>&lt;p&gt;
-    Le backlog initial doit permettre de planifier au moins les 2 ou 3 premiers sprints.
-&lt;/p&gt;</keyConsiderations>
-  <sections xmi:id="_pWL_gAPJEdubhrgDuRb4fA" name="Collecter les éléments du backlog" guid="_pWL_gAPJEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    Le &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Directeur Produit&lt;/a&gt;&amp;nbsp;établit une première liste des exigences (une
-    exigence&amp;nbsp;devient un&amp;nbsp;&lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html&quot;
-    guid=&quot;_-D85cIGIEduKE9hnyImx1Q&quot;&gt;Elément de backlog de produit&lt;/a&gt;)&amp;nbsp;qu'il souhaite voir réalisées pour la fin de la
-    release.
-&lt;/p&gt;
-&lt;p&gt;
-    Pour compléter cette liste et obtenir un backlog suffisant, il est conseillé d'organiser un workshop réunissant toute
-    l'équipe plus des intervenants. Au cours de ce workshop, le &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot; guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Directeur
-    Produit&lt;/a&gt;&amp;nbsp;présente son ébauche de backlog et chacun intervient pour proposer de nouveaux items.
-&lt;/p&gt;
-&lt;p&gt;
-    Il est fréquent qu'un élément du backlog soit identifié&amp;nbsp;comme une histoire d'utilisateur (User story), technique
-    utilisée à l'origine dans EXtreme Programming (XP) et qui s'adapte très bien&amp;nbsp;à Scrum.
-&lt;/p&gt;
-&lt;br /&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_u0Z7sAPJEdubhrgDuRb4fA" name="Ordonner le backlog" guid="_u0Z7sAPJEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    Le &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Directeur Produit&lt;/a&gt;&amp;nbsp;ordonne les éléments du backlog selon une priorité
-    décroissante. Pour lui, A plus prioritaire que B signifie qu'il souhaite disposer, dans un produit partiel, de l'item A
-    avant l'item B.
-&lt;/p&gt;
-&lt;p&gt;
-    Lorsque le backlog contient beaucoup d'éléments, le classement par priorité de chacun est fastidieux et délicat. C'est
-    pourquoi il est utile de définir des &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/guidances/termdefinitions/Theme,_aeYKoIKlEduQgtHqedKdMA.html&quot;
-    guid=&quot;_aeYKoIKlEduQgtHqedKdMA&quot;&gt;Thème&lt;/a&gt;s, d'associer à&amp;nbsp;chaque élément un thème et de définir les&amp;nbsp;priorités
-    sur les thèmes avant de passer aux éléments. Cela peut être fait lors d'une réunion à laquelle participent les &lt;a
-    class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/StakeHolder,_Qqmp8P_AEdqtbrr0B1TG-A.html&quot;
-    guid=&quot;_Qqmp8P_AEdqtbrr0B1TG-A&quot;&gt;Intervenant&lt;/a&gt;s, ainsi que des membres de l'équipe.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <purpose>Le but est de produire un backlog au moins suffisant pour permettre le démarrage de la série des sprints.</purpose>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/Scrum French/Scrum/tasks/Manage problems.xmi b/Scrum French/Scrum/tasks/Manage problems.xmi
deleted file mode 100644
index 3cbc0ce..0000000
--- a/Scrum French/Scrum/tasks/Manage problems.xmi
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-mZfAV7RcWJlp5idlHzeEcA" name="Manage problems,_Xpd5gP_AEdqtbrr0B1TG-A" guid="-mZfAV7RcWJlp5idlHzeEcA" changeDate="2006-12-03T10:05:51.734+0100" version="1.0.0">
-  <keyConsiderations>&lt;p&gt;
-    Cette tâche est centrée sur la résolution de ces problèmes.
-&lt;/p&gt;</keyConsiderations>
-  <sections xmi:id="_LCxqQAB6EduSVaTQTBfIHA" name="Prendre connaissance du problème" guid="_LCxqQAB6EduSVaTQTBfIHA">
-    <sectionDescription>&lt;p&gt;
-    La réunion quotidienne est l'endroit idéal pour déceler les problèmes qu'une équipe rencontre. Elle peut même permettre
-    de les résoudre immédiatement grâce à la collaboration de l'équipe. Cependant :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        il arrive que des problèmes urgents soient soulevés entre 2 réunions quotidiennes
-    &lt;/li&gt;
-    &lt;li&gt;
-        et surtout la résolution des problèmes n'est pas faite en réunion (sauf si elle évidente)
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    Suite à la mise en évidence d'un problème, par exemple lors de la réunion quotidienne,&amp;nbsp;identifier la cause du
-    problème et les impacts sur le projet. Pour cela une communication orale, à l'initiative&amp;nbsp;du&amp;nbsp;&lt;a
-    class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/ScrumMaster,_t1K9kPpYEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_t1K9kPpYEdqsc-f87sBK8A&quot;&gt;ScrumMaster&lt;/a&gt;,&amp;nbsp;avec la personne qui a soulevé le problème est souhaitable.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_PIKyUAB6EduSVaTQTBfIHA" name="Décider d'un plan d'action" guid="_PIKyUAB6EduSVaTQTBfIHA">
-    <sectionDescription>&lt;p&gt;
-    Identifier les solutions possibles.&lt;br /&gt;
-     Une réunion avec le responsable hiérarchique est organisée si des problèmes survenant sur le projet ne peuvent pas
-    être réglés simplement ou sont à un niveau au-dessus de son autorité.
-&lt;/p&gt;
-&lt;p&gt;
-    Le &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/ScrumMaster,_t1K9kPpYEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_t1K9kPpYEdqsc-f87sBK8A&quot;&gt;ScrumMaster&lt;/a&gt;&amp;nbsp;doit s'efforcer de résoudre le problème au plus tôt, pour ne pas
-    perturber l'avancement de l'équipe.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <purpose>Le but est de d'éliminer les problèmes rencontrés par l'équipe pour qu'elle puisse se concentrer sur ses véritables
-objectifs.</purpose>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/Scrum French/Scrum/tasks/Plan release.xmi b/Scrum French/Scrum/tasks/Plan release.xmi
deleted file mode 100644
index 6c78f3b..0000000
--- a/Scrum French/Scrum/tasks/Plan release.xmi
+++ /dev/null
@@ -1,90 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-3f4axrWBKHGv74oKN2x-gQ" name="Plan release,_ho-aIP_BEdqtbrr0B1TG-A" guid="-3f4axrWBKHGv74oKN2x-gQ" changeDate="2006-12-03T09:23:18.328+0100" version="1.0.0">
-  <keyConsiderations>Il s'agit d'un travail collectif à l'initiative du directeur de produit.</keyConsiderations>
-  <sections xmi:id="_8qN08APJEdubhrgDuRb4fA" name="Définir les conditions de succès de la release" guid="_8qN08APJEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    Il existe 2 types de releases&amp;nbsp; :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        une release dirigée par la date de fin. L'objectif est de mettre en production ou à disposition des utilisateurs à
-        une date fixée.
-    &lt;/li&gt;
-    &lt;li&gt;
-        une release dirigée par les fonctionnalités. La liste des exigences est connue et la release prendra fin lorsque
-        toutes les exigences seront réalisées.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    Les conditions de succès sont définies en fonction de ce type de release.
-&lt;/p&gt;
-&lt;br /&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_BuXEQAPKEdubhrgDuRb4fA" name="Estimer les éléments du backlog" guid="_BuXEQAPKEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    L'estimation est faite pour chaque éléments. Il est préférable de travailler en premier sur les plus prioritaires.
-&lt;/p&gt;
-&lt;p&gt;
-    L'estimation est réalisée en équipe.
-&lt;/p&gt;
-&lt;p&gt;
-    La grandeur utilisée pour les estimations est de préférence le point, sans unités. Pour les valeurs utilisées pour les
-    estimations, on utilise souvent la suite de Fibonacci (1, 2, 3, 5, 8 et 13).
-&lt;/p&gt;
-&lt;p&gt;
-    Les techniques d'estimation sont, de préférence, basées sur une approche collective de l'estimation. Il est conseillé
-    de pratiquer le &quot;planning poker&quot; et de travailler par analogie en comparant les éléments estimés.&amp;nbsp;
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_EaLKQAPKEdubhrgDuRb4fA" name="Définir la durée des sprints" guid="_EaLKQAPKEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    Historiquement dans Scrum, la durée d'un sprint est de 30 jours. Cependant il est possible et même recommandé de faire
-    des sprints plus courts. La durée dépend du projet et des contraintes qui s'y appliquent.&lt;br /&gt;
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_HDZ2UAPKEdubhrgDuRb4fA" name="Estimer la vélocité" guid="_HDZ2UAPKEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    L'idéal est que l'équipe ait déjà travaillé ensemble sur un projet afin qu'on ait pu mesurer sa &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/guidances/termdefinitions/Velocity,_HQEP8ILXEduLd8CaF_IcMA.html&quot;
-    guid=&quot;_HQEP8ILXEduLd8CaF_IcMA&quot;&gt;Vélocité&lt;/a&gt;&amp;nbsp;réelle. Elle sera alors utilisée pour cette release, éventuellement
-    ajustée compte tenu de la nature du projet. Attention cependant un point n'a pas forcément la même valeur dans des
-    projets différents.
-&lt;/p&gt;
-&lt;p&gt;
-    Si ce n'est pas le cas, il faut faire une estimation de la vélocité. Le mieux est de travailler sur le contenu du
-    premier sprint de la release et de voir ce que l'équipe pense pouvoir réaliser pendant ce premier sprint. Cela donne
-    une vélocité estimée qui peut être utilisée pour la planification de la release. Ensuite la planification sera basée
-    sur la vélocité mesurée dans les sprints précédents.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_I71XkAPKEdubhrgDuRb4fA" name="Associer les éléments du backlog aux sprints" guid="_I71XkAPKEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    En fonction des paramètres suivants :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        les estimations de chaque item,
-    &lt;/li&gt;
-    &lt;li&gt;
-        l'ordre dans lesquels les items sont classés (la priorité),
-    &lt;/li&gt;
-    &lt;li&gt;
-        la vélocité estimée pour la release,
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    on affecte les items aux sprints de la release.
-&lt;/p&gt;
-&lt;p&gt;
-    Il est normal d'ajuster, c'est à dire de changer légèrement l'ordre des items, ne serait-ce que pour se rapprocher le
-    plus possible de la vélocité (en effet on ne tombe pas toujours &quot;rond&quot;).
-&lt;/p&gt;
-&lt;p&gt;
-    Il faut associer des items aux premiers sprints (les 2 ou 3 premiers), mais il n'est pas indispensable de le faire pour
-    tous les sprints de la release.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <purpose>&lt;p&gt;
-    Elaborer la planification initiale de la release permettant de lancer la série de sprints.
-&lt;/p&gt;</purpose>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/Scrum French/Scrum/tasks/Plan sprint 2.xmi b/Scrum French/Scrum/tasks/Plan sprint 2.xmi
deleted file mode 100644
index f745cf2..0000000
--- a/Scrum French/Scrum/tasks/Plan sprint 2.xmi
+++ /dev/null
@@ -1,105 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-NRwwk6YGAtu25V3Lc04G6w" name="Plan sprint,_4LOggPpaEdqsc-f87sBK8A" guid="-NRwwk6YGAtu25V3Lc04G6w" authors="Claude Aubry" changeDate="2006-12-03T09:57:11.890+0100" version="1.0.0">
-  <keyConsiderations>&lt;p&gt;
-    La réunion de planification de sprint est un travail réalisé en groupe.
-&lt;/p&gt;
-&lt;p&gt;
-    Elle est limitée dans le temps :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        durée max : limitée à 4 heures
-    &lt;/li&gt;
-    &lt;li&gt;
-        durée moyenne : 2 heures
-    &lt;/li&gt;
-&lt;/ul&gt;</keyConsiderations>
-  <sections xmi:id="_TJNsUP--Edqtbrr0B1TG-A" name="Définir le but du sprint" guid="_TJNsUP--Edqtbrr0B1TG-A">
-    <sectionDescription>&lt;p&gt;
-    Au début lors des premiers sprints de la première release d'un produit, le but est bien souvent de montrer la
-    faisabilité de l'architecture envisagée.
-&lt;/p&gt;
-&lt;p&gt;
-    Ensuite, une fois que l'architecture est stabilisée, le but d'un sprint est proposé par le &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot; guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Directeur
-    Produit&lt;/a&gt; et discuté avec l'équipe. Il porte souvent sur un thème fonctionnel.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_xvy5UAPKEdubhrgDuRb4fA" name="Sélectionner les items" guid="_xvy5UAPKEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    Il s'agit de définir le périmètre de ce sprint. Cela est fait en associant un &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html&quot;
-    guid=&quot;_-D85cIGIEduKE9hnyImx1Q&quot;&gt;Elément de backlog de produit&lt;/a&gt;&amp;nbsp;au sprint puis un autre en tenant compte de la
-    vélocité de l'équipe.
-&lt;/p&gt;
-&lt;p&gt;
-    Si un &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/guidances/reports/Release Planning,_Z2NzkIGWEduKE9hnyImx1Q.html&quot;
-    guid=&quot;_Z2NzkIGWEduKE9hnyImx1Q&quot;&gt;Planning de la release&lt;/a&gt;&amp;nbsp;a été effectué, cette étape consiste seulement à valider
-    collectivement le sous-ensemble du backlog prévu pour ce sprint.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_p4C0sP--Edqtbrr0B1TG-A" name="Identifier les tâches à partir des items" guid="_p4C0sP--Edqtbrr0B1TG-A">
-    <sectionDescription>&lt;p&gt;
-    La 2ème partie de la réunion a pour objectif de définir comment l’équipe va s’arranger pour réaliser le résultat
-    attendu du sprint.&lt;br /&gt;
-     Pour cela, chaque &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html&quot;
-    guid=&quot;_-D85cIGIEduKE9hnyImx1Q&quot;&gt;Elément de backlog de produit&lt;/a&gt;&amp;nbsp;sélectionné est décomposé en tâches. Cela permet
-    à toute l’équipe de discuter et d’éclaircir des points de solution par rapport à cet item, en demandant si nécessaire
-    au propriétaire de produit des précisions sur le comportement du produit.&lt;br /&gt;
-&lt;/p&gt;
-&lt;p&gt;
-    Normalement l'ensemble des activités du cycle de vie sont déroulées lors d'un sprint :&lt;br /&gt;
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Les exigences sélectionnées sont spécifiées
-    &lt;/li&gt;
-    &lt;li&gt;
-        L'architecture est remaniée si nécessaire
-    &lt;/li&gt;
-    &lt;li&gt;
-        Les classes et sous-systèmes sont conçus, implémentés et testés
-    &lt;/li&gt;
-    &lt;li&gt;
-        Les différents composants sont intégrés et testés
-    &lt;/li&gt;
-    &lt;li&gt;
-        Le produit est packagé&amp;nbsp;
-    &lt;/li&gt;
-    &lt;li&gt;
-        Les tests d'acceptation sont passés.&lt;br /&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    L'importance donnée à ces activités dépend de la place du sprint dans la release.&lt;br /&gt;
-    &lt;br /&gt;
-     Le travail prévu dans un sprint précédent mais qui n'a pu être réalisé à cause de la réduction des objectifs devient
-    prioritaire pour le sprint suivant.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_DxNQUAPLEdubhrgDuRb4fA" name="Estimer les tâches" guid="_DxNQUAPLEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    Les taches sont estimées en heures. Il est conseillé d'avoir des tâches suffisamment fines pour qu'une estimation reste
-    inférieure à 16 heures.
-&lt;/p&gt;
-&lt;p&gt;
-    L'estimation est faite collectivement, par l'équipe. Au cours de la discussion pour arriver à une estimation, les
-    aspects techniques sont abordés.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_worbAP--Edqtbrr0B1TG-A" name="Attribuer les tâches" guid="_worbAP--Edqtbrr0B1TG-A">
-    <sectionDescription>Une fois que les activités du sprint ont été définies, elles seront affectées aux membres de l'équipe. Les activités
-peuvent être réalisées par une ou plusieurs personnes. Toutes les activités doivent être prises en compte, y compris les
-réunions de travail (hors réunions Scrum), les lectures de documents ou de code.&lt;br /&gt;
-Il est préférable de différer l'affectation de certaines activités, qui seront prises pendant le sprint en fonction des
-disponibilités des membres de l'équipe.</sectionDescription>
-  </sections>
-  <sections xmi:id="_Iq14wAPLEdubhrgDuRb4fA" name="Obtenir l'engagement de l'équipe" guid="_Iq14wAPLEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    Il est souhaitable que l'équipe s'engage collectivement sur le backlog du sprint, c'est à dire sur les éléments du
-    backlog qu'elle estime pouvoir réaliser dans le sprint.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <purpose>Le but est de planifier&amp;nbsp;le sprint&amp;nbsp;qui commence.</purpose>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/Scrum French/Scrum/tasks/Retrospective.xmi b/Scrum French/Scrum/tasks/Retrospective.xmi
deleted file mode 100644
index 243a584..0000000
--- a/Scrum French/Scrum/tasks/Retrospective.xmi
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-S4qXwp40l_8eCcyyI7o-3A" name="Retrospective,_J_sRIP_AEdqtbrr0B1TG-A" guid="-S4qXwp40l_8eCcyyI7o-3A" changeDate="2006-12-03T10:01:12.593+0100" version="1.0.0">
-  <keyConsiderations>&lt;p&gt;
-    Chaque membre de l’équipe est invité à s’exprimer sur ce qui s’est bien et mal passé.
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        durée max : 2 heures
-    &lt;/li&gt;
-    &lt;li&gt;
-        durée moyenne : 1 heure
-    &lt;/li&gt;
-&lt;/ul&gt;</keyConsiderations>
-  <sections xmi:id="_lwzeABGPEduHloEV5-Zv-w" name="Discussion" guid="_lwzeABGPEduHloEV5-Zv-w">
-    <sectionDescription>Chaque membre de l’équipe est invité à s’exprimer sur ce qui s’est bien et mal passé dans l'application de Scrum sur le
-projet.</sectionDescription>
-  </sections>
-  <sections xmi:id="_noL2YBGPEduHloEV5-Zv-w" name="Définir le plan d'actions" guid="_noL2YBGPEduHloEV5-Zv-w">
-    <sectionDescription>&lt;p&gt;
-    L’équipe discute des améliorations possibles et leur donne une priorité.
-&lt;/p&gt;
-&lt;p&gt;
-    Le&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/ScrumMaster,_t1K9kPpYEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_t1K9kPpYEdqsc-f87sBK8A&quot;&gt;ScrumMaster&lt;/a&gt; ajoute les actions d’amélioration dans le backlog.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <purpose>L’objectif est d'améliorer continuellement le processus.</purpose>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/Scrum French/Scrum/tasks/Review sprint.xmi b/Scrum French/Scrum/tasks/Review sprint.xmi
deleted file mode 100644
index a63b191..0000000
--- a/Scrum French/Scrum/tasks/Review sprint.xmi
+++ /dev/null
@@ -1,66 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-zoJryMCuHfxWP7Q5Er195Q" name="Review sprint,_MRrRYPpbEdqsc-f87sBK8A" guid="-zoJryMCuHfxWP7Q5Er195Q" changeDate="2006-12-03T09:52:13.953+0100" version="1.0.0">
-  <keyConsiderations>&lt;p&gt;
-    Travail en groupe (lors de la réunion dite de revue de sprint)
-&lt;/p&gt;
-&lt;p&gt;
-    Pour la réunion :
-&lt;/p&gt;
-&lt;ul class=&quot;noindent&quot;&gt;
-    &lt;li&gt;
-        durée max : &amp;nbsp;2 heures
-    &lt;/li&gt;
-    &lt;li&gt;
-        durée moyenne : 1 heure
-    &lt;/li&gt;
-&lt;/ul&gt;</keyConsiderations>
-  <sections xmi:id="_XL6VgAPLEdubhrgDuRb4fA" name="Préparer la démonstration" guid="_XL6VgAPLEdubhrgDuRb4fA">
-    <sectionDescription>La préparation de la réunion ne doit pas excéder une heure.&lt;br /&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_ZgJB8APLEdubhrgDuRb4fA" name="Effectuer la démonstration" guid="_ZgJB8APLEdubhrgDuRb4fA">
-    <sectionDescription>L’équipe présente le produit partiel résultat de ses travaux, sous forme de démonstration des exigences (histoires
-d'utilisateur) réalisées. Seules les exigences complètement finies (et testées) sont présentées. Cela permet d’avoir une
-mesure objective de l’avancement. &lt;br /&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_cBouUAPLEdubhrgDuRb4fA" name="Evaluer les résultats du sprint" guid="_cBouUAPLEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    Le&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Directeur Produit&lt;/a&gt; et les intervenants présents (clients, utilisateurs) posent des
-    questions à l’équipe, donnent leur impression, font des propositions et des demandes de changement. Le &lt;a
-    class=&quot;elementLink&quot; href=&quot;./../../Scrum/workproducts/Product Backlog,_5ABscPpYEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_5ABscPpYEdqsc-f87sBK8A&quot;&gt;Backlog de produit&lt;/a&gt;&amp;nbsp;est enrichi avec les bugs découverts et les demandes
-    d’évolution.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_hrswoHoYEduJVrY6eKG_mw" name="Calculer la vélocité réelle" guid="_hrswoHoYEduJVrY6eKG_mw">
-    <sectionDescription>&lt;p&gt;
-    La &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/guidances/termdefinitions/Velocity,_HQEP8ILXEduLd8CaF_IcMA.html&quot;
-    guid=&quot;_HQEP8ILXEduLd8CaF_IcMA&quot;&gt;Vélocité&lt;/a&gt;&amp;nbsp;du sprint&amp;nbsp;est obtenue en faisant la somme de tous les points
-    associés aux exigences considérées comme effectivement finies. Elle est comparée à celle des sprints précédents, le
-    plus souvent à travers un &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/guidances/reports/Release Burndown Chart,_vKqe8PpaEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_vKqe8PpaEdqsc-f87sBK8A&quot;&gt;Release Burndown Chart&lt;/a&gt;.&amp;nbsp;&amp;nbsp;
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_d776UHoYEduJVrY6eKG_mw" name="Ajuster le plan de la release" guid="_d776UHoYEduJVrY6eKG_mw">
-    <sectionDescription>&lt;p&gt;
-    Les conditions ont pu changer depuis la dernière planification de la release :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        des items ont pu être ajoutés ou suppirmés, les estimations modifiées,&amp;nbsp;
-    &lt;/li&gt;
-    &lt;li&gt;
-        l'ordre dans lesquels les items sont classés (la priorité) a pu être modifié,
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    De plus la vélocité&amp;nbsp;moyenne a pu évoluer avec la prise de la vélocité calculée du sprint.&amp;nbsp;
-&lt;/p&gt;
-&lt;p&gt;
-    Le &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/guidances/reports/Release Planning,_Z2NzkIGWEduKE9hnyImx1Q.html&quot;
-    guid=&quot;_Z2NzkIGWEduKE9hnyImx1Q&quot;&gt;Planning de la release&lt;/a&gt; est ajusté en tenant compte de ces nouveaux paramètres.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <purpose>&amp;nbsp;Le but est de montrer les exigences réalisées pendant le sprint par une démonstration du produit partiel</purpose>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/Scrum French/Scrum/tasks/Scrum daily meeting.xmi b/Scrum French/Scrum/tasks/Scrum daily meeting.xmi
deleted file mode 100644
index f9cd5b0..0000000
--- a/Scrum French/Scrum/tasks/Scrum daily meeting.xmi
+++ /dev/null
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-vDOuVl_xPKipKd90HQNZng" name="Scrum daily meeting,_d09LYP_AEdqtbrr0B1TG-A" guid="-vDOuVl_xPKipKd90HQNZng" changeDate="2006-12-03T10:07:26.890+0100" version="1.0.0">
-  <keyConsiderations>&lt;p&gt;
-    Se déroule tous les jours, avec toute l'équipe, de préférence le matin en arrivant : il est souhaitable que la réunion
-    ait lieu tous les jours au même endroit et à la même heure.
-&lt;/p&gt;
-&lt;p&gt;
-    La réunion est limitée à 15 minutes.&amp;nbsp;&lt;br /&gt;
-     L’objectif est d’examiner l’avancement des travaux et d'identifier les problèmes potentiels, mais pas de résoudre les
-    problèmes
-&lt;/p&gt;</keyConsiderations>
-  <sections xmi:id="_oUrlcBGOEduHloEV5-Zv-w" name="Préparer" guid="_oUrlcBGOEduHloEV5-Zv-w">
-    <sectionDescription>Chacun met à jour le planning ( le backlog se sprint) en actualisant le reste à faire sur ses tâches, ce qui permet de
-produire un &lt;a class=&quot;elementLink&quot;
-href=&quot;./../../Scrum/guidances/reports/Sprint Burndown Chart,_jC4NwPpaEdqsc-f87sBK8A.html&quot;
-guid=&quot;_jC4NwPpaEdqsc-f87sBK8A&quot;&gt;Sprint Burndown Chart&lt;/a&gt;.</sectionDescription>
-  </sections>
-  <sections xmi:id="_r0KkEBGOEduHloEV5-Zv-w" name="Se réunir" guid="_r0KkEBGOEduHloEV5-Zv-w">
-    <sectionDescription>&lt;p&gt;
-    Chaque membre de l’équipe s’exprime tour à tour, en répondant à 3 questions sur :
-&lt;/p&gt;
-&lt;ol&gt;
-    &lt;li&gt;
-        Ce qui a été fait depuis la mêlée précédente (en principe la veille)
-    &lt;/li&gt;
-    &lt;li&gt;
-        Ce qui va être fait aujourd’hui
-    &lt;/li&gt;
-    &lt;li&gt;
-        Les problèmes rencontrés&amp;nbsp;
-    &lt;/li&gt;
-&lt;/ol&gt;
-&lt;p&gt;
-    Il est souhaitable que la réunion s'effectue avec tous les personnes de l'équipe debout en cercle et en ayant sous les
-    yeux le &lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/workproducts/Sprint backlog,_Dzw70PpZEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_Dzw70PpZEdqsc-f87sBK8A&quot;&gt;Backlog du sprint&lt;/a&gt;&amp;nbsp;et le &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/guidances/reports/Sprint Burndown Chart,_jC4NwPpaEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_jC4NwPpaEdqsc-f87sBK8A&quot;&gt;Sprint Burndown Chart&lt;/a&gt;&amp;nbsp;actualisés.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_vZkkgBGOEduHloEV5-Zv-w" name="Consolider" guid="_vZkkgBGOEduHloEV5-Zv-w">
-    <sectionDescription>Le&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/workproducts/Sprint backlog,_Dzw70PpZEdqsc-f87sBK8A.html&quot;
-guid=&quot;_Dzw70PpZEdqsc-f87sBK8A&quot;&gt;Backlog du sprint&lt;/a&gt;&amp;nbsp;remis à jour sert à prendre une décision sur l'ajustement du but
-du sprint. Il faut avoir à l'esprit qu'un sprint est limité dans le temps (bloc de temps) et qu'il est préférable de
-supprimer du contenu prévu initialement plutôt que d'avoir du retard. &lt;br /&gt;
-Les problèmes soulevés sont résolus&amp;nbsp;lors de&amp;nbsp;&lt;a class=&quot;elementLink&quot;
-href=&quot;./../../Scrum/tasks/Manage problems,_Xpd5gP_AEdqtbrr0B1TG-A.html&quot; guid=&quot;_Xpd5gP_AEdqtbrr0B1TG-A&quot;&gt;Gérer les
-problèmes&lt;/a&gt;&amp;nbsp;à l'initiative du &lt;a class=&quot;elementLink&quot;
-href=&quot;./../../Scrum/roles/ScrumMaster,_t1K9kPpYEdqsc-f87sBK8A.html&quot; guid=&quot;_t1K9kPpYEdqsc-f87sBK8A&quot;&gt;ScrumMaster&lt;/a&gt;.</sectionDescription>
-  </sections>
-  <purpose>Le but est de faire le point sur l'avancement de l'équipe et d'identifier les problèmes. L’objectif est uniquement
-d’examiner l’avancement des travaux, pas de résoudre les problèmes.</purpose>
-  <alternatives>&lt;p&gt;
-    Appelé aussi Stand-Up Meeting (XP)
-&lt;/p&gt;</alternatives>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/Scrum French/Scrum/tasks/Update product backlog.xmi b/Scrum French/Scrum/tasks/Update product backlog.xmi
deleted file mode 100644
index af19cc7..0000000
--- a/Scrum French/Scrum/tasks/Update product backlog.xmi
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-XdgedeazfFRGDxMY3Fnh5g" name="Manage product backlog,_STkWYP_BEdqtbrr0B1TG-A" guid="-XdgedeazfFRGDxMY3Fnh5g" changeDate="2006-12-03T09:12:31.968+0100" version="1.0.0">
-  <keyConsiderations>&lt;p&gt;
-    Pendant le sprint, personne ne peut modifier la sélection des items du backlog effectuée au début du sprint : le
-    périmètre du sprint reste inchangé.
-&lt;/p&gt;
-&lt;p&gt;
-    En revanche, n’importe qui, même un intervenant extérieur, peut proposer de nouveaux items pour plus tard. Ces items
-    sont étudiés et ordonnés par le propriétaire du produit en vue de la planification du prochain sprint.&lt;br /&gt;
-     Les bugs et les demandes d’évolution issus des essais du produit partiel obtenu à la fin du sprint précédent viennent
-    également enrichir le backlog.
-&lt;/p&gt;</keyConsiderations>
-  <sections xmi:id="_c3HaQAPKEdubhrgDuRb4fA" name="Collecter les changements" guid="_c3HaQAPKEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    N’importe qui, même un intervenant extérieur, peut proposer des changements à ajouter au backlog.&lt;br /&gt;
-     Les bugs et les demandes d’évolution issus des essais du produit partiel obtenu à la fin du sprint précédent viennent
-    également enrichir le backlog.
-&lt;/p&gt;
-&lt;p&gt;
-    Ces éléments sont analysés par le propriétaire du produit en vue de la planification du prochain sprint.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <sections xmi:id="_fkXDoAPKEdubhrgDuRb4fA" name="Réordonner les items" guid="_fkXDoAPKEdubhrgDuRb4fA">
-    <sectionDescription>Les éléments ajoutés depuis le sprint précédent sont ordonnés dans le backlog par le&amp;nbsp;&lt;a class=&quot;elementLink&quot;
-href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot; guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Directeur Produit&lt;/a&gt;
-en vue de la planification à venir.</sectionDescription>
-  </sections>
-  <sections xmi:id="_k-kCgAPKEdubhrgDuRb4fA" name="Réestimer les items" guid="_k-kCgAPKEdubhrgDuRb4fA">
-    <sectionDescription>&lt;p&gt;
-    L'estimation en points des nouveaux éléments introduits dans le backlog est faite par l'équipe, de préférence lors d'un
-    travail de groupe avec le Directeur de prouit, un ou 2 jours avant la revue de fin de sprint.
-&lt;/p&gt;
-&lt;p&gt;
-    Des items déjà présents peuvent également être réestimés.
-&lt;/p&gt;</sectionDescription>
-  </sections>
-  <purpose>Actualiser le backlog et ajuster la planification en tenant compte des changements apparus depuis le dernier sprint.</purpose>
-</org.eclipse.epf.uma:TaskDescription>
diff --git a/Scrum French/Scrum/workproducts/Product Backlog Item.xmi b/Scrum French/Scrum/workproducts/Product Backlog Item.xmi
deleted file mode 100644
index adf4810..0000000
--- a/Scrum French/Scrum/workproducts/Product Backlog Item.xmi
+++ /dev/null
@@ -1,56 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-KC1R73i9f6P7ZT4pgBOLzA" name="new_artifact,_-D85cIGIEduKE9hnyImx1Q" guid="-KC1R73i9f6P7ZT4pgBOLzA" changeDate="2006-12-01T23:15:03.002+0100">
-  <mainDescription>C'est une exigence fonctionnelle ou non fonctionnelle (technique), une demande d'évolution, un bug ou tout autre
-chose&amp;nbsp;dont la réalisation apporte de la valeur au &lt;a class=&quot;elementLink&quot;
-href=&quot;./../../Scrum/roles/Product Owner,_ICJyYPpaEdqsc-f87sBK8A.html&quot; guid=&quot;_ICJyYPpaEdqsc-f87sBK8A&quot;&gt;Directeur
-Produit&lt;/a&gt;.&amp;nbsp; 
-&lt;p&gt;
-    Il possède des attributs qui sont généralement :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        une estimation de sa valeur qui est le plus souvent montrée de façon relative aux autres éléments par la notion de
-        priorité,
-    &lt;/li&gt;
-    &lt;li&gt;
-        une estimation de son coût de développement,
-    &lt;/li&gt;
-    &lt;li&gt;
-        éventuellement le thème (domaine fonctionnel) dont il fait partie,
-    &lt;/li&gt;
-    &lt;li&gt;
-        éventuellement son type (défini en fonction du projet, par exemple histoire d'utilisateur, bug, exigence non
-        fonctionnelle),
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    Si on utilise la technique des histoires d'utilisateur (user stories) et le développement dirigé par les tests (TDD),
-    on associe les critères servant aux tests d'acceptation de cet élément.
-&lt;/p&gt;
-&lt;p&gt;
-    La vie d'un PBI passe par les états suivants :
-&lt;/p&gt;
-&lt;ul class=&quot;noindent&quot;&gt;
-    &lt;li&gt;
-        créé
-    &lt;/li&gt;
-    &lt;li&gt;
-        estimé
-    &lt;/li&gt;
-    &lt;li&gt;
-        planifié (associé à un&amp;nbsp;sprint futur
-    &lt;/li&gt;
-    &lt;li&gt;
-        associé au sprint courant (on le réalise)
-    &lt;/li&gt;
-    &lt;li&gt;
-        réalisé
-    &lt;/li&gt;
-    &lt;li style=&quot;list-style: none&quot;&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-  <keyConsiderations>Le principe de Scrum est de finir complètement un PBI dans un sprint.</keyConsiderations>
-  <externalId>PBI</externalId>
-  <purpose>Sert à la gestion de projet : il sera placé dans un sprint</purpose>
-</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/Scrum French/Scrum/workproducts/Product Backlog.xmi b/Scrum French/Scrum/workproducts/Product Backlog.xmi
deleted file mode 100644
index 4d8cb72..0000000
--- a/Scrum French/Scrum/workproducts/Product Backlog.xmi
+++ /dev/null
@@ -1,28 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-Of1SdnAQ9nmsL5DFvD2Uug" name="Product Backlog,_5ABscPpYEdqsc-f87sBK8A" guid="-Of1SdnAQ9nmsL5DFvD2Uug" authors="Claude AUbry" changeDate="2006-12-03T09:31:43.140+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Le backlog du produit est le référentiel des exigences. Il contient des éléments du backlog (appelés aussi des items de
-    backlog de produit).
-&lt;/p&gt;
-&lt;p&gt;
-    Sa vie est liée à celle du produit.
-&lt;/p&gt;</mainDescription>
-  <purpose>Lister toutes les choses à faire&amp;nbsp;du point de vue du client (le quoi)</purpose>
-  <impactOfNotHaving>Obligatoire</impactOfNotHaving>
-  <briefOutline>Visible par tous, il est mis à jour régulièrement. Il est présenté à la revue de planification du sprint et, une fois
-accepté, la partie contenant les exigences allouées au sprint courant est gelée.</briefOutline>
-  <representationOptions>&lt;ul&gt;
-    &lt;li&gt;
-        Cartes (story cards)
-    &lt;/li&gt;
-    &lt;li&gt;
-        Feuille d'un tableur
-    &lt;/li&gt;
-    &lt;li&gt;
-        Outil IceScrum&amp;nbsp;
-    &lt;/li&gt;
-    &lt;li&gt;
-        Base de données
-    &lt;/li&gt;
-&lt;/ul&gt;</representationOptions>
-</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/Scrum French/Scrum/workproducts/Product increment.xmi b/Scrum French/Scrum/workproducts/Product increment.xmi
deleted file mode 100644
index bc47bed..0000000
--- a/Scrum French/Scrum/workproducts/Product increment.xmi
+++ /dev/null
@@ -1,38 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-6aCUL_kawJFNBtfH_sRXkw" name="Product increment,_tCmYEP-xEdqLnajTSLeAsA" guid="-6aCUL_kawJFNBtfH_sRXkw" changeDate="2006-12-03T10:04:18.218+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Le résultat principal d'un sprint est le produit partiel qui réalise, en plus de ce qui existait au début du
-    sprint,&amp;nbsp;les exigences supplémentaires réalisées pendant ce sprint.
-&lt;/p&gt;
-&lt;p&gt;
-    On peut&amp;nbsp;trouver 3 utilisations -après la démonstration lors de la revue de sprintes- du produit partiel obtenu en
-    fin d'itération&amp;nbsp;:
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        il n'est pas utilisé en dehors de l'équipe. Il a été produit pour chercher à minimiser les risques liés à la
-        technologie et à la capacité de l'équipe à intégrer pour produire un &lt;q&gt;build&lt;/q&gt;. Cela arrive surtout au début
-        d'un nouveau produit.
-    &lt;/li&gt;
-    &lt;li&gt;
-        il est utilisé par des clients privilégiés, en plus du directeur produit. Cela leur donne la possibilité de jouer
-        avec, ce qui permet de réduire les risques portant sur l'IHM liées à la facilité d'utilisation des fonctionnalités.
-        Les retours faits iront alimenter le backlog pour prise en compte ultérieure.
-    &lt;/li&gt;
-    &lt;li&gt;
-        il est mis en production ou en exploitation et utilisé par ses utilisateurs finals. C'est évidemment ce qu'il faut
-        viser puisque chaque nouvelle version apporte de la valeur. Autant l'apporter le plus tôt possible, dès qu'elle est
-        disponible. Mais ce n'est généralement pas possible de mettre en production à la fin de chaque sprint : trop de
-        temps serait pris pour passer les tests de recette sur tout le système, déployer sur l'environnement de production,
-        écrire les manuels utilisateurs, préparer et donner la formation aux utilisateurs... C'est pourquoi ce travail
-        particulier nécessite souvent une activité de préparation à la mise en production. Mais si on réussit à limiter le
-        temps pour faire tout ça, on peut alors mettre en production plus souvent qu'à la fin des releases.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;br /&gt;</mainDescription>
-  <keyConsiderations>&lt;p&gt;
-    Le produit évolue pendant toute sa vie jusqu'à son retrait.
-&lt;/p&gt;</keyConsiderations>
-  <briefOutline>Le produit partiel peut être déployé dans l'environnement de production&amp;nbsp;ou simplement mis à disposition des
-utilisateurs.</briefOutline>
-</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/Scrum French/Scrum/workproducts/Sprint Backlog Item.xmi b/Scrum French/Scrum/workproducts/Sprint Backlog Item.xmi
deleted file mode 100644
index 1f7bd5b..0000000
--- a/Scrum French/Scrum/workproducts/Sprint Backlog Item.xmi
+++ /dev/null
@@ -1,20 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-6UJtuFO3WFBFpJOFeV1QMQ" name="new_artifact,_9C78MIHnEdu3SZQ-Dp1OAA" guid="-6UJtuFO3WFBFpJOFeV1QMQ" changeDate="2006-12-02T10:38:33.140+0100">
-  <mainDescription>&lt;p&gt;
-    Chaque tâche possède les attributs suivants :
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        l'estimation du temps à passer pour finir la tâche. Les efforts sont estimés, par l’équipe, en heures sur une
-        échelle qui varie habituellement de 1à 16 heures. Les tâches plus grandes devraient être décomposées. L’estimation
-        du reste à faire est réactualisée tous les jours.
-    &lt;/li&gt;
-    &lt;li&gt;
-        l'&lt;a class=&quot;elementLink&quot; href=&quot;./../../Scrum/workproducts/Product Backlog Item,_-D85cIGIEduKE9hnyImx1Q.html&quot;
-        guid=&quot;_-D85cIGIEduKE9hnyImx1Q&quot;&gt;Elément de backlog de produit&lt;/a&gt;&amp;nbsp;à l'origine de cette tâche
-    &lt;/li&gt;
-    &lt;li&gt;
-        la personne qui prend en compte cette tâche&lt;br /&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/Scrum French/Scrum/workproducts/Sprint backlog.xmi b/Scrum French/Scrum/workproducts/Sprint backlog.xmi
deleted file mode 100644
index da5b496..0000000
--- a/Scrum French/Scrum/workproducts/Sprint backlog.xmi
+++ /dev/null
@@ -1,16 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-8V2DOvzUhvtqwWvTOHMB5g" name="Sprint backlog,_Dzw70PpZEdqsc-f87sBK8A" guid="-8V2DOvzUhvtqwWvTOHMB5g" changeDate="2006-12-03T10:17:45.781+0100" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Il&amp;nbsp;contient la liste des tâches que l’équipe s’engage à faire afin de compléter les éléments de backlog de produit
-    sélectionnés pour ce sprint.&lt;br /&gt;
-     L’équipe peut modifier une tâche, la supprimer ou en ajouter de nouvelles : il est courant que des tâches apparaissent
-    lors du sprint.
-&lt;/p&gt;</mainDescription>
-  <purpose>Il&amp;nbsp;décrit l'ensemble des&amp;nbsp;tâches d'un sprint, avec les ressources qui y sont affectées et le travail qui reste à
-faire. C'est un plan qui porte sur des tâches détaillées, il est dit à &quot;mailles fines&quot;.</purpose>
-  <impactOfNotHaving>Obligatoire</impactOfNotHaving>
-  <briefOutline>&lt;p&gt;
-    C'est un outil de communication essentiel qui aide à gérer le sprint. Il doit être facilement mis à jour et rester
-    visible à toute l'équipe.
-&lt;/p&gt;</briefOutline>
-</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/Scrum French/Scrum/workproducts/resources/EtatsPBI.jpg b/Scrum French/Scrum/workproducts/resources/EtatsPBI.jpg
deleted file mode 100644
index 4e1e28f..0000000
--- a/Scrum French/Scrum/workproducts/resources/EtatsPBI.jpg
+++ /dev/null
Binary files differ
diff --git a/Scrum French/Scrum/workproducttypes/Backlogs.xmi b/Scrum French/Scrum/workproducttypes/Backlogs.xmi
deleted file mode 100644
index 67ae2e4..0000000
--- a/Scrum French/Scrum/workproducttypes/Backlogs.xmi
+++ /dev/null
@@ -1,15 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmi:id="-eSc2tcV1h17HBw_s8ROEVw" name="Backlogs,_d-yk8ABREdu3o4yroaI-tA" guid="-eSc2tcV1h17HBw_s8ROEVw" changeDate="2006-06-22T22:06:50.327+0200">
-  <mainDescription>&lt;p&gt;
-    Les backlogs de Produit et de Sprint sont des éléments de gestion majeurs dans l'utilisation de Scrum.
-&lt;/p&gt;
-&lt;p&gt;
-    A partir des backlogs, on produit des rapports comme le &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/guidances/reports/Release Burndown Chart,_vKqe8PpaEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_vKqe8PpaEdqsc-f87sBK8A&quot;&gt;Release Burndown Chart&lt;/a&gt;&amp;nbsp;ou le &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../Scrum/guidances/reports/Sprint Burndown Chart,_jC4NwPpaEdqsc-f87sBK8A.html&quot;
-    guid=&quot;_jC4NwPpaEdqsc-f87sBK8A&quot;&gt;Sprint Burndown Chart&lt;/a&gt;
-&lt;/p&gt;</mainDescription>
-  <keyConsiderations>Un backlog est une liste d'items. Le terme n'est pas traduit en français car il est couramment utilisé dans la communauté
-des développeurs.</keyConsiderations>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/Scrum French/configurations/Scrum.xmi b/Scrum French/configurations/Scrum.xmi
deleted file mode 100644
index 4575445..0000000
--- a/Scrum French/configurations/Scrum.xmi
+++ /dev/null
@@ -1,27 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:MethodConfiguration xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="_IqDLgP_OEdqtbrr0B1TG-A" name="Scrum" guid="_IqDLgP_OEdqtbrr0B1TG-A" briefDescription="Le processus Scrum" version="1.0.0">
-  <methodPluginSelection href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3eoPpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3erPpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3eofpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3epfpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3eovpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3epPpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3eo_pYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3ep_pYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3erfpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3ervpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3epvpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3er_pYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3eqfpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3eqPpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3eqvpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_rkSgEPpYEdqsc-f87sBK8A"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_SqGkoABREdu3o4yroaI-tA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_9llsAAAvEdubGMceRDupFQ#_9llsAAAvEdubGMceRDupFQ"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_9llsAAAvEdubGMceRDupFQ#_37NW8AL_EduOAKqB9I73uw"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_9llsAAAvEdubGMceRDupFQ#_NSW6sAMAEduOAKqB9I73uw"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_9llsAAAvEdubGMceRDupFQ#_SoXWEAMAEduOAKqB9I73uw"/>
-  <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_s8y1UABREdu3o4yroaI-tA"/>
-  <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_nF6fgALYEduFv7wnrO7SvQ"/>
-  <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_7BSBkABCEduYUKPFgCzFuA"/>
-</org.eclipse.epf.uma:MethodConfiguration>
diff --git a/Scrum French/library.xmi b/Scrum French/library.xmi
deleted file mode 100644
index 16d6058..0000000
--- a/Scrum French/library.xmi
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore" epf:version="1.0.0">
-  <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_hDRYYfpYEdqsc-f87sBK8A" guid="_hDRYYfpYEdqsc-f87sBK8A">
-    <subManagers xmi:id="_5AUAUPpYEdqsc-f87sBK8A" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_5AUAUPpYEdqsc-f87sBK8A"/>
-    <resourceDescriptors xmi:id="_hDRYYvpYEdqsc-f87sBK8A" id="_hDRYYPpYEdqsc-f87sBK8A" uri=""/>
-    <resourceDescriptors xmi:id="_mRDr4PpYEdqsc-f87sBK8A" id="_mQ3eoPpYEdqsc-f87sBK8A" uri="Scrum/plugin.xmi"/>
-    <resourceDescriptors xmi:id="_VRheAYPTEdu0eqo2Hxw7OA" id="_VRheAIPTEdu0eqo2Hxw7OA" uri="IceScrum/plugin.xmi"/>
-  </org.eclipse.epf.uma.resourcemanager:ResourceManager>
-  <org.eclipse.epf.uma:MethodLibrary xmi:id="_hDRYYPpYEdqsc-f87sBK8A" name="scrum" guid="_hDRYYPpYEdqsc-f87sBK8A">
-    <methodPlugins xmi:id="_mQ3eoPpYEdqsc-f87sBK8A" href="uma://_mQ3eoPpYEdqsc-f87sBK8A#_mQ3eoPpYEdqsc-f87sBK8A"/>
-  </org.eclipse.epf.uma:MethodLibrary>
-</xmi:XMI>
diff --git a/XP/.cvsignore b/XP/.cvsignore
deleted file mode 100644
index 6fe43c5..0000000
--- a/XP/.cvsignore
+++ /dev/null
@@ -1 +0,0 @@
-.lock
diff --git a/XP/.project b/XP/.project
deleted file mode 100644
index 7773d54..0000000
--- a/XP/.project
+++ /dev/null
@@ -1,12 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<projectDescription>
-	<name>XP</name>
-	<comment></comment>
-	<projects>
-	</projects>
-	<buildSpec>
-	</buildSpec>
-	<natures>
-		<nature>org.eclipse.epf.library.project.MethodLibraryProjectNature</nature>
-	</natures>
-</projectDescription>
diff --git a/XP/configurations/config_for_xp.xmi b/XP/configurations/config_for_xp.xmi
deleted file mode 100644
index 52715dd..0000000
--- a/XP/configurations/config_for_xp.xmi
+++ /dev/null
@@ -1,29 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:MethodConfiguration xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="_mohucGE-EdqnIZeW8YpHcA" name="config_for_xp" guid="_mohucGE-EdqnIZeW8YpHcA" version="1.0.0">
-  <methodPluginSelection href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{35DCB3E1-2766-423E-A849-57ECD4F41A40}"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6S2E-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6QGE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6RGE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6QWE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6Q2E-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6QmE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6RmE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6TGE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6TWE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6RWE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6TmE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6SGE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6R2E-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_mhU6SWE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_ms9igWE-EdqnIZeW8YpHcA"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{90FB58E1-B403-4358-85D0-BD902528D810}"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{796EA4CB-0038-43B8-A568-792DCC3B9F22}"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{DBE91BD5-0065-4049-AA61-058C77F1D2A3}"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{45A887AB-A968-48AF-8213-4D470DA9DBCC}"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{01E73AC7-B8D8-4B2F-8B29-A28D9813DB6C}"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{BC57C7CE-BFA8-464F-9925-D27A7968B63C}"/>
-  <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{8367713C-3AEA-489D-B136-DB87D6340A3F}"/>
-  <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_um0n8GdjEdqlnYmIxoiUEQ"/>
-  <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_8NSdoGdjEdqlnYmIxoiUEQ"/>
-  <defaultView xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_um0n8GdjEdqlnYmIxoiUEQ"/>
-</org.eclipse.epf.uma:MethodConfiguration>
diff --git a/XP/library.xmi b/XP/library.xmi
deleted file mode 100644
index 02ce1ab..0000000
--- a/XP/library.xmi
+++ /dev/null
@@ -1,11 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<xmi:XMI xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore" epf:version="1.0.0">
-  <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_hmtlAW96EdupM6itjmYdSQ" guid="_hmtlAW96EdupM6itjmYdSQ">
-    <subManagers xmi:id="_TOlmEGMyEdqsrK7eslBiiA" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#_TOlmEGMyEdqsrK7eslBiiA"/>
-    <resourceDescriptors xmi:id="_hmtlAm96EdupM6itjmYdSQ" id="_hmtlAG96EdupM6itjmYdSQ" uri=""/>
-    <resourceDescriptors xmi:id="_1wUXkG96EdupM6itjmYdSQ" id="{35DCB3E1-2766-423E-A849-57ECD4F41A40}" uri="xp/plugin.xmi"/>
-  </org.eclipse.epf.uma.resourcemanager:ResourceManager>
-  <org.eclipse.epf.uma:MethodLibrary xmi:id="_hmtlAG96EdupM6itjmYdSQ" name="XP" guid="_hmtlAG96EdupM6itjmYdSQ">
-    <methodPlugins xmi:id="{35DCB3E1-2766-423E-A849-57ECD4F41A40}" href="uma://{35DCB3E1-2766-423E-A849-57ECD4F41A40}#{35DCB3E1-2766-423E-A849-57ECD4F41A40}"/>
-  </org.eclipse.epf.uma:MethodLibrary>
-</xmi:XMI>
diff --git a/XP/xp/customcategories/conceptual_road_maps.xmi b/XP/xp/customcategories/conceptual_road_maps.xmi
deleted file mode 100644
index 08649a0..0000000
--- a/XP/xp/customcategories/conceptual_road_maps.xmi
+++ /dev/null
@@ -1,9 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-QcM1bn-XJLcMSggRp54YlQ" name="conceptual_road_maps,_mtDpJGE-EdqnIZeW8YpHcA" guid="-QcM1bn-XJLcMSggRp54YlQ" changeDate="2005-12-06T05:01:41.292-0800">
-  <mainDescription>&lt;p class=&quot;node&quot;&gt;
-    &amp;nbsp;
-&lt;/p&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/customcategories/getting_started.xmi b/XP/xp/customcategories/getting_started.xmi
deleted file mode 100644
index ac36596..0000000
--- a/XP/xp/customcategories/getting_started.xmi
+++ /dev/null
@@ -1,92 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-MqIvi7DInwjz8kX7QEyU3g" name="getting_started,_ms9ig2E-EdqnIZeW8YpHcA" guid="-MqIvi7DInwjz8kX7QEyU3g" changeDate="2006-03-02T14:18:20.615-0800">
-  <mainDescription>&lt;h3&gt;
-    &lt;a id=&quot;WhatisXP&quot; name=&quot;WhatisXP&quot;&gt;What is XP?&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    Extreme Programming or XP is a development process that can be used by small to medium sized teams to develop high
-    quality software within a predictable schedule and budget and with a minimum of overhead. XP is currently one of the
-    most widely used agile processes in the industry.
-&lt;/p&gt;
-&lt;p&gt;
-    &lt;img height=&quot;540&quot; alt=&quot;&quot; src=&quot;resources/circleOfLife.jpg&quot; width=&quot;720&quot; usemap=&quot;#xp_practices_image_map&quot; border=&quot;0&quot; /&gt;
-    &lt;map id=&quot;xp_practices_image_map&quot; name=&quot;xp_practices_image_map&quot;&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;298,19,390,88&quot;
-        href=&quot;./../../xp/guidances/concepts/whole_team,7.89591827591278E-306.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;176,135,282,200&quot;
-        href=&quot;./../../xp/guidances/concepts/collective_ownership,9.300699588493279E-306.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;297,168,434,231&quot;
-        href=&quot;./../../xp/guidances/concepts/test_driven_development,1.620567348185129E-306.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;447,135,547,198&quot;
-        href=&quot;./../../xp/guidances/concepts/coding_standard,8.8116853923311E-307.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;15,236,122,305&quot;
-        href=&quot;./../../xp/guidances/concepts/customer_tests,2.297945473205673E-305.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;218,238,362,307&quot;
-        href=&quot;./../../xp/guidances/concepts/pair_programming,3.876855509996079E-307.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;392,241,512,305&quot;
-        href=&quot;./../../xp/guidances/concepts/refactoring_xp_programming,1.4410217108363206E-306.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;614,236,714,302&quot;
-        href=&quot;./../../xp/guidances/concepts/planning_game,2.7371805612676613E-305.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;143,325,270,393&quot;
-        href=&quot;./../../xp/guidances/concepts/continuous_integration,3.193414568279561E-305.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;310,321,412,379&quot;
-        href=&quot;./../../xp/guidances/concepts/simple_design,1.6109092258980447E-306.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;468,323,597,393&quot;
-        href=&quot;./../../xp/guidances/concepts/xp_sustainable_pace,3.133529870649493E-306.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;307,386,413,436&quot;
-        href=&quot;./../../xp/guidances/concepts/metaphor_system_of_names,4.884861766532753E-306.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; coords=&quot;312,475,419,539&quot;
-        href=&quot;./../../xp/guidances/concepts/small_releases,5.762953011420275E-306.html&quot; /&gt;
-        &lt;area shape=&quot;RECT&quot; target=&quot;_blank&quot; coords=&quot;561,494,708,538&quot; href=&quot;http://www.xprogramming.com&quot; /&gt;
-    &lt;/map&gt;
-&lt;/p&gt;
-&lt;p&gt;
-    This diagram arranges the core practices of Extreme Programming in a way that makes them easy to remember and that
-    exemplifies the steering and control cycles of the process. For more details, see &lt;a class=&quot;elementLinkWithType&quot;
-    href=&quot;./../../xp/guidances/concepts/xp_practices,2.2937799026801584E-305.html&quot; guid=&quot;2.2937799026801584E-305&quot;&gt;Concept:
-    XP Practices&lt;/a&gt;.
-&lt;/p&gt;
-&lt;h2&gt;
-    &lt;a id=&quot;Start&quot; name=&quot;Start&quot;&gt;Where do I start?&lt;/a&gt;
-&lt;/h2&gt;
-&lt;p&gt;
-    If you are unfamiliar with XP and want to learn more about it, we suggest you take the following steps:
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Get a quick &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/what_is_xp,9.251272550276345E-306.html&quot; guid=&quot;9.251272550276345E-306&quot;&gt;overview
-        of XP&lt;/a&gt;.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Learn what the &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/motivation,1.6390805262958034E-306.html&quot;
-        guid=&quot;1.6390805262958034E-306&quot;&gt;motivation behind XP&lt;/a&gt; is.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Understand what &lt;a class=&quot;elementLink&quot;
-        href=&quot;./../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html&quot;
-        guid=&quot;1.041091673844025E-305&quot;&gt;Agile Software Development&lt;/a&gt; means.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Take a tour of the &lt;a class=&quot;elementLink&quot;
-        href=&quot;./../../xp/guidances/concepts/xp_values,1.076140803519123E-306.html&quot; guid=&quot;1.076140803519123E-306&quot;&gt;XP
-        Values&lt;/a&gt; and &lt;a class=&quot;elementLink&quot;
-        href=&quot;./../../xp/guidances/concepts/xp_practices,2.2937799026801584E-305.html&quot; guid=&quot;2.2937799026801584E-305&quot;&gt;XP
-        Practices&lt;/a&gt;.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    If you are familiar with XP and are interested in trying XP on your RUP project, we simply suggest you start by reading
-    the &lt;a class=&quot;elementLinkWithUserText&quot;
-    href=&quot;./../../xp/guidances/concepts/extreme_programming,5.2637267673584526E-306.html&quot;
-    guid=&quot;5.2637267673584526E-306&quot;&gt;Extreme Programming Roadmap&lt;/a&gt;.&lt;br /&gt;
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;Who&quot; name=&quot;Who&quot;&gt;Who is behind the plug-in?&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    This plug-in is a collaboration between &lt;a href=&quot;http://www.objectmentor.com/&quot; target=&quot;_blank&quot;&gt;Object Mentor Inc.&lt;/a&gt;
-    and&amp;nbsp;&lt;a href=&quot;http://www.ibm.com/&quot; target=&quot;_blank&quot;&gt;IBM Corporation&lt;/a&gt;.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/customcategories/guidelines_overview.xmi b/XP/xp/customcategories/guidelines_overview.xmi
deleted file mode 100644
index 1bd6357..0000000
--- a/XP/xp/customcategories/guidelines_overview.xmi
+++ /dev/null
@@ -1,6 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-8FSBtYSGN9EGWRr1N6fbPQ" name="guidelines_overview,2.0279775416255596E-305" guid="-8FSBtYSGN9EGWRr1N6fbPQ" changeDate="2005-12-06T04:35:18.106-0800">
-  <mainDescription>&lt;p&gt;
-    &lt;b&gt;Guidelines&lt;/b&gt; provide practical information about the implementation of specific activities in the process.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/customcategories/key_xp_concepts.xmi b/XP/xp/customcategories/key_xp_concepts.xmi
deleted file mode 100644
index b4d2e70..0000000
--- a/XP/xp/customcategories/key_xp_concepts.xmi
+++ /dev/null
@@ -1,2 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-hZ1cvRhigpDb6WbQckPWcA" name="key_xp_concepts,1.9093436569802954E-305" guid="-hZ1cvRhigpDb6WbQckPWcA" changeDate="2006-11-29T17:04:06.831-0800" version="1.0.0"/>
diff --git a/XP/xp/customcategories/references.xmi b/XP/xp/customcategories/references.xmi
deleted file mode 100644
index 2ebe0c8..0000000
--- a/XP/xp/customcategories/references.xmi
+++ /dev/null
@@ -1,3457 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-a8huB5Sn0Qjfe-SkZubH1w" name="references,_mtcqtmE-EdqnIZeW8YpHcA" guid="-a8huB5Sn0Qjfe-SkZubH1w" changeDate="2005-12-06T05:10:54.327-0800">
-  <mainDescription>&lt;a id=&quot;XE_references__bibliography_of&quot; name=&quot;XE_references__bibliography_of&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_bibliography__references_for&quot;
-name=&quot;XE_bibliography__references_for&quot;&gt;&lt;/a&gt; 
-&lt;h5&gt;
-    Topics
-&lt;/h5&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Business Modeling references&quot;&gt;Business Modeling&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Configuration Management references&quot;&gt;Configuration Management&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Miscellaneous references&quot;&gt;Miscellaneous&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Modeling and Unified Modeling Language references&quot;&gt;Modeling and Unified Modeling Language&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Object-Oriented Technology references&quot;&gt;Object-Oriented Technology&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Project Management references&quot;&gt;Project Management&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Requirement Management references&quot;&gt;Requirements Management&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Software Architecture references&quot;&gt;Software Architecture&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Software Development Process references&quot;&gt;Software Development Process&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a href=&quot;#Testing and Quality references&quot;&gt;Testing and Quality&lt;/a&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;h2 align=&quot;left&quot;&gt;
-    &lt;a id=&quot;Business Modeling references&quot; name=&quot;Business Modeling references&quot;&gt;Business Modeling&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BRO95&quot; name=&quot;BRO95&quot;&gt;BRO95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Frederick P. Brooks, Jr. 1995. &lt;i&gt;The Mythical Man-Month-Essays on Software Engineering&lt;/i&gt; 2nd ed.
-                    Reading, MA, Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A classic that should be read and re-read by everyone involved in software development. We recommend
-                    this 20-year anniversary edition rather than the original 1975 edition.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CLA97&quot; name=&quot;CLA97&quot;&gt;CLA97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Carl von Clausewitz 1997. &lt;i&gt;On War.&lt;/i&gt; Wordsworth Editions.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    One of the greatest books ever written on the subject of war, and applicable to the field of
-                    management.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CHM95&quot; name=&quot;CHM95&quot;&gt;CHM95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    James Champy 1995. &lt;i&gt;Reengineering Management: The Mandate for New Leadership.&lt;/i&gt; New York, NY:
-                    HarperCollins.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Gives some insight into the precarious art of managing a business (re-)engineering effort.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DVP93&quot; name=&quot;DVP93&quot;&gt;DVP93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Thomas H. Davenport 1993. &lt;i&gt;Process Innovation-Reengineering Work through&amp;nbsp;Information
-                    Technology.&lt;/i&gt; Boston, MA: Harvard Business School Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Solid and comprehensive introduction about how information technology enables business improvement and
-                    (re-)engineering.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GAO97&quot; name=&quot;GAO97&quot;&gt;GAO97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    United States General Accounting Office 1997. &lt;i&gt;Business Process Reengineering Assessment Guide&lt;/i&gt;.
-                    &lt;a href=&quot;http://www.gao.gov&quot; target=&quot;_blank&quot;&gt;http://www.gao.gov&lt;/a&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    Describes a framework for assessing a business (re-)engineering effort.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ERI00&quot; name=&quot;ERI00&quot;&gt;ERI00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Hans-Erik Eriksson and Magnus Penker 2000. &lt;i&gt;Business Modeling With UML: Business Patterns at
-                    Work.&amp;nbsp;&lt;/i&gt;New York, NY: John Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Presents a set of valuable patterns for business modeling.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;HAM93&quot; name=&quot;HAM93&quot;&gt;HAM93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Michael Hammer and James Champy 1993.&amp;nbsp; &lt;i&gt;Reengineering the Corporation-A Manifesto for Business
-                    Revolution.&lt;/i&gt;&amp;nbsp;&lt;br /&gt;
-                     New York, NY: HarperBusiness.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The book that popularized the movement of business (re-)engineering. An excellent complement to &lt;i&gt;The
-                    Object Advantage-Business Process Reengineering with Object Technology&lt;/i&gt; cited above&lt;i&gt;.&amp;nbsp;&lt;/i&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;HAR91&quot; name=&quot;HAR91&quot;&gt;HAR91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    H. James Harrington 1991. &lt;i&gt;Business Process Improvement: The Breakthrough Strategy for Total Quality,
-                    Productivity, and Competitiveness&lt;/i&gt;. New York, NY: McGraw-Hill.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Another contributor to the topic of business (re-)engineering.&lt;i&gt;&amp;nbsp;&lt;/i&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;JAC94&quot; name=&quot;JAC94&quot;&gt;JAC94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ivar Jacobson, Maria Ericsson, and Agneta Jacobson 1994. &lt;i&gt;The Object Advantage-Business Process
-                    Reengineering with Object Technology&lt;/i&gt;. Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The basis of the Business Modeling discipline, this is the very first book that applied object
-                    technology to the field of business modeling.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KAP96&quot; name=&quot;KAP96&quot;&gt;KAP96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Robert Kaplan and David Norton 1996. &lt;i&gt;The Balanced Scorecard&lt;/i&gt;. Boston, MA: Harvard Business School
-                    Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    Best practices for successfully implementing the Balanced Scorecard.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KOT96&quot; name=&quot;KOT96&quot;&gt;KOT96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    John P. Kotter 1996. &lt;i&gt;Leading Change&lt;/i&gt;. Boston, MA: Harvard Business School Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    A practical, proven model for planning and managing organizational change.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MARS00&quot; name=&quot;MARS00&quot;&gt;MARS00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Chris Marshall 2000. &lt;i&gt;Enterprise Modeling with UML&lt;/i&gt;. Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    Describes how to create business models that facilitate the development software systems.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;NDL97&quot; name=&quot;NDL97&quot;&gt;NDL97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    David A. Nadler and Michael L. Tushman 1999.&amp;nbsp; &lt;i&gt;Competing by Design-the Power of Organizational
-                    Architecture.&lt;/i&gt; Oxford University Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Defines organizational architecture and capabilities as a source of competitive advantage.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;OHM91&quot; name=&quot;OHM91&quot;&gt;OHM91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Kenichi Ohmae 1991.&amp;nbsp; &lt;i&gt;The Mind of the Strategist: The Art of Japanese Business.&lt;/i&gt; McGraw-Hill.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    A crisp and practical guide to strategic management.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ODL98&quot; name=&quot;ODL98&quot;&gt;ODL98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    James J. Odell 1998.&amp;nbsp; &lt;i&gt;Advanced Object-Oriented Analysis &amp;amp; Design Using UML.&lt;/i&gt; Cambridge
-                    University Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Provides a good overview, among other things, on the topic of business rules.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;PFE99&quot; name=&quot;PFE99&quot;&gt;PFE99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Jeffrey Pfeffer and Robert Sutton 1999.&amp;nbsp; &lt;i&gt;The Knowing-Doing Gap.&lt;/i&gt; Boston, MA: Harvard
-                    Business School Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    Discusses the reasons why some organizations do not apply their own lessons learned and provides
-                    pointers for how to overcome this challenge.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;PLR99&quot; name=&quot;PLR99&quot;&gt;PLR99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    R. Steven Player (Editor) and David Keys (Editor) 1999.&amp;nbsp; &lt;i&gt;Activity-Based Management: Arthur
-                    Andersen's Lessons from the ABM Battlefield.&lt;/i&gt; Wiley Cost Management Series.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    An introduction to understanding the management of costs, and how to implement activity-based costing
-                    (ABC) and activity-based management (ABM) systems.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;POR98&quot; name=&quot;POR98&quot;&gt;POR98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Michael Porter 1998.&amp;nbsp; &lt;i&gt;Competitive Strategy: Techniques for Analyzing Industries and
-                    Competitors.&lt;/i&gt; Simon &amp;amp; Schuster, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    A practical guide for the strategic planner.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ROS97&quot; name=&quot;ROS97&quot;&gt;ROS97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ron Ross 1997.&amp;nbsp; &lt;i&gt;The Business Rule Book: Classifying, Defining and Modeling Rules.&lt;/i&gt; Boston,
-                    MA: Database Research Group.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    A complete handbook for the business rules analyst.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;SEY98&quot; name=&quot;SEY98&quot;&gt;SEY98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Patricia Seybold 1998.&amp;nbsp; &lt;i&gt;Customers.com.&lt;/i&gt; Random House Publishing.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;1%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;150%&quot;&gt;
-                    An excellent collection of practical guidelines and case studies on the benefits of e-business and
-                    (re-)engineering.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2 align=&quot;left&quot;&gt;
-    &lt;a id=&quot;Configuration Management references&quot; name=&quot;Configuration Management references&quot;&gt;Configuration Management&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BER92&quot; name=&quot;BER92&quot;&gt;BER92&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    H. Berlack 1992. &lt;i&gt;Software Configuration Management.&lt;/i&gt; New York, NY: John Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BUC93&quot; name=&quot;BUC93&quot;&gt;BUC93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    J. Buckley 1993. &lt;i&gt;Implementing Configuration Management, Hardware, Software and Firmware.&lt;/i&gt;&amp;nbsp;
-                    Los Alamitos, CA: IEEE Computer Science Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;WHI00&quot; name=&quot;WHI00&quot;&gt;WHI00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Brian White and Geoff Glemm 2000. &lt;i&gt;Software Configuration Management Strategies and Rational
-                    ClearCase: A Practical Introduction.&lt;/i&gt; Addison-Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;WHI91&quot; name=&quot;WHI91&quot;&gt;WHI91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    David Whitgift 1991. &lt;i&gt;Methods and Tools for Software Configuration Management.&lt;/i&gt;&amp;nbsp; New York,
-                    NY: John Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2&gt;
-    &lt;a id=&quot;Miscellaneous references&quot; name=&quot;Miscellaneous references&quot;&gt;Miscellaneous&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOU94&quot; name=&quot;BOU94&quot;&gt;BOU94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Serge Bouchy 1994.&amp;nbsp; &lt;i&gt;L'ingénierie des systèmes informatiques évolutifs,&lt;/i&gt; Paris, France:
-                    Eyrolles, 330p.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BRO95&quot; name=&quot;BRO95&quot;&gt;BRO95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Frederick P. Brooks, Jr. 1995. &lt;i&gt;The Mythical Man-Month-Essays on Software Engineering&lt;/i&gt; 2nd ed.
-                    Reading, MA, Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A classic that should be read and re-read by everyone involved in software development. We recommend
-                    this 20-year anniversary edition rather than the original 1975 edition.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;con92&quot; name=&quot;con92&quot;&gt;CON92&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    D. Conner 1992. &lt;i&gt;Managing at the Speed of Change.&lt;/i&gt; New York, NY: Random House, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DAT99&quot; name=&quot;DAT99&quot;&gt;DAT99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    C.J. Date 1999. &lt;i&gt;An Introduction to Database Systems.&lt;/i&gt;&amp;nbsp; 7th ed.&amp;nbsp; New York, NY:
-                    Addison-Wesley Publishing Company, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Excellent introduction, reference, and source of background information on Database Systems.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DAV95&quot; name=&quot;DAV95&quot;&gt;DAV95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Alan Davis 1995. &lt;i&gt;201 Principles of Software Development.&lt;/i&gt;&amp;nbsp; New York, NY: McGraw-Hill.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Full of good advice for every team member on a project.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DEG90&quot; name=&quot;DEG90&quot;&gt;DEG90&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Peter DeGrace and Leslie Stahl 1990. &lt;i&gt;Wicked Problems, Righteous Solutions: A Catalog of Modern
-                    Software Engineering Practices.&lt;/i&gt; Englewood Cliffs, NJ: Yourdon Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    An insightful book on various process lifecycles and their origins, flaws, and strengths; useful for
-                    understanding the importance of process.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DEI84&quot; name=&quot;DEI84&quot;&gt;DEI84&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Harvey M. Deitel 1984. &lt;i&gt;An Introduction to Operating Systems.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;FIS96&quot; name=&quot;FIS96&quot;&gt;FIS96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Charles Fishman 1996. &lt;i&gt;Johnson Space Center Shuttle Software Group, &quot;They Write the Right
-                    Stuff&quot;&lt;/i&gt;&lt;i&gt;.&lt;/i&gt; Fastcompany, Issue 6, p. 95, December, 1996.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GRA97&quot; name=&quot;GRA97&quot;&gt;GRA97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ian Graham, et al. 1997. &lt;i&gt;The OPEN Process Specification&lt;/i&gt;. Harlow, England: Addison Wesley
-                    Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Another process model, coming from down under that shares some principles with the Rational Unified
-                    Process (RUP).
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;hac97&quot; name=&quot;hac97&quot;&gt;HAC97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    JoAnn T. Hackos and Dawn M. Stevens 1997. &lt;i&gt;Standards for Online Communication.&lt;/i&gt; John Wiley and
-                    Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    For the modern technical writer, this book has become the defacto standard. It defines a process for
-                    developing user manuals, specifically focusing on how you produce online help systems.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;HER99&quot; name=&quot;HER99&quot;&gt;HER99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Peter Herzum and Oliver Sims 1999. &lt;i&gt;Business Component Factory: A Comprehensive Overview of
-                    Component-Based Development for the Enterprise.&lt;/i&gt; John Wiley &amp;amp; Sons.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Defines and describes component-based development-from creating small components to creating
-                    federations of large component-based systems.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    IBM2000
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;IBM System Integrated Method.&lt;/i&gt; International Business Machines Corporation 1998, 1999, 2000.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    IBM99a
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;An Approach to Designing e-business Solutions.&lt;/i&gt; International Business Machines Corporation 1999.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    &lt;a href=&quot;http://www.redbooks.ibm.com/abstracts/sg245949.html&quot;
-                    target=&quot;_blank&quot;&gt;http://www.redbooks.ibm.com/abstracts/sg245949.html&lt;/a&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    IBM99b
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;Design Considerations: From Client Server Applications to e-business Applications.&lt;/i&gt; International
-                    Business Machines Corporation 1999.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    &lt;a href=&quot;http://www.redbooks.ibm.com/abstracts/sg245503.html&quot;
-                    target=&quot;_blank&quot;&gt;http://www.redbooks.ibm.com/abstracts/sg245503.html&lt;/a&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    IBM99c
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;The Front of IBM WebSphere-Building e-business User Interfaces.&lt;/i&gt; International Business Machines
-                    Corporation 1999.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    &lt;a href=&quot;http://www.redbooks.ibm.com/abstracts/sg245488.html&quot;
-                    target=&quot;_blank&quot;&gt;http://www.redbooks.ibm.com/abstracts/sg245488.html&lt;/a&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    IBM98a
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;Architecture Description Standard: Overview.&lt;/i&gt;&amp;nbsp; International Business Machines Corporation
-                    1998.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    IBM98b
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;Architecture Description Standard: Semantic Specification.&lt;/i&gt;&amp;nbsp; International Business Machines
-                    Corporation 1998.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Other relevant Web sites for the preceding IBM references are:&lt;br /&gt;
-                     &lt;a href=&quot;http://www.redbooks.ibm.com&quot; target=&quot;_blank&quot;&gt;http://www.redbooks.ibm.com&lt;br /&gt;
-                    &lt;/a&gt; &lt;a href=&quot;http://www.ibm.com/e-business/&quot; target=&quot;_blank&quot;&gt;http://www.ibm.com/e-business/&lt;br /&gt;
-                    &lt;/a&gt; &lt;a href=&quot;http://www.ibm.com/software&quot; target=&quot;_blank&quot;&gt;http://www.ibm.com/software&lt;br /&gt;
-                    &lt;/a&gt; &lt;a href=&quot;http://www.ibm.com/developer/&quot; target=&quot;_blank&quot;&gt;http://www.ibm.com/developer/&lt;br /&gt;
-                    &lt;/a&gt; &lt;a href=&quot;http://www.ibm.com/services/&quot; target=&quot;_blank&quot;&gt;http://www.ibm.com/services/&lt;/a&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;IBM97&quot; name=&quot;IBM97&quot;&gt;IBM97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    IBM 1997. &lt;i&gt;Developing Object-Oriented Software&lt;/i&gt;&lt;i&gt;-&lt;/i&gt;&lt;i&gt;An Experienced- based Approach.&lt;/i&gt;
-                    Upper Saddle River, NJ: Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Like the RUP, an iterative, incremental, object-oriented, scenario-driven, risk-aware process developed
-                    by the IBM Object Technology Center.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;IE610.12&quot; name=&quot;IE610.12&quot;&gt;IE610.12&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    IEEE Std 610.12-1990. &lt;i&gt;IEEE Standard Glossary of Software Engineering Terminology.&lt;/i&gt; The Institute
-                    of Electrical and Electronics Engineers, Inc.: New York, NY, 10017-2394, USA. 1990.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; height=&quot;23&quot;&gt;
-                    &lt;a id=&quot;JAV03&quot; name=&quot;JAV03&quot;&gt;JAV03&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    JavaTM 2 Platform, Standard Edition, v 1.4.2 API Specification -
-                    http://java.sun.com/j2se/1.4.2/docs/api/index.html
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;jel93&quot; name=&quot;jel93&quot;&gt;JEL93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    J. Jellison 1993. &lt;i&gt;Overcoming Resistance: A Practical Guide to Producing Change in the
-                    Workplace.&lt;/i&gt;&amp;nbsp; New York, NY: Simon &amp;amp; Schuster, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KAT93&quot; name=&quot;KAT93&quot;&gt;KAT93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Jon R. Katzenbach and Douglas K. Smith 1993. &lt;i&gt;The Wisdom of Teams.&lt;/i&gt; New York, NY: Harper Business.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The secret of effective teams.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KET98&quot; name=&quot;KET98&quot;&gt;KET98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Nasser Kettani, et al. 1998. &lt;i&gt;De Merise à UML.&lt;/i&gt; Paris, France: Editions Eyrolles.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Merise is a very popular software development methodology in France, which has been upgraded to use
-                    UML. It has some similitude with the RUP.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;LEA97&quot; name=&quot;LEA97&quot;&gt;LEA97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Doug Lea 1999.&amp;nbsp; &lt;i&gt;Concurrent Programming in Java.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MCA95&quot; name=&quot;MCA95&quot;&gt;MCA95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Jim McCarthy 1995.&amp;nbsp; &lt;i&gt;Dynamics of Software Development.&lt;/i&gt; Redmond, WA: Microsoft Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Fifty-three rules of thumb by a Microsoft development manager.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MCO97&quot; name=&quot;MCO97&quot;&gt;MCO97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Steve McConnell 1997.&amp;nbsp; &lt;i&gt;Software Project Survival Guide.&lt;/i&gt; Redmond, WA: Microsoft Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A collection of practical experience on how to deliver successful software projects.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MCO93&quot; name=&quot;MCO93&quot;&gt;MCO93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Steve McConnell 1993. &lt;i&gt;Code Complete&lt;/i&gt;&lt;i&gt;-&lt;/i&gt;&lt;i&gt;A Practical Handbook of Software Construction.&lt;/i&gt;
-                    Redmond, WA: Microsoft Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A great book for the implementers and for testers looking at the implementation, integration, and test
-                    aspects of the development process.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;mos98&quot; name=&quot;mos98&quot;&gt;MOS98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Microsoft 1998. The &lt;i&gt;Microsoft Manual of Style for Technical Publications.&lt;/i&gt;&amp;nbsp; Redmond, WA:
-                    Microsoft Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;STA97&quot; name=&quot;STA97&quot;&gt;STA97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Jennifer Stapleton 1997.&amp;nbsp; &lt;i&gt;The Dynamic System Development Method.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    At 15,000 feet, the DSDM approach could be seen as an introduction to the RUP. Although they use a
-                    different terminology, the two processes are very close to each other, and you can see the RUP as an
-                    instance or an implementation of&amp;nbsp; DSDM.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;TAN86&quot; name=&quot;TAN86&quot;&gt;TAN86&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Andrew S. Tannenbaum 1986. &lt;i&gt;Operating Systems: Design and Implementation.&amp;nbsp;&lt;/i&gt; Upper Saddle
-                    River, NJ: Prentice Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;WID00&quot; name=&quot;WID00&quot;&gt;WID00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    R. Max Wideman and PMForum, February, 1999 and January, 2000. &lt;i&gt;Wideman Comparative Glossary of
-                    Project Management Terms v2.0.&lt;/i&gt; www.pmforum.org
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This great collection of various software engineering terms and their many definitions is available
-                    online at &lt;a href=&quot;http://www.pmforum.org/library/glossary/&quot;
-                    target=&quot;_blank&quot;&gt;http://www.pmforum.org/library/glossary/&lt;/a&gt;.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;YOU97&quot; name=&quot;YOU97&quot;&gt;YOU97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Edward Yourdon 1997. &lt;i&gt;Death March: Managing &quot;Mission Impossible&quot; Projects.&lt;/i&gt; Upper Saddle River,
-                    NJ: Prentice Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    An interesting view on project troubles.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2 align=&quot;left&quot;&gt;
-    &lt;a id=&quot;Modeling and Unified Modeling Language references&quot;
-    name=&quot;Modeling and Unified Modeling Language references&quot;&gt;Modeling and Unified Modeling Language&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;BOO98&quot; name=&quot;BOO98&quot;&gt;BOO98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    G. Booch, J. Rumbaugh, and I. Jacobson, 1998. &lt;i&gt;UML User Guide&lt;/i&gt;. Addison-Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Published at the same time as Rational Unified Process 5.1, this book is an excellent user's guide on
-                    UML by its main authors.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;CHE01&quot; name=&quot;CHE01&quot;&gt;CHE01&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    John Cheesman and John Daniels, 2001. &lt;i&gt;UML Components: A Simple Process for Specifying
-                    Component-Based Software&lt;/i&gt;. Addison-Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This book provides a lot of in-depth practical guidance for specifying component-based systems, at the
-                    same time remaining compact and readable.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;CONA99&quot; name=&quot;CONA99&quot;&gt;CONA99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Jim Conallen, 1999. &lt;i&gt;Building Web Applications with UML.&lt;/i&gt; Addison-Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A good introduction to the basics of web application development in the context of the RUP. This book
-                    also shows how to use the UML to model web applications and introduces a Web Application Extension to
-                    the UML.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;DOUG98&quot; name=&quot;DOUG98&quot;&gt;DOUG98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Bruce Powel Douglass 1998. &lt;i&gt;Real-Time UML.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Using UML as the notation, this book offers good advice on the application of object-oriented
-                    technology for real-time systems.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot;&gt;
-                    &lt;a id=&quot;ERI04&quot; name=&quot;ERI04&quot;&gt;ERI04&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Hans-Erik Eriksson, Magnus Penker, Brian Lyons and David Fado 2004. &lt;i&gt;UML 2 Toolkit&lt;/i&gt;. Indianopolis:
-                    Wiley Publishing, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;ERI97&quot; name=&quot;ERI97&quot;&gt;ERI97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Hans-Erik Eriksson and Magnus Penker 1997. &lt;i&gt;UML Toolkit&lt;/i&gt;. New York: John Wiley &amp;amp; Sons.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A more comprehensive book on UML as seen from Sweden by another pair of Rational friends.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;FOW97&quot; name=&quot;FOW97&quot;&gt;FOW97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Martin Fowler 1997. &lt;i&gt;UML Distilled-Applying the standard object modeling language&lt;/i&gt;. Addison-Wesley
-                    Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A very nice little introduction to UML if you're in a hurry.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;FRA03&quot; name=&quot;FRA03&quot;&gt;FRA03&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    David S. Frankel 2003. &lt;i&gt;Model Driven Architecture: Applying MDA to Enterprise Computing.&lt;/i&gt; John
-                    Wiley &amp;amp; Sons.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td&gt;
-                    A foundational work on the OMG's Model Driven Architecture initiative, written by one of its principal
-                    developers.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;KLE03&quot; name=&quot;KLE03&quot;&gt;KLE03&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Anneke Kleppe, Jos Warmer and Wim Bast 2003. &lt;i&gt;MDA Explained-The Model Driven
-                    Architecture(TM):Practice and Promise.&lt;/i&gt; Addison-Wesley.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td&gt;
-                    More useful insights into MDA from a practitioner's viewpoint, written by contributors to the creation
-                    of MDA.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;LAR02&quot; name=&quot;LAR02&quot;&gt;LAR02&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Craig Larman 2002.&amp;nbsp; &lt;i&gt;Applying UML and Patterns: An Introduction to Object-Oriented Analysis and
-                    Design and the Unified Process,&lt;/i&gt; 2nd ed. Prentice-Hall, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This book is a great illustration of what happens in the Analysis &amp;amp; Design discipline. It teaches
-                    analysis and design, the use of UML, and the application of the concept of pattern in the context of
-                    the Unified Process. By presenting the case study in an iterative, risk-driven, architecture-centric
-                    process, Mr. Larman's advice has a realistic context. He exposes the dynamics of what really happens in
-                    software development and shows the external forces at play. The design activities are connected to
-                    other tasks, and they no longer appear as a purely cerebral activity of systematic transformations or
-                    creative intuition.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;MEL04&quot; name=&quot;MEL04&quot;&gt;MEL04&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Stephen J. Mellor, Kendall Scott, Axel Uhl, Dirk Weise 2004. &lt;i&gt;MDA Distilled-Principles of
-                    Model-Driven Architecture.&lt;/i&gt; Addison-Wesley.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td&gt;
-                    Extracts and presents the essence of MDA, with an emphasis on the technology for executable models.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;MUL98&quot; name=&quot;MUL98&quot;&gt;MUL98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Pierre-Alain Muller 1998.&amp;nbsp; &lt;i&gt;Instant UML.&lt;/i&gt; Wrox Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Another short introduction to UML by a former colleague.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;NBG01&quot; name=&quot;NBG01&quot;&gt;NBG01&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Eric J. Naiburg and Robert A. Maksimchuk 2001. &lt;i&gt;UML For Database Design&lt;/i&gt;. New York, NY:
-                    Addison-Wesley Publishing Company, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Application of UML to database modeling and design.&amp;nbsp; Supported throughout by a case study.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;OMG03&quot; name=&quot;OMG03&quot;&gt;OMG03&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;MDA Guide Version 1.0.1.&lt;/i&gt; Object Management Group. Document omg/2003-06-01, June 2003
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td&gt;
-                    &lt;p&gt;
-                        A specification of the concepts and terminology of Model Driven Architecture from the OMG.
-                    &lt;/p&gt;
-                    &lt;p&gt;
-                        &lt;a href=&quot;http://www.omg.org/mda/specs.htm&quot; target=&quot;_blank&quot;&gt;http://www.omg.org/mda/specs.htm&lt;/a&gt;
-                    &lt;/p&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;QUA98&quot; name=&quot;QUA98&quot;&gt;QUA98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Terry Quatrani 1998. &lt;i&gt;Visual Modeling with Rational Rose and UML.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Provides step-by-step guidance on how to build UML models. At the same time, it follows the RUP, in
-                    effect providing a small scale example.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot;&gt;
-                    &lt;a id=&quot;RUM05&quot; name=&quot;RUM05&quot;&gt;RUM05&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    James Rumbaugh, Ivar Jacobson, Grady Booch, 2005. &lt;i&gt;The Unified Modeling Language Reference Manual,
-                    second edition.&lt;/i&gt; Addison-Wesley, Boston.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;RUM98&quot; name=&quot;RUM98&quot;&gt;RUM98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    J. Rumbaugh, I. Jacobson, and G. Booch, 1998. &lt;i&gt;UML Reference Manual.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Certainly more digestible than the OMG standard; UML fully exposed by its main authors.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;UML01&quot; name=&quot;UML01&quot;&gt;UML01&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;OMG Unified Modeling Language Specification, Version 1.4.&amp;nbsp;&lt;/i&gt; Rational Software Corporation,
-                    18880 Homestead Road, Cupertino, CA 95014, and Object Management Group, Inc., 492 Old Connecticut Path,
-                    Framingham, MA 01701.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The latest specification of the UML. Available online at &lt;a href=&quot;http://www.rational.com/uml&quot;
-                    target=&quot;_blank&quot;&gt;http://www.rational.com/uml&lt;/a&gt;.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot; height=&quot;21&quot;&gt;
-                    &lt;a id=&quot;UML04&quot; name=&quot;UML04&quot;&gt;UML04&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;OMG Unified Modeling Language Specification, Version 2.0.&amp;nbsp;&lt;/i&gt; Object Management Group, Inc.,
-                    Needham, MA 02494
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;11%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Final Adopted Specification (2003-08-02)
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;UML96&quot; name=&quot;UML96&quot;&gt;UML96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    G. Booch, J. Rumbaugh, and I. Jacobson 1996. &lt;i&gt;The Unified Modeling Language for Object-Oriented
-                    Development.&lt;/i&gt; Documentation set, version 0.9 Addendum, Rational Software Corporation.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;11%&quot;&gt;
-                    &lt;a id=&quot;UML95&quot; name=&quot;UML95&quot;&gt;UML95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    G. Booch and J. Rumbaugh 1995. &lt;i&gt;Unified Method for Object-Oriented Development.&lt;/i&gt; Documentation
-                    set, version 0.8, Rational Software Corporation.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2 align=&quot;left&quot;&gt;
-    &lt;a id=&quot;Object-Oriented Technology references&quot; name=&quot;Object-Oriented Technology references&quot;&gt;Object-Oriented
-    Technology&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOO93&quot; name=&quot;BOO93&quot;&gt;BOO93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Grady Booch 1993. &lt;i&gt;Object-Oriented Analysis and Design with Applications,&lt;/i&gt; 2nd edition. Redwood
-                    City, CA: The Benjamin/Cummings Publishing Company.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BUH96&quot; name=&quot;BUH96&quot;&gt;BUH96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    R. J. A. Buhr and R. S. Casselman 1996. &lt;i&gt;Use Case Maps for Object-Oriented Systems.&lt;/i&gt; Upper Saddle
-                    River, NJ: Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This book develops some other views on use cases.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;JAC92&quot; name=&quot;JAC92&quot;&gt;JAC92&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ivar Jacobson, et al. 1992. &lt;i&gt;Object-Oriented Software Engineering-A Use Case-Driven Approach&lt;/i&gt;,
-                    Wokingham, England: Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;RUM91&quot; name=&quot;RUM91&quot;&gt;RUM91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    James Rumbaugh, et al. 1991. &lt;i&gt;Object-Oriented Modeling and Design.&lt;/i&gt; Upper Saddle River, NJ:
-                    Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The three books above are the original roots to the object-oriented analysis and design discipline from
-                    &quot;the three amigos&quot;, just before the advent of the UML and the RUP. Despite the use of their original
-                    notations, they are still the key references for OO designers.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;RUM96&quot; name=&quot;RUM96&quot;&gt;RUM96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    James Rumbaugh 1996. &lt;i&gt;OMT Insights.&lt;/i&gt; New York: SIGS Books.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A complement to the original&amp;nbsp; OMT book, diving into special topics: inheritance, use cases, and so
-                    on.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;SEL94&quot; name=&quot;SEL94&quot;&gt;SEL94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Bran Selic, Garth Gullekson, and Paul Ward 1994. &lt;i&gt;Real-time Object-Oriented Modeling.&lt;/i&gt; New York,
-                    NY: John Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The reference work on using object technology for the design of reactive systems by the people who have
-                    brought us &lt;i&gt;ObjecTime Developer&lt;/i&gt;.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;WIR90&quot; name=&quot;WIR90&quot;&gt;WIR90&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Rebecca Wirfs-Brock, Brian Wilkerson, and Lauren Wiener 1990. &lt;i&gt;Designing Object-Oriented
-                    Software.&lt;/i&gt; Upper Saddle River, NJ: Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This book describes the Class, Responsibility, Collaboration (CRC) approach to object-oriented software
-                    development.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2 align=&quot;left&quot;&gt;
-    &lt;a id=&quot;Project Management references&quot; name=&quot;Project Management references&quot;&gt;Project Management&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;AMI95&quot; name=&quot;AMI95&quot;&gt;AMI95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    K. Pulford, A. Kuntzmann-Combelles, and S. Shirlaw 1995. &lt;i&gt;A Quantitative Approach to Software
-                    Management-The AMI Handbook.&lt;/i&gt; Addison Wesley Longman.&amp;nbsp;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOE00&quot; name=&quot;BOE00&quot;&gt;BOE00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Barry W. Boehm et al, 2000. Software Cost Estimation with COCOMO II. Upper Saddle River, NJ:
-                    Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The successor to the original classic work.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOE81&quot; name=&quot;BOE81&quot;&gt;BOE81&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Barry W. Boehm 1981. &lt;i&gt;Software Engineering Economics.&lt;/i&gt; Upper Saddle River, NJ: Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A classic work on software effort estimation that describes the original COCOMO estimation model.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOE91&quot; name=&quot;BOE91&quot;&gt;BOE91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Barry W. Boehm 1991. &lt;i&gt;Software Risk Management: Principles and Practices&lt;/i&gt;, &lt;i&gt;IEEE Software,&lt;/i&gt;
-                    Jan. 1991, IEEE, pp.32-41.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Still the best little introduction to risk management.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOO95&quot; name=&quot;BOO95&quot;&gt;BOO95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Grady Booch 1995. &lt;i&gt;Object Solutions-Managing the Object-Oriented Project.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A pragmatic book for managers of object-oriented projects; one of the sources on the underlying
-                    philosophy of the RUP.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CAN01&quot; name=&quot;CAN01&quot;&gt;CAN01&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Murray Cantor 2001. &lt;i&gt;Software Leadership.&lt;/i&gt; Addison-Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CAR93&quot; name=&quot;CAR93&quot;&gt;CAR93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Marvin J. Carr, et al. 1993. &lt;i&gt;Taxonomy-Based Risk Identification,&lt;/i&gt; Technical Report
-                    CMU/SEI-93-TR-6, Pittsburgh, PA, SEI, June 1993, 24p.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Provides a source of inspiration to get started on your own list of risks.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CHA89&quot; name=&quot;CHA89&quot;&gt;CHA89&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Robert Charette 1989. &lt;i&gt;Software Engineering Risk Analysis and Management.&lt;/i&gt; New York, NY:
-                    McGraw-Hill.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Practical perspective on risk management.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CHID94&quot; name=&quot;CHID94&quot;&gt;CHID94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Chidamber and Kemerer 1994. &lt;i&gt;A metrics suite for object-oriented design,&lt;/i&gt; IEEE Transactions on
-                    Software Engineering, 20(6), 1994.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    One of the original contributions to the field of OO software metrics.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CLE96&quot; name=&quot;CLE96&quot;&gt;CLE96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Robert T. Clemen 1996. &lt;i&gt;Making Hard Decisions: An Introduction to Decision Analysis.&lt;/i&gt; Duxbury
-                    Press.&amp;nbsp;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Thorough yet accessible treatment of the fundamentals of decision analysis.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DEV95&quot; name=&quot;DEV95&quot;&gt;DEV95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Michael T. Devlin and Walker E. Royce.&amp;nbsp; &lt;i&gt;Improving Software Economics in the Aerospace and
-                    Defense Industry,&lt;/i&gt; Technical Paper TP-46, Santa Clara, CA, Rational Software Corporation, 1995.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;EVA98&quot; name=&quot;EVA98&quot;&gt;EVA98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    James R. Evans and David L. Olson 1998. &lt;i&gt;Introduction to Simulation and Risk Analysis.&lt;/i&gt;&amp;nbsp;
-                    Upper Saddle River, NJ: Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Good introduction to the use of simulation for business modeling.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;FAI94&quot; name=&quot;FAI94&quot;&gt;FAI94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Richard Fairley 1994. &quot;Risk Management for Software Project,&quot; &lt;i&gt;IEEE Software,&lt;/i&gt; 11 (3), May 1994,
-                    pp.57-67
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Straightforward strategy for risk management if you have never done this before.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GIL88&quot; name=&quot;GIL88&quot;&gt;GIL88&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Tom Gilb 1988. &lt;i&gt;Principles of Software Engineering Management.&lt;/i&gt; Harlow, England: Addison Wesley
-                    Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A great book by a pioneer of iterative development, it's full of pragmatic advice for the project
-                    manager.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;HEND96&quot; name=&quot;HEND96&quot;&gt;HEND96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Brian Henderson-Sellers 1996. &lt;i&gt;Object-Oriented Metrics, Measures of Complexity.&lt;/i&gt; Prentice Hall
-                    PTR.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Good, detailed coverage of OO-specific metrics.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;JON94&quot; name=&quot;JON94&quot;&gt;JON94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Capers Jones 1994. &lt;i&gt;Assessment and Control of Software Risks.&lt;/i&gt; Yourdon Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    An indispensable source of risks to check your list against to make sure it's is complete.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KAR96&quot; name=&quot;KAR96&quot;&gt;KAR96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Dale Karolak 1996. &lt;i&gt;Software Engineering Risk Management.&lt;/i&gt; Los Alamitos, CA: IEEE Computer Society
-                    Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Offers more sophisticated advice and techniques for risk management.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MCO96&quot; name=&quot;MCO96&quot;&gt;MCO96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Steve McConnell 1996. &lt;i&gt;Rapid Development.&lt;/i&gt; Redmond, WA: Microsoft Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Excellent coverage of good practice for rapid software development
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MSP97&quot; name=&quot;MSP97&quot;&gt;MSP97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    User's Guide for Microsoft Project 98, Microsoft Corporation, 1997.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;OCO94&quot; name=&quot;OCO94&quot;&gt;OCO94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Fergus O'Connell 1994. &lt;i&gt;How to Run Successful Projects.&lt;/i&gt; New York, NY: Prentice-Hall
-                    International.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A real gem! Everything you really need to know to manage your first project, in 170 pages.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;PMI96&quot; name=&quot;PMI96&quot;&gt;PMI96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;A Guide to the Project Management Body of Knowledge.&lt;/i&gt; The Project Management Institute: Newton
-                    Square, PA, 19073-3299, USA. 1996.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;PUT92&quot; name=&quot;PUT92&quot;&gt;PUT92&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Lawrence Putnam &amp;amp; Ware Myers 1992. &lt;i&gt;Measures for Excellence: Reliable Software On Time, Within
-                    Budget.&lt;/i&gt; Yourdon Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ROY98&quot; name=&quot;ROY98&quot;&gt;ROY98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Walker Royce 1998. &lt;i&gt;Software Project Management: A Unified Framework.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    An indispensable companion to the RUP, this book describes the spirit of the Rational Process and its
-                    underlying software economics. Full of great advice for the project manager.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;VOS96&quot; name=&quot;VOS96&quot;&gt;VOS96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    David Vose 1996. &lt;i&gt;Quantitative Risk Analysis: A Guide to Monte Carlo Simulation Modeling.&lt;/i&gt; John
-                    Wiley &amp;amp; Sons.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A good guide to the modeling of uncertainty using Monte Carlo techniques.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;WHIT97&quot; name=&quot;WHIT97&quot;&gt;WHIT97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Scott Whitmire 1997. &lt;i&gt;Object-Oriented Design Measurement.&lt;/i&gt; John Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A good, if mathematically challenging, treatment of the theoretical basis of software measurement.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2 align=&quot;left&quot;&gt;
-    &lt;a id=&quot;Requirement Management references&quot; name=&quot;Requirement Management references&quot;&gt;Requirements Management&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;AND96&quot; name=&quot;AND96&quot;&gt;AND96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Stephen J. Andriole 1996. &lt;i&gt;Managing Systems Requirements: Methods, Tools, and Cases.&lt;/i&gt; McGraw Hill.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BEY98&quot; name=&quot;BEY98&quot;&gt;BEY98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Hugh Beyer and Karen Holtzblatt 1998. &lt;i&gt;Contextual Design.&lt;/i&gt; San Francisco, CA: Morgan Kaufmann
-                    Publishers.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BIT03&quot; name=&quot;BIT03&quot;&gt;BIT03&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Kurt Bittner and Ian Spence 2003. &lt;i&gt;Use Case Modeling.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Comprehensive coverage of use case techniques and practices, including useful examples showing how
-                    use-case specifications evolve over time.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;COC01a&quot; name=&quot;COC01a&quot;&gt;COC01a&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Alistair Cockburn 2001. &lt;i&gt;Writing Effective Use Cases.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Excellent guidance for those who need to write use cases. Multiple styles and techniques contrasted
-                    with insight in an unbiased way. Many helpful tips to improve your use cases.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CON99&quot; name=&quot;CON99&quot;&gt;CON99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Larry Constantine and Lucy A.D. Lockwood 1999. &lt;i&gt;Software for Use.&lt;/i&gt; Reading, MA: Addison Wesley
-                    Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    An excellent book on user-centric design, focusing on techniques and practical guidelines for
-                    developing software that is usable.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;COO99&quot; name=&quot;COO99&quot;&gt;COO99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Alan Cooper1999. &lt;i&gt;The Inmates are Running the Asylum.&lt;/i&gt; Indianapolis, IN: SAMS.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DAV93&quot; name=&quot;DAV93&quot;&gt;DAV93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Alan Davis 1993. &lt;i&gt;Software Requirements-Objects, Functions and States.&lt;/i&gt; Englewood Cliffs, NJ:
-                    Prentice Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;FIS91&quot; name=&quot;FIS91&quot;&gt;FIS91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Roger Fisher and William Ury 1991. &lt;i&gt;Getting to Yes-Negotiating Agreement Without Giving In, 2nd
-                    Edition.&lt;/i&gt; Penguin Books USA.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GAU89&quot; name=&quot;GAU89&quot;&gt;GAU89&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Donald Gause and Gerald Weinberg 1989. &lt;i&gt;Exploring Requirements-Quality Before Design.&lt;/i&gt; New York,
-                    NY: Dorset House.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GOU88&quot; name=&quot;GOU88&quot;&gt;GOU88&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    John D. Gould 1988. &quot;How to Design Usable Systems&quot;, in Helander, Martin, ed. &lt;i&gt;Handbook of Computer
-                    Interaction&lt;/i&gt;, pp. 757-789, North-Holland, Amsterdam, The Netherlands.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GOU87&quot; name=&quot;GOU87&quot;&gt;GOU87&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    John D. Gould, Stephen J. Boies, Stephen Levy, John T. Richards and Jim Schoonard 1987. &quot;The 1984
-                    Olympic Message System: a test of behavioral principles of system design&quot;, in &lt;i&gt;Communications of the
-                    ACM&lt;/i&gt;, Vol. 30, No. 9, pp. 758-769.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GRA92&quot; name=&quot;GRA92&quot;&gt;GRA92&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Robert Grady 1992. &lt;i&gt;Practical Software Metrics for Project Management and Process Improvement&lt;/i&gt;.
-                    Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot; height=&quot;28&quot;&gt;
-                    &lt;a id=&quot;HOL96&quot; name=&quot;HOL96&quot;&gt;HOL96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td width=&quot;88%&quot; colspan=&quot;2&quot; height=&quot;28&quot;&gt;
-                    Holtzblatt, K., and H. Beyer 1996. &quot;Contextual Design: Principles and Practice,&quot; &lt;i&gt;Field Methods for
-                    Software and Systems Design&lt;/i&gt;. D. Wixon and J. Ramey (Eds.), NY, NY: John Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;IE830&quot; name=&quot;IE830&quot;&gt;IE830&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    IEEE Std 830-1993. &lt;i&gt;Recommended Practice for Software Requirements Specifications.&lt;/i&gt; Software
-                    Engineering Standards Committee of the IEEE Computer Society: New York, NY, 1993.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ISO13407&quot; name=&quot;ISO13407&quot;&gt;ISO13407&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    ISO/TC159 1999. &lt;i&gt;Human-centred design processes for interactive systems.&lt;/i&gt; Report ISO 13407:1999,
-                    International Organization for Standardization, Geneva, Switzerland.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KOV99&quot; name=&quot;KOV99&quot;&gt;KOV99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Benjamin L. Kovitz 1999. &lt;i&gt;Practical Software Requirements-A Manual of Content &amp;amp; Style.&lt;/i&gt;
-                    Manning Publications.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;LEF99&quot; name=&quot;LEF99&quot;&gt;LEF99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Dean Leffingwell and Don Widrig 1999. &lt;i&gt;Effective Requirements Management.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot; height=&quot;21&quot;&gt;
-                    &lt;a id=&quot;MAY99&quot; name=&quot;MAY99&quot;&gt;MAY99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td width=&quot;88%&quot; colspan=&quot;2&quot; height=&quot;21&quot;&gt;
-                    Deborah J. Mayhew1999. &lt;i&gt;The Usability Engineering Lifecycle.&lt;/i&gt; Morgan Kaufmann Publishers.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;SCH98&quot; name=&quot;SCH98&quot;&gt;SCH98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Geri Schneider and Jason P. Winters 1998. &lt;i&gt;Applying Use Cases-A Practical Guide.&lt;/i&gt; Addison Wesley
-                    Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;SOM97&quot; name=&quot;SOM97&quot;&gt;SOM97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ian Sommerville and Pete Sawyer 1997. &lt;i&gt;Requirements Engineering-A Good Practice Guide.&lt;/i&gt; New York,
-                    NY: John Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;THA97&quot; name=&quot;THA97&quot;&gt;THA97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Richard H. Thayer and Merlin Dorfman 1997. &lt;i&gt;Software Requirements Engineering, 2nd Edition.&lt;/i&gt; IEEE
-                    Computer Society Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;WEI95&quot; name=&quot;WEI95&quot;&gt;WEI95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Gerald Weinberg, 1995. &quot;Just Say No! Improving the Requirements Process&quot;, &lt;i&gt;American Programmer&lt;/i&gt;,
-                    October 1995.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2 align=&quot;left&quot;&gt;
-    &lt;a id=&quot;Software Architecture references&quot; name=&quot;Software Architecture references&quot;&gt;Software Architecture&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot; valign=&quot;top&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BAS98&quot; name=&quot;BAS98&quot;&gt;BAS98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Len Bass, Paul Clements, and Rick Kazman 1998. &lt;i&gt;Software Architecture in Practice.&lt;/i&gt; Addison Wesley
-                    Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A handbook of software architecture, with numerous case studies.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOS00&quot; name=&quot;BOS00&quot;&gt;BOS00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Jan Bosch 2000. &lt;i&gt;Design and Use of Software Architecture.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BUS96&quot; name=&quot;BUS96&quot;&gt;BUS96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Frank Buschmann, Régine Meunier, Hans Rohnert, Peter Sommerlad, and Michael Stahl 1996.
-                    &lt;i&gt;Pattern-Oriented Software Architecture-A System of Patterns&lt;/i&gt;, New York, NY: John Wiley and Sons,
-                    Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Following the model of the &quot;gang of four&quot; book (Gamma, et al, see above) this book makes an inventory
-                    of a wide range of design patterns at the level of the architecture.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CKK02&quot; name=&quot;CKK02&quot;&gt;CKK02&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Paul Clements, Rick Kazman, and Mark Klein 2002. &lt;i&gt;Evaluating Software Architecture&lt;/i&gt;, Addison
-                    Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CLE02&quot; name=&quot;CLE02&quot;&gt;CLE02&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Paul Clements et al. 2002. &lt;i&gt;Documenting Software Architectures: Views and Beyond&lt;/i&gt;, Addison Wesley
-                    Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;CLN02&quot; name=&quot;CLN02&quot;&gt;CLN02&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Paul Clements and Linda Northrop 2002. &lt;i&gt;Software Product Lines: Practice and Patterns&lt;/i&gt;, Addison
-                    Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The preceding three books are from the Software Engineering Institute's architecture study group.
-                    &lt;i&gt;Evaluating Software Architecture&lt;/i&gt; provides useful input for architectural reviews. &lt;i&gt;Documenting
-                    Software Architectures: Views and Beyond&lt;/i&gt; fully embraces the concept of views and helps with
-                    developing a Software Architecture document.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DIK01&quot; name=&quot;DIK01&quot;&gt;DIK01&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    David M. Dikel, David Kane, and James R. Wilson 2001. &lt;i&gt;Software Architecture - Organizational
-                    Principles and Patterns&lt;/i&gt;, Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Describes the VRAPS model of architecting: Vision, Rhythm, Anticipation, Partnering, and
-                    Simplification. This is a good reference for the budding architect to put his or her role in context.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;FOW97a&quot; name=&quot;FOW97a&quot;&gt;FOW97a&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Martin Fowler 1997. &lt;i&gt;Analysis Patterns: Reusable Object Models.&lt;/i&gt; Addison Wesley Longman.&amp;nbsp;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GAM94&quot; name=&quot;GAM94&quot;&gt;GAM94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides 1994. &lt;i&gt;Design Patterns-Elements of
-                    Reusable Object-Oriented Software.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    One of the earlier works on patterns, this book deals with patterns &quot;in the small&quot;.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GAR93&quot; name=&quot;GAR93&quot;&gt;GAR93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    David Garlan and Mary Shaw. &lt;i&gt;An Introduction to Software Architecture.&amp;nbsp;&lt;/i&gt; SEI Technical Report
-                    CMU/SEI-94-TR-21.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;HOF99&quot; name=&quot;HOF99&quot;&gt;HOF99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Christine Hofmeister, Robert Nord, and Dilip Soni 1999. &lt;i&gt;Applied Software Architecture.&lt;/i&gt; Addison
-                    Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Proposes an alternate set of architectural views and describes the corresponding process. As the views
-                    are not too far from the RUP views, this book is an excellent complement to the guidance found in RUP.
-                    Contains several examples of architecture from the biomedical field.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;IEP1471&quot; name=&quot;IEP1471&quot;&gt;IEP1471&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;IEEE Recommended Practice for Architectural Description&lt;/i&gt;, IEEE Std P1471, 2000.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This standard recommends architectural description based on the concept of multiple views, of which the
-                    RUP 4+1 view is an example.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;JAC97&quot; name=&quot;JAC97&quot;&gt;JAC97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ivar Jacobson, Martin Griss and Patrik Jonsson, 1997. &lt;i&gt;Software Reuse-Architecture, Process and
-                    Organization for Business Success&lt;/i&gt;. Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A great companion book to the RUP, this book offers insights on the design of components and systems of
-                    interconnected system, and lays out a strategy for institutionalizing a practice of systematic reuse at
-                    the corporate level.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KRU95&quot; name=&quot;KRU95&quot;&gt;KRU95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Philippe Kruchten 1995, &quot;The 4+1 view model of architecture,&quot; &lt;i&gt;IEEE Software.&lt;/i&gt; 12(6), November
-                    1995.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The origin of the 4+1 views used for architectural description in the RUP.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;LMFS96&quot; name=&quot;LMFS96&quot;&gt;LMFS96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Lockheed Martin Federal STARS (Software Technology for Adaptable, Reliable Systems) Program. Domain
-                    Engineering Guidebook.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This Guidebook provides a high-level description of the Domain Engineering&amp;nbsp; process in the context
-                    of a real organization-the U.S. Air Force's Space and Warning Systems Center.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;PW92&quot; name=&quot;PW92&quot;&gt;PW92&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Dewayne E. Perry and Alexander L. Wolf. &lt;i&gt;Foundations for the Study of Software Architecture.&lt;/i&gt; ACM
-                    SIGSOFT Software Engineering Notes, 17(4):40-52, October 1992.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;REC97&quot; name=&quot;REC97&quot;&gt;REC97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Eberhardt Rechtin and Mark Maier 1997. &lt;i&gt;The Art of System Architecting.&lt;/i&gt; Boca Ration, FL: CRC
-                    Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Although not specifically directed to software engineers, these two books are extremely valuable for
-                    software architects: in particular, they introduce an invaluable set of heuristics and many examples of
-                    architecture.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;REC91&quot; name=&quot;REC91&quot;&gt;REC91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Eberhardt Rechtin 1991. &lt;i&gt;Systems Architecting: creating and building complex systems&lt;/i&gt;. Englewood
-                    Cliffs NJ: Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ROY91&quot; name=&quot;ROY91&quot;&gt;ROY91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Walker E. Royce and Winston Royce, &quot;Software Architecture: Integrating Process and Technology,&quot;
-                    &lt;i&gt;Quest,&lt;/i&gt; 14 (1), 1991, Redondo Beach, CA: TRW, pp.2-15.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;SHA96&quot; name=&quot;SHA96&quot;&gt;SHA96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Mary Shaw and David Garlan 1996. &lt;i&gt;Software Architecture-Perspectives on an Emerging Discipline.&lt;/i&gt;
-                    Upper Saddle River, NJ: Prentice-Hall.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A good introduction to the concepts and problems of software architecture.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;WIT94&quot; name=&quot;WIT94&quot;&gt;WIT94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Bernard I. Witt, F. Terry Baker, and Everett W. Merritt 1994. &lt;i&gt;Software Architecture and
-                    Design-Principles, Models, and Methods.&lt;/i&gt; New York, NY: Van Nostrand Reinhold.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    One of the first comprehensive book written on software architecture.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2&gt;
-    &lt;a id=&quot;Software Development Process references&quot; name=&quot;Software Development Process references&quot;&gt;Software Development
-    Process&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;AMB99&quot; name=&quot;AMB99&quot;&gt;AMB99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Scott W. Ambler 1999. &lt;i&gt;More Process Patterns: Delivering Large-Scale Systems Using Object
-                    Technology&lt;/i&gt;. New York, NY: SIGS Books/Cambridge University Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The companion to [AMB98].
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;AMB98&quot; name=&quot;AMB98&quot;&gt;AMB98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Scott W. Ambler 1998. &lt;i&gt;Process Patterns: Building Large-Scale Systems Using Object Technology&lt;/i&gt;.
-                    New York, NY: SIGS Books/Cambridge University Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A good resource on process tailoring and applying object-oriented techniques to software engineering
-                    projects.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOE96&quot; name=&quot;BOE96&quot;&gt;BOE96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Barry W. Boehm 1996, &quot;Anchoring the Software Process,&quot; &lt;i&gt;IEEE Software,&lt;/i&gt; July 1996, pp.73-82.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This article defines the four phases and the corresponding milestones.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BOE88&quot; name=&quot;BOE88&quot;&gt;BOE88&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Barry W. Boehm 1988, &quot;A Spiral Model of Software Development and Enhancement,&quot; &lt;i&gt;Computer,&lt;/i&gt; May
-                    1988, IEEE, pp.61-72.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This seminal article defines the principles and motivations of iterative development.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;COC01&quot; name=&quot;COC01&quot;&gt;COC01&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Alistair Cockburn 2001. &lt;i&gt;Agile Software Development&lt;/i&gt; Addison-Wesley Publishing Co.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Peers into the team dynamics, the cultures, the communications aspects of software development.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;DOD94&quot; name=&quot;DOD94&quot;&gt;DOD94&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    &lt;i&gt;Software Development and Documentation,&lt;/i&gt; MIL-STD-498, U.S. Department of Defense, December 1994.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;FER01&quot; name=&quot;FER01&quot;&gt;FER01&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Xavier Ferre et al. 2001, &quot;Usability Basics for Software Developers,&quot; &lt;i&gt;IEEE Software,&lt;/i&gt; January
-                    2001, pp. 22-29.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;HIG00&quot; name=&quot;HIG00&quot;&gt;HIG00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    James A. Highsmith 2000. &lt;i&gt;Adaptive Software Development: A Collaborative Approach to Managing Complex
-                    Systems&lt;/i&gt;. Dorset House.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This book is a great companion book to the RUP-a fantastic and convincing plea for iterative
-                    development. Very practical advice for the project manager.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;HUM89&quot; name=&quot;HUM89&quot;&gt;HUM89&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Watts S. Humphrey 1989. &lt;i&gt;Managing the Software Process&lt;/i&gt;. Reading, MA: Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A classic book on software process and the capability maturity model developed at the Software
-                    Engineering Institute.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ISO95&quot; name=&quot;ISO95&quot;&gt;ISO95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    ISO/IEC 12207 &lt;i&gt;Information Technology-Software Life-cycle Processes.&lt;/i&gt; ISO, Geneva, 1995, 57p.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ISO91&quot; name=&quot;ISO91&quot;&gt;ISO91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    ISO 9000-3 &lt;i&gt;Guidelines for the Application of ISO 9001 to the Development, Supply, and Maintenance of
-                    Software.&lt;/i&gt; ISO, Geneva 1991.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Two key standards for software process definition and assessment.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;JAC98&quot; name=&quot;JAC98&quot;&gt;JAC98&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ivar Jacobson, Grady Booch, and James Rumbaugh 1998. &lt;i&gt;The Unified Software Development Process.&lt;/i&gt;
-                    Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This recent textbook is a more thorough description of the Unified Process and is a useful companion to
-                    the RUP. Also provides examples of UML modeling.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;JAC97&quot; name=&quot;JAC97&quot;&gt;JAC97&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ivar Jacobson, Martin Griss, and Patrik Jonsson 1997. &lt;i&gt;Software Reuse-Architecture, Process and
-                    Organization for Business Success.&lt;/i&gt; Addison Wesley Longman.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This textbook on software reuse is great complement to the RUP. It features also some great chapters on
-                    architecture.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;JEF01&quot; name=&quot;JEF01&quot;&gt;JEF01&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Ron Jeffries, Ann Anderson, and Chet Hendrickson 2001. &lt;i&gt;Extreme Programming Installed.&lt;/i&gt;
-                    Addison-Wesley.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This book describes practical Extreme Programming techniques.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KRU96&quot; name=&quot;KRU96&quot;&gt;KRU96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Philippe Kruchten 1996. &quot;A Rational Development Process&quot;&lt;i&gt;,&lt;/i&gt; &lt;i&gt;CrossTalk&lt;/i&gt;, 9 (7), July 1996,
-                    p.11-16.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Developed with Walker Royce, Sue Mickel, and a score of Rational consultants, this article describes
-                    the iterative lifecycle of the Rational Process.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KRU91&quot; name=&quot;KRU91&quot;&gt;KRU91&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Philippe Kruchten 1991. &quot;Un processus de dévelopment de logiciel itératif et centré sur
-                    l´architecture&quot;, &lt;i&gt;Proceedings of the 4th International Conference on Software Engineering, December
-                    1991&lt;/i&gt;, Toulouse, France, EC2.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The Rational iterative process in French.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KRU00&quot; name=&quot;KRU00&quot;&gt;KRU00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Philippe Kruchten 2000. &lt;i&gt;The Rational Unified Process, An Introduction, Second Edition.&lt;/i&gt; Addison
-                    Wesley Longman.&amp;nbsp;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Indespensible as an introductory text, this &quot;mile wide, inch deep&quot; overview quickly introduces you to
-                    the concepts, structure, content, and motivation of the RUP.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KRO03&quot; name=&quot;KRO03&quot;&gt;KRO03&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Per Kroll and Philippe Kruchten 2003. &lt;i&gt;The Rational Unified Process Made Easy, A Practitioners Guide
-                    to the RUP.&lt;/i&gt; Addison Wesley Longman.&amp;nbsp;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A practical guide to adopting the spirit, principles and practices of the RUP. An invaluable resource
-                    in helping you decide how to apply the RUP in your organization or project.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MCF96&quot; name=&quot;MCF96&quot;&gt;MCF96&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Robert McFeeley 1996. &lt;i&gt;IDEAL: A User's Guide for Software Process Improvement.&lt;/i&gt; Software
-                    Engineering Institute, Pittsburgh, PA, CMU/SEI-96-HB-001.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Describes a software process improvement program model called IDEAL, a generic description of a
-                    sequence of recommended steps for initiating and managing a process implementation project.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;PAR86&quot; name=&quot;PAR86&quot;&gt;PAR86&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    David L. Parnas and Paul C. Clements, &quot;A Rational Design Process: How and Why to Fake It&quot;, &lt;i&gt;IEEE
-                    Trans. Software Eng.,&lt;/i&gt; Feb. 1986, pp.251-257.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;PAU93&quot; name=&quot;PAU93&quot;&gt;PAU93&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Mark Paulk, et al. 1993. &lt;i&gt;Capability Maturity Model for Software, Version 1.1.&lt;/i&gt; Software
-                    Engineering Institute, Pittsburgh, PA SEI-93-TR-024.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    The original reference for the capability maturity model.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ROY90&quot; name=&quot;ROY90&quot;&gt;ROY90&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Walker E. Royce, &quot;TRW's Ada Process Model for Incremental Development of Large Software Systems&quot;,
-                    &lt;i&gt;Proceedings ICSE 12, March 26-30, 1990,&lt;/i&gt; Nice, France, IEEE, pp.2-11.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;ROY70&quot; name=&quot;ROY70&quot;&gt;ROY70&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Winston W. Royce, &quot;Managing the Development of Large Software Systems: Concepts and Techniques&quot;,
-                    &lt;i&gt;Proceedings, WESCON&lt;/i&gt;, August 1970.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h2 align=&quot;left&quot;&gt;
-    &lt;a id=&quot;Testing and Quality references&quot; name=&quot;Testing and Quality references&quot;&gt;Testing and Quality&lt;/a&gt;
-&lt;/h2&gt;
-&lt;div align=&quot;center&quot;&gt;
-    &lt;table width=&quot;100%&quot; summary=&quot;layout table&quot; border=&quot;0&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BAC01a&quot; name=&quot;BAC01a&quot;&gt;BAC01a&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    James Bach 2001. &lt;i&gt;What Is Exploratory Testing? (And How It Differs from Scripted Testing).&lt;/i&gt;
-                    Software Testing and Quality Engineering Magazine, Jan 29, 2001.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This article is available online at &lt;a
-                    href=&quot;http://www.stickyminds.com/sitewide.asp?sid=582697&amp;amp;sqry=%2AJ%28MIXED%29%2AR%28createdate%29%2AK%28simplesite%29%2AF%28what+is+exploratory+testing%29%2A&amp;amp;sidx=0&amp;amp;sopp=10&amp;amp;ObjectId=2255&amp;amp;Function=DETAILBROWSE&amp;amp;ObjectType=COL&quot;
-                     target=&quot;_blank&quot;&gt;http://www.stickyminds.com&lt;/a&gt;.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BAS87&quot; name=&quot;BAS87&quot;&gt;BAS87&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    BAS87 Victor R. Basili and H. Dieter Rombach 1987. &lt;i&gt;Tailoring the Software Process to Project Goals
-                    and Environments.&lt;/i&gt; Proceedings of the 9th International Conference on Software Engineering Software,
-                    IEEE Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BEI95&quot; name=&quot;BEI95&quot;&gt;BEI95&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Boris Beizer 1995. &lt;i&gt;Black Box Testing.&lt;/i&gt; New York, NY: John Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Various strategies to develop test cases for the functional testing of software. Dr. Beizer's writing
-                    style and wit make this book easy and fun to read, with excellent, understandable examples.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;BLA99&quot; name=&quot;BLA99&quot;&gt;BLA99&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Rex Black 1999. &lt;i&gt;Managing the Testing Process.&lt;/i&gt; Microsoft Press.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This book is a good source of information about managing system testing teams.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;GLA81&quot; name=&quot;GLA81&quot;&gt;GLA81&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Robert L. Glass 1981. &lt;i&gt;Persistent Software Errors.&lt;/i&gt; IEEE Transactions on Software Engineering,
-                    March 1981.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;IE829&quot; name=&quot;IE829&quot;&gt;IE829&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    IEEE 829-1983 &lt;i&gt;Standard for Software Test Documentation.&lt;/i&gt; Software Engineering Standards Committee
-                    of the IEEE Computer Society, New York.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KAN01&quot; name=&quot;KAN01&quot;&gt;&lt;/a&gt;KAN01
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Cem Kaner, James Bach, and Bret Pettichord 2001. &lt;i&gt;Lessons Learned in Software Testing.&lt;/i&gt; John Wiley
-                    &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    A wealth of tips and tricks that help to address a wide variety of issues faced in the testing of
-                    computer software. Broad coverage of management, psychological as well as the technical aspects of
-                    software testing. Valuable guidance for the novice and the expert alike.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;KAN99&quot; name=&quot;KAN99&quot;&gt;&lt;/a&gt;KAN99
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Cem Kaner, Jack Falk, and Hung Quoc Nguyen 1999. &lt;i&gt;Testing Computer Software, 2nd Edition.&lt;/i&gt; John
-                    Wiley &amp;amp; Sons, Inc.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    Billed as &quot;The best-selling software testing book of all time&quot;, this book offers a broad coverage of
-                    various aspects of software testing.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MAR00&quot; name=&quot;MAR00&quot;&gt;MAR00&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Brian Marick 2000. &lt;i&gt;Faults of Omission.&lt;/i&gt; Software Testing and Quality Engineering Magazine,
-                    March-April 2000.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This article is available online at: &lt;a href=&quot;http://www.testing.com/writings/omissions.pdf&quot;
-                    target=&quot;_blank&quot;&gt;http://www.testing.com/writings/omissions.pdf&lt;/a&gt;.&lt;br /&gt;
-                     (&lt;a href=&quot;http://www.adobe.com/products/acrobat/alternate.html&quot; target=&quot;_blank&quot;&gt;Get Adobe Reader&lt;/a&gt;)
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;MYE79&quot; name=&quot;MYE79&quot;&gt;MYE79&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Glenford J. Myers 1979. &lt;i&gt;The Art of Software Testing&lt;/i&gt;, John Wiley &amp;amp; Sons, Inc., New York.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                    This is one of the classic works of software testing literature. Even today this timelesss text offers
-                    useful, practical, and relevent guidance.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                    &lt;a id=&quot;OST84&quot; name=&quot;OST84&quot;&gt;OST84&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td colspan=&quot;2&quot;&gt;
-                    Thomas J. Ostrand and Elaine J. Weyuker 1984. &lt;i&gt;Collecting and Categorizing Software Error Data in an
-                    Industrial Environment.&lt;/i&gt; Journal of Systems and Software, Vol. 4, 1984.
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td valign=&quot;top&quot; width=&quot;12%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;10%&quot;&gt;
-                &lt;/td&gt;
-                &lt;td style=&quot;PADDING-BOTTOM: 10px&quot; width=&quot;78%&quot;&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/customcategories/resources/circleOfLife.jpg b/XP/xp/customcategories/resources/circleOfLife.jpg
deleted file mode 100644
index 3772826..0000000
--- a/XP/xp/customcategories/resources/circleOfLife.jpg
+++ /dev/null
Binary files differ
diff --git a/XP/xp/customcategories/resources/extreme_programming,5.2637267673584526E-306.html b/XP/xp/customcategories/resources/extreme_programming,5.2637267673584526E-306.html
deleted file mode 100644
index 3eb88af..0000000
--- a/XP/xp/customcategories/resources/extreme_programming,5.2637267673584526E-306.html
+++ /dev/null
@@ -1,273 +0,0 @@
-<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Concept: Extreme Programming</title>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
-<meta name="element_type" content="concept">
-<meta content="description" name="filetype">
-<meta name="role" content="">
-<link type="text/css" href="./../../../css/default.css" rel="StyleSheet">
-<script src="./../../../scripts/contentpage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
-					backPath = './../../../';
-				</script>
-</head>
-<body onload="createSectionLinks('div', 'sectionHeading', './../../../images/');">
-<table width="100%" cellspacing="0" cellpadding="0" border="0">
-<tr>
-<td valign="top"><a name="Top"></a>
-<table cellpadding="0" cellspacing="0" border="0">
-<tr>
-<td class="pageTitle">Concept: Extreme Programming</td>
-</tr>
-</table>
-<table cellspacing="0" cellpadding="0" border="0" width="100%">
-<tr>
-<td class="pageTitleSeparator"><img height="1" alt="" src="./../../../images/shim.gif"></td>
-</tr>
-</table>
-<div class="overview">
-<table cellpadding="0" cellspacing="0" border="0" width="97%">
-<tr>
-<td>
-<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
-<tr>
-<td valign="top"></td>
-</tr>
-</table>
-</td>
-</tr>
-</table>
-</div>
-<div class="sectionHeading">Main Description</div>
-<div class="sectionContent">
-<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
-<tr valign="top">
-<td class="sectionTableCell"><a id="XE_xp__conceptual_process_roadmap" name="XE_xp__conceptual_process_roadmap"></a><a id="XE_roadmap__for_xp_practices" name="XE_roadmap__for_xp_practices"></a> 
-<h3>
-    Topics
-</h3>
-<div align="left">
-    <table width="70%" border="1">
-        <tbody valign="top">
-            <tr>
-                <td width="315" height="178">
-                    <ul>
-                        <li>
-                            <a href="#Introduction">Introduction</a>
-                        </li>
-                        <li style="LIST-STYLE-TYPE: none">
-                            <ul>
-                                <li>
-                                    <a href="#About">About XP</a>
-                                </li>
-                            </ul>
-                        </li>
-                    </ul>
-                    <p>
-                        <br />
-                        <br />
-                    </p>
-                    <ul>
-                        <li>
-                            <a href="#Characteristics">Characteristics of an XP Project</a>
-                        </li>
-                        <li>
-                            <a href="#GettingStarted">How to Get Started</a>
-                        </li>
-                        <li>
-                            <a href="#Phases">Phases and Iterations</a>
-                        </li>
-                    </ul>
-                </td>
-                <td width="315" height="178">
-                    <b>Additional Guidance:</b> 
-                    <ul>
-                        <li>
-                            Guidelines 
-                            <ul>
-                                <li>
-                                    <a class="elementLink" href="./../../../xp/guidances/guidelines/refactoring,8.137126904637637E-306.html" guid="8.137126904637637E-306">Refactoring</a>
-                                </li>
-                                <li>
-                                    <a class="elementLinkWithUserText" href="./../../../xp/guidances/guidelines/test_driven_development_tdd,3.9254165491375454E-306.html" guid="3.9254165491375454E-306">Test First Development</a>
-                                </li>
-                                <li>
-                                    <a class="elementLinkWithUserText" href="./../../../xp/guidances/guidelines/pair_programming,3.85153041801319E-307.html" guid="3.85153041801319E-307">Pair Programming</a>
-                                </li>
-                                <li>
-                                    <a class="elementLinkWithUserText" href="./../../../xp/guidances/guidelines/planning_game,6.7335956461328426E-307.html" guid="6.7335956461328426E-307">Planning Game</a>
-                                </li>
-                                <li style="LIST-STYLE-TYPE: none">
-                                    <br />
-                                    <br />
-                                </li>
-                            </ul>
-                        </li>
-                        <li>
-                            <a class="elementLinkWithUserText" href="./../../../xp/guidances/supportingmaterials/bup_xp_plug-in_resource_center,2.315717433735515E-305.html" guid="2.315717433735515E-305">Additional XP Resources</a>
-                        </li>
-                    </ul>
-                    <b>Additional Concepts:</b> 
-                    <ul>
-                        <li>
-                            <a class="elementLink" href="./../../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html" guid="1.041091673844025E-305">Agile Software Development</a>
-                        </li>
-                    </ul>
-                </td>
-            </tr>
-        </tbody>
-    </table>
-</div>
-<br />
-<br />
-<h1>
-    <a id="Introduction" name="Introduction">Introduction</a>
-</h1>
-<p>
-    This roadmap provides information for getting started and applying the practices of eXtreme Programming (XP) to a
-    software development project. The roadmap can be used as a guide to the content delivered in the BUP XP Plug-In.
-</p>
-<h3>
-    <a id="About" name="About">About XP</a>&nbsp;
-</h3>
-<p>
-    Extreme Programming is an instance of an <a class="elementLink" href="./../../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html" guid="1.041091673844025E-305">Agile Software Development</a> method. XP is a method that is optimized for small to
-    medium-sized project teams that fit a certain profile. It promotes rapid feedback and response to continual change. It
-    is based upon the four <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/xp_values,1.076140803519123E-306.html" guid="1.076140803519123E-306">values</a> of simplicity, communication, feedback, and courage and is consistent with the
-    values of agile software development.
-</p>
-<br />
-<p>
-    Extreme Programming is an instance of an agile method for developing software. It is based upon the core principle of
-    agility and consists of twelve practices that, when applied to an appropriate software development project, can produce
-    high-quality software. If you are unfamiliar with the concepts surrounding XP, you should start by reading <a class="elementLink" href="./../../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html" guid="1.041091673844025E-305">Agile Software Development</a>.
-</p>
-<h3>
-    <a id="Characteristics" name="Characteristics">Characteristics of an XP Project</a>
-</h3>
-<p>
-    Extreme Programming or XP is a development process that can be used by small to medium-sized teams to develop high
-    quality software within a predictable schedule and budget and with a minimum of overhead. Since XP relies heavily on
-    direct and frequent communication between the team members, the team should be co-located. An ideal project for using
-    XP would be one that has most of the following characteristics:
-</p>
-<ul>
-    <li>
-        A small to medium-sized team (fewer than 20 people on the complete team)
-    </li>
-    <li>
-        Co-located, preferably in a single area with a large common space
-    </li>
-    <li>
-        A committed, full-time, on-site customer or customer representative
-    </li>
-    <li style="LIST-STYLE-TYPE: none">
-        <br />
-    </li>
-</ul>
-<h3>
-    <a id="Phases" name="Phases">Phases and Iterations</a>
-</h3>
-<p>
-    An XP project is one that is based on rapid feedback through short iterations and frequent releases. BUP and XP share a
-    fundamental belief that iterative development is the best way to deliver valuable software to your customers. The
-    concept of phases, as usually described in a BUP configuration, is somewhat different. Decisions described in the BUP
-    phases that define milestones occur, but they are not called specifically as defining phases. For a discussion of how
-    the phases are related to an XP project, see the discussion of <a class="elementLinkWithUserText" href="./../../../xp/deliveryprocesses/bup_phases_and_xp,{63BD15C5-40EF-469A-A22A-3291734B60F4}.html" guid="{63BD15C5-40EF-469A-A22A-3291734B60F4}">Phases</a>.
-</p>
-<h3>
-    <a id="GettingStarted" name="GettingStarted">How to Get Started</a>
-</h3>
-<p>
-    This section provides a recommended way to approach XP for your project. You don't have to follow the steps as
-    specified, but if you have little experience with XP, we recommend following them as closely as possible the first
-    time.
-</p>
-<table cellspacing="2" cellpadding="1" width="91%" border="1">
-    <tbody>
-        <tr>
-            <th width="10%">
-                Step
-            </th>
-            <th align="left" width="47%">
-                Do this ...
-            </th>
-            <th align="left" width="43%">
-                in order to...
-            </th>
-        </tr>
-        <tr>
-            <td align="middle" width="10%">
-                1
-            </td>
-            <td width="47%">
-                Familiarize yourself with the&nbsp;<a class="elementLink" href="./../../../xp/guidances/concepts/motivation,1.6390805262958034E-306.html" guid="1.6390805262958034E-306">motivation</a> for using XP, the <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/what_is_xp,9.251272550276345E-306.html" guid="9.251272550276345E-306">short description</a> of XP, and the <a class="elementLink" href="./../../../xp/guidances/concepts/xp_practices,2.2937799026801584E-305.html" guid="2.2937799026801584E-305">XP Practices</a> 
-            </td>
-            <td width="43%">
-                understand the fundamental principles of XP and how the practices support each other.
-            </td>
-        </tr>
-        <tr>
-            <td align="middle" width="10%">
-                2
-            </td>
-            <td width="47%">
-                Read the key concepts of <a class="elementLink" href="./../../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html" guid="1.041091673844025E-305">Agile Software Development</a> 
-            </td>
-            <td width="43%">
-                understand the collaborative and social aspects of XP.
-            </td>
-        </tr>
-        <tr>
-            <td align="middle" width="10%">
-                3
-            </td>
-            <td width="47%">
-                Determine if XP is appropriate for your project by reviewing <a href="#Characteristics">The Characteristics
-                of an XP Project</a> 
-            </td>
-            <td width="43%">
-                decide if XP may be appropriate for your project.
-            </td>
-        </tr>
-        <tr>
-            <td align="middle" width="10%">
-                4
-            </td>
-            <td width="47%">
-                Read about the <a class="elementLinkWithUserText" href="./../../../xp/guidances/guidelines/xp_environment,3.754748120034442E-307.html" guid="3.754748120034442E-307">XP Environment</a>.
-            </td>
-            <td width="43%">
-                prepare the physical and tool environment for your team.
-            </td>
-        </tr>
-        <tr>
-            <td align="middle" width="10%">
-                5
-            </td>
-            <td width="47%">
-                Read the <a class="elementLink" href="./../../../xp/guidances/supportingmaterials/getting_started_with_xp,1.2284921351651456E-304.html" guid="1.2284921351651456E-304">Getting Started with XP</a> guidelines.
-            </td>
-            <td width="43%">
-                get suggestions on how to start an XP project.
-            </td>
-        </tr>
-    </tbody>
-</table>
-<br />
-<br />
-<br />
-<br /></td>
-</tr>
-</table>
-</div>
-<table cellpadding="0" cellspacing="0" border="0" class="copyright">
-<tr>
-<td class="copyright"></td>
-</tr>
-</table>
-</td>
-</tr>
-</table>
-</body>
-</html>
diff --git a/XP/xp/customcategories/resources/xp_getting_started_guidelines.htm b/XP/xp/customcategories/resources/xp_getting_started_guidelines.htm
deleted file mode 100644
index 983817c..0000000
--- a/XP/xp/customcategories/resources/xp_getting_started_guidelines.htm
+++ /dev/null
@@ -1,79 +0,0 @@
-<!-- RPW META DATA START --
-<rpw name="MetaData" meta_value="anonymous" meta_name="element_type"></rpw>
-<rpw name="MetaData" meta_value="guideline" meta_name="filetype"></rpw>
--- RPW META DATA END -->
-
-<html>
-
-<head>
-<link rel="stylesheet" href="../../../rop.css" type="text/css">
-<title>Guidelines:&nbsp;<rpw name="InsertPresentationName"></rpw></title>
-<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
-</head>
-
-
-<body>
-
-<rpw name="Warning"><b>!RPW INCLUDE! DO NOT MOVE/MODIFY !RPW INCLUDE!</b><br></rpw>
-<rpw name="Include">rpw/startBorder.rpw</rpw>
-<rpw name="Warning"><br><b>!RPW INCLUDE! DO NOT MOVE/MODIFY !RPW INCLUDE!</b></rpw>
-
-
-<h1 class="banner"><a name="Top"></a>Guidelines:&nbsp;<rpw name="PresentationName">Adopting 
-  XP Practices</rpw> <a name="XE_xp__adopting_practices"></a><a name="XE_adopting_practices__in_xp"></a></h1>
-<p>XP is a set of synergistic practices. Because the practices depend upon each 
-  other, people often wonder where they should start. In general, we recommend 
-  that you stop and consciously decide to adopt as many of the XP practices as 
-  possible.</p>
-<p>However, if that induces too much stress, consider adopting the practices in 
-  this order.</p>
-<p><b><a href="../../../components/pc_xp_essentials/pc_xp_integration/co_continuous_integration.htm">Establish 
-  a solid build process</a></b>. If you are not able to reliably build the software 
-  you are working on, you can&8217;t really go further. Once you have a reliable 
-  build process, make sure that you run whatever <a href="../../../components/pc_xp_essentials/pc_xp_testing/co_customer_tests.htm">tests</a> 
-  you have prior to each checking.</p>
-<p><b><a href="../../../components/pc_xp_essentials/pc_xp_programming/co_pair_program.htm">Pair 
-  programming</a></b> is often a significantly different way of working for most 
-  developers. It takes a little bit of time to get used to it, but as a team does, 
-  they recognize that they are a much more powerful team because everyone&#8217;s 
-  knowledge of the system grows rapidly. In addition, quality goes up because 
-  there are two sets of eyes on all work as it is being done. When you adopt pair 
-  programming, ideally you should have an <a href="../../../components/pc_xp_essentials/pc_xp_management/xp_open_workspace_guidelines.htm">open 
-  workspace</a>.</p>
-<p>As your team gets started with pair programming, you should adopt the <b><a href="../../../components/pc_xp_essentials/co_planning_game.htm">Planning 
-  Game</a></b>. The Planning Game will help you identify good goals for your next 
-  release, iteration, and day of work. At the end of your first iteration, you 
-  will have a velocity that you can use to get a sense of how long it takes you 
-  do do your work. As you do your planning, talk to your customer about producing 
-  acceptance tests and being available to the team.</p>
-<p>As you work together on your first iteration, try doing <a href="../../../components/pc_xp_essentials/co_test_driven_development.htm"><b>test-driven 
-  development</b></a>. It will feel strange at first. If it doesn&#8217;t, you 
-  are probably doing it wrong. Over time, it will feel like a more natural way 
-  to develop software. Recognize that, at first, your velocity will be rather 
-  low. This is a side effect of the learning process. Over the next few iterations 
-  your speed will increase.</p>
-<p>As you move forward, learn how to <a href="../../../components/pc_xp_essentials/pc_xp_programming/co_refactoring.htm"><b>refactor</b></a> 
-  and start to practice <a href="../../../components/pc_xp_essentials/co_collective_code_ownership.htm"><b>collective 
-  code ownership</b></a>. Often collective code ownership is a little scary at 
-  first, but as you pair, you will notice that everyone is learning what it takes 
-  to work with the system. When people volunteer for tasks, they either volunteer 
-  only for what they know how to do or for things that they can get help on from 
-  a partner.</p>
-<p>Once you have a few iterations under your belt, you will be able to understand 
-  how the process works and how the different practices interact and support each 
-  other. Finally, listen to the feedback coming from your team. That feedback 
-  is critical and can be used to improve and adapt the process to your team&#8217;s 
-  particular needs and problems.</p>
-
-
-<p><br/><br/></p>
-
-<rpw name="Warning"><b>!RPW INCLUDE! DO NOT MOVE/MODIFY !RPW INCLUDE!</b><br></rpw>
-<rpw name="Include">rpw/endBorderOmRat.rpw</rpw>
-<rpw name="Include">rpw/endBorder.rpw</rpw>
-<rpw name="Warning"><br><b>!RPW INCLUDE! DO NOT MOVE/MODIFY !RPW INCLUDE!</b></rpw>
-
-</body>
-
-</html>
-
diff --git a/XP/xp/customcategories/resources/xp_practices,2.2937799026801584E-305.html b/XP/xp/customcategories/resources/xp_practices,2.2937799026801584E-305.html
deleted file mode 100644
index f77493f..0000000
--- a/XP/xp/customcategories/resources/xp_practices,2.2937799026801584E-305.html
+++ /dev/null
@@ -1,115 +0,0 @@
-<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<head>
-<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>Concept: XP Practices</title>
-<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
-<meta name="element_type" content="concept">
-<meta content="description" name="filetype">
-<meta name="role" content="">
-<link type="text/css" href="./../../../css/default.css" rel="StyleSheet">
-<script src="./../../../scripts/contentpage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
-					backPath = './../../../';
-				</script>
-</head>
-<body onload="createSectionLinks('div', 'sectionHeading', './../../../images/');">
-<table width="100%" cellspacing="0" cellpadding="0" border="0">
-<tr>
-<td valign="top"><a name="Top"></a>
-<table cellpadding="0" cellspacing="0" border="0">
-<tr>
-<td class="pageTitle">Concept: XP Practices</td>
-</tr>
-</table>
-<table cellspacing="0" cellpadding="0" border="0" width="100%">
-<tr>
-<td class="pageTitleSeparator"><img height="1" alt="" src="./../../../images/shim.gif"></td>
-</tr>
-</table>
-<div class="overview">
-<table cellpadding="0" cellspacing="0" border="0" width="97%">
-<tr>
-<td>
-<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
-<tr>
-<td valign="top"></td>
-</tr>
-</table>
-</td>
-</tr>
-</table>
-</div>
-<div class="sectionHeading">Main Description</div>
-<div class="sectionContent">
-<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
-<tr valign="top">
-<td class="sectionTableCell"><a id="XE_xp__practices_of" name="XE_xp__practices_of"></a><a id="XE_practices_in__xp" name="XE_practices_in__xp"></a> 
-<p>
-    XP is a collection of guiding values and best practices. Most of these practices have been used in the industry in some
-    shape or form for a number of years. XP has simply identified them and tried to push the envelope of these practices in
-    order to get the most benefit from them. Taken individually, these practices are all fairly simple. But it is the sum
-    of all of them that provides the most benefit as they reinforce each other to address the most difficult problems teams
-    encounter when developing software.
-</p>
-<br />
-<br />
-<p>
-    <img height="540" alt="" src="./../../../xp/resources/circleOfLife.jpg" width="720" usemap="#xp_practices_image_map"     border="0" /> <map id="xp_practices_image_map" name="xp_practices_image_map">
-        <area shape="RECT" coords="298,19,390,88"         href="./../../../xp/guidances/concepts/whole_team,7.89591827591278E-306.html" />
-        <area shape="RECT" coords="176,135,282,200"         href="./../../../xp/guidances/concepts/collective_ownership,9.300699588493279E-306.html" />
-        <area shape="RECT" coords="297,168,434,231"         href="./../../../xp/guidances/concepts/test_driven_development,1.620567348185129E-306.html" />
-        <area shape="RECT" coords="447,135,547,198"         href="./../../../xp/guidances/concepts/coding_standard,8.8116853923311E-307.html" />
-        <area shape="RECT" coords="15,236,122,305"         href="./../../../xp/guidances/concepts/customer_tests,2.297945473205673E-305.html" />
-        <area shape="RECT" coords="218,238,362,307"         href="./../../../xp/guidances/concepts/pair_programming,3.876855509996079E-307.html" />
-        <area shape="RECT" coords="392,241,512,305"         href="./../../../xp/guidances/concepts/refactoring_xp_programming,1.4410217108363206E-306.html" />
-        <area shape="RECT" coords="614,236,714,302"         href="./../../../xp/guidances/concepts/planning_game,2.7371805612676613E-305.html" />
-        <area shape="RECT" coords="143,325,270,393"         href="./../../../xp/guidances/concepts/continuous_integration,3.193414568279561E-305.html" />
-        <area shape="RECT" coords="310,321,412,379"         href="./../../../xp/guidances/concepts/simple_design,1.6109092258980447E-306.html" />
-        <area shape="RECT" coords="468,323,597,393"         href="./../../../xp/guidances/concepts/xp_sustainable_pace,3.133529870649493E-306.html" />
-        <area shape="RECT" coords="307,386,413,436"         href="./../../../xp/guidances/concepts/metaphor_system_of_names,4.884861766532753E-306.html" />
-        <area shape="RECT" coords="312,475,419,539"         href="./../../../xp/guidances/concepts/small_releases,5.762953011420275E-306.html" />
-        <area shape="RECT" target="_blank" coords="561,494,708,538" href="http://www.xprogramming.com" />
-    </map>
-</p>
-<p>
-    This diagram arranges the core practices of Extreme Programming in a way that makes them easy to remember and that
-    exemplifies the steering and control cycles of the process.
-</p>
-<p>
-    The outer red circle is called the "Circle of Life". It's what keeps an XP project going, producing tested working
-    software. The <a class="elementLink" href="./../../../xp/guidances/concepts/whole_team,7.89591827591278E-306.html" guid="7.89591827591278E-306">Whole Team</a>, customer members and development members, work together--preferably
-    physically together--to build the project. Using the <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/planning_game,2.7371805612676613E-305.html" guid="2.7371805612676613E-305">Planning Game</a> elements of Release Planning and Iteration Planning, they plan a
-    series of <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/small_releases,5.762953011420275E-306.html" guid="5.762953011420275E-306">Small
-    Releases</a> of software that demonstrably pass all the <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/customer_tests,2.297945473205673E-305.html" guid="2.297945473205673E-305">Customer Tests</a>.
-</p>
-<p>
-    The innermost blue circle describes the day to day, moment to moment, work of the XP developers. Each feature is
-    addressed with <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/simple_design,1.6109092258980447E-306.html" guid="1.6109092258980447E-306">Simple Design</a>, ensuring that the design of the system is just right for the features
-    supported. The programmers work in <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/pair_programming,3.876855509996079E-307.html" guid="3.876855509996079E-307">pairs</a> for all production code development, providing continuous code review and
-    valuable, team-wide understanding of the system. They build the software using <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/test_driven_development,1.620567348185129E-306.html" guid="1.620567348185129E-306">Test-Driven Development,</a> a technique that produces well-crafted and well-tested
-    software with a minimum of wasted effort, and the design is kept clean by the continuous improvement process of <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/refactoring_xp_programming,1.4410217108363206E-306.html" guid="1.4410217108363206E-306">Refactoring</a>.
-</p>
-<p>
-    The middle green circle contains the important supporting practices of XP. The software is designed according to a
-    common, shared, evolving <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/metaphor_system_of_names,4.884861766532753E-306.html" guid="4.884861766532753E-306">Metaphor</a> that helps it all hang together. It is kept <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/continuous_integration,3.193414568279561E-305.html" guid="3.193414568279561E-305">continuously integrated</a> with many system builds every day, each one fully tested. The
-    team shares ownership of of all the code so that needed changes can be made by any qualified pair, not just by one
-    individual. Since everyone works on everything, the team evolves a <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/coding_standard,8.8116853923311E-307.html" guid="8.8116853923311E-307">standard
-    way of coding</a>. Finally, XP teams work at a <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/xp_sustainable_pace,3.133529870649493E-306.html" guid="3.133529870649493E-306">sustainable pace</a> that enables them to deliver tested software on a predictable basis
-    from the first day of the project until the last.
-</p>
-<p>
-    <br />
-    &nbsp;
-</p></td>
-</tr>
-</table>
-</div>
-<table cellpadding="0" cellspacing="0" border="0" class="copyright">
-<tr>
-<td class="copyright"></td>
-</tr>
-</table>
-</td>
-</tr>
-</table>
-</body>
-</html>
diff --git a/XP/xp/customcategories/xp_best_practices.xmi b/XP/xp/customcategories/xp_best_practices.xmi
deleted file mode 100644
index b1d62db..0000000
--- a/XP/xp/customcategories/xp_best_practices.xmi
+++ /dev/null
@@ -1,83 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-LVHbtWMGC3pAL9abD018MA" name="xp_best_practices,4.315031901943112E-306" guid="-LVHbtWMGC3pAL9abD018MA" changeDate="2006-12-01T15:22:33.700-0800" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    Extreme Programming is based on core values of &lt;a class=&quot;elementLinkWithUserText&quot;
-    href=&quot;./../../xp/guidances/concepts/xp_values,1.076140803519123E-306.html&quot; guid=&quot;1.076140803519123E-306&quot;&gt;communication,
-    simplicity, feedback, and courage&lt;/a&gt;. These are not just buzzwords: they pervade the behavior of XP practitioners and
-    the choice of XP practices.
-&lt;/p&gt;
-&lt;p&gt;
-    More than anything else, XP is about people, people coming together and working together to build software. The
-    practices of XP are there to enable people to work together; the practices try never to get in the way of the human
-    enterprise of building software that meets business needs. Thus, the practices of XP, while quite disciplined, are
-    there to enable interactions among individuals, never to replace or interfere with those interactions.
-&lt;/p&gt;
-&lt;h3&gt;
-    XP Practices
-&lt;/h3&gt;
-&lt;p&gt;
-    &lt;b&gt;&lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../xp/guidances/concepts/xp_practices,2.2937799026801584E-305.html&quot;
-    guid=&quot;2.2937799026801584E-305&quot;&gt;Overview&lt;/a&gt;&lt;/b&gt;
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLink&quot; href=&quot;./../../xp/guidances/concepts/whole_team,7.89591827591278E-306.html&quot;
-        guid=&quot;7.89591827591278E-306&quot;&gt;Whole Team&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../xp/guidances/concepts/planning_game,2.7371805612676613E-305.html&quot;
-        guid=&quot;2.7371805612676613E-305&quot;&gt;Planning Game&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../xp/guidances/concepts/small_releases,5.762953011420275E-306.html&quot;
-        guid=&quot;5.762953011420275E-306&quot;&gt;Small Releases&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../xp/guidances/concepts/customer_tests,2.297945473205673E-305.html&quot;
-        guid=&quot;2.297945473205673E-305&quot;&gt;Customer Tests&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../xp/guidances/concepts/simple_design,1.6109092258980447E-306.html&quot;
-        guid=&quot;1.6109092258980447E-306&quot;&gt;Simple Design&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/pair_programming,3.876855509996079E-307.html&quot;
-        guid=&quot;3.876855509996079E-307&quot;&gt;Pair Programming&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/test_driven_development,1.620567348185129E-306.html&quot;
-        guid=&quot;1.620567348185129E-306&quot;&gt;Test Driven Development&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/refactoring_xp_programming,1.4410217108363206E-306.html&quot;
-        guid=&quot;1.4410217108363206E-306&quot;&gt;Refactoring&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/metaphor_system_of_names,4.884861766532753E-306.html&quot;
-        guid=&quot;4.884861766532753E-306&quot;&gt;Metaphor&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/continuous_integration,3.193414568279561E-305.html&quot;
-        guid=&quot;3.193414568279561E-305&quot;&gt;Continuous Integration&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/collective_ownership,9.300699588493279E-306.html&quot;
-        guid=&quot;9.300699588493279E-306&quot;&gt;Collective Ownership&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../xp/guidances/concepts/coding_standard,8.8116853923311E-307.html&quot;
-        guid=&quot;8.8116853923311E-307&quot;&gt;Coding Standard&lt;/a&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;a class=&quot;elementLinkWithUserText&quot;
-        href=&quot;./../../xp/guidances/concepts/xp_sustainable_pace,3.133529870649493E-306.html&quot;
-        guid=&quot;3.133529870649493E-306&quot;&gt;Sustainable Pace&lt;/a&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/customcategories/xp_roles_and_tasks.xmi b/XP/xp/customcategories/xp_roles_and_tasks.xmi
deleted file mode 100644
index fc6b18a..0000000
--- a/XP/xp/customcategories/xp_roles_and_tasks.xmi
+++ /dev/null
@@ -1,94 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-c5D4uYtVcDvab8GzkO0HiQ" name="xp_roles_and_activities,3.967980776087095E-306" guid="-c5D4uYtVcDvab8GzkO0HiQ" changeDate="2006-11-29T16:43:23.824-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_activities__overview_of_xp_and_rup_activities&quot; name=&quot;XE_activities__overview_of_xp_and_rup_activities&quot;&gt;&lt;/a&gt; 
-&lt;div align=&quot;left&quot;&gt;
-    &lt;table width=&quot;75%&quot; border=&quot;1&quot;&gt;
-        &lt;tbody&gt;
-            &lt;tr&gt;
-                &lt;td width=&quot;6%&quot; rowspan=&quot;2&quot;&gt;
-                    &amp;nbsp;
-                &lt;/td&gt;
-                &lt;td align=&quot;middle&quot; colspan=&quot;5&quot;&gt;
-                    &lt;a class=&quot;elementLink&quot; href=&quot;./../../xp/guidances/concepts/whole_team,7.89591827591278E-306.html&quot;
-                    guid=&quot;7.89591827591278E-306&quot;&gt;Whole Team&lt;/a&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td align=&quot;middle&quot; colspan=&quot;2&quot;&gt;
-                    &lt;a class=&quot;elementLink&quot;
-                    href=&quot;./../../xp/guidances/supportingmaterials/xp_customer_team,2.9889538140050517E-306.html&quot;
-                    guid=&quot;2.9889538140050517E-306&quot;&gt;XP Customer Team&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td align=&quot;middle&quot;&gt;
-                    &lt;a class=&quot;elementLink&quot;
-                    href=&quot;./../../xp/guidances/supportingmaterials/xp_developer_team,8.608243854485154E-306.html&quot;
-                    guid=&quot;8.608243854485154E-306&quot;&gt;XP Developer Team&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td align=&quot;middle&quot; colspan=&quot;2&quot;&gt;
-                    &lt;a class=&quot;elementLink&quot;
-                    href=&quot;./../../xp/guidances/supportingmaterials/xp_organization,5.613949040902463E-308.html&quot;
-                    guid=&quot;5.613949040902463E-308&quot;&gt;XP Organization&lt;/a&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-            &lt;tr&gt;
-                &lt;td align=&quot;middle&quot;&gt;
-                    &lt;b&gt;XP Roles&lt;/b&gt; 
-                &lt;/td&gt;
-                &lt;td align=&quot;middle&quot; width=&quot;17%&quot;&gt;
-                    &lt;a class=&quot;elementLinkWithUserText&quot;
-                    href=&quot;./../../xp/roles/xp_customer,{3C90DD4F-CFDB-4111-922D-3B840B8942DE}.html&quot;
-                    guid=&quot;{3C90DD4F-CFDB-4111-922D-3B840B8942DE}&quot;&gt;Customer&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td align=&quot;middle&quot;&gt;
-                    &lt;a class=&quot;elementLinkWithUserText&quot;
-                    href=&quot;./../../xp/roles/xp_tester,{FB65D00B-8304-4CF7-9969-52CE82F503DC}.html&quot;
-                    guid=&quot;{FB65D00B-8304-4CF7-9969-52CE82F503DC}&quot;&gt;Tester&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td align=&quot;middle&quot;&gt;
-                    &lt;a class=&quot;elementLinkWithUserText&quot;
-                    href=&quot;./../../xp/roles/xp_programmer,{08A6AF28-69B1-42DC-A957-2E6CDCB436C1}.html&quot;
-                    guid=&quot;{08A6AF28-69B1-42DC-A957-2E6CDCB436C1}&quot;&gt;Programmer&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td align=&quot;middle&quot; width=&quot;13%&quot;&gt;
-                    &lt;a class=&quot;elementLinkWithUserText&quot;
-                    href=&quot;./../../xp/roles/xp_tracker,{D8FE277E-4F9A-47EB-855F-C451D601BBAF}.html&quot;
-                    guid=&quot;{D8FE277E-4F9A-47EB-855F-C451D601BBAF}&quot;&gt;Tracker&lt;/a&gt; 
-                &lt;/td&gt;
-                &lt;td align=&quot;middle&quot; width=&quot;12%&quot;&gt;
-                    &lt;a class=&quot;elementLinkWithUserText&quot;
-                    href=&quot;./../../xp/roles/xp_coach,{9C440605-FF0E-4D37-A774-BBF8B5F47AB6}.html&quot;
-                    guid=&quot;{9C440605-FF0E-4D37-A774-BBF8B5F47AB6}&quot;&gt;Coach&lt;/a&gt; 
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-    &lt;br /&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;h3&gt;
-    XP Roles and Tasks
-&lt;/h3&gt;
-&lt;p&gt;
-    XP defines a more limited set of roles and tasks than Unified Process. The XP roles usually have much broader scope
-    than Unified Process roles. There is a definite push in XP to move away from specialization where only one person on a
-    team has knowledge of specific and critical parts of the system or technology. The consequence is that the XP roles
-    usually map to more than one Unified Process role. Some Unified Process roles/tasks/artifacts do not map to anything in
-    XP as XP has a somewhat smaller scope than Unified Process.
-&lt;/p&gt;
-&lt;h4&gt;
-    Definition of Roles and Tasks in Unified Process
-&lt;/h4&gt;
-&lt;p&gt;
-    &lt;b&gt;Roles&lt;/b&gt; are typically realized by an individual or a set of individuals working together as a team. A project team
-    member typically fulfills many different roles. &lt;b&gt;Roles&lt;/b&gt; are not individuals; instead, they describe how
-    individuals behave in the business and what responsibilities these individuals have. While most roles are realized by
-    people within the organization, people outside of the development organization play an important role. A &lt;b&gt;role&lt;/b&gt; is
-    an abstract definition of a set of &lt;b&gt;tasks&lt;/b&gt; performed and &lt;b&gt;artifacts&lt;/b&gt; generated.
-&lt;/p&gt;
-&lt;p&gt;
-    &lt;b&gt;Roles&lt;/b&gt; have a set of cohesive&amp;nbsp;&lt;b&gt;tasks&lt;/b&gt; to be performed. These&amp;nbsp;&lt;b&gt;tasks&lt;/b&gt; are closely related and
-    functionally coupled and are often best performed by the same individual.&amp;nbsp;Tasks are closely related to
-    &lt;b&gt;artifacts&lt;/b&gt;. Artifacts provide the input and output for the&amp;nbsp;tasks and the mechanism by which information is
-    communicated between tasks.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/customcategories/xp_white_papers.xmi b/XP/xp/customcategories/xp_white_papers.xmi
deleted file mode 100644
index af9d616..0000000
--- a/XP/xp/customcategories/xp_white_papers.xmi
+++ /dev/null
@@ -1,20 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-_GqtAEsGnq12qQmyqWdHHQ" name="xp_white_papers,6.505229665845286E-306" guid="-_GqtAEsGnq12qQmyqWdHHQ" changeDate="2005-12-06T04:42:48.153-0800">
-  <mainDescription>&lt;p&gt;
-    Additional white papers related to XP can be found at:
-&lt;/p&gt;
-&lt;p&gt;
-    White papers relate to the &lt;a href=&quot;http://www.objectmentor.com/processImprovement/xpRupResourceCenter/index%20&quot;&gt;BUP XP
-    Plug-In Resource Center&lt;/a&gt;.
-&lt;/p&gt;
-&lt;p&gt;
-    White papers related to Agile methods and Object Oriented Programming at &lt;a
-    href=&quot;http://www.objectmentor.com/resources&quot; target=&quot;_blank&quot;&gt;http://www.objectmentor.com/resources&lt;/a&gt;&lt;a
-    href=&quot;http://www.objectmentor.com&quot;&gt;&lt;/a&gt;
-&lt;/p&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;br /&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/agile_software_development.xmi b/XP/xp/guidances/concepts/agile_software_development.xmi
deleted file mode 100644
index 934aba0..0000000
--- a/XP/xp/guidances/concepts/agile_software_development.xmi
+++ /dev/null
@@ -1,76 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-EHSlFv7Gla5oCPGBiaZKow" name="agile_software_development,1.041091673844025E-305" guid="-EHSlFv7Gla5oCPGBiaZKow" changeDate="2006-11-29T15:32:13.357-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_agile_software_development__process_differentiators&quot;
-name=&quot;XE_agile_software_development__process_differentiators&quot;&gt;&lt;/a&gt; 
-&lt;h2&gt;
-    &lt;a id=&quot;Intro&quot; name=&quot;Intro&quot;&gt;Introduction&lt;/a&gt;
-&lt;/h2&gt;
-&lt;p&gt;
-    Extreme Programming is probably the best known and very likely the most used of what have come to be known as agile
-    software development methods. There are many software professionals working on agile methods today. There have been
-    several international conferences on agile methods, numerous papers, many websites, and quite a few books. We'll key
-    our discussion from the Agile Manifesto at &lt;a href=&quot;http://www.agilemanifesto.org&quot;
-    target=&quot;_blank&quot;&gt;www.agilemanifesto.org&lt;/a&gt;.
-&lt;/p&gt;
-&lt;p&gt;
-    We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have
-    come to value:
-&lt;/p&gt;
-&lt;h2&gt;
-    &lt;a id=&quot;Individuals&quot; name=&quot;Individuals&quot;&gt;Individuals and Interactions Over Processes and Tools&lt;/a&gt;
-&lt;/h2&gt;
-&lt;p&gt;
-    Processes and tools are very important. We wouldn't be writing this and you wouldn't be reading it were that not true.
-    The best processes and tools, we believe, are those that enable the individuals who are part of a software project to
-    do their job most effectively. To do that, the processes and tools need to facilitate the human interactions that bring
-    about understanding and cooperation. The agile methods use the smallest amount of process that's safe and the simplest
-    tools that are effective in aid of those individuals and interactions.
-&lt;/p&gt;
-&lt;h2&gt;
-    &lt;a id=&quot;Working&quot; name=&quot;Working&quot;&gt;Working Software Over Comprehensive Documentation&lt;/a&gt;
-&lt;/h2&gt;
-&lt;p&gt;
-    Documentation can be very important to a software project. Sometimes it's the only way to communicate ideas across
-    space and time. For an ongoing software project, however, there is a much better way to know what's going on and to
-    steer the project.
-&lt;/p&gt;
-&lt;p&gt;
-    Observe the software. The software can be tested, used, and inspected, and all the answers you get are unambiguous. The
-    agile methods focus on keeping the software visible, beginning as early as possible. The best XP projects begin
-    producing tested visible software in the first couple of weeks of the project and never stop.
-&lt;/p&gt;
-&lt;h2&gt;
-    &lt;a id=&quot;Customer&quot; name=&quot;Customer&quot;&gt;Customer Collaboration Over Contract Negotiation&lt;/a&gt;
-&lt;/h2&gt;
-&lt;p&gt;
-    Many software projects require a contract, and all benefit from a clear understanding of what will be done. Attempts to
-    over-constrain the initial understanding, however, almost always backfire. Too often, the result can be a &quot;letter of
-    the law&quot; product that pleases neither the developers nor the users. Agile methods recognize that all stakeholders will
-    be learning over the course of the project. Agile projects are thus set up to facilitate learning and to take advantage
-    of it.
-&lt;/p&gt;
-&lt;h2&gt;
-    &lt;a id=&quot;Responding&quot; name=&quot;Responding&quot;&gt;Responding to Change Over Following a Plan&lt;/a&gt;
-&lt;/h2&gt;
-&lt;p&gt;
-    Too many changes of direction can cause a project to go out of control, costing too much or never finishing. Initial
-    plans, however, cannot know which potential changes should be accommodated and which ignored. Agile methods address
-    this issue in two ways:
-&lt;/p&gt;
-&lt;p&gt;
-    First, they respond to change by planning publicly and often. Small changes are dealt with in frequent in-team small
-    planning sessions, while the big picture is published and processed by all stakeholders, again very frequently.
-&lt;/p&gt;
-&lt;p&gt;
-    Second, the development techniques in the agile methods generally allow stakeholders to substitute new and better ideas
-    for earlier notions without exorbitant increases in costs.
-&lt;/p&gt;
-&lt;h2&gt;
-    &lt;a id=&quot;Summary&quot; name=&quot;Summary&quot;&gt;Summary&lt;/a&gt;
-&lt;/h2&gt;
-&lt;p&gt;
-    As you study Extreme Programming and as you use it, it's important to keep these agile values in mind. As you tune and
-    adjust the process to your situation, working with the values will enable you to get the best results from the least
-    effort.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/coding_standard.xmi b/XP/xp/guidances/concepts/coding_standard.xmi
deleted file mode 100644
index d5f0a6b..0000000
--- a/XP/xp/guidances/concepts/coding_standard.xmi
+++ /dev/null
@@ -1,33 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="--qg2qc3dqmgeB63Nx7Zndg" name="coding_standard,8.8116853923311E-307" guid="--qg2qc3dqmgeB63Nx7Zndg" changeDate="2006-11-09T16:13:06.585-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__coding_standard&quot; name=&quot;XE_xp__coding_standard&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_coding_standard__practice_of&quot;
-name=&quot;XE_coding_standard__practice_of&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_engineering_practices__coding_standard&quot;
-name=&quot;XE_engineering_practices__coding_standard&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Description
-&lt;/h3&gt;
-&lt;p&gt;
-    Using a coding standard is a software development practice that has been widely accepted in the industry. The need for
-    this practice takes on added importance in XP because of the increased level of communication required by collective
-    ownership, pair programming and the constant refactoring of the code. The team should have a standard way of naming and
-    formatting things so they can understand the code quickly and know where to look at all times.
-&lt;/p&gt;
-&lt;p&gt;
-    Ideally, the coding standard should be the result of team consensus. In some cases, decisions will be arbitrary
-    (placement of braces). Each item in the standard should support one or more goals, improved communication being one of
-    the most critical goals. Once the team agrees on a standard, all members of the teams are expected to follow it. Pair
-    programming and collective code ownership is sufficient to reinforce the use of the standard within the team. With
-    time, the team will use and modify the standard to develop a style that is well adapted to their environment.
-&lt;/p&gt;
-&lt;h3&gt;
-    Benefits
-&lt;/h3&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        &lt;b&gt;Improved communication&lt;/b&gt;: increases the ability to read each other's code.
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Refactoring support&lt;/b&gt;: provides consistently shaped code.
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/collective_ownership.xmi b/XP/xp/guidances/concepts/collective_ownership.xmi
deleted file mode 100644
index 23cdb73..0000000
--- a/XP/xp/guidances/concepts/collective_ownership.xmi
+++ /dev/null
@@ -1,36 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-YP0i7TC6QNgemddcj1iE7g" name="collective_ownership,9.300699588493279E-306" guid="-YP0i7TC6QNgemddcj1iE7g" changeDate="2006-11-13T14:36:27.348-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__collective_ownership&quot; name=&quot;XE_xp__collective_ownership&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_collective_ownership__practice_of&quot;
-name=&quot;XE_collective_ownership__practice_of&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_engineering_practices__collective_ownership&quot;
-name=&quot;XE_engineering_practices__collective_ownership&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Description
-&lt;/h3&gt;
-&lt;p&gt;
-    The practice of collective ownership states that any member of the team can change any piece of code in the system at
-    any time.
-&lt;/p&gt;
-&lt;p&gt;
-    Having a good suite of tests and being able to integrate continuously is critical to ensuring that this practice works
-    well. Without the tests, it would be impossible to know that a critical piece of the system was modified improperly
-    because of inappropriate understanding. Integrating frequently and testing ensures that such problems are caught and
-    fixed quickly. Used with pair programming, collective code ownership is an effective way to spread the knowledge of the
-    system across the entire team.
-&lt;/p&gt;
-&lt;h3&gt;
-    Benefits
-&lt;/h3&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        &lt;b&gt;Shared knowledge of the code&lt;/b&gt;: allows programmers to become familiar with more of the code and benefit from
-        the experience of others.
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Simpler code&lt;/b&gt;: causes complex code to be found and refactored more quickly as many pairs of eyes read the
-        same code.
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Get things done quickly&lt;/b&gt;: removes hurdles so changes can be made by those that need them when they need them.
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/continuous_integration.xmi b/XP/xp/guidances/concepts/continuous_integration.xmi
deleted file mode 100644
index ed5830f..0000000
--- a/XP/xp/guidances/concepts/continuous_integration.xmi
+++ /dev/null
@@ -1,43 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-35rZhRLEVuTVI4280ncN0A" name="continuous_integration,3.193414568279561E-305" guid="-35rZhRLEVuTVI4280ncN0A" changeDate="2006-11-08T16:55:42.002-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__continuous_integration&quot; name=&quot;XE_xp__continuous_integration&quot;&gt;&lt;/a&gt;&lt;a
-id=&quot;XE_continuous_integration__practice_of&quot; name=&quot;XE_continuous_integration__practice_of&quot;&gt;&lt;/a&gt;&lt;a
-id=&quot;XE_engineering_practices__continuous_integration&quot; name=&quot;XE_engineering_practices__continuous_integration&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Description
-&lt;/h3&gt;
-&lt;p&gt;
-    One of the goals of XP is to ensure that the customer can feel and touch actual progress that reflects the investment
-    to date. As the team builds the software incrementally according to the customer's priority, the new functionality is
-    continuously integrated and demonstrated to the customer.
-&lt;/p&gt;
-&lt;p&gt;
-    Integration in XP can happen several times a day. As developers finish some work, they integrate what they have done.
-    Typically, integration is done on an integration machine in order to serialize the process. Integration is supported by
-    unit tests and acceptance tests. When a pair of programmers first sits at the integration machine, the current code
-    base passes all tests. They start by integrating their changes into the code and checking for conflicts. Then, they run
-    all tests. Should any test fail, the pair is responsible for fixing the code and making it pass. Since the tests were
-    all passed before, the failures are in some way related to the modifications that have made to the code. Once all the
-    tests have passed, the integration can be considered a success and another pair can now integrate its changes. The
-    integrated build can then be handed over to the customer, who can see the new functionality on a running system.
-&lt;/p&gt;
-&lt;p&gt;
-    This practice obviously requires the use of tools and an environment that supports fast integration/build/test cycles.
-&lt;/p&gt;
-&lt;h3&gt;
-    Benefits
-&lt;/h3&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        &lt;b&gt;Simplified and faster integrations&lt;/b&gt;: reduces important conflicts associated with big bang integration and
-        insures that people are working with the latest version of the code.
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Improved feedback&lt;/b&gt;: shows constant and demonstrable progress (it takes a running system to pass the
-        customer's acceptance tests).
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;System always shippable&lt;/b&gt;: the latest version of the system passing all tests is always available.
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/customer_tests.xmi b/XP/xp/guidances/concepts/customer_tests.xmi
deleted file mode 100644
index 1d9ff82..0000000
--- a/XP/xp/guidances/concepts/customer_tests.xmi
+++ /dev/null
@@ -1,31 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-oW2j2l-rXqHeWPIgjPpbng" name="customer_tests,2.297945473205673E-305" guid="-oW2j2l-rXqHeWPIgjPpbng" changeDate="2006-11-10T09:32:51.048-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__customer_tests&quot; name=&quot;XE_xp__customer_tests&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_customer_tests__practice_of&quot;
-name=&quot;XE_customer_tests__practice_of&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_engineering_practices__customer_tests&quot;
-name=&quot;XE_engineering_practices__customer_tests&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Description
-&lt;/h3&gt;
-&lt;p&gt;
-    One of the rights in the customer bill of rights tells the customer he will be able to see progress in the form of a
-    working system that passes repeatable tests that he specifies. These tests are what we call the Customer Tests. The
-    customer specifies one or more Customer Tests for each user story in the system, describing in detail how each story is
-    expected to work. Because the tests are put into executable form and are fully automated, they tell programmers what
-    needs to be done in a unambiguous way (tests pass or fail) and allow the customer to feel confident that the system is
-    meeting his needs.
-&lt;/p&gt;
-&lt;h3&gt;
-    Benefits
-&lt;/h3&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Ability to see &lt;b&gt;tangible and verifiable progress&lt;/b&gt;.
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Ultimate traceability&lt;/b&gt;: the Customer Tests are executable system requirements.
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Repeatability&lt;/b&gt;: because they are automated, the tests can be run at any time.
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/developer_testing.xmi b/XP/xp/guidances/concepts/developer_testing.xmi
deleted file mode 100644
index eda0627..0000000
--- a/XP/xp/guidances/concepts/developer_testing.xmi
+++ /dev/null
@@ -1,515 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-aJBLg1aguP1bIWvQbJSd6w" name="developer_testing,4.085829182735815E-305" guid="-aJBLg1aguP1bIWvQbJSd6w" changeDate="2006-11-13T14:42:19.105-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_test__developer_testing__concept_of&quot; name=&quot;XE_test__developer_testing__concept_of&quot;&gt;&lt;/a&gt;&lt;a
-id=&quot;XE_design__developer_testing__concept_of&quot; name=&quot;XE_design__developer_testing__concept_of&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    &lt;a id=&quot;Introduction&quot; name=&quot;Introduction&quot;&gt;&lt;/a&gt;Introduction
-&lt;/h3&gt;
-&lt;p&gt;
-    The phrase &quot;Developer Testing&quot; is used to categorize the testing activities most appropriately performed by software
-    developers. It also includes the artifacts created by those activities. Developer Testing encompasses the work
-    traditionally thought of under the following categories: Unit Testing, much of Integration Testing, and some aspects of
-    what is most often referred to as System Testing. While Developer Testing is traditionally associated with activities
-    in the Implementation discipline, it also has a relationship to activities in the Analysis and Design discipline.
-&lt;/p&gt;
-&lt;p&gt;
-    By thinking of Developer Testing in this &quot;holistic&quot; way, you help to mitigate some of the risk associated with the more
-    &quot;atomistic&quot; approach traditionally taken. In the traditional approach to Developer Testing, the effort is initially
-    focused on evaluating that all units are working independently. Late in the development life-cycle, as the development
-    work nears completion, the integrated units are assembled into a working subsystem or system and tested in this setting
-    for the first time.
-&lt;/p&gt;
-&lt;p&gt;
-    This approach has a number of failings. Firstly, because it encourages a staged approach to the testing of the
-    integrated units and later subsystems, any errors identified during these tests are often found too late. This late
-    discovery typically results in the decision to take no corrective action, or it requires major rework to correct. This
-    rework is both expensive and detracts from making forward progress in other areas. This increases the risk of the
-    project being derailed or abandoned.
-&lt;/p&gt;
-&lt;p&gt;
-    Secondly, creating rigid boundaries between Unit, Integration and System Test increases the probability that errors
-    spanning the boundaries will be discovered by no one. The risk is compounded when responsibility for these types of
-    tests is assigned to separate teams.
-&lt;/p&gt;
-&lt;p&gt;
-    The style of developer testing recommended by&amp;nbsp;iterative processes&amp;nbsp;encourages the developer to focus on the
-    most valuable and appropriate tests to conduct at the given point in time. Even within the scope of a single iteration,
-    it is usually more efficient for the developer to find and correct as many of the defects in her own code as possible,
-    without the additional overhead in hand-off to a separate test group. The desired result is the early discovery of the
-    most significant software errors&amp;nbsp;- regardless of whether those errors are in the independent unit, the integration
-    of the units or the working of the integrated units within a meaningful end-user scenario.
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;DeveloperTestingPitfalls&quot; name=&quot;DeveloperTestingPitfalls&quot;&gt;&lt;/a&gt;Pitfalls Getting Started with Developer Testing
-&lt;/h3&gt;
-&lt;p&gt;
-    Many developers who begin trying to do a substantially more thorough job of testing give up the effort shortly
-    thereafter. They find that it does not seem to be yielding value. Further, some developers who begin well with
-    developer testing find that they've created an unmaintainable test suite that is eventually abandoned.
-&lt;/p&gt;
-&lt;p&gt;
-    This page gives some guidelines for getting over the first hurdles and for creating a test suite that avoids the
-    maintainability trap. For more information, see &lt;a href=&quot;../../workguid/wg_mnttstste.htm&quot;&gt;Guidelines: Maintaining
-    Automated Test Suites&lt;/a&gt;.
-&lt;/p&gt;
-&lt;h4&gt;
-    Establish expectations
-&lt;/h4&gt;
-&lt;p&gt;
-    Those who find developer testing rewarding do it. Those who view it as a chore find ways to avoid it. This is simply in
-    the nature of most developers in most industries, and treating it as a shameful lack of discipline hasn't historically
-    been successful. Therefore, as a developer you should expect testing to be rewarding and do what it takes to make it
-    rewarding.
-&lt;/p&gt;
-&lt;p&gt;
-    Ideal developer testing follows a very tight edit-test loop. You make a small change to the product, such as adding a
-    new method to a class, then you immediately rerun your tests. If any test breaks, you know exactly what code is the
-    cause. This easy, steady pace of development is the greatest reward of developer testing. A long debugging session
-    should be exceptional.
-&lt;/p&gt;
-&lt;p&gt;
-    Because it's not unusual for a change made in one class to break something in another, you should expect to rerun not
-    just the changed class's tests, but many tests. Ideally, you rerun the complete test suite for your component many
-    times per hour. Every time you make a significant change, you rerun the suite, watch the results, and either proceed to
-    the next change or fix the last change. Expect to spend some effort making that rapid feedback possible.
-&lt;/p&gt;
-&lt;h4&gt;
-    Automate your tests
-&lt;/h4&gt;
-&lt;p&gt;
-    Running tests often is not practical if tests are manual. For some components, automated tests are easy. An example
-    would be an in-memory database. It communicates to its clients through an API and has no other interface to the outside
-    world. Tests for it would look something like this:
-&lt;/p&gt;
-&lt;blockquote&gt;
-&lt;pre&gt;
-/* Check that elements can be added at most once. */
-// Setup
-Database db = new Database();
-db.add(&quot;key1&quot;, &quot;value1&quot;);
-// Test
-boolean result = db.add(&quot;key1&quot;, &quot;another value&quot;);
-expect(result == false);
-&lt;/pre&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    The tests are different from ordinary client code in only one way: instead of believing the results of API calls, they
-    check. If the API makes client code easy to write, it makes test code easy to write. If the test code is &lt;i&gt;not&lt;/i&gt;
-    easy to write, you've received an early warning that the API could be improved. Test-first design is thus consistent
-    with the iterative processes' focus on addressing important risks early.
-&lt;/p&gt;
-&lt;p&gt;
-    The more tightly connected the component is to the outside world, however, the harder it will be to test. There are two
-    common cases: graphical user interfaces and back-end components.
-&lt;/p&gt;
-&lt;h5&gt;
-    Graphical user interfaces
-&lt;/h5&gt;
-&lt;p&gt;
-    Suppose the database in the example above receives its data via a callback from a user-interface object. The callback
-    is invoked when the user fills in some text fields and pushes a button. Testing this by manually filling in the fields
-    and pushing the button isn't something you want to do many times an hour. You must arrange a way to deliver the input
-    under programmatic control, typically by &quot;pushing&quot; the button in code.
-&lt;/p&gt;
-&lt;p&gt;
-    Pushing the button causes some code in the component to be executed. Most likely, that code changes the state of some
-    user-interface objects. So you must also arrange a way to query those objects programmatically.
-&lt;/p&gt;
-&lt;h5&gt;
-    Back-end components
-&lt;/h5&gt;
-&lt;p&gt;
-    Suppose the component under test doesn't implement a database. Instead, it's a wrapper around a real, on-disk database.
-    Testing against that real database might be difficult. It might be hard to install and configure. Licenses for it might
-    be expensive. The database might slow down the tests enough that you're not inclined to run them often. In such cases,
-    it's worthwhile to &quot;stub out&quot; the database with a simpler component that does just enough to support the tests.
-&lt;/p&gt;
-&lt;p&gt;
-    Stubs are also useful when a component that your component talks to isn't ready yet. You don't want your testing to
-    wait on someone else's code.
-&lt;/p&gt;
-&lt;p&gt;
-    For more information, see &lt;a href=&quot;../implemen/co_stubs.htm&quot;&gt;Concepts: Stubs&lt;/a&gt;.
-&lt;/p&gt;
-&lt;h4&gt;
-    Don't write your own tools
-&lt;/h4&gt;
-&lt;p&gt;
-    Developer testing seems pretty straightforward. You set up some objects, make a call through an API, check the result,
-    and announce a test failure if the results aren't as expected. It's also convenient to have some way to group tests so
-    that they can be run individually or as complete suites. Tools that support those requirements are called &lt;i&gt;test
-    frameworks&lt;/i&gt;.
-&lt;/p&gt;
-&lt;p&gt;
-    Developer testing &lt;b&gt;is&lt;/b&gt; straightforward, and the requirements for test frameworks are not complicated. If, however,
-    you yield to the temptation of writing your own test framework, you'll spend much more time tinkering with the
-    framework than you probably expect. There are many test frameworks available, both commercial and open source, and
-    there's no reason not to use one of those.
-&lt;/p&gt;
-&lt;h4&gt;
-    Do create support code
-&lt;/h4&gt;
-&lt;p&gt;
-    Test code tends to be repetitive. It's common to see sequences of code like this:
-&lt;/p&gt;
-&lt;blockquote&gt;
-&lt;pre&gt;
-// null name not allowed
-retval = o.createName(&quot;&quot;); 
-expect(retval == null);
-// leading spaces not allowed
-retval = o.createName(&quot; l&quot;); 
-expect(retval == null);
-// trailing spaces not allowed
-retval = o.createName(&quot;name &quot;); 
-expect(retval == null);
-// first character may not be numeric
-retval = o.createName(&quot;5allpha&quot;); 
-expect(retval == null);
-&lt;/pre&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    This code is created by copying one check, pasting it, then editing it to make another check.
-&lt;/p&gt;
-&lt;p&gt;
-    The danger here is twofold. If the interface changes, much editing will have to be done. (In more complicated cases, a
-    simple global replacement won't suffice.) Also, if the code is at all complicated, the intent of the test can be lost
-    amid all the text.
-&lt;/p&gt;
-&lt;p&gt;
-    When you find yourself repeating yourself, seriously consider factoring out the repetition into support code. Even
-    though the code above is a simple example, it's more readable and maintainable if written like this:
-&lt;/p&gt;
-&lt;blockquote&gt;
-&lt;pre&gt;
-void expectNameRejected(MyClass o, String s) {
-    Object retval = o.createName(s);
-    expect(retval == null);
-}
-...
-// null name not allowed
-expectNameRejected(o, &quot;&quot;); 
-// leading spaces not allowed.
-expectNameRejected(o, &quot; l&quot;); 
-// trailing spaces not allowed.
-expectNameRejected(o, &quot;name &quot;); 
-// first character may not be numeric.
-expectNameRejected(o, &quot;5alpha&quot;); 
-&lt;/pre&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    Developers writing tests often err on the side of too much copying-and-pasting. If you suspect yourself of that
-    tendency, it's useful to consciously err in the other direction. Resolve that you will strip your code of all duplicate
-    text.
-&lt;/p&gt;
-&lt;h4&gt;
-    Write the tests first
-&lt;/h4&gt;
-&lt;p&gt;
-    Writing the tests after the code is a chore. The urge is to rush through it, to finish up and move on. Writing tests
-    before the code makes testing part of a positive feedback loop. As you implement more code, you see more tests passing
-    until finally all the tests pass and you're done. People who write tests first seem to be more successful, and it takes
-    no more time. For more on putting tests first, see &lt;a class=&quot;elementLinkWithType&quot;
-    href=&quot;./../../../xp/guidances/concepts/test-first_design,6.556259235358794E-306.html&quot;
-    guid=&quot;6.556259235358794E-306&quot;&gt;Concept: Test-first Design&lt;/a&gt;
-&lt;/p&gt;
-&lt;h4&gt;
-    Keep the tests understandable
-&lt;/h4&gt;
-&lt;p&gt;
-    You should expect that you, or someone else, will have to modify the tests later. A typical situation is that a later
-    iteration calls for a change to the component's behavior. As a simple example, suppose the component once declared a
-    square root method like this:
-&lt;/p&gt;
-&lt;blockquote&gt;
-    &lt;p&gt;
-        &lt;font size=&quot;+0&quot;&gt;double sqrt(double x);&lt;/font&gt;
-    &lt;/p&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    In that version, a negative argument caused &lt;font size=&quot;+0&quot;&gt;sqrt&lt;/font&gt; to return NaN (&quot;not a number&quot; from the IEEE
-    754-1985 &lt;i&gt;Standard for Binary Floating-Point Arithmetic&lt;/i&gt;). In the new iteration, the square root method will
-    accept negative numbers and return a complex result:
-&lt;/p&gt;
-&lt;blockquote&gt;
-    &lt;p&gt;
-        &lt;font size=&quot;+0&quot;&gt;Complex sqrt(double x);&lt;/font&gt;
-    &lt;/p&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    Old tests for &lt;font size=&quot;+0&quot;&gt;sqrt&lt;/font&gt; will have to change. That means understanding what they do, and updating them
-    so that they work with the new &lt;font size=&quot;+0&quot;&gt;sqrt&lt;/font&gt;. When updating tests, you must take care not to destroy
-    their bug-finding power. One way that sometimes happens is this:
-&lt;/p&gt;
-&lt;blockquote&gt;
-&lt;pre&gt;
-void testSQRT () {
-    //  Update these tests for Complex 
-    // when I have time -- bem
-    /*
-double result = sqrt(0.0);
-...
-    */
-}
-&lt;/pre&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    Other ways are more subtle: the tests are changed so that they actually run, but they no longer test what they were
-    originally intended to test. The end result, over many iterations, can be a test suite that is too weak to catch many
-    bugs. This is sometimes called &quot;test suite decay&quot;. A decayed suite will be abandoned, because it's not worth the
-    upkeep.
-&lt;/p&gt;
-&lt;p&gt;
-    You can't maintain a test's bug-finding power unless it's clear what &lt;a class=&quot;elementLinkWithUserText&quot;
-    href=&quot;./../../../xp/guidances/concepts/test-ideas_list,8.834380241450745E-306.html#TestIdeas&quot;
-    guid=&quot;8.834380241450745E-306&quot;&gt;Test Ideas&lt;/a&gt; a test implements. Test code tends to be under-commented, even though it's
-    often harder to understand the &quot;why&quot; behind it than product code.
-&lt;/p&gt;
-&lt;p&gt;
-    Test suite decay is less likely in the direct tests for &lt;font size=&quot;+0&quot;&gt;sqrt&lt;/font&gt; than in indirect tests. There will
-    be code that calls &lt;font size=&quot;+0&quot;&gt;sqrt&lt;/font&gt;. That code will have tests. When &lt;font size=&quot;+0&quot;&gt;sqrt&lt;/font&gt; changes,
-    some of those tests will fail. The person who changes &lt;font size=&quot;+0&quot;&gt;sqrt&lt;/font&gt; will probably have to change those
-    tests. Because he's less familiar with them, and because their relationship to the change is less clear, he's more
-    likely to weaken them in the process of making them pass.
-&lt;/p&gt;
-&lt;p&gt;
-    When you're creating support code for tests (as urged above), be careful: the support code should clarify, not obscure,
-    the purpose of the tests that use it. A common complaint about object-oriented programs is that there's no one place
-    where anything's done. If you look at any one method, all you discover is that it forwards its work somewhere else.
-    Such a structure has advantages, but it makes it harder for new people to understand the code. Unless they make an
-    effort, their changes are likely to be incorrect or to make the code even more complicated and fragile. The same is
-    true of test code, except that later maintainers are even less likely to take due care. You must head off the problem
-    by writing understandable tests.
-&lt;/p&gt;
-&lt;h4&gt;
-    Match the test structure to the product structure
-&lt;/h4&gt;
-&lt;p&gt;
-    Suppose someone has inherited your component. They need to change a part of it. They may want to examine the old tests
-    to help them in their new design. They want to update the old tests before writing the code (test-first design).
-&lt;/p&gt;
-&lt;p&gt;
-    All those good intentions will go by the wayside if they can't find the appropriate tests. What they'll do is make the
-    change, see what tests fail, then fix those. That will contribute to test suite decay.
-&lt;/p&gt;
-&lt;p&gt;
-    For that reason, it's important that the test suite be well structured, and that the location of tests be predictable
-    from the structure of the product. Most usually, developers arrange tests in a parallel hierarchy, with one test class
-    per product class. So if someone is changing a class named &lt;font size=&quot;+0&quot;&gt;Log&lt;/font&gt;, they know the test class is
-    &lt;font size=&quot;+0&quot;&gt;TestLog&lt;/font&gt;, and they know where the source file can be found.
-&lt;/p&gt;
-&lt;h4&gt;
-    Let tests violate encapsulation
-&lt;/h4&gt;
-&lt;p&gt;
-    You might limit your tests to interacting with your component exactly as client code does, through the same interface
-    that client code uses. However, this has disadvantages. Suppose you're testing a simple class that maintains a doubly
-    linked list:
-&lt;/p&gt;
-&lt;p align=&quot;center&quot;&gt;
-    &lt;img height=&quot;46&quot; alt=&quot;&quot; src=&quot;resources/dvltst-img1.gif&quot; width=&quot;195&quot; /&gt;
-&lt;/p&gt;
-&lt;p class=&quot;picturetext&quot;&gt;
-    Fig1: Double-linked list
-&lt;/p&gt;
-&lt;p&gt;
-    In particular, you're testing the &lt;font size=&quot;+0&quot;&gt;DoublyLinkedList.insertBefore(Object existing, Object
-    newObject)&lt;/font&gt; method. In one of your tests, you want to insert an element in the middle of the list, then check if
-    it's been inserted successfully. The test uses the list above to create this updated list:
-&lt;/p&gt;
-&lt;p align=&quot;center&quot;&gt;
-    &lt;img height=&quot;46&quot; alt=&quot;&quot; src=&quot;resources/dvltst-img2.gif&quot; width=&quot;318&quot; /&gt;
-&lt;/p&gt;
-&lt;p class=&quot;picturetext&quot;&gt;
-    Fig2: Double-linked list - item inserted
-&lt;/p&gt;
-&lt;p&gt;
-    It checks the list correctness like this:
-&lt;/p&gt;
-&lt;blockquote&gt;
-&lt;pre&gt;
-// the list is now one longer. 
-expect(list.size()==3);
-// the new element is in the correct position
-expect(list.get(1)==m);
-// check that other elements are still there.
-expect(list.get(0)==a);
-expect(list.get(2)==z);
-&lt;/pre&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    That seems sufficient, but it's not. Suppose the list implementation is incorrect and backward pointers are not set
-    correctly. That is, suppose the updated list actually looks like this:
-&lt;/p&gt;
-&lt;p align=&quot;center&quot;&gt;
-    &lt;img height=&quot;73&quot; alt=&quot;&quot; src=&quot;resources/dvltst-img3.gif&quot; width=&quot;318&quot; /&gt;
-&lt;/p&gt;
-&lt;p class=&quot;picturetext&quot;&gt;
-    Fig3: Double-linked list - fault in implementation
-&lt;/p&gt;
-&lt;p&gt;
-    If &lt;font size=&quot;+0&quot;&gt;DoublyLinkedList.get(int index)&lt;/font&gt; traverses the list from the beginning to the end (likely),
-    the test would miss this failure. If the class provides &lt;font size=&quot;+0&quot;&gt;elementBefore&lt;/font&gt; and &lt;font
-    size=&quot;+0&quot;&gt;elementAfter&lt;/font&gt; methods, checking for such failures is straightforward:
-&lt;/p&gt;
-&lt;blockquote&gt;
-&lt;pre&gt;
-// Check that links were all updated
-expect(list.elementAfter(a)==m);
-expect(list.elementAfter(m)==z);
-expect(list.elementBefore(z)==m); //this will fail
-expect(list.elementBefore(m)==a);
-&lt;/pre&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    But what if it doesn't provide those methods? You could devise more elaborate sequences of method calls that will fail
-    if the suspected defect is present. For example, this would work:
-&lt;/p&gt;
-&lt;blockquote&gt;
-&lt;pre&gt;
-// Check whether back-link from Z is correct.
-list.insertBefore(z, x);
-// If it was incorrectly not updated, X will have 
-// been inserted just after A.
-expect(list.get(1)==m); 
-&lt;/pre&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    But such a test is more work to create and is likely to be significantly harder to maintain. (Unless you write good
-    comments, it will not be at all clear why the test is doing what it's doing.) There are two solutions:
-&lt;/p&gt;
-&lt;ol&gt;
-    &lt;li&gt;
-        Add the &lt;font size=&quot;+0&quot;&gt;elementBefore&lt;/font&gt; and &lt;font size=&quot;+0&quot;&gt;elementAfter&lt;/font&gt; methods to the public
-        interface. But that effectively exposes the implementation to everyone and makes future change more difficult.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Let the tests &quot;look under the hood&quot; and check pointers directly.
-    &lt;/li&gt;
-&lt;/ol&gt;
-&lt;p&gt;
-    The latter is usually the best solution, even for a simple class like &lt;font size=&quot;+0&quot;&gt;DoublyLinkedList&lt;/font&gt; and
-    especially for the more complex classes that occur in your products.
-&lt;/p&gt;
-&lt;p&gt;
-    Typically, tests are put in the same package as the class they test. They are given protected or friend access.
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;TestDesignMistakes&quot; name=&quot;TestDesignMistakes&quot;&gt;&lt;/a&gt;Characteristic Test Design Mistakes
-&lt;/h3&gt;
-&lt;p&gt;
-    Each test exercises a component and checks for correct results. The design of the test-the inputs it uses and how it
-    checks for correctness-can be good at revealing defects, or it can inadvertently hide them. Here are some
-    characteristic test design mistakes.
-&lt;/p&gt;
-&lt;h4&gt;
-    Failure to specify expected results in advance
-&lt;/h4&gt;
-&lt;p&gt;
-    Suppose you're testing a component that converts XML into HTML. A temptation is to take some sample XML, run it through
-    the conversion, then look at the results in a browser. If the screen looks right, you &quot;bless&quot; the HTML by saving it as
-    the official expected results. Thereafter, a test compares the actual output of the conversion to the expected results.
-&lt;/p&gt;
-&lt;p&gt;
-    This is a dangerous practice. Even sophisticated computer users are used to believing what the computer does. You are
-    likely to overlook mistakes in the screen appearance. (Not to mention that browsers are quite tolerant of misformatted
-    HTML.) By making that incorrect HTML the official expected results, you make sure that the test can never find the
-    problem.
-&lt;/p&gt;
-&lt;p&gt;
-    It's less dangerous to doubly-check by looking directly at the HTML, but it's still dangerous. Because the output is
-    complicated, it will be easy to overlook errors. You'll find more defects if you write the expected output by hand
-    first.
-&lt;/p&gt;
-&lt;h4&gt;
-    Failure to check the background
-&lt;/h4&gt;
-&lt;p&gt;
-    Tests usually check that what should have been changed has been, but their creators often forget to check that what
-    should have been left alone has been left alone. For example, suppose a program is supposed to change the first 100
-    records in a file. It's a good idea to check that the 101&lt;sup&gt;st&lt;/sup&gt; hasn't been changed.
-&lt;/p&gt;
-&lt;p&gt;
-    In theory, you would check that nothing in the &quot;background&quot;-the entire file system, all of memory, everything reachable
-    through the network-has been left alone. In practice, you have to choose carefully what you can afford to check. But
-    it's important to make that choice.
-&lt;/p&gt;
-&lt;h4&gt;
-    Failure to check persistence
-&lt;/h4&gt;
-&lt;p&gt;
-    Just because the component tells you a change has been made, that doesn't mean it has actually been committed to the
-    database. You need to check the database via another route.
-&lt;/p&gt;
-&lt;h4&gt;
-    Failure to add variety
-&lt;/h4&gt;
-&lt;p&gt;
-    A test might be designed to check the effect of three fields in a database record, but many other fields need to be
-    filled in to execute the test. Testers will often use the same values over and over again for these &quot;irrelevant&quot;
-    fields. For example, they'll always use the name of their lover in a text field, or 999 in a numeric field.
-&lt;/p&gt;
-&lt;p&gt;
-    The problem is that sometimes what shouldn't matter actually does. Every so often, there's a bug that depends on some
-    obscure combination of unlikely inputs. If you always use the same inputs, you stand no chance of finding such bugs. If
-    you persistently vary inputs, you might. Quite often, it costs almost nothing to use a number different than 999 or to
-    use someone else's name. When varying the values used in tests costs almost nothing and it has some potential benefit,
-    then vary. (Note: It's unwise to use names of old lovers instead of your current one if your current lover works with
-    you.)
-&lt;/p&gt;
-&lt;p&gt;
-    Here's another benefit. One plausible fault is for the program to use field &lt;i&gt;X&lt;/i&gt; when it should have used field
-    &lt;i&gt;Y&lt;/i&gt;. If both fields contain &quot;Dawn&quot;, the fault can't be detected.
-&lt;/p&gt;
-&lt;h4&gt;
-    Failure to use realistic data
-&lt;/h4&gt;
-&lt;p&gt;
-    It's common to use made-up data in tests. That data is often unrealistically simple. For example, customer names might
-    be &quot;Mickey&quot;, &quot;Snoopy&quot;, and &quot;Donald&quot;. Because that data is different from what real users enter - for example, it's
-    characteristically shorter - it can miss defects real customers will see. For example, these one-word names wouldn't
-    detect that the code doesn't handle names with spaces.
-&lt;/p&gt;
-&lt;p&gt;
-    It's prudent to make a slight extra effort to use realistic data.
-&lt;/p&gt;
-&lt;h4&gt;
-    Failure to notice that the code does nothing at all
-&lt;/h4&gt;
-&lt;p&gt;
-    Suppose you initialize a database record to zero, run a calculation that should result in zero being stored in the
-    record, then check that the record is zero. What has your test demonstrated? The calculation might not have taken place
-    at all. Nothing might have been stored, and the test couldn't tell.
-&lt;/p&gt;
-&lt;p&gt;
-    That example sounds unlikely. But this same mistake can crop up in subtler ways. For example, you might write a test
-    for a complicated installer program. The test is intended to check that all temporary files are removed after a
-    successful installation. But, because of all the installer options, in that test, one particular temporary file wasn't
-    created. Sure enough, that's the one the program forgot to remove.
-&lt;/p&gt;
-&lt;h4&gt;
-    Failure to notice that the code does the wrong thing
-&lt;/h4&gt;
-&lt;p&gt;
-    Sometimes a program does the right thing for the wrong reasons. As a trivial example, consider this code:
-&lt;/p&gt;
-&lt;blockquote&gt;
-&lt;pre&gt;
-if (a &amp;lt; b &amp;amp;&amp;amp; c) 
-    return 2 * x;
-else
-    return x * x;
-&lt;/pre&gt;
-&lt;/blockquote&gt;
-&lt;p&gt;
-    The logical expression is wrong, and you've written a test that causes it to evaluate incorrectly and take the wrong
-    branch. Unfortunately, purely by coincidence, the variable X has the value 2 in that test. So the result of the wrong
-    branch is accidentally correct - the same as the result the right branch would have given.
-&lt;/p&gt;
-&lt;p&gt;
-    For each expected result, you should ask if there's a plausible way in which that result could be gotten for the wrong
-    reason. While it's often impossible to know, sometimes it's not.
-&lt;/p&gt;
-&lt;br /&gt;
-&lt;br /&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/extreme_programming.xmi b/XP/xp/guidances/concepts/extreme_programming.xmi
deleted file mode 100644
index 6e210bb..0000000
--- a/XP/xp/guidances/concepts/extreme_programming.xmi
+++ /dev/null
@@ -1,229 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-27sE-swoOUGtar9a0f3RPw" name="extreme_programming,5.2637267673584526E-306" guid="-27sE-swoOUGtar9a0f3RPw" changeDate="2006-12-01T15:11:05.063-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__conceptual_process_roadmap&quot; name=&quot;XE_xp__conceptual_process_roadmap&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_roadmap__for_xp_practices&quot;
-name=&quot;XE_roadmap__for_xp_practices&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Topics
-&lt;/h3&gt;
-&lt;div align=&quot;left&quot;&gt;
-    &lt;table width=&quot;70%&quot; border=&quot;1&quot;&gt;
-        &lt;tbody valign=&quot;top&quot;&gt;
-            &lt;tr&gt;
-                &lt;td width=&quot;315&quot; height=&quot;178&quot;&gt;
-                    &lt;ul&gt;
-                        &lt;li&gt;
-                            &lt;a href=&quot;#Introduction&quot;&gt;Introduction&lt;/a&gt;
-                        &lt;/li&gt;
-                        &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;&gt;
-                            &lt;ul&gt;
-                                &lt;li&gt;
-                                    &lt;a href=&quot;#About&quot;&gt;About XP&lt;/a&gt;
-                                &lt;/li&gt;
-                            &lt;/ul&gt;
-                        &lt;/li&gt;
-                        &lt;li&gt;
-                            &lt;a href=&quot;#Characteristics&quot;&gt;Characteristics of an XP Project&lt;/a&gt;
-                        &lt;/li&gt;
-                        &lt;li&gt;
-                            &lt;a href=&quot;#Phases&quot;&gt;Phases and Iterations&lt;/a&gt;
-                        &lt;/li&gt;
-                        &lt;li&gt;
-                            &lt;a href=&quot;#GettingStarted&quot;&gt;How to Get Started&lt;/a&gt;
-                        &lt;/li&gt;
-                    &lt;/ul&gt;
-                &lt;/td&gt;
-                &lt;td width=&quot;315&quot; height=&quot;178&quot;&gt;
-                    &lt;b&gt;Additional Guidance:&lt;/b&gt; 
-                    &lt;ul&gt;
-                        &lt;li&gt;
-                            Guidelines
-                        &lt;/li&gt;
-                        &lt;li style=&quot;LIST-STYLE-TYPE: none&quot;&gt;
-                            &lt;ul&gt;
-                                &lt;li&gt;
-                                    &lt;a class=&quot;elementLink&quot;
-                                    href=&quot;./../../../xp/guidances/guidelines/refactoring,8.137126904637637E-306.html&quot;
-                                    guid=&quot;8.137126904637637E-306&quot;&gt;Refactoring&lt;/a&gt;
-                                &lt;/li&gt;
-                                &lt;li&gt;
-                                    &lt;a class=&quot;elementLinkWithUserText&quot;
-                                    href=&quot;./../../../xp/guidances/guidelines/test_driven_development_tdd,3.9254165491375454E-306.html&quot;
-                                     guid=&quot;3.9254165491375454E-306&quot;&gt;Test First Development&lt;/a&gt;
-                                &lt;/li&gt;
-                                &lt;li&gt;
-                                    &lt;a class=&quot;elementLinkWithUserText&quot;
-                                    href=&quot;./../../../xp/guidances/guidelines/pair_programming,3.85153041801319E-307.html&quot;
-                                    guid=&quot;3.85153041801319E-307&quot;&gt;Pair Programming&lt;/a&gt;
-                                &lt;/li&gt;
-                                &lt;li&gt;
-                                    &lt;a class=&quot;elementLinkWithUserText&quot;
-                                    href=&quot;./../../../xp/guidances/guidelines/planning_game,6.7335956461328426E-307.html&quot;
-                                    guid=&quot;6.7335956461328426E-307&quot;&gt;Planning Game&lt;/a&gt;
-                                &lt;/li&gt;
-                            &lt;/ul&gt;
-                        &lt;/li&gt;
-                    &lt;/ul&gt;
-                    &lt;br /&gt;
-                     &lt;b&gt;Additional Concepts:&lt;/b&gt; 
-                    &lt;ul&gt;
-                        &lt;li&gt;
-                            &lt;a class=&quot;elementLink&quot;
-                            href=&quot;./../../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html&quot;
-                            guid=&quot;1.041091673844025E-305&quot;&gt;Agile Software Development&lt;/a&gt;
-                        &lt;/li&gt;
-                    &lt;/ul&gt;
-                &lt;/td&gt;
-            &lt;/tr&gt;
-        &lt;/tbody&gt;
-    &lt;/table&gt;
-&lt;/div&gt;
-&lt;br /&gt;
-&lt;br /&gt;
-&lt;h1&gt;
-    &lt;a id=&quot;Introduction&quot; name=&quot;Introduction&quot;&gt;Introduction&lt;/a&gt;
-&lt;/h1&gt;
-&lt;p&gt;
-    This roadmap provides information for getting started and applying the practices of eXtreme Programming (XP) to a
-    software development project.
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;About&quot; name=&quot;About&quot;&gt;About XP&lt;/a&gt;&amp;nbsp;
-&lt;/h3&gt;
-&lt;p&gt;
-    Extreme Programming is an instance of an &lt;a class=&quot;elementLink&quot;
-    href=&quot;./../../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html&quot;
-    guid=&quot;1.041091673844025E-305&quot;&gt;Agile Software Development&lt;/a&gt; method. XP is a method that is optimized for small to
-    medium-sized project teams that fit a certain profile. It promotes rapid feedback and response to continual change. It
-    is based upon the four &lt;a class=&quot;elementLinkWithUserText&quot;
-    href=&quot;./../../../xp/guidances/concepts/xp_values,1.076140803519123E-306.html&quot; guid=&quot;1.076140803519123E-306&quot;&gt;values&lt;/a&gt;
-    of simplicity, communication, feedback, and courage and is consistent with the values of agile software development.
-&lt;/p&gt;
-&lt;p&gt;
-    Extreme Programming is an instance of an agile method for developing software. It is based upon the core principle of
-    agility and consists of twelve practices that, when applied to an appropriate software development project, can produce
-    high-quality software. If you are unfamiliar with the concepts surrounding XP, you should start by reading &lt;a
-    class=&quot;elementLink&quot; href=&quot;./../../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html&quot;
-    guid=&quot;1.041091673844025E-305&quot;&gt;Agile Software Development&lt;/a&gt;.
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;Characteristics&quot; name=&quot;Characteristics&quot;&gt;Characteristics of an XP Project&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    Extreme Programming or XP is a development process that can be used by small to medium-sized teams to develop high
-    quality software within a predictable schedule and budget and with a minimum of overhead. Since XP relies heavily on
-    direct and frequent communication between the team members, the team should be co-located. An ideal project for using
-    XP would be one that has most of the following characteristics:
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        A small to medium-sized team (fewer than 20 people on the complete team)
-    &lt;/li&gt;
-    &lt;li&gt;
-        Co-located, preferably in a single area with a large common space
-    &lt;/li&gt;
-    &lt;li&gt;
-        A committed, full-time, on-site customer or customer representative
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;Phases&quot; name=&quot;Phases&quot;&gt;Phases and Iterations&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    An XP project is one that is based on rapid feedback through short iterations and frequent releases.&amp;nbsp;Unified
-    Process&amp;nbsp;and XP share a fundamental belief that iterative development is the best way to deliver valuable software
-    to your customers. The concept of phases, as usually described in the Unified Process, is somewhat different. Decisions
-    described in the Unified Process phases that define milestones occur, but they are not called specifically as defining
-    phases.
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;GettingStarted&quot; name=&quot;GettingStarted&quot;&gt;How to Get Started&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    This section provides a recommended way to approach XP for your project. You don't have to follow the steps as
-    specified, but if you have little experience with XP, we recommend following them as closely as possible the first
-    time.
-&lt;/p&gt;
-&lt;table cellspacing=&quot;2&quot; cellpadding=&quot;1&quot; width=&quot;91%&quot; border=&quot;1&quot;&gt;
-    &lt;tbody&gt;
-        &lt;tr&gt;
-            &lt;th width=&quot;10%&quot;&gt;
-                Step
-            &lt;/th&gt;
-            &lt;th align=&quot;left&quot; width=&quot;47%&quot;&gt;
-                Do this ...
-            &lt;/th&gt;
-            &lt;th align=&quot;left&quot; width=&quot;43%&quot;&gt;
-                in order to...
-            &lt;/th&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;td align=&quot;middle&quot; width=&quot;10%&quot;&gt;
-                1
-            &lt;/td&gt;
-            &lt;td width=&quot;47%&quot;&gt;
-                Familiarize yourself with the&amp;nbsp;&lt;a class=&quot;elementLink&quot;
-                href=&quot;./../../../xp/guidances/concepts/motivation,1.6390805262958034E-306.html&quot;
-                guid=&quot;1.6390805262958034E-306&quot;&gt;motivation&lt;/a&gt; for using XP, the &lt;a class=&quot;elementLinkWithUserText&quot;
-                href=&quot;./../../../xp/guidances/concepts/what_is_xp,9.251272550276345E-306.html&quot;
-                guid=&quot;9.251272550276345E-306&quot;&gt;short description&lt;/a&gt; of XP, and the &lt;a class=&quot;elementLink&quot;
-                href=&quot;./../../../xp/guidances/concepts/xp_practices,2.2937799026801584E-305.html&quot;
-                guid=&quot;2.2937799026801584E-305&quot;&gt;XP Practices&lt;/a&gt; 
-            &lt;/td&gt;
-            &lt;td width=&quot;43%&quot;&gt;
-                understand the fundamental principles of XP and how the practices support each other.
-            &lt;/td&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;td align=&quot;middle&quot; width=&quot;10%&quot;&gt;
-                2
-            &lt;/td&gt;
-            &lt;td width=&quot;47%&quot;&gt;
-                Read the key concepts of &lt;a class=&quot;elementLink&quot;
-                href=&quot;./../../../xp/guidances/concepts/agile_software_development,1.041091673844025E-305.html&quot;
-                guid=&quot;1.041091673844025E-305&quot;&gt;Agile Software Development&lt;/a&gt; 
-            &lt;/td&gt;
-            &lt;td width=&quot;43%&quot;&gt;
-                understand the collaborative and social aspects of XP.
-            &lt;/td&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;td align=&quot;middle&quot; width=&quot;10%&quot;&gt;
-                3
-            &lt;/td&gt;
-            &lt;td width=&quot;47%&quot;&gt;
-                Determine if XP is appropriate for your project by reviewing &lt;a href=&quot;#Characteristics&quot;&gt;The Characteristics
-                of an XP Project&lt;/a&gt; 
-            &lt;/td&gt;
-            &lt;td width=&quot;43%&quot;&gt;
-                decide if XP may be appropriate for your project.
-            &lt;/td&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;td align=&quot;middle&quot; width=&quot;10%&quot;&gt;
-                4
-            &lt;/td&gt;
-            &lt;td width=&quot;47%&quot;&gt;
-                Read about the &lt;a class=&quot;elementLinkWithUserText&quot;
-                href=&quot;./../../../xp/guidances/guidelines/xp_environment,3.754748120034442E-307.html&quot;
-                guid=&quot;3.754748120034442E-307&quot;&gt;XP Environment&lt;/a&gt;.
-            &lt;/td&gt;
-            &lt;td width=&quot;43%&quot;&gt;
-                prepare the physical and tool environment for your team.
-            &lt;/td&gt;
-        &lt;/tr&gt;
-        &lt;tr&gt;
-            &lt;td align=&quot;middle&quot; width=&quot;10%&quot;&gt;
-                5
-            &lt;/td&gt;
-            &lt;td width=&quot;47%&quot;&gt;
-                Read the &lt;a class=&quot;elementLink&quot;
-                href=&quot;./../../../xp/guidances/supportingmaterials/getting_started_with_xp,1.2284921351651456E-304.html&quot;
-                guid=&quot;1.2284921351651456E-304&quot;&gt;Getting Started with XP&lt;/a&gt; guidelines.
-            &lt;/td&gt;
-            &lt;td width=&quot;43%&quot;&gt;
-                get suggestions on how to start an XP project.
-            &lt;/td&gt;
-        &lt;/tr&gt;
-    &lt;/tbody&gt;
-&lt;/table&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/metaphor_system_of_names.xmi b/XP/xp/guidances/concepts/metaphor_system_of_names.xmi
deleted file mode 100644
index ebb542b..0000000
--- a/XP/xp/guidances/concepts/metaphor_system_of_names.xmi
+++ /dev/null
@@ -1,40 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-2OU2wQP_WNWX5zzWzx4ANw" name="metaphor_system_of_names,4.884861766532753E-306" guid="-2OU2wQP_WNWX5zzWzx4ANw" changeDate="2006-11-08T16:24:49.021-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__metaphor_(system_of_names)&quot; name=&quot;XE_xp__metaphor_(system_of_names)&quot;&gt;&lt;/a&gt;&lt;a
-id=&quot;XE_metaphor_(system_of_names)__practice_of&quot; name=&quot;XE_metaphor_(system_of_names)__practice_of&quot;&gt;&lt;/a&gt;&lt;a
-id=&quot;XE_engineering_practices__metaphor_(system_of_names)&quot; name=&quot;XE_engineering_practices__metaphor_(system_of_names)&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Description
-&lt;/h3&gt;
-&lt;p&gt;
-    This metaphor is a design overview. It is a way of defining the system using a commonly understandable vocabulary with
-    its associated relationships. It allows the whole team to talk about the structure of the software in a convenient and
-    memorable way. A good metaphor is one that all team members can understand easily, remember, and always keep in the
-    back of their minds. It provides a unifying direction that developers can follow as they build the system a small piece
-    at a time.
-&lt;/p&gt;
-&lt;p&gt;
-    Metaphors are not always easy to find at the start of a project. In that case, teams can simply identify the key
-    objects and their interactions in the system (System of Names). The real metaphor might emerge later on. When everybody
-    on the team can explain quickly the system through its major objects and their interactions, the goal has been reached.
-&lt;/p&gt;
-&lt;p&gt;
-    The iterative nature of XP causes the architecture of our system to evolve over time. The metaphor is not static; it
-    will change and hopefully improve over time as our understanding of the system improves.
-&lt;/p&gt;
-&lt;p&gt;
-    An example of a metaphor would be something like: &quot;It's like a subway system with passengers and stations, tickets and
-    turnstiles, etc.&quot;.
-&lt;/p&gt;
-&lt;h3&gt;
-    Benefits
-&lt;/h3&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        &lt;b&gt;Communication&lt;/b&gt;: customer and developer define a common language they can use to talk about the system.
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Direction&lt;/b&gt;: the metaphor helps guide the developers towards the solution.
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/motivation.xmi b/XP/xp/guidances/concepts/motivation.xmi
deleted file mode 100644
index 4a39f82..0000000
--- a/XP/xp/guidances/concepts/motivation.xmi
+++ /dev/null
@@ -1,55 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-nIpFvBhY9WogqrEQv4NknQ" name="why_xp,1.6390805262958034E-306" guid="-nIpFvBhY9WogqrEQv4NknQ" changeDate="2006-11-08T15:24:24.660-0800" version="1.0.0">
-  <mainDescription>&lt;p&gt;
-    The goal of a software process is to guide the software development organization to:
-&lt;/p&gt;
-&lt;ol&gt;
-    &lt;li&gt;
-        Get the right software done.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Get the software done right.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Get the software done quickly.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Get the software done frugally.
-    &lt;/li&gt;
-&lt;/ol&gt;
-&lt;p&gt;
-    There are many approaches to this problem. Some software processes are high in ceremony. They guide the developers to
-    create many artifacts. They punctuate the project with phases and sign-offs. They release infrequently, sometimes
-    solely upon project completion. There is a time and place for such processes.
-&lt;/p&gt;
-&lt;p&gt;
-    On the other hand, the most important and scarce resource in any project is the time of the developers. High ceremony
-    processes fill that time with work activities that center around artifacts and reviews instead of around the core
-    artifacts of code and tests. For many projects this is an exorbitant expense.
-&lt;/p&gt;
-&lt;p&gt;
-    To manage this expense, many projects need a process that uses a minimum of ceremony and concentrates on the core
-    artifacts. They need a feedback-driven process that delivers working software rapidly in quick releases.
-&lt;/p&gt;
-&lt;p&gt;
-    XP is just such a low ceremony process. It is used by those teams and for those projects where ceremony is of little
-    value, but rapid feedback is of high value. Such projects tend to be small to medium sized - fewer than one or two
-    million lines of code - and involve fewer than one or two dozen developers. They tend to exist in environments of
-    intense business and or technical change. They are, of course, exceedingly common.
-&lt;/p&gt;
-&lt;p&gt;
-    A lack of ceremony does not imply a lack of management. XP places a lot of emphasis on techniques for planning,
-    estimation, and schedule management. Creating, maintaining, and managing a project plan is a very big part of XP.
-&lt;/p&gt;
-&lt;p&gt;
-    A lack of ceremony also does not imply a lack of discipline. XP espouses discipline for every facet of the project.
-    There is discipline for testing, integration, planning, reviewing, and for producing software with a high quality
-    internal structure. The goal is to keep the project moving and the software easy to modify, easy to extend, and easy to
-    develop.
-&lt;/p&gt;
-&lt;p&gt;
-    In short, XP puts the emphasis on ensuring that the team is working on the minimum set of activities and artifacts that
-    will produce the right software, built right, built quickly and built frugally.&lt;br /&gt;
-    &lt;br /&gt;
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/pair_programming.xmi b/XP/xp/guidances/concepts/pair_programming.xmi
deleted file mode 100644
index 61a1f07..0000000
--- a/XP/xp/guidances/concepts/pair_programming.xmi
+++ /dev/null
@@ -1,42 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-n52TyFa7Reb3LOJV1JMpvg" name="pair_programming,3.876855509996079E-307" guid="-n52TyFa7Reb3LOJV1JMpvg" changeDate="2006-11-09T16:16:04.083-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__pair_programming&quot; name=&quot;XE_xp__pair_programming&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_pair_programming__practice_of&quot;
-name=&quot;XE_pair_programming__practice_of&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_engineering_practices__pair_programming&quot;
-name=&quot;XE_engineering_practices__pair_programming&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Description
-&lt;/h3&gt;
-&lt;p&gt;
-    All production software in XP is produced by two programmers, sitting side by side, at the same machine. This practice
-    ensures that all production code is reviewed by at least one other programmer and results in better design, better
-    testing, and better code.
-&lt;/p&gt;
-&lt;p&gt;
-    Research into pair programming shows that pairing produces better code in about the same time as programmers working
-    singly.
-&lt;/p&gt;
-&lt;p&gt;
-    Pairing also serves to communicate knowledge throughout the team. As pairs switch, everyone gets the benefits of
-    everyone's specialized knowledge. Programmers learn, their skills improve, and they become more valuable to the team
-    and to the company.
-&lt;/p&gt;
-&lt;h3&gt;
-    Benefits
-&lt;/h3&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Better design, code and tests.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Application and skill knowledge sharing across team.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;h3&gt;
-    Related Information
-&lt;/h3&gt;
-&lt;p&gt;
-    See the &lt;a class=&quot;elementLinkWithUserText&quot;
-    href=&quot;./../../../xp/guidances/guidelines/pair_programming,3.85153041801319E-307.html&quot; guid=&quot;3.85153041801319E-307&quot;&gt;Pair
-    Programming Guidelines&lt;/a&gt;.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/planning_game.xmi b/XP/xp/guidances/concepts/planning_game.xmi
deleted file mode 100644
index b4d0953..0000000
--- a/XP/xp/guidances/concepts/planning_game.xmi
+++ /dev/null
@@ -1,99 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-CPHs6R59_druVDY6nRjHEw" name="planning_game,2.7371805612676613E-305" guid="-CPHs6R59_druVDY6nRjHEw" changeDate="2006-11-13T15:39:25.183-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__planning_game&quot; name=&quot;XE_xp__planning_game&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_planning_game__practice_of&quot;
-name=&quot;XE_planning_game__practice_of&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_engineering_practices__planning_game&quot;
-name=&quot;XE_engineering_practices__planning_game&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Description
-&lt;/h3&gt;
-&lt;p&gt;
-    The purpose of planning is to ensure that we are working on the most valuable things at all times. As much as we would
-    like to, planning is not about predicting the future. Even the best, most thought out plans need to be continually
-    refined. They require continuous and constant feedback to be useful.
-&lt;/p&gt;
-&lt;p&gt;
-    XP proposes the following planning hierarchy:
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Projects are split into releases that typically last two to three months.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Releases are split into iterations that typically last two to three weeks.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Iterations are planned into tasks that typically last one to two days.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    The XP planning game has two main activities:
-&lt;/p&gt;
-&lt;h4&gt;
-    Release Planning
-&lt;/h4&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Customer presents user stories to the team.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Programmers estimate the user stories.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Customers selects a set of user stories for the next release. The total of the estimates of the selected stories
-        cannot exceed the team's previous release velocity (how much they did the previous release).
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;h4&gt;
-    Iteration Planning
-&lt;/h4&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Customer presents the user stories that will be worked on for the iteration. These stories usually come from the
-        release. Stories not in the release can be selected for the iteration, but the customer will have to push out an
-        existing story of the same size out of the iteration and the release. This is done so the team does not commit to
-        do more work than they have shown they can do in the past.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Programmers break down the stories into engineering tasks.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Programmers sign up and estimate engineering tasks.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Programmers do a sanity check to make sure all these tasks can be done by comparing against what was done the
-        previous iteration.
-    &lt;/li&gt;
-    &lt;li&gt;
-        If there is too much to do, the customer will drop one or more user story from the iteration.
-    &lt;/li&gt;
-    &lt;li&gt;
-        If there is not enough work, the customer can add one or more story to fill the iteration.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;h3&gt;
-    Benefits
-&lt;/h3&gt;
-&lt;ul class=&quot;noindent&quot;&gt;
-    &lt;li&gt;
-        Provides &lt;b&gt;quick and meaningful feedback&lt;/b&gt;.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Provides &lt;b&gt;lots of opportunities&lt;/b&gt; to use that feedback &lt;b&gt;to steer the team to success&lt;/b&gt;.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Provides &lt;b&gt;clear&lt;/b&gt;, long-term &lt;b&gt;strategic&lt;/b&gt; (release plan) &lt;b&gt;and&lt;/b&gt; short-term &lt;b&gt;tactical goals&lt;/b&gt;
-        (iteration plan).
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Allows the team to manage themselves&lt;/b&gt; (task list).
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;h3&gt;
-    Related Information
-&lt;/h3&gt;
-&lt;p&gt;
-    See the &lt;a class=&quot;elementLinkWithUserText&quot;
-    href=&quot;./../../../xp/guidances/guidelines/planning_game,6.7335956461328426E-307.html&quot;
-    guid=&quot;6.7335956461328426E-307&quot;&gt;Planning Game Guidelines&lt;/a&gt;.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/product_quality.xmi b/XP/xp/guidances/concepts/product_quality.xmi
deleted file mode 100644
index 694c958..0000000
--- a/XP/xp/guidances/concepts/product_quality.xmi
+++ /dev/null
@@ -1,169 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-nGaswirSOYturOoUWwGdRw" name="product_quality,3.712584012051524E-306" guid="-nGaswirSOYturOoUWwGdRw" changeDate="2006-11-10T10:10:29.938-0800" version="1.0.0">
-  <mainDescription>&lt;h3&gt;
-    &lt;a id=&quot;Introduction&quot; name=&quot;Introduction&quot;&gt;Introduction&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    If you're serious about producing an excellent product, you face two problems:
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        How do you know when the product is good enough?
-    &lt;/li&gt;
-    &lt;li&gt;
-        If the product is not yet good enough, how do you assure that the stakeholders involved know that?
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;p&gt;
-    The answer to the first question lets you release the product. The answer to the second question helps you avoid
-    releasing a bad product.
-&lt;/p&gt;
-&lt;p&gt;
-    You might think: &quot;I don't want to ship a merely good enough product; I want to ship a &lt;i&gt;great&lt;/i&gt; product!&quot; Let's
-    explore that. What happens when you tell your coworkers, managers, or investors that you have high quality standards
-    and intend to ship a great product? If it's early in the project cycle, they probably nod and smile. Everyone likes
-    quality. However, if it's late in the project cycle, you're under a lot of pressure to complete the project. Creating a
-    great product might require that you perform extensive testing, fix many problems (even small ones), add features, or
-    even scrap and rewrite a large part of the code. You will also have to resolve disputes over different visions of good
-    quality. Greatness is hard work. Perfection is even harder! Eventually, the people who control the project will come to
-    you and say something like: &quot;Perfection would be nice, but we have to be practical. We're running a business. Quality
-    is good, but not quality &lt;i&gt;at any cost&lt;/i&gt;. As you know, all software has bugs.&quot;
-&lt;/p&gt;
-&lt;p&gt;
-    Greatness can be a motivating goal. It appeals to the pride you have in your work. But there are problems with using
-    what amounts to &quot;if quality is good, more quality must be better&quot; to justify the pursuit of excellence. For one thing,
-    making such an argument can portray you as a quality fanatic, rather than a balanced thinker. For another thing, it
-    ignores the cost factor. A BMW is a nice car, but it costs a lot more than a Saturn. A Saturn may not be the ultimate
-    driving experience, but it's nice for the money. In leaving out cost, the &lt;i&gt;&lt;b&gt;more is better&lt;/b&gt;&lt;/i&gt; argument also
-    ignores diminishing returns. The better your product, the harder it gets to justify further improvement. While you
-    labor to gold-plate one aspect of a product, out of necessity you must ignore other aspects of the product or even the
-    potential opportunities presented by another project. The business has to make choices every day about the best use of
-    its resources. There are factors other than quality that must be considered.
-&lt;/p&gt;
-&lt;p&gt;
-    The &lt;i&gt;&lt;b&gt;good enough quality&lt;/b&gt;&lt;/i&gt; concept (GEQ) is, paradoxically, a more effective argument than &lt;i&gt;&lt;b&gt;more is
-    better&lt;/b&gt;&lt;/i&gt;, because it provides a target that is either achievable or not achievable, in which case it becomes a de
-    facto argument for canceling or rechartering the project.
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;GEQParadigms&quot; name=&quot;GEQParadigms&quot;&gt;Paradigms of Good Enough&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    Most businesses practice some form of good enough reasoning about their products. The only ones that don't are those
-    who believe they have achieved perfection, because they lack the imagination and skill to see how their products might
-    be improved.
-&lt;/p&gt;
-&lt;p&gt;
-    Here are some models of &lt;i&gt;&lt;b&gt;good enough&lt;/b&gt;&lt;/i&gt; that have been tried. Some of them are more effective than others,
-    depending on the situation:
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        &lt;b&gt;Not too Bad&lt;/b&gt; &lt;i&gt;(&quot;we're not dead yet&quot;) -&lt;/i&gt; Our quality only has to be good enough so we can continue to
-        stay in business. Make it good enough so that we aren't successfully sued.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Positive Infallibility&lt;/b&gt; &lt;i&gt;(&quot;anything we do is good&quot;) -&lt;/i&gt; Our organization is the best in the world.
-        Because we're so good, anything we do is automatically good. Think about success. Don't think about failure because
-        &quot;negative&quot; thinking makes for poor quality.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Righteous Exhaustion&lt;/b&gt; &lt;i&gt;(&quot;perfection or bust&quot;) -&lt;/i&gt; No product is good enough; it's effort that counts. And
-        only our complete exhaustion will be a good enough level of effort. Business issues are not our concern. We will do
-        everything we possibly can to make it perfect. Since we'll never be finished improving, someone will have to come
-        in and pry it from our fingers if they want it. Then they will bear the blame for any quality problems, not
-        us.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Customer is Always Right&lt;/b&gt; &lt;i&gt;(&quot;customers seem to like it&quot;) -&lt;/i&gt; If customers like it, it must be good
-        enough. Of course, you can't please everybody all the time. And if a current or potential customer doesn't like the
-        product, it's up to them to let us know. We can't read their minds.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Defined Process&lt;/b&gt; &lt;i&gt;(&quot;we follow a Good Process&quot;) -&lt;/i&gt; Quality is the result of the process we use to build
-        the product. We have defined our process and we think it's a good process. Therefore, as long as we follow the
-        process, a good enough product will inevitably result.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Static Requirements&lt;/b&gt; &lt;i&gt;(&quot;we satisfy the Requirements&quot;) -&lt;/i&gt; We have defined quality in terms of objective,
-        quantifiable, noncontroversial goals. If we meet those goals, we have a good enough product, no matter what other
-        subjective, non-quantifiable, controversial goals might be suggested.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Accountability&lt;/b&gt; &lt;i&gt;(&quot;we fulfill our promises&quot;) -&lt;/i&gt; Quality is defined by contract. We promise to do certain
-        things and achieve certain goals. If we fulfill our contract, that's good enough.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Advocacy&lt;/b&gt; &lt;i&gt;(&quot;we make every reasonable effort&quot;) -&lt;/i&gt; We advocate excellence. Throughout the project, we
-        look for ways to prevent problems, and to find and fix the ones we couldn't prevent. If we work faithfully toward
-        excellence, that will be good enough.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-    &lt;li&gt;
-        &lt;b&gt;Dynamic Tradeoff&lt;/b&gt; &lt;i&gt;(&quot;we weigh many factors&quot;) -&lt;/i&gt; With respect to our mission and the situation at hand, a
-        product is good enough when it has sufficient benefits, no critical problems, its benefits sufficiently outweigh
-        its non-critical problems, and it would cause more harm than good to continue improving it.&lt;br /&gt;
-        &lt;br /&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;IsHighQualityExpensive&quot; name=&quot;IsHighQualityExpensive&quot;&gt;Is High Quality Necessarily More Expensive?&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    Depending on a lot of factors, such as process, skill, technology, tools, environment, and culture, you may be able to
-    produce a much higher quality product for the same cost. A more testable and maintainable product will cost less to
-    improve and other costs are specifically associated with poor quality, such as support costs and costs to the customer.
-&lt;/p&gt;
-&lt;p&gt;
-    The cost of quality is a complex issue and it's difficult to make broad generalizations. However, you can say with
-    certainty that you can always spend more time on much better tests, much more error handling, and more fixing or
-    rewriting of every part of the product. No matter how good you are, that costs something. And if you can't think of
-    more improvements to make, it's more likely that you've reached the upper limit of your imagination, not of quality.
-&lt;/p&gt;
-&lt;p&gt;
-    In the software industry GEQ is inspired more as a response to one particular cost than any other: the cost of not
-    releasing the product &lt;i&gt;soon enough&lt;/i&gt;. The specter of the market window, or the external deadline, imposes penalties
-    upon us if we can't meet the challenge. That's why the ends of projects are so often characterized by frenzied triage.
-    If you want to know what an organization really believes is good enough, and how well prepared they are for it, witness
-    the last three days of any six-month software project. See what happens when a new problem is reported on the last day.
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;Quantification&quot; name=&quot;Quantification&quot;&gt;Wouldn't Quantification Help?&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    It can be tempting to reduce quality to a number, then set a numerical threshold that represents good enough quality.
-    This is a problem, because you can only measure factors that &lt;i&gt;relate&lt;/i&gt; to quality. You can't measure quality
-    itself. This is partly because the word &quot;quality&quot; is just a label for a relationship between a person and a thing.
-    &quot;This product is high in quality&quot; is just another way of saying &quot;Somebody values this product&quot;. It's a statement about
-    the product, but also a statement about people and the surrounding context. Even if the product stays the same, people
-    and situations change, so there can be no single, static, &lt;i&gt;true&lt;/i&gt; measure of quality.
-&lt;/p&gt;
-&lt;p&gt;
-    There are many measures you might use to get a sense of quality, even if you can't measure it completely and
-    objectively. Even so, the question of what quality is good enough requires sophisticated judgment. You can't escape
-    from the fact that, in the end, people have to think it through and make a judgment. For a simple product, that
-    judgment might be easy. For a complex, high-stakes product, it's very difficult.
-&lt;/p&gt;
-&lt;h3&gt;
-    &lt;a id=&quot;FurtherInfo&quot; name=&quot;FurtherInfo&quot;&gt;Further Information&lt;/a&gt;
-&lt;/h3&gt;
-&lt;p&gt;
-    To assist you with evaluating product quality, the following types of information are available for most of the
-    artifacts included in the Unified Process:
-&lt;/p&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Artifact Guidelines and Checkpoints: information on how to develop, evaluate, and use the artifact.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Templates: &quot;models&quot; or prototypes of the artifact, providing structure and guidance for content.&lt;br /&gt;
-    &lt;/li&gt;
-&lt;/ul&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/refactoring_xp_programming.xmi b/XP/xp/guidances/concepts/refactoring_xp_programming.xmi
deleted file mode 100644
index 34d0dbb..0000000
--- a/XP/xp/guidances/concepts/refactoring_xp_programming.xmi
+++ /dev/null
@@ -1,75 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" epf:version="1.0.0" xmi:id="-U8NScY6mORb4XPcNZ_mrEA" name="refactoring_xp_programming,1.4410217108363206E-306" guid="-U8NScY6mORb4XPcNZ_mrEA" changeDate="2006-11-09T16:20:46.023-0800" version="1.0.0">
-  <mainDescription>&lt;a id=&quot;XE_xp__refactoring&quot; name=&quot;XE_xp__refactoring&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_refactoring__practice_of&quot;
-name=&quot;XE_refactoring__practice_of&quot;&gt;&lt;/a&gt;&lt;a id=&quot;XE_engineering_practices__refactoring&quot;
-name=&quot;XE_engineering_practices__refactoring&quot;&gt;&lt;/a&gt; 
-&lt;h3&gt;
-    Description
-&lt;/h3&gt;
-&lt;p&gt;
-    Refactoring is the practice of improving the design of a system without changing its behavior. Refactoring is a
-    critical practice and skill in iterative development. The programmer is either adding a new feature or refactoring. XP
-    programmers consciously choose between refactoring and adding new functionality on a minute-by-minute basis. Some
-    refactorings are trivial, such as renaming or moving things. Other refactorings allow you to exchange procedural logic
-    with polymorphism, and still larger refactorings exist to introduce design patterns.
-&lt;/p&gt;
-&lt;p&gt;
-    While processes like Extreme Programming rely on refactoring to let the design emerge, the usefulness of refactoring
-    extends beyond the Agile Methodologies. As feature requests and bug fixes require changes to a system, refactoring
-    techniques allow the programmers to maintain a good design. Refactoring can also be used to improve the design of an
-    existing system.
-&lt;/p&gt;
-&lt;p&gt;
-    Refactoring is not new. Developers have been refactoring for years, though only recently have people started to catalog
-    refactorings. Refactoring has become such an important part of development that professional-level Integrated
-    Development Environments (IDEs) either include built-in tools or have plug-ins to provide refactoring support.
-&lt;/p&gt;
-&lt;p&gt;
-    If your system isn't being refactored as it is modified, your design deteriorates; methods become longer, classes take
-    on more responsibility, more code gets cut and pasted around your system, previously cut-and-pasted code has to be
-    modified in several places.
-&lt;/p&gt;
-&lt;p&gt;
-    If your system becomes brittle and inflexible, your developers will have to spend more time and money to add features
-    or fix bugs. As the design continues to deteriorate, fixing one bug creates two more, or the cost of adding a new
-    feature out weighs the benefit of having it because so much of the system has to be modified. There are many analogies
-    to describe this battle against entropy; from cleaning as you go to design debt.
-&lt;/p&gt;
-&lt;p&gt;
-    Knowing the refactorings isn't enough. Developers must be able to identify problem areas of the program design (often
-    referred to as &quot;smells&quot;). These are the places where refactoring can be used to improve the design of the code. Design
-    skill and experience are needed to recognize bad code smells.
-&lt;/p&gt;
-&lt;p&gt;
-    Automated tests provide a safety net when making changes. The automated tests report when the functionality of the
-    system changes. Make a structural change to the software; see that the tests still pass. You can confidently refactor.
-&lt;/p&gt;
-&lt;p&gt;
-    Where do all these tests come from? In XP, they are developed using &lt;a class=&quot;elementLinkWithUserText&quot;
-    href=&quot;./../../../xp/guidances/concepts/test_driven_development,1.620567348185129E-306.html&quot;
-    guid=&quot;1.620567348185129E-306&quot;&gt;Test-Driven Development&lt;/a&gt;. It is possible to refactor without tests, but you run the
-    risk of unknowingly introducing bugs or breaking existing functionality.
-&lt;/p&gt;
-&lt;h3&gt;
-    Benefits
-&lt;/h3&gt;
-&lt;ul&gt;
-    &lt;li&gt;
-        Allows the design to emerge over time.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Keeps the design from rotting.
-    &lt;/li&gt;
-    &lt;li&gt;
-        Reduces cost of change.
-    &lt;/li&gt;
-&lt;/ul&gt;
-&lt;h3&gt;
-    Related Information
-&lt;/h3&gt;
-&lt;p&gt;
-    &amp;nbsp;See the &lt;a class=&quot;elementLinkWithUserText&quot;
-    href=&quot;./../../../xp/guidances/guidelines/refactoring,8.137126904637637E-306.html&quot;
-    guid=&quot;8.137126904637637E-306&quot;&gt;Refactoring Guidelines&lt;/a&gt;.
-&lt;/p&gt;</mainDescription>
-</org.eclipse.epf.uma:ContentDescription>
diff --git a/XP/xp/guidances/concepts/resources/dvltst-img1.gif b/XP/xp/guidances/concepts/resources/dvltst-img1.gif
deleted file mode 100644
index 8082009..0000000
--- a/XP/xp/guidances/concepts/resources/dvltst-img1.gif
+++ /dev/null
Binary files differ
diff --git a/XP/xp/guidances/concepts/resources/dvltst-img2.gif b/XP/xp/guidances/concepts/resources/dvltst-img2.gif
deleted file mode 100644
index 381f405..0000000
--- a/XP/xp/guidances/concepts/resources/dvltst-img2.gif
+++ /dev/null
Binary files differ
diff --git