Deriving Contextual Definition and Requirements from Use Cases of Autonomous Drive
| dc.contributor.author | LINDER, JENNIFER | |
| dc.contributor.author | SUBBIAH, PADMINI | |
| dc.contributor.department | Chalmers tekniska högskola / Institutionen för data och informationsteknik | sv |
| dc.contributor.examiner | Berger, Christian | |
| dc.contributor.supervisor | Heyn, Hans-Martin | |
| dc.contributor.supervisor | Knauss, Eric | |
| dc.date.accessioned | 2021-09-07T12:04:57Z | |
| dc.date.available | 2021-09-07T12:04:57Z | |
| dc.date.issued | 2021 | sv |
| dc.date.submitted | 2020 | |
| dc.description.abstract | Context-aware systems, like Advanced Driving Assistance Systems, need to be clearly defined for which context they can operate within i.e., the Operational Design Domain needs to be clearly defined to ensure safe operation. The complex and dy namic environment that those systems operate in makes it challenging to effectively describe the context and the Operational Design Domain. The lack of common def initions and a standard process for deriving contextual definition and requirements from use cases decelerate efficient progress of the development of safe context-aware systems. There is a clear need for established and common definitions for the key concepts: operational design domain and context. Further, requirements for context aware systems need to be efficiently related to the context they are valid for, so safety can be ensured during operation. Based on qualitative research, this study interviewed thirteen automotive experts to explore the definition of the key concepts and the process itself. The study provides qualitative models for definitions of the key concepts: use cases, operational design domain, requirements, and context. Further, the current processes and what works well in the industry are explored. Challenges and improvements for the process of deriving contextual definition and requirements from use cases are presented. The result shows that there is a lack of common process across the industry and there are several different understand ings of the definitions for the key concepts: operational design domain and context. The challenges identified further shows the need for a more established and common process, and highlights certain areas of concern that industries could improve. The major contributions of the thesis are an eminent understanding of the key concepts for development of context-aware systems and the highlighted challenges areas that should be addressed. The results can be used for creating improved processes, practices, or templates for common definitions of operational design domain and context. | sv |
| dc.identifier.coursecode | MPSOF | sv |
| dc.identifier.uri | https://hdl.handle.net/20.500.12380/304078 | |
| dc.language.iso | eng | sv |
| dc.setspec.uppsok | Technology | |
| dc.subject | Operational design domain | sv |
| dc.subject | requirements | sv |
| dc.subject | use cases | sv |
| dc.subject | context | sv |
| dc.subject | contextual definition | sv |
| dc.subject | autonomous driving | sv |
| dc.subject | qualitative research | sv |
| dc.subject | process | sv |
| dc.subject | requirements engineering | sv |
| dc.subject | thesis | sv |
| dc.title | Deriving Contextual Definition and Requirements from Use Cases of Autonomous Drive | sv |
| dc.type.degree | Examensarbete för masterexamen | sv |
| dc.type.uppsok | H |