Difference between revisions of "Documentation-Rons-Rules-For-Tools"
From Slicer Wiki
| Line 17: | Line 17: | ||
</ref> | </ref> | ||
| − | =How To | + | =How To Make Algorithms Robust= |
| − | *Build a case library with 10 cases | + | *Build a case library with 10 or more cases |
| − | *Use | + | *Use half for development, cycle through the cases daily |
| − | *Use the other | + | *Use the other half for testing |
==References== | ==References== | ||
<references/> | <references/> | ||
Revision as of 13:53, 7 March 2011
Home < Documentation-Rons-Rules-For-ToolsIntroduction
"Rules for tools" is an informal set of rules that developers should keep in mind when working on interactive tools for translational clinical research. If you follow them, you will create tools that many people will use.
- You make it, I break it
- Your tool works when it works on my laptop with my data. Until then its useless to me.
- I am lazy. Make my life easy. [1]
- No more than one parameter that I can set.
- If I need more than 20 seconds to figure out how to set the parameter, I won't!
- If I can take my lunch break while your algorithm is running, I won't return to it. [2]
How To Make Algorithms Robust
- Build a case library with 10 or more cases
- Use half for development, cycle through the cases daily
- Use the other half for testing
References
- ↑
- Minimize the number of clicks
- Minimize the distance my pointer has to travel
- Make sure your module sets up everything for me, but allow me to override. E.g. if you create an output file, use the input filename plus name of the module.
- ↑
- under a minute is good
- 5 minutes are acceptable
- 10 minutes or more are not
