Eine Plattform für die Wissenschaft: Bauingenieurwesen, Architektur und Urbanistik
Eine Plattform für die Wissenschaft: Bauingenieurwesen, Architektur und Urbanistik
D2.1 Specification of Use Cases
The purpose of this deliverable is to set the scene, where the project will actively contribute. It begins with an analysis of the current status of the four test sites (Austria, Germany, Italy, and cross border site), and goes from the defined use case instances (called “scenarios - SCN”) to the definition of functional and non-functional requirements. The defined requirements will serve as an input to the following project work such as specification and definition of its architecture, and subsequently to the development work. ICT4CART use cases were carefully selected based on specific criteria. These are: i) alignment with EU policy and relevant forums and initiatives, ii) significant impact on connected automation, iii) the ability to generalise on the results (applicable in other scenarios and environments), and iv) interest to the consortium members and relevance to their industrial roadmaps. Moreover, these use cases are serving one of the main targets of the project, which is to show that the proposed and implemented ICT infrastructure architecture is flexible and adaptable and can serve the needs of various automated driving use cases (safety critical, comfort, etc.) with different requirements, across test sites with different capabilities. The ICT4CART use cases can be global or local, can be associated with network slices or not, can use Edge Clouds/Computing or not, can use different radio technologies and can be used everywhere (roaming aspect). They also consider mechanisms for cybersecurity, authentication, integrity and privacy. The following Use Cases (UCs) will be implemented to validate and demonstrate ICT4CART developments: UC1) Smart Parking & IoT services, UC2) Dynamic adaptation of vehicle automation level based on infrastructure information, UC3) Intersection crossing (urban) & lane merging (highway) – “virtual mirror”, UC4) Cross Border Interoperability. For each of the UCs, the project focuses on several representative traffic situations, called “scenarios” hereinafter, which demonstrate the influence of the project outcome to the most critical traffic conditions in matters of safety and performance. For each scenario, the realisation prerequisites, the required physical and digital equipment, are considered. Throughout that process, a comparison of the current technological level with the ICT4CART potential upgrades is inevitable. Moreover, considering the story (the sequence of actions) for each one of the scenarios, a concise list of the functional requirements is completed. The way that the ICT4CART components should perform and interact with each other in order to provide the specific functionalities can then be defined. The outcome is a catalogue of non-functional requirements. In this document, the term non-functional requirements, is used to describe the requirements that ensure the correct operation of the ICT4CART components in the system, e.g., performance, operation conditions, scalability requirements etc. Ensuring that the scenario based catalogue of requirements is concise, a mapping can then be performed with the ICT4CART components of a high-level architecture in WP3.
D2.1 Specification of Use Cases
The purpose of this deliverable is to set the scene, where the project will actively contribute. It begins with an analysis of the current status of the four test sites (Austria, Germany, Italy, and cross border site), and goes from the defined use case instances (called “scenarios - SCN”) to the definition of functional and non-functional requirements. The defined requirements will serve as an input to the following project work such as specification and definition of its architecture, and subsequently to the development work. ICT4CART use cases were carefully selected based on specific criteria. These are: i) alignment with EU policy and relevant forums and initiatives, ii) significant impact on connected automation, iii) the ability to generalise on the results (applicable in other scenarios and environments), and iv) interest to the consortium members and relevance to their industrial roadmaps. Moreover, these use cases are serving one of the main targets of the project, which is to show that the proposed and implemented ICT infrastructure architecture is flexible and adaptable and can serve the needs of various automated driving use cases (safety critical, comfort, etc.) with different requirements, across test sites with different capabilities. The ICT4CART use cases can be global or local, can be associated with network slices or not, can use Edge Clouds/Computing or not, can use different radio technologies and can be used everywhere (roaming aspect). They also consider mechanisms for cybersecurity, authentication, integrity and privacy. The following Use Cases (UCs) will be implemented to validate and demonstrate ICT4CART developments: UC1) Smart Parking & IoT services, UC2) Dynamic adaptation of vehicle automation level based on infrastructure information, UC3) Intersection crossing (urban) & lane merging (highway) – “virtual mirror”, UC4) Cross Border Interoperability. For each of the UCs, the project focuses on several representative traffic situations, called “scenarios” hereinafter, which demonstrate the influence of the project outcome to the most critical traffic conditions in matters of safety and performance. For each scenario, the realisation prerequisites, the required physical and digital equipment, are considered. Throughout that process, a comparison of the current technological level with the ICT4CART potential upgrades is inevitable. Moreover, considering the story (the sequence of actions) for each one of the scenarios, a concise list of the functional requirements is completed. The way that the ICT4CART components should perform and interact with each other in order to provide the specific functionalities can then be defined. The outcome is a catalogue of non-functional requirements. In this document, the term non-functional requirements, is used to describe the requirements that ensure the correct operation of the ICT4CART components in the system, e.g., performance, operation conditions, scalability requirements etc. Ensuring that the scenario based catalogue of requirements is concise, a mapping can then be performed with the ICT4CART components of a high-level architecture in WP3.
D2.1 Specification of Use Cases
Panagiotis Lytrivis (Autor:in) / Vasilis Sourlas (Autor:in) / Visintainer Filippo (Autor:in) / Amendola Danilo (Autor:in) / Test side leaders and SCN leaders (Autor:in)
15.03.2019
oai:zenodo.org:6372539
Paper
Elektronische Ressource
Englisch
DDC:
720