I'm working on the the UI on a course fee search system. One of the requirements that came out from the discovery stage was the ability for staff to quickly find course fee information from a set of criteria.
My initial thought was to utilise the screen real estate and put the search,results and detail on the same page:
Example prototype is here: http://share.flairbuilder.com/?url=http://info.uwe.ac.uk/prototype/fees/fees.fbp
I've found a few results on this UI pattern and the designing web interfaces site suggest this is a master/detail pattern which
Ideal for creating an efficient user experience by allowing the user to stay in the same screen while navigating between items
I haven't tested this yet on a set of users. Some feedback from business people have suggested splitting the search results and detail on separate pages as this is 'expected' behaviour for search results
This may help users who are searching for 1 course fee detail but staff using this system who need to quickly find sets of course fee information by changing the search criteria it may be slower and less effective?
what do you think?