HomeFinder: Difference between revisions
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
== Short description == | == Short description == | ||
The dynamic Homfinder was created to search and visualize Databases. As the name implies the first use case scenario was a | The dynamic Homfinder was created to search and visualize Databases. As the name implies, the first use case scenario was a home finding application, where the user was able to find real estates, by adjusting graphical widgets (sliders, ...). | ||
== Advantages using dynamic Homfinder == | == Advantages using dynamic Homfinder == | ||
Revision as of 23:36, 26 April 2006
Authors
Short description
The dynamic Homfinder was created to search and visualize Databases. As the name implies, the first use case scenario was a home finding application, where the user was able to find real estates, by adjusting graphical widgets (sliders, ...).
Advantages using dynamic Homfinder
- Continuous update of the query results
- Fully visual interface (no query language needed)
- Reversible operations
- Immediate results
- almost no training needed
Disadvantages using dynamic Homefinder
- complex dynamic Queries need a lot of screen real estate
- underlying data structures need to support rapid querying
Suitable Datatypes
- data should be graphical representable
- slider widgets rely on numeric data
Interaction
- multiple slider interface
- buttons
- dynamic map display that displays house location
- single view
Internal Links
References
- [ACM, 1992] ACM, I ACM Press New York, http://portal.acm.org/citation.cfm?id=133216&coll=portal&dl=ACM&CFID=8530671&CFTOKEN=55015481