🚀 go-pugleaf

In article <...> hufnagel@cse.uta.edu (Stephen Hufnagel) writes:

   A simple extention is to use CSP to specify the concurrency and Z to 
   specify the processes. Another extention is to use path expressions
   to specify the concurrency and Z ...
     Good luck!

On a serious note, 

  * CSP can be used for the specification and analysis of patterns of
    communication (that's what a CSP process is).  These patterns can
    evolve concurrently, and timing information is easily included.

  * Z can be used for the specification and analysis of state-based 
    or transformational systems.  Extending Z to deal with real-time
    systems, which are

        ---  reactive (maintain a continuous interaction with their
             environment)
    
        ---  distributed (may be required to perform several tasks
             concurrently) 

        ---  timed (may be subject to complex timing constraints)

    is not an easy task.  In particular cases, a satisfactory
    treatment of timed or concurrent behaviour can be achieved
    with a suitable choice of abstraction, but this can't really
    be generalised. 
    
So it seems sensible to use CSP (or something very like it) and Z
together, using CSP to specify the patterns of communication between
system components, and then Z to specify the computational (or
transformational) aspects of the components themselves.

This is all a bit ad-lib, I'm afraid, but I hope that it helps...

Jim









--