That look's interesting. Do you have experience using this method? <br><br>Arnaud<br><br><div class="gmail_quote">On Sat, Nov 5, 2011 at 7:09 PM, Albert Y. C. Lai <span dir="ltr"><<a href="mailto:trebla@vex.net">trebla@vex.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 11-11-05 01:17 PM, Grigory Sarnitskiy wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you are to describe a system, which consists of several subsystems, how do you approach the problem? What types, classes, functions whatever do you introduce?<br>
<br>
I guess it is a common problem, is there a general method? Just to describe, not to solve (though if the description implies the solution then it is wonderful).<br>
</blockquote>
<br></div>
I would try Michael Jackson's Problem Frames.<div class="HOEnZb"><div class="h5"><br>
<br>
______________________________<u></u>_________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org" target="_blank">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/<u></u>mailman/listinfo/haskell-cafe</a><br>
</div></div></blockquote></div><br>