Richard F. Paige
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Previous Organizations / Institutes
The organizations / institutes from the scholar's other articles in the past ten years
Research Subjects
Richard F. Paige has a total of 99 co-authors. Here are the top co-authors by number of shared publications:
- Dimitrios S. Kolovos
University of York, York, United Kingdom
12 shared publications - Alan Wassyng
McMaster University
10 shared publications - Mark Lawford
McMaster University
9 shared publications - Athanasios Zolotas
Department of Computer Science, University of York, York, UK
8 shared publications - Vera Pantelic
McMaster University, McMaster Centre for Software Certification (McSCert), Hamilton, Ontario, Canada
6 shared publications - Sébastien Mosser
McMaster Centre for Software Certification (McSCert), McMaster University, Hamilton, ON, Canada
5 shared publications
Latest Publications
- Open Access
- 4 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 269-273
CARLA Scenario Editor
The CARLA open-source driving simulator is widely used to assess autonomous vehicle behaviour. Specifying a scenario within the CARLA ecosystem involves splitting it across configuration files and behaviour code for each actor. Both must be written by hand and kept consistent, which becomes tedious and error-prone as scenarios grow in complexity. Further, constructing safety-critical non-standard scenarios remains a particular challenge. In this paper, we introduce the CARLA Scenario Editor, a model-driven interactive trajectory generation tool for creating and manipulating safety-critical scenarios for CARLA. Unlike existing CARLA tools, the CARLA Scenario Editor allows users to directly draw and edit multi-vehicle trajectories on a map loaded in CARLA. Scenarios are captured in a single declarative model, from which the tool generates the behaviour tree and configuration that CARLA’s ScenarioRunner module, a scenario execution engine within CARLA’s ecosystem, executes. The combination of direct trajectory editing, freedom from road network constraints, and single-workflow execution streamlines the task of creating diverse scenarios that are difficult to reproduce using CARLA’s default navigation logic and existing tools.
- 4 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 269-273
Open AccessCARLA Scenario Editor
The CARLA open-source driving simulator is widely used to assess autonomous vehicle behaviour. Specifying a scenario within the CARLA ecosystem involves splitting it across configuration files and behaviour code for each actor. Both must be written by hand and kept consistent, which becomes tedious and error-prone as scenarios grow in complexity. Further, constructing safety-critical non-standard scenarios remains a particular challenge. In this paper, we introduce the CARLA Scenario Editor, a model-driven interactive trajectory generation tool for creating and manipulating safety-critical scenarios for CARLA. Unlike existing CARLA tools, the CARLA Scenario Editor allows users to directly draw and edit multi-vehicle trajectories on a map loaded in CARLA. Scenarios are captured in a single declarative model, from which the tool generates the behaviour tree and configuration that CARLA’s ScenarioRunner module, a scenario execution engine within CARLA’s ecosystem, executes. The combination of direct trajectory editing, freedom from road network constraints, and single-workflow execution streamlines the task of creating diverse scenarios that are difficult to reproduce using CARLA’s default navigation logic and existing tools.
- Open Access
- 4 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 813-822
A Model-Based Approach to Security Assessment of Robotic Systems in Healthcare: The Case of a Quadruped Robot
Robotic systems are increasingly being adopted in healthcare environments such as rehabilitation centres, in order to help support overburdened staff by performing more routine tasks. However, deploying a robot in a clinical setting introduces security risks that must be assessed before use. Small facilities rarely have access to the specialised expertise or budget needed to perform a full cybersecurity audit, and existing approaches to security analysis rely heavily on the expert knowledge of the analyst. We propose a model-based security analysis approach that assists non-experts in assessing the security of a deployed system. The approach guides non-experts in creating attack trees using both generic guidewords, as well as guidewords that are derived from system models. Additionally, an LLM is used to act as a security expert team member in the attack tree creation process. We have a security expert create a prompt template as a one-time activity, so that non-experts only need to fill in specific information on the system in order to get an attack tree output by the LLM. We use an example scenario of a Unitree Go2 Air robot dog deployed in a rehabilitation centre to demonstrate various aspects of our approach. We show initial steps towards creating a prompt template for the LLM, and show the usefulness of both the generic and model-based guidewords in creating more relevant attack trees by non-experts.
- 4 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 813-822
Open AccessA Model-Based Approach to Security Assessment of Robotic Systems in Healthcare: The Case of a Quadruped Robot
Robotic systems are increasingly being adopted in healthcare environments such as rehabilitation centres, in order to help support overburdened staff by performing more routine tasks. However, deploying a robot in a clinical setting introduces security risks that must be assessed before use. Small facilities rarely have access to the specialised expertise or budget needed to perform a full cybersecurity audit, and existing approaches to security analysis rely heavily on the expert knowledge of the analyst. We propose a model-based security analysis approach that assists non-experts in assessing the security of a deployed system. The approach guides non-experts in creating attack trees using both generic guidewords, as well as guidewords that are derived from system models. Additionally, an LLM is used to act as a security expert team member in the attack tree creation process. We have a security expert create a prompt template as a one-time activity, so that non-experts only need to fill in specific information on the system in order to get an attack tree output by the LLM. We use an example scenario of a Unitree Go2 Air robot dog deployed in a rehabilitation centre to demonstrate various aspects of our approach. We show initial steps towards creating a prompt template for the LLM, and show the usefulness of both the generic and model-based guidewords in creating more relevant attack trees by non-experts.
- Open Access
- 4 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 783-792
SMDSL: A Domain-Specific Language for Describing Software Platform Migrations
- 4 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 783-792
Open AccessSMDSL: A Domain-Specific Language for Describing Software Platform Migrations
- Open Access
- 4 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 693-702
Privacy Policy Modeling using Metamodel-Guided LLMs
- 4 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 693-702
Open AccessPrivacy Policy Modeling using Metamodel-Guided LLMs
- 8 August 2026
- Published by Springer Nature
- p. 213-227
Chaining Unsafe Control Actions in STPA
- Open Access
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 26-30
Model Cards for Responsible AI: Stop Carding, Start Modelling
- 12 April 2026
- Published by Association for Computing Machinery (ACM)
- p. 26-30
Open AccessModel Cards for Responsible AI: Stop Carding, Start Modelling
- 22 August 2025
- Published by Springer Nature
- p. 18-32
Principled Safety Assurance Arguments
- Open Access
- 22 September 2024
- Published by Association for Computing Machinery (ACM)
- p. 1146-1155
Towards Model Product Lines: Composition of EMF Models
State-of-the-art Product Line Engineering (PLE) tools, while powerful and supporting of significant PLE scenarios, generally lack support for EMF (Eclipse Modeling Framework) models. The limited support is due not to insufficient adoption of EMF, but rather to the absence of a clear semantics for EMF model composition. This paper defines composition semantics for EMF models so that they become first class citizens in PLE, enabling Model Product Lines (MPL). As a result, any EMF language can be used in developing an MPL. By using EMF models directly as features, MPLs can leverage the ecosystem of tools that support EMF, specifically to improve PLE.
- 22 September 2024
- Published by Association for Computing Machinery (ACM)
- p. 1146-1155
Open AccessTowards Model Product Lines: Composition of EMF Models
State-of-the-art Product Line Engineering (PLE) tools, while powerful and supporting of significant PLE scenarios, generally lack support for EMF (Eclipse Modeling Framework) models. The limited support is due not to insufficient adoption of EMF, but rather to the absence of a clear semantics for EMF model composition. This paper defines composition semantics for EMF models so that they become first class citizens in PLE, enabling Model Product Lines (MPL). As a result, any EMF language can be used in developing an MPL. By using EMF models directly as features, MPLs can leverage the ecosystem of tools that support EMF, specifically to improve PLE.
- Open Access
- 22 September 2024
- Published by Association for Computing Machinery (ACM)
- p. 725-734
A Tool For Feature-Requirement Traceability Using Requirement Canvas and Encapsulation
System traceability from requirements to implementation is desirable, often mandatory, for complex and safety-critical system development. However, maintaining traceability documentation can be extremely taxing and tedious through iterative and incremental development life cycles. The problem is further exacerbated when product variability is introduced in the system development. Feature modelling and product line engineering are becoming increasingly common in safety-critical domains such as the automotive domain when manufacturers must consider maintaining documentation for multiple variations of a single vehicle. This problem is made even more complex by the yearly iterations they have on their vehicles. Thus, we introduce CyclicL, a tool for developing, managing, and modelling feature-requirement traceability through iterative and incremental development strategies. CyclicL is designed to facilitate traceability between features and requirements through various product iterations, and multiple incremental feature and requirement changes.
- 22 September 2024
- Published by Association for Computing Machinery (ACM)
- p. 725-734
Open AccessA Tool For Feature-Requirement Traceability Using Requirement Canvas and Encapsulation
System traceability from requirements to implementation is desirable, often mandatory, for complex and safety-critical system development. However, maintaining traceability documentation can be extremely taxing and tedious through iterative and incremental development life cycles. The problem is further exacerbated when product variability is introduced in the system development. Feature modelling and product line engineering are becoming increasingly common in safety-critical domains such as the automotive domain when manufacturers must consider maintaining documentation for multiple variations of a single vehicle. This problem is made even more complex by the yearly iterations they have on their vehicles. Thus, we introduce CyclicL, a tool for developing, managing, and modelling feature-requirement traceability through iterative and incremental development strategies. CyclicL is designed to facilitate traceability between features and requirements through various product iterations, and multiple incremental feature and requirement changes.
- Open Access
- 22 September 2024
- Published by Association for Computing Machinery (ACM)
- p. 1180-1187
Mapping Requirements to Features to Create Traceability in Product Line Models
Developers and engineers have shown the many benefits of feature modelling for identifying reusable software and hardware components across product lines and platforms. However, a gap exists when it comes to identifying reusable products, and requirements across iterations of features. Due to the ambiguous relationship between features and requirements, it can be difficult to determine the boundary between them. We propose a methodology for using features to encapsulate requirements by establishing a clear hierarchy between features and requirements. This will assist feature-requirement traceability tooling and automation development.
- 22 September 2024
- Published by Association for Computing Machinery (ACM)
- p. 1180-1187
Open AccessMapping Requirements to Features to Create Traceability in Product Line Models
Developers and engineers have shown the many benefits of feature modelling for identifying reusable software and hardware components across product lines and platforms. However, a gap exists when it comes to identifying reusable products, and requirements across iterations of features. Due to the ambiguous relationship between features and requirements, it can be difficult to determine the boundary between them. We propose a methodology for using features to encapsulate requirements by establishing a clear hierarchy between features and requirements. This will assist feature-requirement traceability tooling and automation development.