The document describes a task engine with different levels. At level 0, a controller service handles task posting and getting. Level 1 adds an engine core and input/output queues. Level 2 includes a repository. Level 3 incorporates test cases. Level 4 shows handling current and new workflow tasks. Level 5 illustrates a chained workflow task. An E-R diagram then models the relationships between tasks, workflows, inputs, outputs, and links.

1. TASK ENGINE

2. Level 0
C
O
N
T
R
O
L
L
E
R
S
E
R
V
I
C
E
POST TASK
GET TASK
Input queue

3. LEVEL 1
C
O
N
T
R
O
L
L
E
R
S
E
R
V
I
C
E ENGINE CORE
INPUT QUEUE
POST TASK
GET TASK
OUTPUT QUEUE

4. LEVEL 2
C
O
N
T
R
O
L
L
E
R
S
E
R
V
I
C
E
R
E
P
O
S
I
T
O
R
Y
POST TASK
GET TASK
ENGINE CORE

5. Level 3
C
O
N
T
R
O
L
L
E
R
S
E
R
V
I
C
E
R
E
P
O
S
I
T
O
R
Y
TEST CASE
POST
TEST CASE
GET
ENGINE CORE
GET
POST

6. Level 4
C
O
N
T
R
O
L
L
E
R
S
E
R
V
I
C
E
R
E
P
O
S
I
T
O
R
Y
ENGINE CORE
CURRENT WORKFLOW
TASK
NEW WORKFLOW
TASK

7. Level 5
Chained
Workflow
task

8. E-R Diagram
TASK ID
WF ID
WW
1:M
1:M
1:M
O/P ID
Tasks
Task
name
Con
sists
WORKFLOW
WF
NAME
INPUTS
OUTPUTS
NAME
TYPE
VALUE
I/P Link
TYPE
I/P
LINK
NAME
VALUE
cont
ains
contains
I/P ID