23.08.2013 Views

Specification of Reactive Hardware/Software Systems - Electronic ...

Specification of Reactive Hardware/Software Systems - Electronic ...

Specification of Reactive Hardware/Software Systems - Electronic ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

316 Behaviour-Preserving Transformations<br />

c<br />

A B<br />

a<br />

b<br />

c<br />

d<br />

a<br />

¡<br />

¢<br />

¡<br />

c<br />

A B<br />

The reason is that the specification <strong>of</strong> the left-hand side <strong>of</strong> the picture allows communication<br />

between A and B over channel b, whereas the right-hand side does not allow any<br />

communication between the two parties!<br />

Transformation 12<br />

e p<br />

<br />

envs¥ BSpec Sys ¥ Sys<br />

¥ 1<br />

¢<br />

¡<br />

<br />

e p<br />

envs¥ BSpec Sys ¥ Sys<br />

¥ 2<br />

if Sys p<br />

1 and Sys p<br />

2 are non-conflicting ¨<br />

Two systems <strong>of</strong> process and cluster classes Sys p<br />

1<br />

a<br />

and Sysp<br />

2<br />

if for every class name occurring in Sys p<br />

1 as well as Sys p<br />

tions are syntactically identical.<br />

b<br />

b<br />

c<br />

are defined to be non-conflicting<br />

2, the corresponding class defini-<br />

By 12 it is allowed to add a new class or to remove an existing class from a system <strong>of</strong><br />

process and cluster classes Sys p contained in some configuration conf p . Note, however,<br />

that the resulting configuration, say conf p ¡ , must be a valid one, i.e. that conf p ¡ ¡ Conf p .<br />

In the case conf p ¡ is a system specification, this means that it has to conform to all the<br />

context conditions as defined in Subsection 9.4.<br />

Transformation 13<br />

(i) C c (E1 ¥¡ ¡ ¡ ¥ Er)¥<br />

<br />

p<br />

§ § E1© BSpec ¥¡ ¡ ¡ ¥ Er© Pr ¥<br />

P1<br />

if Cc denotes the name <strong>of</strong> a cluster class defined in Sysp by<br />

<br />

¥ Sys p ¥ Sys<br />

cluster class Cc ¡ ¥ Pr ¥¡ ¡<br />

¡ ¡<br />

P1<br />

communication channels ch1 chk<br />

message interface la 1 ¡ ¡ la behaviour specification<br />

l<br />

BSpecp ¢<br />

¡<br />

d<br />

a<br />

<br />

¥ Sys p Sys ¥<br />

(ii) <br />

§ BSpece Cc ¡ ¡£ Er¢ ¥ envs¥ Sys E1£ ¡ p ¢ <br />

¡<br />

e BSpec ¥ envs¥ p Sys ¥ Sys<br />

¥ Sys<br />

if Cc is defined in a similar way as in (i) and if Reset(BSpece )<br />

BSpecp E1© P1 ¥¡ ¡ ¡ ¥ Er © Pr . ¨<br />

§ §<br />

Transformation 13 states that the collaborating behaviour <strong>of</strong> the instances from which a<br />

cluster instance is constituted is equivalent to the behaviour <strong>of</strong> the cluster instance itself.<br />

It is therefore allowed to replace any cluster by the system <strong>of</strong> instances from which it is<br />

constituted. On the other hand any system <strong>of</strong> collaborating instances can be combined<br />

into an appropriate cluster instance, thereby introducing an extra hierarchical level in the<br />

corresponding system specification. Clustering a system <strong>of</strong> instances may involve the

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!