Load specification

Type EObject

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.

Type EngineeredElement

Engineer manager(s).

Type Alignment
Homogenous true
Strict containment true

Aims to which this alignable aligns. E.g. a module level principle may align to organization pirinciples.

Type Objective

All objectives for this endeavor - a union of objectives and linkedObjectives.

Type Property
Homogenous true

Map entries

Type Engineer

Engineer responsible for completion of this endeavor. For a simple issue it would be an engineer working on the issue, for other endeavors the assignee’s may not actually work on issues, but rather coordinate. E.g. increment assignee responsibility would be similar to those of a scrum master.

Type EBoolean

Indicates that this capability is available and issues which require it are workable, unless they have other unavailable requirements.

Type EDouble

Number representing benefit of this endeavor. Can be explicitly provided or derived.

Type IssueCategory
Homogenous true

Issue category.

Type Issue
Homogenous true

Issues can be infinitely nested to form a Work Breakdown Structure.

Type Feature

Issue can contribute to zero or more features.

Type EDouble

Monetary cost for this issue, e.g. cost of materials.

Type EString

Description in HTML.

Type EObject

Element documentation, e.g. Markdown documentation.

Type Duration

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

Type EDouble

Effort for this issue.

end

Type Temporal
Homogenous true
Strict containment true

Period end.

Type Increment

Increment for which this issue is directly scheduled. Issue can be scheduled for an increment directly or indirectly via features and releases. Release increment can be different from issue incrmenent. E.g. issue can be scheduled for May, but its release might be scheduled for July.

Type Objective

Objectives defined under Engineer for this endeavor.

Type EString

Element name.

Type Note
Homogenous true

Issue notes are used for discussion and to record progress, remaining effort, and issue status if it is not set at the issue level.

Type Objective
Homogenous true

Assignee’s objectives for this endeavor.

Type EString

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

Type IssuePriority

Issue status.

Type Release

Engineered capability can be planned for zero or more releases.

Type Representation
Homogenous true

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

Type Capability

Capabilities required to start working on an issue.

Type NamedElement

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

Type Document
Homogenous true

Sections for model element documentation.

Type IssueSeverity

Issue status.

Type Temporal
Homogenous true
Strict containment true

Period start.

Type IssueStatus

Issue status.

Type TableOfContents
Homogenous true
Strict containment true

Table of contents configuration.

uri

Type EString

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.

Type EString

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