Non-functional requirements testing in the Medtech industry
| dc.contributor.author | Martinsson, Marcus | |
| dc.contributor.author | Nordeman, Per | |
| dc.contributor.department | Chalmers tekniska högskola / Institutionen för matematiska vetenskaper | sv |
| dc.contributor.examiner | Lundh, Torbjörn | |
| dc.contributor.supervisor | Torkar, Richard | |
| dc.contributor.supervisor | Stein, Carl | |
| dc.date.accessioned | 2021-09-13T13:16:52Z | |
| dc.date.available | 2021-09-13T13:16:52Z | |
| dc.date.issued | 2021 | sv |
| dc.date.submitted | 2020 | |
| dc.description.abstract | Although software testing is widely used during the software development phase of medical technologies (Medtech), there is no common ground regarding identification, separation, and testing of functional and non-functional requirements within the development cycle. The objective of this thesis was to implement a taxonomy for non-functional requirements within the Medtech industry, and to build an automated test framework including tests for non-functional requirements linked to user experience. The methodology used for the thesis was action research, iterated through a research, construction and a simulation phase for each test. Information gathered regarding test development was collected through interviews, documents, experience, and prior work. A taxonomy for identifying, separating, and prioritizing software requirements was developed. Further, an automated test framework was developed which included automated tests evaluating the reliability, performance, scalability, and portability of the software system. Two reliability tests were developed to evaluate the stability and placement of medical tools within the simulation. An additional test was developed evaluating the performance, scalability, and portability of the software system. It was shown that automated tests can detect and notify software developers and project managers with information regarding non-functional requirements of their software system. Although non-functional requirements often can be difficult to comprehend, the result within this thesis suggests that there is great value in identifying, classifying, and testing non-functional requirements within the Medtech software development cycle to secure a satisfied end-user. | sv |
| dc.identifier.coursecode | MVEX03 | sv |
| dc.identifier.uri | https://hdl.handle.net/20.500.12380/304112 | |
| dc.language.iso | eng | sv |
| dc.setspec.uppsok | PhysicsChemistryMaths | |
| dc.subject | Requirements engineering, Non-functional requirements, Taxonomy, Software development, Medtech software, Automated testing, User experience | sv |
| dc.title | Non-functional requirements testing in the Medtech industry | sv |
| dc.type.degree | Examensarbete för masterexamen | sv |
| dc.type.uppsok | H | |
| local.programme | Biomedical engineering (MPBME), MSc |