| January 2009 | ||||||
|---|---|---|---|---|---|---|
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | ||||
| 4 | 5 | 6 | 7 | 8 | 9 | 10 |
| 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| 18 | 19 | 20 | 21 | 22 | 23 | 24 |
| 25 | 26 | 27 | 28 | 29 | 30 | 31 |
Software MFA Week 1 Status ReportAs a first step in my project, Brian asked me to find examples of software that are related to my work and suggest them for annotation. I went through the software listed at http://testingfaqs.org/ and found the following:
Brian says one of these projects was a failed work, but that it would be useful to discuss why it failed in the annotation. he didn't say which one though -- it's my task to determine that.
Also, I spent some time looking for a candidate for software to instrument using the concepts I will be exploring in my work. For what I have in mind, a good candidate would be some kind of server-side process that is intended to run continuously for long periods and be typically deployed on a system that is difficult or impossible to place under the control of the usual desktop development tools like IDEs, debuggers, etc. Since I'm using ruby for this project, I think MiniRubyWiki will fit the bill. It runs stand-alone (no web server required), is small, and already includes a page called the WikiNerveCenterWikiNerveCenter. If you have any other suggestions, I'd be happy to hear them. Another potential, if the wiki doesn't work out, is Cerise, "a Ruby web/application server following the same general pattern as J2EE application servers". Finally, if Dave Thomas agrees, I could instrument the code for the website management package he wrote.