[Aiml-programr-developers] First post summary...

[Nicholas H.Tollervey]

For the sake of completeness, the following is a summary of Mauro's
suggestions for modus operandi and the next steps:

<quote>

I would like to rework with you the whole project, I think it would be
much more fun than fixing the old one. Still, it is nice to have
something that works to play with.

I think that we should then proceed as follows:
1 - we select a small set of classes we consider "central"
2 - we discuss and rework them
2.1 - If possible we do not break programR, but this is not a priority
3 - priority is to have Unit/Functional  tests for the central classes

After a while, the old classes will all be integrated/obsolete.

I think that as first step, this should do.
We can use Dia for UML, but in a typical TestDrivenDevelopment, the
test remain central, not the design.
A good candidate as "central class" is graph_master.

</quote>

I would like to add that I think we should also have a clear
specification of the processes we intend to implement through the use of
use-cases, stories and the more formal activity diagrams. Like Mauro
(see above), I think reworking the whole project rather than fixing the
old one will be more fun and give us more scope for changing and
re-designing (where necessary) the library.

Best wishes,

Nicholas