Premium
A Task‐Based Approach to User Interface Design for a Web‐Based Hydrologic Information Systems
Author(s) -
Soh LeenKiat,
Zhang Jing,
Samal Ashok
Publication year - 2006
Publication title -
transactions in gis
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.721
H-Index - 63
eISSN - 1467-9671
pISSN - 1361-1682
DOI - 10.1111/j.1467-9671.2006.01005.x
Subject(s) - computer science , task (project management) , interface (matter) , field (mathematics) , visualization , user interface , point (geometry) , data mining , data science , systems engineering , engineering , bubble , maximum bubble pressure method , operating system , geometry , mathematics , parallel computing , pure mathematics
Hydroinformatics is a new and rapidly developing field that integrates knowledge and understanding of water resources with the latest developments in information technology to improve decision‐making in many critical applications. It encompasses methods for data capture, storage, processing, analysis and visualization, and the use of advanced modeling, simulation, optimization and knowledge‐based tools and systems infrastructure. Three types of hydrological data are most commonly used: flow rate in major rivers and streams, height of water in wells, and precipitation. To get a complete view of the state of water at a given point in space and time, one must analyze many different types of hydrological data together to derive information using an online GIS tool. To help use these disparate data sources more effectively and efficiently, we have built an online interface called the IJEDI WebCenter for Hydroinformatics using a task‐based approach. In this design, we first identify the tasks that users perform to study water‐related issues, then organize data for each task, and build task‐specific tools to present and analyze data and information. In a study involving both novices and experts in hydrology, we found that the both groups performed water‐related studies more effectively and efficiently than they would have without the WebCenter.