Dear Vedrin & All:

Vedrin - so nice to have your help on useful summaries :).  Suggestions 
look like a good capture from our discussion and we should proceed.

The link for http://www.opentox.org/dev/requirements/use-cases is 
intended as a place-holder for completed reviewed use cases and I hope 
we load cases there as we achieve that in the New Year, but this is a 
current behind working todo.  It would be ok to use there, but perhaps 
better would be to set up corresponding testcase pages for FastTox and 
ToxModel for the first Prototype/iterations 3-4 in the test area:
http://www.opentox.org/dev/testing

Otherwise suggest we go ahead e.g.,
a. Micha/Andreas setup initial structure (pages, alert function, 
template, any guidance .. etc.)
b. Nina/Christoph/Stefan ¦ IDEA/IST/TUM setup initial outline on pages 
for primary two test cases
c. All contributors add relevent comments/links/edits/links to 
individual or API issue trackers/deliverables cross referencing etc.
d. We could add Test Case issue trackers
...
We can then treat this area as the centralised ongoing reference for 
updates from all on first Prototype/iterations 3-4 tasks/issues and 
which can also be referred/linked to from OTD emails.

Barry

Vedrin Jeliazkov wrote:
> Hi Micha, Barry, Christoph, All,
>
> During today's conference call we've agreed that we need to put
> together development roadmaps for the FastTox and ToxModel usecases.
> I'm wondering whether the appropriate location for publishing these
> roadmaps is here:
>
> http://www.opentox.org/dev/requirements/use-cases
>
> Could you please clarify?
>
> In fact, it would be very nice if Micha could create placeholders for
> these two pages at the appropriate location and provide pointers to
> the list, in order to get this work item started as soon as possible.
>
> I've also tried to write down a very short summary of the items that
> need to be included in these pages (in my opinion):
>
> 1) Detailed usecase workflow, linking each step to relevant
> services/implementations and specifying the exact functional
> dependencies all the way down to API compliant curl
> requests/responses, as well as any additional requirements (when
> applicable).
>
> 2) A table listing all workflow steps (states+transitions), specifying
> the current progress, involved developers, any further workflow
> step-specific comments, as well as links to relevant bug/issue
> trackers where specific workflow step related issues should be
> reported.
>
> 3) A section for GUI design, including information on proposed
> platform/tools (e.g. Java Web Start, RoR, PHP, etc), general GUI
> workflow description, screenshots and links to relevant bug/issue
> trackers where GUI testing issues should be reported.
>
> 4) Pointers to any running (FastTox or ToxModel) test instances and
> their associated bug/issue trackers.
>
> It would be nice if we could avoid duplicate work by creating and
> making available some reasonable development roadmap template, which
> is generic enough to be used for any use case. Any volunteers for
> performing this work?
>
> Kind regards,
> Vedrin
> _______________________________________________
> Development mailing list
> Development at opentox.org
> http://www.opentox.org/mailman/listinfo/development
>
>