Vestige: A visualization framework for engineering geometry-related software

Teseo Schneider, Patrick Zulian, Mohammad R. Azadmanesh, Rolf Krause, Matthias Hauswirth

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Geometry-related software is increasingly important in computational science and visual computing. Engineering such software is particularly challenging due to the size and complexity of the data it operates on. In this paper we present VESTIGE, a framework that employs visualization to address that challenge. VESTIGE targets four software engineering activities: (1) visualization-guided development, (2) monitoring and bug detection, (3) test oracle generation, and (4) debugging. We present five scenarios from our real-life experience as developers of geometry-related software that show how VESTIGE helps to improve the software development process. Integrating VESTIGE into the development workflow takes little effort and can have significant benefits.

Original languageEnglish (US)
Title of host publication2015 IEEE 3rd Working Conference on Software Visualization, VISSOFT 2015 - Proceedings
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages26-35
Number of pages10
ISBN (Electronic)9781467375269
DOIs
StatePublished - Nov 19 2015
Event3rd IEEE Working Conference on Software Visualization, VISSOFT 2015 - Bremen, Germany
Duration: Sep 27 2015Sep 28 2015

Publication series

Name2015 IEEE 3rd Working Conference on Software Visualization, VISSOFT 2015 - Proceedings

Conference

Conference3rd IEEE Working Conference on Software Visualization, VISSOFT 2015
Country/TerritoryGermany
CityBremen
Period09/27/1509/28/15

Keywords

  • Data visualization
  • Debugging
  • Inspection
  • Monitoring
  • Software
  • Software algorithms
  • Visualization

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'Vestige: A visualization framework for engineering geometry-related software'. Together they form a unique fingerprint.

Cite this