References

Participant(s) accountable for the element, i.e. ultimately answerable for the correct and thorough completion of an activity or artifact. Accountable must sign off (approve) work that responsible provides.

If this reference is not set then EObjectActionProvider creates a new Action using AppFactory in newAction() method. If this reference is set and is Action then a copy of the action is created and returned. Otherwise the reference value it is adapted to ActionProvider which is used to create an action. This allows to merge actions and chain action generation. E.g. generate Ecore model documentation and merge it into the Engineering documentation.

Artifact responsibility assignments if different from the flow element responsibility assignments. E.g. a person responsible for an activity may delegate responsibility for some artifact to another participant. In this case another participant becomes responsible and the participant responsible for the activity becomes accounable for the artifact.

Calls to other flow elements.

Participant(s) whose opinions are sought, typically subject-matter experts.

Element documentation. Documentation elements are adapted to SupplierFactory<InputStream> during generation. Exec content classes such as Markdown and Interpolator can be used as documentation elements.

Elements can extend other elements and inherit their configuration - set attributes and references. For top-level packages inheritance shall be explicitly set using superPackages reference. For nested packages and other package elements extends is derived from containing packages. For nested packages super-packages derived from containment precede explicitly specified super-packages, i.e. the explicitly specified super-packages (mix-ins) can override configuration inherited via containment.

Derived reference - known elements extending this element. Known means elements in the same resource set.

Participant(s) who are kept up-to-date on progress and with whom there is one-way communication.

Input artifacts for this flow element. E.g. artifacts required to start working on an activity.

Transitions which have this flow element as their target.

Calls which have this flow element as their target.

Markers pointing to where this model element was loaded from - location, line and column numbers. Multiple markers are supported for situations when a single model element is loaded from multiple locations, e.g. a row in an Excel document or a database and then pom.xml and readme.md is a source repository. Another possiblity is an element being created from a prototype and then loaded - in this case the object will inherit markers from its prototype and will have a marker point to the location where it was loaded from. Markers are listed in the reverse order, i.e. the prototype marker would be after the load marker in the list.

Output artifacts of this flow element.

Outbound transitions to other flow elements.

Participants of this flow element, e.g. people working on an activity.

Properties can be used to customize the documentation generation process, e.g. provide configuration for generation of representation diagram elements.

This reference is set by create() method and points to a package element which created and configured this element.

Mapping of representation names to values - Diagrams which serve as templates for generating diagram content from the package element.

Resources used by participants of this flow element. E.g. tools used to complete an activity.

Participant(s) responsible for the element, e.g. for completion of an activity.

Derived opposite to Service target.