| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-KMs0edThk3xs9MAS7GAxng" |
| name="delayed_assignment,_rlrykJcbEd2sTqxclDgvog" guid="-KMs0edThk3xs9MAS7GAxng" |
| changeDate="2008-10-11T02:16:37.125-0700" version="7.2.0"> |
| <mainDescription><p>
 |
| Delayed assignment is also sometimes referred to as "late" assignment.
 |
| </p>
 |
| <p>
 |
| There are two common types of delayed assignment, delayed role assignment and delayed category assignment.&nbsp;
 |
| </p>
 |
| <h3>
 |
| Delayed role assignment
 |
| </h3>
 |
| <p>
 |
| Roles are assigned to tasks as the performing role and to work products as the role that is responsible for the work
 |
| product.
 |
| </p>
 |
| <p>
 |
| Delayed role assignment is where the assignment of a role to a task or work product is not done where the task or the
 |
| work product is defined. The result is that the roles can be swapped out without changing the tasks or the work
 |
| products. This supports the customization of the method to support a specific organization or set of governance
 |
| policies.
 |
| </p>
 |
| <p>
 |
| Specifically, when delayed role assignment is used:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The base definition of a task should not refer to specific performing role(s)
 |
| </li>
 |
| <li>
 |
| The base definition of a work product should not refer to specific responsible role
 |
| </li>
 |
| <li>
 |
| The base definition of a role should not refer to being responsible for specific work product(s) and/or refer to
 |
| specific performed task(s).
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Delayed role assignment affects both the structuring of the method (relationships between elements) and the detailing
 |
| of method elements (hyperlinks in the text).&nbsp;Specifically, when delayed role assignment is used:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| (structure) Performing roles are assigned separate from the base task definition.
 |
| </li>
 |
| <li>
 |
| (structure) Responsible roles are assigned separate from the base role definition.
 |
| </li>
 |
| <li>
 |
| (detail) Work products are written without referencing a specific responsible role.
 |
| </li>
 |
| <li>
 |
| (detail) Tasks are written without referencing specific performing role(s).&nbsp;&nbsp;
 |
| </li>
 |
| <li>
 |
| (detail) Roles are written without referencing specific tasks and/or work products.
 |
| </li>
 |
| <li>
 |
| (detail) Instead of referring to a specific role, you can refer to the skills or competencies needed.&nbsp;If a
 |
| role must be mentioned, use a generic role name (in lower case) that is easily understood.
 |
| </li>
 |
| </ul>
 |
| <h3>
 |
| Delayed standard category assignment
 |
| </h3>
 |
| <p>
 |
| Delayed standard category assignment is an approach where method elements are defined without referencing a specific
 |
| standard category in order to make it easier to define alternate categorization schemes (i.e., different domains,
 |
| disciplines, etc).
 |
| </p>
 |
| <p>
 |
| When&nbsp;delayed standard category assignment&nbsp;is used, assignment of elements to standard categories is not done
 |
| in the base method element definition.&nbsp;The assignments can be defined in sub-packages in the same plug-in as the
 |
| element or in a completely separate plug-in.&nbsp;
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
