Difference between revisions of "Documentation-Rons-Rules-For-Tools"
From Slicer Wiki
| Line 3: | Line 3: | ||
#You make it, I break it | #You make it, I break it | ||
| − | #Your tool | + | #Your tool does not exist until it works on my laptop with my data. <ref>Until then, it's an unconfirmed rumor.</ref> |
#I am lazy. Make my life easy. <ref>User friendliness: | #I am lazy. Make my life easy. <ref>User friendliness: | ||
*Minimize the number of clicks | *Minimize the number of clicks | ||
Revision as of 14:05, 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 does not exist until it works on my laptop with my data. [1]
- I am lazy. Make my life easy. [2]
- No more than one simpleparameter, that I can set. [3]
- If I can take my lunch break while your algorithm is running, I won't return to it. [4]
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
- ↑ Until then, it's an unconfirmed rumor.
- ↑ User friendliness:
- Minimize the number of clicks
- Minimize the distance my pointer has to travel
- Have good default values for the parameter and I/O, and allow me to override.
- ↑ If I need more than 20 seconds to figure out how to set the parameter, I won't!
- ↑ Performance Requirements
- under a minute is good
- 5 minutes are acceptable
- 10 minutes or more are not
