Action Benefit Cost model (ABC model)

Inspiration

SoS-level manager, who is charge of operating and managing SoS, may not have all internal information of each CS. This feature makes it difficult for the manager to predict behaviors of CSs. To solve such lack of information, we borrow the Cost-Benefit analysis from Economics and Game theory. This theory assumes that all participants tries to maximize their utility which is cost-benefit. Also, most of CSs are existing systems because if SoS tries to implement all systems, then it is very expensive. Those systems definitely have their requirements, goals. Existing CSs may achieve their goals even if they are in SoS. This feature can apply cost-benefit analysis. Their behavior selection mechanism is represented using utility to achieve its goal rather than modeling decision mechanism of each CS.

Action Benefit Cost (ABC) modeling

We model each CS (system) using a set of capable behaviors. Behavior is represented using action. Action consists of two parts, benefit and cost. Benefit is acquired interest which is taken for a Cs by performing an action. This represents that the action is how Cs-level or SoS-level goal closely related is. Cost is a representation of consumed resources by performing an action.

Base action class is in BaseAction file. There are number of abstract methods you need to extend to simulate SoS scenario.

/*
 * Abstract methods
 */
public abstract void addBenefit(int additionalBenefit);
public abstract BaseAction clone();
public abstract void reset();
public abstract void randomGenerate();
public abstract String getDebugTrace();
public abstract DebugProperty getDebugProperty();

Last two methods are for debugging and your verification property. If your verification property needs to look at every time tick, then you need to extend those method and implement them containing sufficient information to verify properties.

You can look at example scenario model.