| <?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\activity.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: activity.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,3.132140065969088E-305 CRC: 1426221836 -->Activity<!-- END:presentationName,3.132140065969088E-305 --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,3.132140065969088E-305 CRC: 3400579481 -->An Activity supports the nesting and logical grouping of related process elements also referred to as Breakdown Elements (e.g. other Activities or Task Descriptors). The concepts Phase, Iteration, Delivery Process, and Capability Pattern are defined as special Activities.<!-- END:briefDescription,3.132140065969088E-305 --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,_zaqEMNnmEdmO6L4XMImrsA CRC: 911979929 --><p> |
| Activities are the fundamental concept for defining processes. Activities define the breakdown as well as flow of |
| work. In other words, Activities can be nested into each other defining a breakdown structure of work or they can |
| define predecessor relationships to other Activities defining a flow presented in Activity diagrams. Activities |
| can also contain references to Task, Roles, and Work Products called <a class="elementLink" |
| href="./../../../base_concepts/guidances/concepts/descriptor,_5V9HEBUEEdqrUt4zetC1gg.html" |
| guid="_5V9HEBUEEdqrUt4zetC1gg">Descriptor</a>. Activities as well as Descriptors relate to timelines by allowing |
| their instances to define start and/or end dates. Further, they specify information relevant to the instantiation |
| of work in project such as if an Activity shall be performed several times and if so if they can be performed in |
| parallel (hasMultipleOccurrences attribute) or one after other (isRepeatable attribute). Activities and Task |
| Descriptors can also be event driven or describing ongoing work that does not have a fixed start and end time. |
| </p> |
| <p> |
| UMA defines several special Activities that allow expressing processes with terms many users are familiar |
| with. For example, Phase or Iteration are just special Activities for which specific attribute values have been |
| set with predefined values. A process such as a <a class="elementLink" |
| href="./../../../base_concepts/guidances/concepts/capability_pattern,1.7072348895114264E-305.html" |
| guid="1.7072348895114264E-305">Capability Pattern</a> or <a class="elementLink" |
| href="./../../../base_concepts/guidances/concepts/delivery_process,_EhgqwO8MEdmKSqa_gSYthg.html" |
| guid="_EhgqwO8MEdmKSqa_gSYthg">Delivery Process</a> is also nothing else than just a special Activity that |
| contains additional documentation on why and how to use the process. Hence, because Activities could be nested into |
| each other, so can processes. |
| </p><!-- END:mainDescription,_zaqEMNnmEdmO6L4XMImrsA --> |
| </body> |
| </html> |
