Add mru in target's orgnism and scientist

also remove search more button and put function in to list est: 0.5 - 1.0 day

PIMS estimate practice by Chris Morris

In order to get useful priorities from the PSB, we must be able to offer them better time estimates for development tasks. In order to begin getting practical experience of this, please do the following before each development task. (This does not apply to fixing defects. Fixing an individual defect is too uncertain, and we have a well established average that as a team we can fix 30 per week.) - write down two numbers, the minimum and maximum number of hours that you expect the task to take you. A normal uncertainty is a factor of two, e.g. 4-8 hours. If you are working on a "new feature", enter them into the issue tracker, there is a space for them. - If the uncertainty is greater than a factor of two, write down why, e.g. "BioJava might do this already, or might not". - If the uncertainty is less than a factor of two, write down why, e.g. "Lots of experience on similar tasks". - If the max estimate is more than 24 hours, the task is too large to estimate. Spend some time working out how to subdivide it into tasks that are 1-3 days work each. Then estimate each separately. This process isn't easy, but spending an hour to plan a week's work is not time wasted. - when you finish the job, write down how many hours coding it actually took. Compare it with your estimates. If we each do this, then by the time we next meet we will have some real experience to compare. After a few weeks practise, your estimates really will improve.

top10 hotkeys

Control-Shift-T Open type. Forget manually navigating through the source tree unless you're procrastinating. Control-Shift-R Open resource (looks for more than just Java files). F3 Open declaration. Alt-left arrow Go back in navigation history. Alt-right arrow Go forward. Control-Q Go to last edit location. Control-Shift-G Find references in workspace. Control-Shift-F Reformat code (according to code style settings). Control-O Quick outline. Within the editor, this key combination allows you to jump to a method or attribute by typing a few letters of the name. Control-/ Comment/uncomment a line. Can also work on many lines at a time. Control-Alt-down Copy highlighted line(s). Alt-down Move line(s) down. Alt-up arrow works as well Control-Shift-L view a list of all keys Control-Shift-L -second time into the Keys Preferences dialog

Eclipse plugin in use

EclEmma - Java Code Coverage for Eclipse http://www.eclemma.org/ Jester - the JUnit test tester http://jester.sourceforge.net/ Jester is different than code coverage tools, because it can find code that is executed by the running of tests but not actually tested. RMBench Modeller -RMBench Modeller is a graphical modelling tool for relational databases that aims to provide a one-stop focused solution to database modelling needs. RMBench is based on Eclipse and GEF, and supports the most important database systems, both commercial and open source. RMBench is available as a free edition with a limitation to 40 tables and 3 diagrams, and a (almost free) commercial edition which removes these limits and adds more features. http://code.google.com/p/alloy4eclipse/ An eclipse plugin for the Alloy4 tool

upgrader 26 (1.0 ->1.0)

previous job: Create and run on example DB used 1 day Found problem: error msg of no-unique is not clear need to fix no-unique names improve standard upgrader to create/remove not-null constraint automatically reupgrade example db (est: 0.5day) transfer data from applicationdata to experiment (est: 0.5 day) Done in X2 reasons: (1) lack real testing data (2) the unchangeable role is not predicted (3)can not fully focus on this