Official websites use. Share sensitive information only on official, secure websites. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than the author s must be honored.
Abstracting with credit is permitted. Request permissions from permissions acm. The modern web is a successful platform for large scale interactive web applications, including visualizations.
However, there are no established design principles for building complex visual analytics VA web applications that could efficiently integrate visualizations with data management, computational transformation, hypothesis testing, and knowledge discovery. This imposes a time-consuming design and development process on many researchers and developers.
To address these challenges, we consider the design requirements for the development of a module-based VA system architecture, adopting existing practices of large scale web application development. This platform defines: 1 a specification for an architecture for building VA applications with multi-level modularity, and 2 methods for optimizing module interaction, re-usage, and extension. To demonstrate how this platform can be used to integrate a number of data management, interactive visualization, and analysis tools, we implement an example application for simple VA tasks including raw data input and representation, interactive visualization and analysis.
Over the two last decades, the web has proven itself to be a successful platform for the development of information visualizations [ 26 ]. Web-based visualization solutions dramatically reduce deployment issues by running directly in the desktop or mobile web browser, yielding a high degree of accessibility, and by avoiding complex installation, version update, incompatibility, and other problems characteristic of standalone software [ 32 ].
