blob: 40bb5c2681a09d247939d3d273807db06fa3a262 [file] [log] [blame]
<?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\process_contribution.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: process_contribution.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_NYASQBtqEdqSLrJ4Ij2LVA CRC: 532834662 -->Process Contribution<!-- END:presentationName,_NYASQBtqEdqSLrJ4Ij2LVA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_NYASQBtqEdqSLrJ4Ij2LVA CRC: 3279084604 -->A Process Contribution is a special Process that externally defines additions and changes to an existing Process without directly modifying it.<!-- END:briefDescription,_NYASQBtqEdqSLrJ4Ij2LVA -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,-x11qt8TVnuIKeMC69UP1TQ CRC: 1071435359 --><p>
A Process Contribution is a special Process that externally defines additions and changes to an existing Process
without directly modifying the existing Process. It achieves this by describing these additions and changes in a
separate Process structure. This structures' elements relate to the other Process's elements using "Contributes" and
"Replace" specializations. Process Contributions are normally packaged with Method Plug-ins that extend existing Method
Plug-in with new capabilities.
</p>
<p>
A Process Contribution is a kind of "process plug-in" that plugs additional breakdown structures into an existing
Process and therefore updates it afterwards with new or changed capabilities. For example, the J2EE Plug-in plugs into
the technology independent main Plug-in. It may update the generic Delivery Processes defined in that Plug-in with J2EE
specific Activities. A respective ".NET Plug-in" could define similar updates relevant for that technology platform. A
process practitioner could then apply the chosen Plug-in, thereby generating a technology specific Process, but keeping
maintenance of his/her Processes minimal, because technology specific parts are kept separate and will be applied on
demand only.
</p><!-- END:mainDescription,-x11qt8TVnuIKeMC69UP1TQ -->
</body>
</html>