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

Unresolved include directive in modules/task_planning/pages/service_model.adoc - include::ROOT:partial$classes/i_work_plan_definition.adoc[]

Unresolved include directive in modules/task_planning/pages/service_model.adoc - include::ROOT:partial$classes/i_task_plan_materialised.adoc[]

Unresolved include directive in modules/task_planning/pages/service_model.adoc - include::ROOT:partial$classes/i_work_plan_definition.adoc[]

Unresolved include directive in modules/task_planning/pages/service_model.adoc - include::ROOT:partial$classes/i_task_plan_materialised.adoc[]