Development of a Mesh Generation Code with a Graphical Front-End: A Case Study

Development of a Mesh Generation Code with a Graphical Front-End: A Case Study

Jeffrey Carver (University of Alabama, USA)
Copyright: © 2011 |Pages: 16
DOI: 10.4018/joeuc.2011100101
OnDemand PDF Download:
$37.50

Abstract

Scientists and engineers are increasingly developing software to enable them to do their work. A number of characteristics differentiate the software development environment in which a scientist or engineer works from the development environment in which a more traditional business/IT software developer works. This paper describes a case study, specifically about the development of a mesh-generation code. The goal of this case study was to understand the process for developing the code and identify some lessons learned that can be of use to other similar teams. Specifically, the paper reports on lessons learned concerning: requirements evolution, programming language choice, methods of communication among teammates, and code structure.
Article Preview

Introduction And Background

The development of software applications for use in Computational Science and Engineering (CSE) is an important and growing segment of the software development landscape. The development of CSE software differs from the development of the typical types of software that software engineering researchers study (Carver, Kendall, Squires, & Post, 2007; Carver, 2009; Kelly, 2007; Segal, 2008; Wilson, 2006). These differences mean that many existing software engineering practices are not directly applicable within the CSE domain. Some of these characteristics are:

  • The requirements discovery and gathering process is often difficult due to the large number of unknowns at the beginning of a project;

  • Achieving the correct scientific or engineering output is more important to the developers than using correct or appropriate software engineering techniques; and

  • Even when they are aware of traditional software engineering processes, which is not common, developers tend to be averse to using those processes.

Most software engineering research has been conducted in a business-oriented environment rather than a research-oriented environment. It is not clear whether the results of this research and the lessons learned about the usefulness of various techniques will translate to the CSE environment. To better understand the impact of the CSE environment and to document successful CSE software development practices, the author, along with other colleagues, as part of the DARPA High Productivity Computing Systems (HPCS) project (http://www.highproductivity.org), have conducted a series of case studies of successful CSE projects. To protect the anonymity of the projects, we assign each one a bird pseudonym. This paper describes the seventh case study in the series after Falcon (Post, Kendall, & Whitney, 2005), Hawk (Kendall et al., 2005), Condor (Kendall, Mark, Post, Squires, & Halverson, 2005), Eagle (Kendall, Post, Squires, & Carver, 2006), Nene (Kendall, Post, & Mark, January, 2007), and Osprey (Kendall et al., 2008) which will be referred to as the HARRIER project.

The common objectives for all of the case studies in the series are to (Carver et al., 2007):

  • provide feedback to software vendors about issues that should be addressed to improve productivity;

  • develop a body of case studies of CSE projects that can serve as a guide to the community; and

  • document lessons learned about CSE software development to provide a resource for other similar teams.

The case study approach, as defined by Yin, is a well-understood method for gathering this type of information (Yin, 2002). The case studies, including the one reported in this paper, all followed a similar format that has proved successful. To provide context for this paper, a brief summary of the methodology is provided. The complete methodology is described in a previous publication (Carver et al., 2007). After identifying a suitable project, members of the code team complete a survey to provide background information about the project. Using this information, the researcher develops a set of questions that will be used to explore interesting topics further during an on-site interview. The researcher conducts the on-site interview with the team to gather more detailed information about the software development processes. Finally, using information from the survey and interview, the researcher writes a report that is circulated with the development team to ensure its accuracy.

Complete Article List

Search this Journal:
Reset
Open Access Articles: Forthcoming
Volume 29: 4 Issues (2017): 3 Released, 1 Forthcoming
Volume 28: 4 Issues (2016)
Volume 27: 4 Issues (2015)
Volume 26: 4 Issues (2014)
Volume 25: 4 Issues (2013)
Volume 24: 4 Issues (2012)
Volume 23: 4 Issues (2011)
Volume 22: 4 Issues (2010)
Volume 21: 4 Issues (2009)
Volume 20: 4 Issues (2008)
Volume 19: 4 Issues (2007)
Volume 18: 4 Issues (2006)
Volume 17: 4 Issues (2005)
Volume 16: 4 Issues (2004)
Volume 15: 4 Issues (2003)
Volume 14: 4 Issues (2002)
Volume 13: 4 Issues (2001)
Volume 12: 4 Issues (2000)
Volume 11: 4 Issues (1999)
Volume 10: 4 Issues (1998)
Volume 9: 4 Issues (1997)
Volume 8: 4 Issues (1996)
Volume 7: 4 Issues (1995)
Volume 6: 4 Issues (1994)
Volume 5: 4 Issues (1993)
Volume 4: 4 Issues (1992)
Volume 3: 4 Issues (1991)
Volume 2: 4 Issues (1990)
Volume 1: 3 Issues (1989)
View Complete Journal Contents Listing