Strategies for enabling software reuse within the earth science community

Samadi, Shahin; Almaeh, N.; Wolfe, Robert E.; Olding, S. W.; Isaac, D.

doi:10.1109/igarss.2004.1370796

Cited by 6 publications

(18 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The next section will discuss the team's findings in comparison to several similar types of research [2,11,12].…”

Section: Summary Of Findingsmentioning

confidence: 97%

“…Heritage software Software reused from a previously flown or currently in-space mission. Horizontal reuse As defined by Samadi et al in [2], horizontal reuse represents the reuse of software components across a broad range of application domains. Independent assessment (IA) A subset of IV&V tasks performed on a mission to determine its viability and predict its risk.…”

Section: Reuse Terminologymentioning

confidence: 99%

“…Verification Confirmation by examination and the provision of objective evidence that specified requirements objectives have been fulfilled[13]. Vertical reuse As defined by Samadi et al in [2], vertical reuse represents reuse of software components within a specific domain. White-box reuse Modification and integration of software components into new applications.…”

Section: Reuse Terminologymentioning

confidence: 99%

“…• Section 6 compares the research approach and findings with three similar studies conducted by Lynex and Layzell [11], Morisio et al [12], and Samadi et al [2]. • Section 7 explains the various forms of reuse encountered throughout the study in terms of distinct genealogies and introduces the concept of context variables and their impact on software reuse.…”

mentioning

confidence: 96%

“…Software reuse, which is loosely defined by Samadi et al in [2] as the "reapplication of various kinds of knowledge about one system to another system in order to reduce the effort of developing and maintaining that system," is an attempt by software engineers to emulate and exploit the benefits enjoyed by component reuse in the physical realm.…”

mentioning

confidence: 99%

See 4 more Smart Citations

A study of software reuse in NASA legacy systems

Orrego

Mundy

2007

Innovations Syst Softw Eng

View full text Add to dashboard Cite

Software reuse is regarded as a highly important factor in reducing development overheads for new software projects; however, much of the literature is concerned with cost and labor savings that reuse brings to industrial software development and little is known about the inherent risks associated with reuse, particularly in the case of mission and safety-critical software systems. We present the preliminary findings of a research project geared toward assessing the impact of risk in National Aeronautics and Space Administration (NASA) legacy software in flight control systems. We introduce the concept of context variables and the impact they have on reuse within these legacy systems as well as the genealogy classification models, which provide a simple, concise method of mapping reuse between families of software projects.

show abstract

“…The next section will discuss the team's findings in comparison to several similar types of research [2,11,12].…”

Section: Summary Of Findingsmentioning

confidence: 97%

Section: Reuse Terminologymentioning

confidence: 99%

Section: Reuse Terminologymentioning

confidence: 99%

mentioning

confidence: 96%

mentioning

confidence: 99%

See 3 more Smart Citations

A study of software reuse in NASA legacy systems

Orrego

Mundy

2007

Innovations Syst Softw Eng

View full text Add to dashboard Cite

show abstract

Claims about the use of software engineering practices in science: A systematic literature review

Heaton

Carver

2015

Information and Software Technology

View full text Add to dashboard Cite

a b s t r a c tContext: Scientists have become increasingly reliant on software in order to perform research that is too timeintensive, expensive, or dangerous to perform physically. Because the results produced by the software drive important decisions, the software must be correct and developed efficiently. Various software engineering practices have been shown to increase correctness and efficiency in the development of traditional software. It is unclear whether these observations will hold in a scientific context.Objective: This paper evaluates claims from software engineers and scientific software developers about 12 different software engineering practices and their use in developing scientific software. Method:We performed a systematic literature review examining claims about how scientists develop software. Of the 189 papers originally identified, 43 are included in the literature review. These 43 papers contain 33 different claims about 12 software engineering practices. Results:The majority of the claims indicated that software engineering practices are useful for scientific software development. Every claim was supported by evidence (i.e. personal experience, interview/survey, or case study) with slightly over half supported by multiple forms of evidence. For those claims supported by only one type of evidence, interviews/surveys were the most common. The claims that received the most support were: "The effectiveness of the testing practices currently used by scientific software developers is limited" and "Version control software is necessary for research groups with more than one developer." Additionally, many scientific software developers have unconsciously adopted an agile-like development methodology.Conclusion: Use of software engineering practices could increase the correctness of scientific software and the efficiency of its development. While there is still potential for increased use of these practices, scientific software developers have begun to embrace software engineering practices to improve their software. Additionally, software engineering practices still need to be tailored to better fit the needs of scientific software development.

show abstract

Software search is not a science, even among scientists: A survey of how scientists and engineers find software

Hucka

Graham

2018

Journal of Systems and Software

View full text Add to dashboard Cite

a b s t r a c tImproved software discovery is a prerequisite for greater software reuse: after all, if someone cannot find software for a particular task, they cannot reuse it. Understanding people's approaches and preferences when they look for software could help improve facilities for software discovery. We surveyed people working in several scientific and engineering fields to better understand their approaches and selection criteria. We found that even among highly-trained people, the rudimentary approaches of relying on general Web searches, the opinions of colleagues, and the literature were still the most commonly used. However, those who were involved in software development differed from nondevelopers in their use of social help sites, software project repositories, software catalogs, and organization-specific mailing lists or forums. For example, software developers in our sample were more likely to search in community sites such as Stack Overflow even when seeking ready-to-run software rather than source code, and likewise, asking colleagues was significantly more important when looking for ready-to-run software. Our survey also provides insight into the criteria that matter most to people when they are searching for readyto-run software. Finally, our survey also identifies some factors that can prevent people from finding software.

show abstract

Strategies for enabling software reuse within the earth science community

Cited by 6 publications

References 4 publications

A study of software reuse in NASA legacy systems

A study of software reuse in NASA legacy systems

Claims about the use of software engineering practices in science: A systematic literature review

Software search is not a science, even among scientists: A survey of how scientists and engineers find software

Contact Info

Product

Resources

About