Path: utzoo!utgpu!watserv1!watmath!att!dptg!ulysses!andante!mit-eddie!mintaka!yale!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpcc01!aspen!fraley
From: fraley@aspen.IAG.HP.COM (Bob Fraley)
Newsgroups: comp.object
Subject: Re: OOA, OOD and processes
Message-ID: <8740002@aspen.IAG.HP.COM>
Date: 13 Jul 90 23:37:52 GMT
References: <1100@fang.dsto.oz>
Organization: HP Information Architecture Group - Cupertino, CA
Lines: 16

One reference to concurrent design in object-oriented systems is the
Object-Oriented Concurrent Systems tutorial in OOPSLA '89.  You might
also check references on Actors.

It has always seemed to me that once you have defined your objects and the
interactions between them, concurrency design is achieved by partitioning
the objects into processes.  The interactions between processes are then
visible, and technology can be selected for achieving the communication
based on the nature of the interactions.

I havn't seen any good treatment of response time analysis for such a 
design, but there is a reference to this in the March 1990 article by 
Berzins and Luqi in IEEE Software.  I suspect that you'd need to build
a simulation to make sure that you've made a good choice.

Bob Fraley