Transactional Service Model

Overview

The information structures required to represent planned Tasks and references at design and runtime are non-trivial. For this reason, an abstract service is defined, with a transactional interface that converts calls into correct underlying information structures. The following UML diagram illustrates the services.

PROC task planning.service
Figure 1. proc.task_planning.service package

Definition Interface

TBC:

Execution-time Interface

TBC:

Class Descriptions

I_WORK_PLAN_DEFINITION Interface

  • Definition

Interface

I_WORK_PLAN_DEFINITION

Description

Task planning API that converts transactional calls to correct Task Planning information structures at Work Plan level.

Functions

Signature

Meaning

0..1

plans (): List<UID_BASED_ID>

List of Task Plan ids for this Work Plan.

0..1

plan (
a_task_plan_id: UID_BASED_ID[1]
): List<I_TASK_PLAN_DEFINITION>

Obtain a Task Plan definition API interface.

I_TASK_PLAN_MATERIALISED Interface

  • Definition

Interface

I_TASK_PLAN_MATERIALISED

Description

Task planning API for materialised Task Plan level.

Functions

Signature

Meaning

0..1

materialise

0..1

activate

0..1

terminate

I_WORK_PLAN_DEFINITION Interface

  • Definition

Interface

I_WORK_PLAN_DEFINITION

Description

Task planning API that converts transactional calls to correct Task Planning information structures at Work Plan level.

Functions

Signature

Meaning

0..1

plans (): List<UID_BASED_ID>

List of Task Plan ids for this Work Plan.

0..1

plan (
a_task_plan_id: UID_BASED_ID[1]
): List<I_TASK_PLAN_DEFINITION>

Obtain a Task Plan definition API interface.

I_TASK_PLAN_MATERIALISED Interface

  • Definition

Interface

I_TASK_PLAN_MATERIALISED

Description

Task planning API for materialised Task Plan level.

Functions

Signature

Meaning

0..1

materialise

0..1

activate

0..1

terminate