Interface Activity

All Superinterfaces:
BreakdownElement, Classifier, DescribableElement, Element, org.eclipse.emf.ecore.EObject, FulfillableElement, MethodElement, NamedElement, org.eclipse.emf.common.notify.Notifier, PackageableElement, ProcessElement, Type, VariabilityElement, WorkBreakdownElement, WorkDefinition
All Known Subinterfaces:
CapabilityPattern, DeliveryProcess, Iteration, Phase, Process, ProcessPlanningTemplate
All Known Implementing Classes:
ActivityImpl, CapabilityPatternImpl, DeliveryProcessImpl, IterationImpl, PhaseImpl, ProcessImpl, ProcessPlanningTemplateImpl

public interface Activity
extends WorkBreakdownElement, FulfillableElement, VariabilityElement, WorkDefinition
A representation of the model object 'Activity'. An Activity is a Work Breakdown Element and Work Definition which supports the nesting and logical grouping of related Breakdown Elements forming breakdown structures. Although Activity is a concrete meta-class, other classes which represent breakdown structures derive from it; such as Phase, Iteration, Delivery Process, or Capability Pattern. Activity represents a grouping element for other Breakdown Elements such as Activities, Descriptors, Milestones, etc. It is not per-se a 'high-level' grouping of only work as in other meta-models, but groups any kind of Breakdown Elements. For example, one can define valid Activities that group only Work Products Descriptors without any matching Task Descriptors. Activities also inherit all properties from Work Breakdown Element and indirectly from Process Element; i.e. Activity is ready to have a full content description attached to it. This definition of Activity extends Activity introduced in the package Breakdown with new capabilities and is the basis for the definition of the class Process. Extends Activity with an association to Roadmap. This definition of Activity also participates in the extension of the Discipline category. Activity in the package Method Plugin inherits from Variability Element to extend Activity with new capabilities for variability. Activity inherits the semantics of Variability Element which provides key mechanism to enable dynamic binding of Capability Patterns in Processes as well as Process Contributions. Variability is used in the following way for Activities: - Extend: To apply a Capability Pattern to a process one would create an Activity which extends the pattern's top-level activity. Through extension the extending Activity inherits the patterns Breakdown Elements. - Replace: To replace an Activity of an applied Capability Pattern or an existing process for which one develops a Process Contribution (or a combination of both) one would create an Activity and specify the replace variability specialization between them. - Contribute: To contribute new Breakdown Elements to an existing Activity one would define an Activity with Breakdown Elements that relates via the Contributes Variability Specialization to this existing Activity. The contributing Activity's Breakdown Elements will be added to the contributed Activity.

The following features are supported:

See Also: