And if you do, can you give some background information on the implementation and the reasons for implementing this pattern?
The pattern is described in more detail in these articles:
+2
A:
Yes - we had a problem in that many of the administrators of our software found it too difficult to use. To solve this we used Microsoft's WinForms IUI framework build a new configuration and management tool for our software.
User feedback has been extremely positive, particularly with everything being task driven - i.e. the links on our home page include thing like "Create new user", "Create new department" - rather then the user having to discover how to do this by clicking through a series of menus. Since the inductive interface is more similar to a web-browser (hypertext links, back/forward buttons) it seems much easier for new users to learn.
John Sibly
2008-09-16 09:50:31
Thanks for your answer! When you say Microsoft's WinForms IUI framework, do you mean the Navigation library that is used here http://msdn.microsoft.com/en-us/library/ms951103.aspx?
michielvoo
2008-09-16 13:02:29
Yes that is exactly the one. Bare in mind that it's not an officially released framework so there were a couple of quirks we had to work around (resizing in particular) - however these were not that significant. Your other option would be to use WPF.
John Sibly
2008-09-16 13:07:39
+1
A:
I would suggest to use IUI Interfaces, whenever you use a software not on a daily basis...
Whenever you use an application only once a month, it could be very usefull to be guided through...
I have implemented IUI always manual, or at least used a Wizard-User-Control.
Peter Gfader
2008-11-14 08:57:35
+1
A:
You should be careful about making a too simple system. Expert users (bankers, insurers, CRMs, etc) should have as much information an possibilites on the screen as possible. Proceeding through forms that validate slowly has been found to be annyoing if you use that form several times during the workday.
smerten
2008-11-14 09:22:27