Absolute Relative Assignment Table

Absolute Relative Table Overview

Version 1.0 of BloomingLeaf allows users to set Absolute and Relative assignments for evolving intentions and relationships.

Basic Setup

Supposed we have our Goal Model as such in Figure 1 :

Figure 1

Table specification

Goal_0, Goal1_4, and Goal_2 have all been assigned a User Defined evolving function, consisting of multiple segments (or Epochs). Each Goal has the following initial satisfaction value.

Goal Names	Initial Satisfaction Value
Goal_0	Denied(T,FD)
Goal_1_4	Partially Denied(T,PD)
Goal_2	Denied(T,FD)

Users will be able to define relationships between two Epoch boundaries as either = or <, where = indicates that two Epoch boundaries have same time points and < indicating one of the Epoch boundary appears prior to another Epoch boundary. Our Absolute Relative Table for following model will look like in Figure 2. The relationship between Goal_2 and Goal_0 is a +|-S link and Goal_0 to Goal_1_4 is set to a +|+S link. The Absolute Relative table will allow users to set Time Points of Absolute Intention Assignment and Absolute Relative Assignment.

Figure 2

Users can also go back to the model and add more Goals and constraint links and the table will update with already saved entries along with new entries for added models.

For example, user has added two more Goals: Goal 4 and Goal 5, and added a constraint link of or|no from Goal 4 to Goal 5:

Then, if we go back to our Absolute Relative Table, then users will see new entries appended to the table (see Figure 3):

Figure 3

TODO: Introduce the context and what the table is used for. Define Epoch Boundary.