<?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-21T03:27:40Z</responseDate><request verb="GetRecord" identifier="oai:macsphere.mcmaster.ca:11375/33068" metadataPrefix="dim">https://prod-ms-be.lib.mcmaster.ca/server/oai/request</request><GetRecord><record><header><identifier>oai:macsphere.mcmaster.ca:11375/33068</identifier><datestamp>2026-09-24T03:32:12Z</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">Wassyng, Alan</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="advisor">Lawford, Mark</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author">Annable, Nicholas</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="department">Software Engineering</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2026-04-22T20:20:34Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued">2026</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://hdl.handle.net/11375/33068</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://doi.org/10.71548/18128</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract">Safety-critical systems must be shown to be safe before their deployment. It has become common to argue that a system is safe using an assurance case, and in many domains assurance cases are recommended or required due to the numerous benefits they provide. In the current state of the art, practitioners often develop assurance cases in a case-by-case way guided by their own expertise and experience, with little available in terms of systematic methods or principles to assist them. This makes it difficult to produce rigorous and convincing assurance cases, and is even more difficult when doing so for large-scale and complex modern safety-critical systems. Recently, the Workflow+ framework has provided a way to capture information necessary for safety assurance in a very detailed, traceable and consistent way. In this thesis, we make the case that pairing such models with a well-articulated notion of safety assurance case and safety argument enables a systematic approach to safety assurance. This is achieved by defining several principles for safety assurance cases and arguments that define the task well enough that it can be made methodical and semi-automatable. This is illustrated using Workflow+, but the concept and principles are general, and gives a way to address the long-standing issues of uncertainty and variability that cause ad-hoc, case-by-case safety assurance arguments.</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degreetype">Thesis</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="degree">Doctor of Philosophy (PhD)</dim:field>
   <dim:field mdschema="dc" element="rights" lang="en">Attribution 4.0 International</dim:field>
   <dim:field mdschema="dc" element="rights" qualifier="uri">http://creativecommons.org/licenses/by/4.0/</dim:field>
   <dim:field mdschema="dc" element="subject">Assurance Case</dim:field>
   <dim:field mdschema="dc" element="subject">Safety Assurance</dim:field>
   <dim:field mdschema="dc" element="subject">Model-Driven Engineering</dim:field>
   <dim:field mdschema="dc" element="title">Generating Assurance Cases from Workflow+ Models</dim:field>
   <dim:field mdschema="dc" element="type" lang="en">Thesis</dim:field>
   <dim:field mdschema="others" element="access-status">open.access</dim:field>
</dim:dim></metadata></record></GetRecord></OAI-PMH>