A Tool Prototype Supporting Risk-Based Testing in Agile Embedded Software Development

Sammanfattning

Risk-Based Testing is a testing approach in software development that involves identifying, analyzing, controlling, testing, and reporting risks. The strategy provides several benefits and helps companies control risks and manage them effectively. However, the testing strategy may become challenging with new technologies, increased deployment and development of new features, and larger projects. Westermo is a manufacturer and vendor of industrial ethernet networks and data communications products for mission-critical systems in harsh environments. Risk-based testing is a critical component of their software development process to maintain high-quality deployments. Westermo's current approach to documenting and monitoring risks is done through spreadsheets. Over time, as new features are implemented and deployed, these spreadsheets become more complex and challenging to manage. As such, Westermo is currently seeking to replace them with a new risk management tool supporting risk-based testing. In this thesis, I investigated how one can prototype a risk management tool to support the risk-based testing process at Westermo. To this end, a deeper understanding of how current risk-based testing is performed and managed during software development was required. I also had to identify the challenges with the current approach for documenting and monitoring risks and the requirements for a new tool. I investigated these issues using a combination of qualitative research strategies and divided the work into three phases. In the first phase, I observed internal process documentation and three risk analysis workshops with a total of 14 participants held by Westermo. This was followed by interviewing two software developers and one project manager to identify requirements for a new tool. The next step was to develop a prototype and in the final phase, I evaluated the utility of the design with two focus groups for a total of six participants. Ideally, according to the requirements I identified, the risk management tool should facilitate the documenting and monitoring of the risks and provide functions to add, manage and visualize the risks from a larger release perspective and a smaller feature perspective in a simple and efficient manner.