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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

9.5 A Computational Interleaving Semantics 273<br />

(5)<br />

(6)<br />

(7)<br />

second part ensures that BSpec e is built from the same instances, in the same<br />

way, as BSpec p § § E1© P1 ¥¡ ¡ ¡ ¥ Er © Pr . Intuitively this means that the latter behaviour<br />

specification is a ’decent’ descendant <strong>of</strong> the former one. BSpec p § § E1© P1 ¥¡ ¡ ¡ ¥ Er© Pr <br />

denotes the syntactic substitution <strong>of</strong> each Pi by Ei in BSpec p . The precise definition<br />

is given later in this subsection. Function Reset calculates, given an (extended)<br />

behaviour specification, the corresponding initial specification. Reset is defined<br />

later in this subsection.<br />

<br />

e<br />

¥ envs1¥ BSpec1 Sysp ¡ Conf ¥ Sys p e<br />

<br />

BSpec ¥ 2 ¥ envs2 ¥<br />

Sysp ¡ Conf ¥ Sys p<br />

e<br />

<br />

¢ BSpec1 BSpec e 2 ¥ envs1 envs2 Sys ¥ p ¡ Conf ¥ Sys p<br />

<br />

¥ ¥ envs¥ ¡ Sys<br />

<br />

L¥ envs¥<br />

e p<br />

BSpec Sys<br />

p<br />

Conf<br />

e<br />

BSpec Sys p Sys ¥ ¡ Conf p<br />

<br />

¥ ¥ envs¥ Sys ¡ <br />

envs¥ ¥ Sys ¥ ¡ §<br />

e p<br />

BSpec Sys<br />

p<br />

Conf<br />

e p<br />

BSpec f Sys<br />

p<br />

Conf<br />

Sys p and Sys are assumed to satisfy context conditions (1’) ¡ ¡ (15’) <strong>of</strong> Section 9.4.<br />

We can now see why a system specification <br />

¥ Sys BSpec¥ p Sys contains the empty-list<br />

¥<br />

part. This seemingly superfluous list allows us to consider a system specification as a<br />

special kind <strong>of</strong> configuration, thereby simplifying our theory. By induction it is easy<br />

to show that indeed ¥ S<strong>Specification</strong>s Conf p . Note that the difference between a system<br />

specification and a configuration is that system specifications can only describe systems<br />

in their initial states, i.e. before initialisation has taken place. Configurations, on the<br />

other hand, are also able to describe systems during execution or simulation.<br />

As explained before, S p£ e denotes an extended process statement that still has to be executed<br />

by some process object. S p£ e , an element <strong>of</strong> set Stat p£ e , is defined as<br />

S p£ e :: S<br />

ch!m(E1 ¥¡ ¡ ¡ ¥ En) ¡<br />

ch?m(p1¥¡ ¡ ¡ ¥ pm ¡ E) ¡<br />

m(E1 ¥¡ ¡ ¡ ¥ En)(p1¥¡ ¡ ¡ ¥ pm)<br />

¡<br />

S ¡ p£ e<br />

; Sp<br />

1<br />

S ¡ p<br />

1<br />

2<br />

or Sp<br />

2<br />

§ E S ¡ p<br />

if E then S ¡ p<br />

1 else S p<br />

2 fi<br />

do E then S ¡ p od<br />

S ¡ p£ e<br />

1 abort S p<br />

¡<br />

2<br />

S p£ e<br />

1 interrupt S p<br />

2<br />

¡ m(p1£ ¡ ¡£ pm) Sp£ e ¡<br />

S ¡ p£ e<br />

1 interrupted S p<br />

2 ¥ Sp£ e<br />

2<br />

¡¡<br />

Here, m(p1£ ¡ ¡ ¡£ pm) S p£ e indicates that the method body <strong>of</strong> method m is being executed<br />

and that after successful termination <strong>of</strong> this execution the process has to resume its

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

Saved successfully!

Ooh no, something went wrong!