|
Hi Jie,
I think you're correct - the purpose of having the
Process View is to articulate (visually) inter-process and inter-thread
boundaries. The value of visualing inter-process boundaries is, for example, in
the identification of potential performance bottlenecks (since inter-process
communication is much slower than intra-process communication). The value of
visualing inter-thread boundaries is, for example, in the identification of
points of concurrency (and therefore a potential point of
synchronization).
I think it's also worth noting that you don't always
have to create a Process View, even if you do have multiple processes or
threads. This is particularly true when there is a well-understood architecture
being used (such as J2EE, where web server and application server usually reside
in separate processes). In essence - if the value in communicating the Process
View outweighs the cost of creating and maintaining it, then (in my humble
opinion!) it should be built.
Regards, Pete ===================================
|
- (ROSE) Architectural Process View Jie Zhao
- Eeles, Peter
