[erlang-questions] Erlang Process Notation?

[Torben Hoffmann]

Hi Max,

You might want to have a look at Object Process Methodology:
https://en.wikipedia.org/wiki/Object_Process_Methodology

The thing that makes OPM stand out is that it makes both objects and 
processes (not the same meaning as in Erlang) first class citizens. This 
allows for a very natural description of how data is processed and where 
the functionality should be located.

I use it as a way to depict the high level architecture and data flow 
more than anything else. It is sufficiently light weight to be done and 
maintained and expressive enough to have conversations about what is 
going on.

If you want to model an Erlang process with OPM it would come out as an 
object (sounds weird, but stay with me) that exhibits a number of 
processes (where a process is an API function of the process).

I have not tried the tool that has been developed for OPM - I made my 
own stencil for Dia.

Other nice features of OPM:

  * there is a 1-to-1 mapping between the graphical representation and
    its textual one.
  * you can zoom in and out in your model - not seen with UML or
    anything else.

But you would have to get the OPM tool or write some tool yourself to 
get the most out of these things.

Cheers,
___
  /orben

On 2012-12-14 08:51, Max Bourinov wrote:
> Hi Erlangers,
>
> I am wondering if there is any notation for Erlang processes? I want 
> to use it to describe my systems visually. Something like UML class 
> diagrams but for Erlang (I know that class diagram is not the best 
> example).
>
> p.s.: I heavily use sequence diagrams and they help a lot.
>
> Best regards,
> Max
>
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

-- 
http://www.linkedin.com/in/torbenhoffmann

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20121214/a162a583/attachment.htm>