© Erich Ortner, TUD. Das elastische Unternehmen (2008) 1 Temporal and Modal Logic Based Event...

© Erich Ortner, TUD. Das elastische Unternehmen

(2008) 1

Temporal and Modal Logic Based Event Languages for the Development of Reactive

Application Systems

Prof. Dr. Erich [email protected]

Dipl.-Wirtsch.-Math. Tobias Schneider [email protected]

Technische Universität DarmstadtDevelopment of Application Systems

Hochschulstraße 164287 Darmstadt, Germany


(2008) 2

Enterprise Engineering:Enterprise Domains and Language Types

SCM ERP CRM

Databases PlatformsData Inventory/ IT-

Infrastructure

Application Software/ Services

Workflows/Operational Organization

Collaborator/ Structural

Organization

Event-Languages (… does occur)

Organizational- and Computer-Processes

Thing-Languages (… is a)

Organizational- and Computer-

Objects


(2008) 3

Two directions of development away from Thing-Language

EventEvent

ProcessProcess

InteractionInteraction

CommunicationCommunication

ThingThing

(Occurance) (Dialog)

Event-Language

Thing-Language


(2008) 4

Event Based Approaches

Event-drivenEvent-oriented

Events are primary items we are looking for

Fundamental new approach to IT-usage by users (Internet of Events)

Events are triggers from other primary items we are looking for

Event-occurrances in UML (like Triggers)


(2008) 5

What is an Event?

An event is a certain occurance (action, process) which is singular in time and space.

Object

Thing Occurance

We distinguish elementary events, their schemas and complex events and their schemas, which are constructed (modelled) by assembling elementary events (their schemas).

A process is the directed operating sequence of an occurance.


(2008) 6

The grammar of an event-language

For example, an event can be determined individually (singular) as an unpersonalized occurance or process.

(The loading of this craft) takes place at the factory every wednesday.

or as a personalized action(The loading of this craft by the employees) takes place at the factory of our provider every wednesday.

(For „takes place“ we can also say „does occur“ or„happens“ and so on.)


(2008) 7

Why the event-oriented approach is more powerfull than the thing-oriented approach

Event-Processing:Thing-Processing:

An enterprise is an

architecture of

Thing-Types!

An enterprise is an

architecture of

Event-Clusters!

• coarse-grained

• „Stuctural organization“

• fine-grained

• „Process- or operational organization“


(2008) 8 8

Determination of Thing-Concepts and Event-Concept from a language-logical point of view

What is an Event-Concept?What is a Thing-Concept?

PERSON (x) {true, false}

MüllerMayer

Schulze…

( ) : is a …

Intension : Thing-SchemaExtension : Set of singular things

GETTINGwater(z) {true, false}

Event aEvent bEvent c

…

( ) : does occur as …

Intension : Event-SchemaExtension : Set of singlar events


(2008) 9

Putting (Logic-)Theories Together to Capture More Meaning

Temporal Logic: point in time – duration

Modal Logic: necessary – possible

Normative Logic: bidden – forbidden

Practice Logic: reachable – avoidable

and so on...


(2008) 10

EOA: Event-Oriented Architecture

Information

• This is (in use as) a hole-riddled BUCKET

Modal and Temporal Logic-based Event-Management• First the OPENING (of the house) must occur (and is necessary)

before the BRINGING (of water) can occur (and is possible)• THE OPENING (of the house) and the PLUGGING (of the

bucket) can occur simultaneously

Event Class• The quick BRINGING … (does occur)• The … OPENING … (does occur)• The … PLUGGING … (does occur)

Entity Class• This BUCKET is hole-riddled (in use)• Peter is a quick BRINGER (in use)• This HOUSE is open (in use)

Database:• Peter is (available as) a quick (attribute: realization capability) BRINGER• This is (available as) a hole-riddled (attribute: usage status) BUCKET• This is (available as) an open (attribute: admission status) HOUSE

Common or Standardized (Normative) Rational Language:• Peter (does) quickly bring fresh water from deep well with hole-riddled bucket

into open house• etc.

Presentation Layer

Coordination Layer

Application Layer

Administration Layer

Neutral Basis

Interaction

Next paper: Dialog-logic Based Event Languages for the Development of Interactive Application Systems


(2008) 11

What is an interaction from a language-theoretical point of view?

Interaction =DF a joint, coordinated execution of Event-Schemas by the participants of interaction at a certain time and space.


(2008) 12

Separated Modeling of Event- and Coordination-Schemas

Event-Schemas => e.g. BPMN-Diagrams

Coordination-Schemas => e.g. Protocol State Machines

Protocol State Machines describe only legal sequences of events (without effects).


(2008) 13

Modeling Coordination with respect to a different depth of description of Events

Events*

Normal Events

e.g. sales

Abnormal Events

Anticipated

e.g. sales return

Non-Anticipated

e.g. thefts or spoiled goods

*) Rommelspacher, J.: Ereignisgetriebene Architekturen, in: Wirtschaftsinformatik, 4, pp. 314-317 (2008)


(2008) 14

Modeling the coordination with different interactive participants

• D. Harel and A. Pueli: On the Development of Reactive Systems (1985)

M

• Transformational systems as a black box

• Algorithm-oriented

M

e1 e3e2

E = {e1, e2, …}

• Reactive Systems as a black cactus

• Interaction-oriented“One cannot say a system is entirely transformational or entirely interactive. Instead the terms predominantly transformational or predominantly reactive are recommendable.”


(2008) 15

Event- versus Object-oriented Approach

Event-oriented Approach Object-oriented Approach

Event-

ProcessingEvent-Things

Thing-

ProcessingThing-Events

Sprachkritische EAWS (2008) © Erich Ortner, TUD. 16

Common Neutral Model for the Development of Event-oriented Application Systems

Enterprise Task- and

Event-Architecture

(applicability)

Enterprise Service-

and IT-Architecture

(runnability)

Requirements

Engineering

(appropriateness)

The Wedding (accept-ability)

The Resilient Enterprise

Customer

Producer

ContinuousReconstruction

II

III

I

Sprachkritische EAWS (2008) © Erich Ortner, TUD. 17

Implementation of Event-Schemas as a Workunit Server and of Coordiation-Schemas as a Control Flow Server and Conductor

Worklist(HB-Services)

Conductor

DataServer Organization

Server

(Interaktion)WorkunitServer

Control Flow Server

Applications in Processes

(IT-Services)

Workflow Operation

Server (work equipment)

(Anwender in Prozessen)

1. Administration Layer3. Coordination

Layer

2. Application Layer

4. Presentation Layer

Idea: “Every server is

designed as a configurator”

(Interaction)(Operation)

(Workers in Action)


(2008) 18

Thank

You


(2008) 19

Temporal and Modal Logic Based Event Languages for the Development of Reactive

Application Systems

Prof. Dr. Erich [email protected]

Dipl.-Wirtsch.-Math. Tobias Schneider [email protected]

Technische Universität DarmstadtDevelopment of Application Systems

Hochschulstraße 164287 Darmstadt, Germany


(2008) 20

Enterprise Engineering:Enterprise Domains and Language Types

SCM ERP CRM

Databases PlatformsData Inventory/ IT-

Infrastructure

Application Software/ Services

Workflows/Operational Organization

Collaborator/ Structural

Organization

Event-Languages (… does occur)

Organizational- and Computer-Processes

Thing-Languages (… is a)

Organizational- and Computer-

Objects


(2008) 21

Two directions of development away from Thing-Language

EventEvent

ProcessProcess

InteractionInteraction

CommunicationCommunication

ThingThing

(Occurance) (Dialog)

Event-Language

Thing-Language


(2008) 22

Event Based Approaches

Event-drivenEvent-oriented

Events are primary items we are looking for

Fundamental new approach to IT-usage by users (Internet of Events)

Events are triggers from other primary items we are looking for

Event-occurrances in UML (like Triggers)


(2008) 23

What is an Event?

An event is a certain occurance (action, process) which is singular in time and space.

Object

Thing Occurance

We distinguish elementary events, their schemas and complex events and their schemas, which are constructed (modelled) by assembling elementary events (their schemas).

A process is the directed operating sequence of an occurance.


(2008) 24

The grammar of an event-language

For example, an event can be determined individually (singular) as an unpersonalized occurance or process.

(The loading of this craft) takes place at the factory every wednesday.

or as a personalized action(The loading of this craft by the employees) takes place at the factory of our provider every wednesday.

(For „takes place“ we can also say „does occur“ or„happens“ and so on.)


(2008) 25

Why the event-oriented approach is more powerfull than the thing-oriented approach

Event-Processing:Thing-Processing:

An enterprise is an

architecture of

Thing-Types!

An enterprise is an

architecture of

Event-Clusters!

• coarse-grained

• „Stuctural organization“

• fine-grained

• „Process- or operational organization“


(2008) 26 26

Determination of Thing-Concepts and Event-Concept from a language-logical point of view

What is an Event-Concept?What is a Thing-Concept?

PERSON (x) {true, false}

MüllerMayer

Schulze…

( ) : is a …

Intension : Thing-SchemaExtension : Set of singular things

GETTINGwater(z) {true, false}

Event aEvent bEvent c

…

( ) : does occur as …

Intension : Event-SchemaExtension : Set of singlar events


(2008) 27

Putting (Logic-)Theories Together to Capture More Meaning

Temporal Logic: point in time – duration

Modal Logic: necessary – possible

Normative Logic: bidden – forbidden

Practice Logic: reachable – avoidable

and so on...


(2008) 28

EOA: Event-Oriented Architecture

Information

• This is (in use as) a hole-riddled BUCKET

Modal and Temporal Logic-based Event-Management• First the OPENING (of the house) must occur (and is necessary)

before the BRINGING (of water) can occur (and is possible)• THE OPENING (of the house) and the PLUGGING (of the

bucket) can occur simultaneously

Event Class• The quick BRINGING … (does occur)• The … OPENING … (does occur)• The … PLUGGING … (does occur)

Entity Class• This BUCKET is hole-riddled (in use)• Peter is a quick BRINGER (in use)• This HOUSE is open (in use)

Database:• Peter is (available as) a quick (attribute: realization capability) BRINGER• This is (available as) a hole-riddled (attribute: usage status) BUCKET• This is (available as) an open (attribute: admission status) HOUSE

Common or Standardized (Normative) Rational Language:• Peter (does) quickly bring fresh water from deep well with hole-riddled bucket

into open house• etc.

Presentation Layer

Coordination Layer

Application Layer

Administration Layer

Neutral Basis

Interaction

Next paper: Dialog-logic Based Event Languages for the Development of Interactive Application Systems


(2008) 29

What is an interaction from a language-theoretical point of view?

Interaction =DF a joint, coordinated execution of Event-Schemas by the participants of interaction at a certain time and space.


(2008) 30

Separated Modeling of Event- and Coordination-Schemas

Event-Schemas => e.g. BPMN-Diagrams

Coordination-Schemas => e.g. Protocol State Machines

Protocol State Machines describe only legal sequences of events (without effects).


(2008) 31

Modeling Coordination with respect to a different depth of description of Events

Events*

Normal Events

e.g. sales

Abnormal Events

Anticipated

e.g. sales return

Non-Anticipated

e.g. thefts or spoiled goods

*) Rommelspacher, J.: Ereignisgetriebene Architekturen, in: Wirtschaftsinformatik, 4, pp. 314-317 (2008)


(2008) 32

Modeling the coordination with different interactive participants

• D. Harel and A. Pueli: On the Development of Reactive Systems (1985)

M

• Transformational systems as a black box

• Algorithm-oriented

M

e1 e3e2

E = {e1, e2, …}

• Reactive Systems as a black cactus

• Interaction-oriented“One cannot say a system is entirely transformational or entirely interactive. Instead the terms predominantly transformational or predominantly reactive are recommendable.”


(2008) 33

Event- versus Object-oriented Approach

Event-oriented Approach Object-oriented Approach

Event-

ProcessingEvent-Things

Thing-

ProcessingThing-Events


(2008) 34

A Two-Level (Interactive) Event-Language

A) What we need is an (executable) event-oriented (programming-) language, that works on two different language-layers:

1.) Layer of event-statement

2.) Layer of event-characterization

“Interactions are events, too!”

B) Dialog-logic based “protocol state machine” if the language is an interactive event-language.


(2008) 35

A model of computer-related

symbol-manipulation

(Alan M. Turing, 1912 – 1954)

3.1

A model of human-related symbol-manipulation

(Paul Lorenzen, 1915 – 1994)

The logical form that leads to movement.

Pointer

Data stream

Control-Unit


(2008) 36

The dialog of the sentence of the excluded contradiction

(1) The proponent posts his thesis: He states that “¬(A^¬A)”.

(2) The opponent has to strike back, by stating “A^¬A”.

(3) The opponent’s strike can be answered by the proponent by attacking the left side of the statement (?1). He questions, that A is true.

(4) The opponent has to defend A. He has to prove, that A is true.

(5) The proponent attacks the right side of the statement(?2) “¬A”.

(6) The opponent has to prove that “¬A” is true.

(7) In that case the proponent can state (A), which has been proved by the opponent in (4).

The dialog ends here, because the opponent already proved, that (A) is true and by demanding to prove that (A) is true from the proponent, the proponent can answer that (A) has already been proved.


(2008) 37

Common Neutral Model for the Development of Event-oriented Application Systems

Enterprise Task- and

Event-Architecture

(applicability)

Enterprise Service-

and IT-Architecture

(runnability)

Requirements

Engineering

(appropriateness)

The Wedding (accept-ability)

The Resilient Enterprise

Customer

Producer

ContinuousReconstruction

II

III

I


(2008) 38

Implementation of Event-Schemas as a Workunit Server and of Coordiation-Schemas as a Control Flow Server and Conductor

Worklist(HB-Services)

Conductor

DataServer Organization

Server

(Interaktion)WorkunitServer

Control Flow Server

Applications in Processes

(IT-Services)

Workflow Operation

Server (work equipment)

(Anwender in Prozessen)

1. Administration Layer3. Coordination

Layer

2. Application Layer

4. Presentation Layer

Idea: “Every server is

designed as a configurator”

(Interaction)(Operation)

(Workers in Action)


(2008) 39

Foundations of the language Crictical Approved*):The Most Important Milestones

6. Language- and Software- Architecturese.g. Edsger W. Dijkstra, 1930-2002

7. The Concept of Truth and other Generalizations for the Justification of Sentences e.g. Karl Popper, 1902-1994

1. Concepts and EntitiesGottlob Frege, 1848-1925

2. Proper Names andSingular DescriptionsBertrand Russel, 1872-1970

3. Object Language / Meta LanguageAlfred Tarski, 1901-1983

4. Teachings ofElementary SentencePaul Lorenzen, 1915-1994

5. Classification and Compositione.g. David Hilbert, 1862-1943

Universal literacy: from computerscience upward. An appeal for more extensive expression and under-standing.H. Wedekind & E. Ortner inCommun. of the ACM 47(6): 101-104 (2004)

Living the

Constructivist

*)Wedekind, H.; Ortner, E.; Inhetveen, R.: Informatik als Grundbildung, 6 Aufsätze in: Informatik-Spektrum, Heft 2 (2004) bis Heft 1 (2005).


(2008) 40

From an Internet of Things to an Internet of Events

World Wide Web

Software Knowledge

Hardware – Technology Carriers – People

Objects/Computer

Technology

Usersresp.

Human Beings

Event andWorkflow Control

HCI HCI:Human-Computer-Interface


(2008) 41

Enterprise Engineering Science is Interdisciplinary

Business and M

anagement

Science and E

ngineering

Econom

ics and Social S

ciences

Math and O

perations Research

Com

puter Science &

Info. System

s

Industrial and System

s Engineering

Business A

nthropology

Organizational C

hange & Learning


(2008) 42

Common Education and Specialization of humans in the knowledge-age

EnterpriseEngineer

User


(2008) 43

Enterprise Computer Science & Interdisciplinarity

Language Critical Computer Science = Philosophy of Science of the 21st Century

Interdisciplinary Sciences = Ubiquitous Computing• Web Science• Services Science• Enterprise Computer Science

Education = World Wide Situation• (Classical) Logic Gained by

Learning the Mother Tongue

• Interdisciplinary Studies(e.g. Enterprise Engineering)at Universities


(2008) 44

Thank

You

© Erich Ortner, TUD. Das elastische Unternehmen (2008) 1 Temporal and Modal Logic Based Event...

Documents

Transcript of © Erich Ortner, TUD. Das elastische Unternehmen (2008) 1 Temporal and Modal Logic Based Event...