Sextant: A tool to specify and visualize software metrics for Java source-code

Victor Winter, Carl Reinke, Jonathan Guerrero

Research output: Chapter in Book/Report/Conference proceedingConference contribution

6 Scopus citations

Abstract

The success of software development efforts typically require guidance derived from a deep understanding of its design space.Well-crafted software metrics can impart invaluable insight into the nature of software and can provide the underpinnings for informed decisions involving design and implementation trade-offs. Leveraging metrics to their full capacity requires (1) the ability to quickly develop custom metrics that are domain-specific and even application specific, and (2) the ability to present metrics-related information in a comprehensible fashion. This paper describes a tool, called Sextant, whose purpose is to achieve the goals stated in the previous paragraph. An overview of Sextant is given followed by two in-depth real-world examples of how the use of metrics can positively impact software development efforts.

Original languageEnglish (US)
Title of host publication2013 4th International Workshop on Emerging Trends in Software Metrics, WETSoM 2013 - Proceedings
Pages49-55
Number of pages7
DOIs
StatePublished - 2013
Event2013 4th International Workshop on Emerging Trends in Software Metrics, WETSoM 2013 - San Francisco, CA, United States
Duration: May 21 2013May 21 2013

Publication series

NameInternational Workshop on Emerging Trends in Software Metrics, WETSoM
ISSN (Print)2327-0950
ISSN (Electronic)2327-0969

Conference

Conference2013 4th International Workshop on Emerging Trends in Software Metrics, WETSoM 2013
Country/TerritoryUnited States
CitySan Francisco, CA
Period5/21/135/21/13

Keywords

  • Java
  • Sextant
  • program transformation
  • software metrics
  • software visualization
  • source code analysis

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'Sextant: A tool to specify and visualize software metrics for Java source-code'. Together they form a unique fingerprint.

Cite this