| <?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="_0LCr8BUFEdqrUt4zetC1gg" guid="_0LCr8BUFEdqrUt4zetC1gg" changeDate="2006-04-13T14:26:20.262-0700"> |
| <mainDescription><p> |
| Method Plugin conceptually represents a unit for configuration, modularization, extension, packaging, and deployment of |
| method content and processes.&nbsp; A Process Engineer shall design&nbsp;Plugins and allocate content to these Plugins |
| with requirements for extensibility, modularity, reuse, and maintainability in mind. |
| </p> |
| <p> |
| Plug-ins can directly contribute new content, replace existing content, or to cross-reference to any Content Element or |
| Process within another Plug-in that it extends.&nbsp; Similar to UML 2.0's 'package merge' mechanism transformation |
| interpretations, interpreting these Method Plug-in mechanisms results into new extended Method Content and |
| Processes.&nbsp; For example, a might contain additional steps for Tasks, new Work Products extensions to existing |
| Roles to be responsible for the new Work Products, additional relationships of existing Content Elements to new |
| specific Guidance elements (such as Guidelines, White Papers, Checklists), additional Activities for a Delivery |
| Process, new Capability Patterns, etc.&nbsp; A Method Plug-in defines these extension using Variability Element |
| relationships and interpretation of these leads to new Method Content and Processes. |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |