| <?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="-FD4UbInbyzlaGxB9oPHdcg" name="composite_role,_P9gp0BtHEdqSLrJ4Ij2LVA" guid="-FD4UbInbyzlaGxB9oPHdcg" changeDate="2005-09-01T17:19:52.101-0700"> |
| <mainDescription><p> |
| A Composite Role is a grouping of Roles that can be used in an Activity or Process to reduce the number of Roles. A |
| Composite Role is thus for the Tasks and Work Products defined for the Roles it refers to. A typical use of this |
| construct occurs within a Process designed for a small team in which multiple standard Roles from the Method Content |
| are assigned to a single resource. By using a Composite Role the Process suggests a typical clustering of Roles to |
| Resources.<br /> |
| </p> |
| <p> |
| A simple example is a Composite Role named <em><strong>Developer</strong></em> that groups together the |
| <em><strong>Implementer</strong></em> and <em><strong>Tester</strong></em> Roles. Now, every time one of the Roles |
| Implementer or Tester would normally be used within the breakdown structure, Developer is used instead. Hence, if a |
| Task Descriptor is added to the Process, that has Implementer or Tester as the primary performer, this Role would be |
| automatically be substituted by&nbsp;the Composite Role instance Developer that links back to either Tester or |
| Implementer (or both if both were listed as the Task performers). |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |