Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
People who refuse to give up their bank records, tax records & details of any benefits they've claimed and the records of their car movements for the last year, or refuse to submit to an interrogation on whether they are the same person that this mountain of data belongs to will be denied passports from March 26th.
The Blair Govt has already admitted that this and other data will be cross-linked so that the Home Office and other officials can spy on the everyday lives of innocent Britons.
Britons were already the most spied upon nation in Western Europe. Data-mining through this unprecedented level of mass-surveillance allows any future British govt to leapfrog even countries like China and North Korea."
1. "What does something do? What is something?" type of questions.
2. "How can something be accomplished?" type of questions.
Providing information 1 is trivial — you just need to iterate through all menus, widgets and components on the screen, and describe them one by one. You can also have things like tooltips, whatsthis widgets, etc. that can be associated with every displayed widget.
How does one give a systematic list of the second type of questions? The problem is tricky because the keywords users might use to search for help might not be the exact technical terms used in the manual. For example, users may "know" that they need to use a text-box, but may not know that the thing to be used is called a text-box.
How would you, as a developer, arrange information in a way that is easy to discover for end users who know only their functional requirements? What other techniques can you use to speed up (I'm extremely sorry...) "software-usage knowledge discovery"?"