Managing scientific software complexity with Bocca and CCA

  • Authors:
  • Benjamin A. Allan;Boyana Norris;Wael R. Elwasif;Robert C. Armstrong

  • Affiliations:
  • (Correspd. E-mail: baallan@sandia.gov) Sandia National Laboratories, Livermore, CA, USA;Argonne National Laboratory, Argonne, IL, USA;Oak Ridge National Laboratories, Oak Ridge, TN, USA;Sandia National Laboratories, Livermore, CA, USA

  • Venue:
  • Scientific Programming - Complexity in Scalable Computing
  • Year:
  • 2008

Quantified Score

Hi-index 0.00

Visualization

Abstract

In high-performance scientific software development, the emphasis is often on short time to first solution. Even when the development of new components mostly reuses existing components or libraries and only small amounts of new code must be created, dealing with the component glue code and software build processes to obtain complete applications is still tedious and error-prone. Component-based software meant to reduce complexity at the application level increases complexity to the extent that the user must learn and remember the interfaces and conventions of the component model itself. To address these needs, we introduce Bocca, the first tool to enable application developers to perform rapid component prototyping while maintaining robust software-engineering practices suitable to HPC environments. Bocca provides project management and a comprehensive build environment for creating and managing applications composed of Common Component Architecture components. Of critical importance for high-performance computing (HPC) applications, Bocca is designed to operate in a language-agnostic way, simultaneously handling components written in any of the languages commonly used in scientific applications: C, C++, Fortran, Python and Java. Bocca automates the tasks related to the component glue code, freeing the user to focus on the scientific aspects of the application. Bocca embraces the philosophy pioneered by Ruby on Rails for web applications: start with something that works, and evolve it to the user's purpose.