Strict Standards: Declaration of Doku_Renderer_metadata::table_open() should be compatible with Doku_Renderer::table_open($maxcols = NULL, $numrows = NULL, $pos = NULL) in /var/www/operationalsemantics.net/public_html/behaviouralwiki/inc/parser/metadata.php on line 24

Strict Standards: Declaration of Doku_Renderer_metadata::table_close() should be compatible with Doku_Renderer::table_close($pos = NULL) in /var/www/operationalsemantics.net/public_html/behaviouralwiki/inc/parser/metadata.php on line 24

A. ABSTRACT

Maximum 200 words, maximum 5 keywords or very short phrases

General remark: Be very clear and precise as this section will form the basis for COST information – web site and booklets – and reporting. The Abstract should include the broader scientific context of the Action as well as the expected deliverables and benefits. It should also indicate the European added value of the Action and the reasons for undertaking it in the COST framework.

Modern society is increasingly dependent on large-scale software systems that are distributed, collaborative and communication-centred. Correctness and reliability of such systems depend on consistency and compatibility between components and services that are newly developed or that may already exist. The consequences of failure are severe, including security breaches and unavailability of essential services. Current software development technology is not well suited to production of these large-scale systems, because of the lack of appropriate high-level structuring abstractions for complex communication behaviour.

Modern society is increasingly dependent on large-scale software systems that are distributed, collaborative and communication-centred. Correctness and reliability of such systems depend on compatibility between components and services that are newly developed or may already exist. The consequences of failure are severe, including security breaches and unavailability of essential services. Current software development technology is not well suited to producing these large-scale systems, because of the lack of high-level structuring abstractions for complex communication behaviour.

This Action will use behavioural type theory as the basis for new foundations, programming languages, and software development methods for communication-intensive distributed systems. Behavioural type theory encompasses concepts such as interfaces, communication protocols, contracts, and choreography. As a unifying structural principle it will transform the theory and practice of distributed software development.

The significance of behavioural types has been recognised world-wide during the last five years. European researchers are internationally leading. There is an urgent need for European co-ordination to avoid duplication of effort, facilitate interactions among research groups, and ensure that the field proceeds efficiently from academic research to industrial practice. This Action will provide the co-ordination layer and leverage the efforts of European researchers, to increase the competitiveness of the European software industry.

Keywords: distributed software infrastructure, software development methodology, foundations of programming languages, service-oriented computing, behavioural types

ABSTRACT: discussion

Simon: Please precede remarks with your name.

Simon: New abstract and fewer keywords.

Kohei: Hope I have improved, just changes in wording. Still 200 words in wc.

Pawel: in the Abstract, the only contribution of the Action is stated as:

type theory as a unifying structural method.

This statement may not be enough for the Abstract, and the meaning is too vague (what does it really mean?). If the Abstract should be stand alone in the application, more should be said here, e.g. something like in the paragraph (…),

the central research goal of this Action is to (..)

on Page 4.