| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\base_concepts\guidances\concepts\method_plugin.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: method_plugin.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_0KeEMBUFEdqrUt4zetC1gg CRC: 2385089299 -->Method Plugin<!-- END:presentationName,_0KeEMBUFEdqrUt4zetC1gg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_0KeEMBUFEdqrUt4zetC1gg CRC: 2594956519 -->A Method Plugin represents a physical container for Method Packages. It defines a largest granularity level for the modularization and organization of method content and processes.<!-- END:briefDescription,_0KeEMBUFEdqrUt4zetC1gg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,_0LCr8BUFEdqrUt4zetC1gg CRC: 1742179216 --><p> |
| Method Plugin conceptually represents a unit for configuration, modularization, extension, packaging, and deployment of |
| method content and processes. A Process Engineer shall design 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. 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. 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. A Method Plug-in defines these extension using Variability Element |
| relationships and interpretation of these leads to new Method Content and Processes. |
| </p><!-- END:mainDescription,_0LCr8BUFEdqrUt4zetC1gg --> |
| </body> |
| </html> |
