Adding precondition and postcondition could be handy for cases where the
task is to be carried out by software: Each task becomes a test case
which can be test automatically.
<task>
<title>Stripping Path Characters</title>
<precondition>
<programlisting>../foo./bar</programlisting>
</precondition>
<procedure>
<programlisting>strip_path_caracters(string)</programlisting>
</procedure>
<postcondition>
<programlisting>foobar</programlisting>
</postcondition>
</task>
This is user documentation of a software task (what a specific
function/method does), not really modeling IMHO.
Tobi
--
http://www.pinkjuice.com/
