Load specification

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.

Allocations of engineer’s capacity to work on this engineered element issues for a particular endeavor and issue category.

Map entries

Engineer’s capacity for a particular endeavor

Description in HTML.

Sub-forums.

Element documentation, e.g. Markdown documentation.

Engineer’s domains

Positive period duration in ISO-8601 durations format. E.g. P1M for one month or P20D for 20 days.

Period end.

Members of this organization.

Experts have expertise with the element, but no authority. E.g. they can help others with using the element, but cannot make changes in the element without owners’ approval.

Operations exported by this connection target, e.g. module operations exported by its interface.

A persona may extend another persona. E.g. “Moderator” discussion forum persona extends “User” persona, which may in turn extend “Visitor” persona. This persona inherits goals for the extended personas.

Persona goals are used to elicit and align endeavors. E.g. new product features.

Increments are defined under engineer/organization.

Issue categories are defined under engineer/organization.

Issue priorities are defined under engineer/organization.

Issue severities are defined under engineer/organization.

Issue statuses are defined under engineer/organization.

Issues (work items) for this element.

Engineer manager(s).

Modules (products) are defined under engineer or organization.

Element name.

Engineer’s objectives for a particular endeavor

Element owners have both expertise and authority over the element.

Element path is typically used as a key (EKey) in a containing collection.

Personas which this engineer/organization builds products for.

Principles associated with this element to support decision making.

Default engineer rate. Can be customized in capacity.

Pluggable representations of a model element, e.g. a component diagram for modules.

Engineers which represent this persona. E.g. in a hierarchical organization some units or engineers may build products for internal customers - other units or engineers. In this case some of those internal customers act as persona representatives and work with the persona owner to identify persona goals and product features to address those goals.

Resources associated with the element, e.g. documentation.

Sections for model element documentation.

Engineer may perform shared activities (services) which can be parts of persona journeys.

Period start.

Table of contents configuration.

Discussion topics in this forum.

If element’s URI is not set then its default value is derived from the container URI and containment reference. This is a logical URI and it can be used for cross-referencing of elements in a resource-independent fashion.

Optional unique identifier for this model element. For root objects UUID is used to compute URI, if the URI is not set.