ERP Course: Analysis Patterns

Planning and Trading

Readings: Chapter 8 and 9 from Martin
Fowler
Peter Dolog
dolog [at] cs [dot] aau [dot] dk
E2-201
Information Systems
October 27, 2006
Planning

Plan is a set of actions which are carried out by resources

Actions are planed, completed, abondoned,
postponed/suspended
They have resources allocated
A protocol is a set of actions repeated many times
Activities has outcomes and conditions to start

Peter Dolog, ERP Course, Analysis Pattern II 2

Properties of Actions

Peter Dolog, ERP Course, Analysis Pattern II 3

Basic Structure of Plans and Actions

Peter Dolog, ERP Course, Analysis Pattern II 4

Complemented and Abandoned Actions

Peter Dolog, ERP Course, Analysis Pattern II 5

Suspension of Actions

Peter Dolog, ERP Course, Analysis Pattern II 6

A Plan Consisting of References to Proposed Actions

Peter Dolog, ERP Course, Analysis Pattern II 7

Replacement Plans

Peter Dolog, ERP Course, Analysis Pattern II 8

Plans as Actions and Compound Actions

Peter Dolog, ERP Course, Analysis Pattern II 9

Structure for Protocols

Peter Dolog, ERP Course, Analysis Pattern II 10

Relationships among Action, Plan, and Protocol

Peter Dolog, ERP Course, Analysis Pattern II 11

Plan as a DAG of Proposed Actions

Peter Dolog, ERP Course, Analysis Pattern II 12

Protocol as DAG

Peter Dolog, ERP Course, Analysis Pattern II 13

Action’s Use of Resources

Peter Dolog, ERP Course, Analysis Pattern II 14

Ressource Allocation for Assets

Peter Dolog, ERP Course, Analysis Pattern II 15

Allowing Specific Allocations of Consumables

Peter Dolog, ERP Course, Analysis Pattern II 16

Links Between Observation, Plan, and Action

Peter Dolog, ERP Course, Analysis Pattern II 17

The Use of Start and Outcome Functions at the
Knowledge Level

Peter Dolog, ERP Course, Analysis Pattern II 18

Trading

Trade is about buying and selling

Trade is described by a contract
Contracts can be grouped into portfolios
Prices of goods change according to whether you look at them
from selling and buying point of view – quotes
Rapid changes can be captured by scenarios

Peter Dolog, ERP Course, Analysis Pattern II 19

Contract

Peter Dolog, ERP Course, Analysis Pattern II 20

Buyers and Sellers and Relationship

Peter Dolog, ERP Course, Analysis Pattern II 21

Counterparty and Primaryparty

Peter Dolog, ERP Course, Analysis Pattern II 22

Party mappings

Peter Dolog, ERP Course, Analysis Pattern II 23

Portfolio

Peter Dolog, ERP Course, Analysis Pattern II 24

Dynamic portfolios with filters
Portfolio «derived» Contract
-Value(scenario) -Value(scenario)
* *

{All instances on contract on which self.filter is true}

1..1 +filter

BooleanMethod

Peter Dolog, ERP Course, Analysis Pattern II 25

Contract Selectors

Peter Dolog, ERP Course, Analysis Pattern II 26

 Date

Several filter types 0..1

*
+start +end
0..1 *
+primaryparties
Instrument ContractSelector Party
+counterparties
* *
* *
* *

HardCodedFilter ContractFilter
-Value(scenario) -isIncluded
+selectContracts(in Collection)

* 1..1

Portfolio «derived» Contract

1..1 +filter -Value(scenario) -Value(scenario)
* *
BooleanMethod

{All instances on contract on which self.filter is true}

SetFilter
SetOperation
* {documentation = Instances: Union, Intersection, Negation}

* 1..1
Peter Dolog, ERP Course, Analysis Pattern II 27
Quotes Quote {spread = bid - offer
+bid : Number AND
{bid = offer} mid=(bid + offer)/2}
+offer : Number
+mid : Number
+spread : Number
+print()

OneWayQuote TwoWayQuote

Instrument
+price : Quote

Peter Dolog, ERP Course, Analysis Pattern II 28

Changes in Quotes

Peter Dolog, ERP Course, Analysis Pattern II 29

Scenarios

Peter Dolog, ERP Course, Analysis Pattern II 30

Derived Scenario Elements

Peter Dolog, ERP Course, Analysis Pattern II 31