<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-11-21T02:18:03Z</responseDate><request verb="GetRecord" identifier="oai:macsphere.mcmaster.ca:11375/24007" metadataPrefix="dim">https://prod-ms-be.lib.mcmaster.ca/server/oai/request</request><GetRecord><record><header><identifier>oai:macsphere.mcmaster.ca:11375/24007</identifier><datestamp>2026-09-24T18:21:02Z</datestamp><setSpec>com_11375_271</setSpec><setSpec>col_11375_272</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="advisor">Smith, Spencer</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="advisor">Shankar, Sumanth</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author">Srinivasan, Malavika</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department" lang="en_US">Computing and Software</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2019-03-12T19:00:09Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2019-03-12T19:00:09Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued">2018</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/11375/24007</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://doi.org/10.71548/22292</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en_US">Scientific Computing (SC) software has significant societal impact due to its application&#xd;
in safety related domains, such as nuclear, aerospace, military, and medicine.&#xd;
Unfortunately, recent research has shown that SC software does not always achieve&#xd;
the desired software qualities, like maintainability, reusability, and reproducibility.&#xd;
Software Engineering (SE) practices have been shown to improve software qualities,&#xd;
but SC developers, who are often the scientists themselves, often fail to adopt SE&#xd;
practices because of the time commitment.&#xd;
To promote the application of SE in SC, we conducted a case study in which we&#xd;
developed new SC software. The software, we developed will be used in predicting&#xd;
the nature of solidification in a casting process to facilitate the reduction of expensive&#xd;
defects in parts. During the development process, we adopted SE practices and&#xd;
involved the scientists from the beginning. We interviewed the scientists before and&#xd;
after software development, to assess their attitude towards SE for SC.&#xd;
The interviews revealed a positive response towards SE for SC. In the post development&#xd;
interview, scientists had a change in their attitudes towards SE for SC&#xd;
and were willing to adopt all the SE approaches that we followed. However, when it&#xd;
comes to producing software artifacts, they felt overburdened and wanted more tools&#xd;
to reduce the time commitment and to reduce complexity.&#xd;
While contrasting our experience with the currently held perceptions of scientific&#xd;
software development, we had the following observations: a) Observations that&#xd;
agree with the existing literature: i) working on something that the scientists&#xd;
are interested in is not enough to promote SE practices, ii) maintainability is a secondary&#xd;
consideration for scientific partners, iii) scientists are hesitant to learn SE&#xd;
practices, iv) verification and validation are challenging in SC, v) scientists naturally&#xd;
follow agile methodologies, vi) common ground for communication has always been&#xd;
a problem, vii) an interdisciplinary team is essential, viii) scientists tend to choose&#xd;
programming language based on their familiarity, ix) scientists prefer to use plots to&#xd;
visualize, verify and understand their science, x) early identification of test cases is&#xd;
advantageous, xi) scientists have a positive attitude toward issue trackers, xii) SC&#xd;
software should be designed for change, xiii) faking a rational design process for documentation&#xd;
is advisable for SC, xiv) Scientists prefer informal, collegial knowledge&#xd;
transfer, to reading documentation, b) Observations that disagree with the existing&#xd;
literature: i) When unexpected results were obtained, our scientists chose&#xd;
to change the numerical algorithms, rather than question their scientific theories,&#xd;
ii) Documentation of up-front requirements is feasible for SC&#xd;
We present the requirement specification and design documentation for our software&#xd;
as an evidence that with proper abstraction and application of “faked rational&#xd;
design process”, it is possible to document up-front requirements and improve quality.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degreetype" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree" lang="en_US">Master of Science (MSc)</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en_US">en</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Software Quality</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Scientific Computing</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Software Engineering</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">SRS</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Document Driven Design</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Faked Rational Process Design</dim:field>
   <dim:field mdschema="dc" element="subject" lang="en_US">Design for Change</dim:field>
   <dim:field mdschema="dc" element="title" lang="en_US">INVESTIGATING COMMON PERCEPTIONS OF SOFTWARE ENGINEERING METHODS APPLIED TO SCIENTIFIC COMPUTING SOFTWARE</dim:field>
   <dim:field mdschema="dc" element="type" lang="en_US">Thesis</dim:field>
   <dim:field mdschema="others" element="access-status">open.access</dim:field>
</dim:dim></metadata></record></GetRecord></OAI-PMH>