Implementation Event
Welcome » All things and their becoming » Techno Order (scope) » Model element » Event » Implementation Event


An Implementation Event is an Event, denoting a state change at the Implementation and Migration Extension.

Further clarification: An Implementation Event is a behaviour element that denotes a state change related to implementation or migration.

Work Packages may be triggered or interrupted by an Implementation Event. Also, work packages may raise events that trigger other behaviour. Unlike a Work Package, an event is instantaneous: it does not have duration.

An Implementation Event may have a time attribute that denotes the moment or moments at which the event happens.

Implementation Events access Deliverables to fulfil project objectives.

An Implementation Event may trigger or be triggered (raised) by a Work Package or a Plateau. An Implementation Event may access a Deliverable and may be composed of other Implementation Events.

An Implementation Event may be associated with any core element; e.g., to indicate a lifecycle state change.

The name of an Implementation Event should preferably be a verb in the perfect tense.

Category: Implementation and Migration Extension and Behaviour aspect

Examples: "Release to production", "Project initiation phase completed".

Sources:

Questions, answers and comments

Add a New Comment

This class in the classification of its order

The (ontological) order of Implementation Event is the Techno Order.
Code: —