Tensions Between Scientific Programming and the Scientific Method

dc.contributor.authorWidder, David Gray
dc.date.accessioned2017-10-12T14:38:49Z
dc.date.available2017-10-12T14:38:49Z
dc.date.issued2017
dc.description65 pages. A thesis presented to the Department of Computer and Information Science and the Clark Honors College of the University of Oregon in partial fulfillment of the requirements for degree of Bachelor of Science, Spring 2017
dc.description.abstractThis thesis evaluates eleven scientific programmers against six best practices. The six best practices extracted from literature are: 1) the presence of a Distinct Design Phase, 2) Documentation, 3) the Use of Existing, Trustworthy Code, 4) the Use of Formal Version Control, 5) a Testing procedure, and 6) the Public Release of Code. A survey and interview were conducted on eleven participants to produce a case study on each participant’s purpose of their code, their self identified process difficulties, their tool use, their self identified areas for growth, and their perceptions of the importance of programming to their discipline. An evaluation of the extent to which the six best practices were followed is then presented. To conclude, three recommendations on how to increase adherence to best practices are presented: education about existing processes and tools, the adaption of existing processes and tools, and incentivizing adherence to best practices.en_US
dc.identifier.urihttps://hdl.handle.net/1794/22906
dc.language.isoen_US
dc.publisherUniversity of Oregon
dc.rightsCreative Commons BY-NC-ND 4.0-US
dc.subjectScientific methoden_US
dc.subjectScientific programmingen_US
dc.subjectSoftware engineeringen_US
dc.subjectBest practicesen_US
dc.subjectEnd user programmingen_US
dc.titleTensions Between Scientific Programming and the Scientific Method
dc.typeThesis/Dissertation

Files

Original bundle

Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Final_thesis_Widder.pdf
Size:
670.68 KB
Format:
Adobe Portable Document Format