Canada Spends Logo

Explore our Budget 2026 analysis

Grant: Collaborative Research and Development Grants

McMaster University

$6,250.00

A literate process for the certification of scientific and engineering software

FY 2014-15

Summary
Our principal objective is to develop certifiable scientific and engineering software. One problem with current processes is that there is considerable duplication between software artifacts, as well as a definite lack of traceability between these artifacts. We believe that we can solve both of these problems by adapting the ideas behind Literate Programming (LP), in which programs are written first with the goal of being understandable to human readers, rather than being artificially constrained by the ordering and formatting required by conventional computer code.In classical LP, from literate source files two items are extracted: the user readable documentation and the computer readable source code. Our proposed literate process will extend this idea so that ""source"" files can be processed in multiple ways to extract not just the code and its explanation, but also the requirements specification, the Application Program Interface (API), the test cases, the test report and the build instructions. This will allow us to share the considerable amount of information in common between all these software artifacts, thus decreasing duplication. At the same time traceability is increased, since this shared information will be extracted into the correct artifacts.To develop, motivate and document the literate process we will use a case study of code generation for a family of ordinary differential equation (ODE) solvers. In the family approach code is generated taking into account the commonalities in the family, but distinguishing each member based on its variabilities. The code generation approach facilitates reuse of certified components, leading to quick certification. The family of ODE solvers will be put in the context of nuclear safety analysis. In particular, an example will be developed that solves a system of ODEs as part of the thermal analysis of fuel pins in a nuclear reactor.
Program
Collaborative Research and Development Grants
Location
Ontario, Canada
Recipient Type
Academia
Type
Grant
Source
NSERC's Awards Data

As published

Application id
447544-2013
Name nom
Smith, Spencer
Department département
Computing and Software
Organization id
27
Institution établissement
McMaster University
Province en
Ontario
Province fr
Ontario
Country en
CANADA
Country fr
CANADA
Fiscal year exercice financier
2014
Competition year année de concours
2013
Award amount
6250
Program id
CRDPJ
Program name en
Collaborative Research and Development Grants
Program name fr
Subventions de recherche et développement coopérative
Group en
Research partnerships programs
Group fr
Programmes de partenariat
Committee code
96
Committee name en
RPP Internal Decision Cttee
Committee name fr
Cté de décision interne - PPR
Area of application code
302
Area of application group en
Energy resources
Area of application group fr
Ressources d'énergie
Area of application en
Nuclear energy
Area of application fr
Énergie nucléaire
Research subject code
2706
Research subject group en
Information technology
Research subject group fr
Technologie de l'information
Research subject en
Software engineering
Research subject fr
Génie logiciel
Partie
1
Nb partie
5
Application title
A literate process for the certification of scientific and engineering software
Keyword
NSERC
Application summary
Our principal objective is to develop certifiable scientific and engineering software. One problem with current processes is that there is considerable duplication between software artifacts, as well as a definite lack of traceability between these artifacts. We believe that we can solve both of these problems by adapting the ideas behind Literate Programming (LP), in which programs are written first with the goal of being understandable to human readers, rather than being artificially constrained by the ordering and formatting required by conventional computer code.In classical LP, from literate source files two items are extracted: the user readable documentation and the computer readable source code. Our proposed literate process will extend this idea so that ""source"" files can be processed in multiple ways to extract not just the code and its explanation, but also the requirements specification, the Application Program Interface (API), the test cases, the test report and the build instructions. This will allow us to share the considerable amount of information in common between all these software artifacts, thus decreasing duplication. At the same time traceability is increased, since this shared information will be extracted into the correct artifacts.To develop, motivate and document the literate process we will use a case study of code generation for a family of ordinary differential equation (ODE) solvers. In the family approach code is generated taking into account the commonalities in the family, but distinguishing each member based on its variabilities. The code generation approach facilitates reuse of certified components, leading to quick certification. The family of ODE solvers will be put in the context of nuclear safety analysis. In particular, an example will be developed that solves a system of ODEs as part of the thermal analysis of fuel pins in a nuclear reactor.