Hello to all contributors, admins, users, and supporters,
I would really like to see the concepts behind Care2x written down. I'd like to have a clear description of each module what it is meant to be good for. Some kind of requirements specification. Using "normal people" language, not IT expressions. So the right question is: Elpidio, what did you bear in mind, when you started to program the ... module. (Rather than "on what buttons can I click on that page"). In addition I think, a good requirement spec could be directly used for the documentation as well as for QA purposes, as one can use any single requirement as doc item. And also for generating test cases. Thoughts? In addition I would like to discuss any thoughts about using the wiki as "documentation backbone" like it's used at present. A peacefull new year to all Nino ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Care2002-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/care2002-developers
