Alan Wassyng
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Subjects
Alan Wassyng has a total of 44 co-authors. Here are the top co-authors by number of shared publications:
- Mark Lawford
McMaster University
13 shared publications - Richard F. Paige
McMaster University
10 shared publications - Nicholas Annable
McMaster University
4 shared publications - Thomas Chiang
Computing and Software, McSCert, McMaster University, Hamilton, ON, Canada
4 shared publications - Vera Pantelic
McMaster University, McMaster Centre for Software Certification (McSCert), Hamilton, Ontario, Canada
4 shared publications - Spencer Deevy
McMaster University
3 shared publications
Latest Publications
- 8 August 2026
- Published by Springer Nature
- p. 213-227
Chaining Unsafe Control Actions in STPA
- 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. 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.
- 9 September 2024
- Published by Springer Nature
- p. 134-149
Comprehensive Change Impact Analysis Applied to Advanced Automotive Systems
- 9 September 2024
- Published by Springer Nature
- p. 134-149
Comprehensive Change Impact Analysis Applied to Advanced Automotive Systems
- 14 September 2023
- Published by Springer Nature
- p. 26-31
Assurance Cases for Timing Properties of Automotive TSN Networks
- 14 September 2023
- Published by Springer Nature
- p. 26-31
Assurance Cases for Timing Properties of Automotive TSN Networks
- 14 September 2023
- Published by Springer Nature
- p. 5-14
Using Assurance Cases to Prevent Malicious Behaviour from Targeting Safety Vulnerabilities
- 14 September 2023
- Published by Springer Nature
- p. 5-14
Using Assurance Cases to Prevent Malicious Behaviour from Targeting Safety Vulnerabilities
- 11 September 2023
- Published by Springer Nature
- p. 25-38
Redesigning Medical Device Assurance: Separating Technological and Clinical Assurance Cases
- 11 September 2023
- Published by Springer Nature
- p. 25-38
Redesigning Medical Device Assurance: Separating Technological and Clinical Assurance Cases
- 16 June 2023
- Published by Springer Nature in Software and Systems Modeling
- Vol. 22 (5) , 1713-1732
Repository mining for changes in Simulink and Stateflow models
- 16 June 2023
- Published by Springer Nature in Software and Systems Modeling
- Vol. 22 (5) , 1713-1732
Repository mining for changes in Simulink and Stateflow models
- Open Access
Separating Technological and Clinical Safety Assurance for Medical Devices
The safety and clinical effectiveness of medical devices are closely associated with their specific use in clinical treatments. Assuring safety and the desired clinical effectiveness is challenging. Different people may react differently to the same treatment due to variability in their physiology and genetics. Thus, we need to consider the outputs and behaviour of the device itself as well as the effect of using the device to treat a wide variety of patients. High-intensity focused ultrasound systems and radiation therapy machines are examples of systems in which this is a primary concern. Conventional monolithic assurance cases are complex, and this complexity affects our ability to address these concerns adequately. Based on the principle of separation of concerns, we propose separating the assurance of the use of these types of systems in clinical treatments into two linked assurance cases. The first assurance case demonstrates the safety of the manufacturer's device independent of the clinical treatment. The second demonstrates the safety and clinical effectiveness of the device when it is used in a specific clinical treatment. We introduce the idea of these separate assurance cases, and describe briefly how they are separated and linked.
Open AccessSeparating Technological and Clinical Safety Assurance for Medical Devices
The safety and clinical effectiveness of medical devices are closely associated with their specific use in clinical treatments. Assuring safety and the desired clinical effectiveness is challenging. Different people may react differently to the same treatment due to variability in their physiology and genetics. Thus, we need to consider the outputs and behaviour of the device itself as well as the effect of using the device to treat a wide variety of patients. High-intensity focused ultrasound systems and radiation therapy machines are examples of systems in which this is a primary concern. Conventional monolithic assurance cases are complex, and this complexity affects our ability to address these concerns adequately. Based on the principle of separation of concerns, we propose separating the assurance of the use of these types of systems in clinical treatments into two linked assurance cases. The first assurance case demonstrates the safety of the manufacturer's device independent of the clinical treatment. The second demonstrates the safety and clinical effectiveness of the device when it is used in a specific clinical treatment. We introduce the idea of these separate assurance cases, and describe briefly how they are separated and linked.