| <?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\capability_pattern.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: capability_pattern.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,1.7072348895114264E-305 CRC: 2925390144 -->Capability Pattern<!-- END:presentationName,1.7072348895114264E-305 --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,1.7072348895114264E-305 CRC: 2643350980 -->A Capability Pattern is a special Process that describes a reusable cluster of Activities in common process areas that produces a result of observable value.<!-- END:briefDescription,1.7072348895114264E-305 --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,_zag6RdnmEdmO6L4XMImrsA CRC: 3921446002 --><a id="XE_WORKFLOW__KEY_CONCEPTS" name="XE_workflow__key_concepts"></a> |
| <p> |
| Capabilities Patterns express and communicate process knowledge for a key area of interest such as a Discipline |
| or a practice and can be directly used by process practitioners to guide their work. They are also used as |
| building blocks to assemble <a class="elementLinkWithUserText" |
| href="./../../../base_concepts/guidances/concepts/delivery_process,_EhgqwO8MEdmKSqa_gSYthg.html" |
| guid="_EhgqwO8MEdmKSqa_gSYthg">Delivery Processes</a> or larger Capability Patterns ensuring optimal reuse and |
| application of the key practices they express. |
| </p> |
| <p> |
| Examples for Capability Pattern could be 'use case-based requirements management', 'use case analysis', or 'unit |
| testing'. Typically but not necessarily, Capability Patterns have the scope of one Discipline providing a breakdown of |
| reusable complex Activities, relationships to the Roles which perform Tasks within these Activities, as well as to the |
| Work Products that are used and produced. Generally, a Capability Pattern does not relate to any specific phase |
| or iteration of a development lifecycle, and should not imply any. In other words, a pattern should be designed |
| in a way that it is applicable anywhere in a Delivery Process. This enables its Activities to be flexibly |
| assigned to whatever phases there are in the Delivery Process to which it is being applied. An exception to this |
| would be capability patterns that are intended to provide a template for quickly creating an iteration or portion of an |
| iteration for a particular phase in a Delivery Process.<br /> |
| <br /> |
| Key applications or areas of reuse for Capability Patterns are: |
| </p> |
| <ul> |
| <li> |
| To serve as building blocks for assembling Delivery Processes or larger Capability Patterns. Normally |
| developing a Delivery Process is not done from scratch but by systematically applying and binding patterns. |
| </li> |
| <li> |
| To support direct execution in a development project that does not work following a well-defined process, but works |
| based on loosely connected process fragments of practices in a flexible manner (for example, Agile Development). |
| </li> |
| <li> |
| To support process education by describing knowledge for a key area such as practices on how to perform the work |
| for a Discipline (for example, Requirements Management), for a specific development technique (aspect-oriented |
| development), or a specific technical area (for example, relational database design), which is used for education |
| and teaching.<br /> |
| </li> |
| </ul> |
| <p> |
| The workflow of a Capability Pattern is usually represented using the UML Activity Diagram notation. |
| </p> |
| <p align="center"> |
| <img alt="Sample activity diagram representing the workflow of a Capability Pattern" src="resources/wf_req.gif" /> |
| </p> |
| <p> |
| <font size="1">Sample activity diagram representing the workflow of a Capability Pattern</font>.<br /> |
| </p> |
| <br /> |
| <br /><!-- END:mainDescription,_zag6RdnmEdmO6L4XMImrsA --> |
| </body> |
| </html> |
