PRE2017 3 Groep16: Difference between revisions

From Control Systems Technology Group
Jump to navigation Jump to search
No edit summary
No edit summary
Line 79: Line 79:
Creating own ideas/mockups
Creating own ideas/mockups
Testing mockups
Testing mockups
[[Coaching Questions Group 16]]

Revision as of 11:08, 16 February 2018

Introduction

YO


USE Analysis

Week 1

Rivelino Wattimena (0967390) Jeroen van Meurs - 0946114 Tim Driessen (0954562) Jorik Mols (0851883) Lisanne Willems (0954451)


Subject Objectives Users State of the art (25 artikelen) approach planning milestones deliverables who will do what?

Subject Interaction between pedestrians and autonomous vehicles


Problem statement: Imagine a world in which autonomous vehicles fill the streets. For a lot of people this would be ideal trafic control. However, no human control over the car brings some setbacks. One of these setbacks is interaction with pedestrians that are crossing the road. In today's traffic, a car driver will usually wave at the pedestrians, to show that they have been seen and they can cross the road. However, with autonomous self driving cars, no humans are in control of the vehicle. Then how do pedestrians know that the vehicle has seen them? Also the opposite case is important, how do autonomous vehicles know the pedestrians have seen them? This human-vehicle interaction problem is of great importance for the general safety in trafic. For this problem, we will try to come up with some solutions.

Objectives: Create a safer environment An interaction between autonomous vehicles and pedestrians that increases safety (for all involved) in traffic.

Users: Pedestrians, autonomous vehicle,

Society:


Enterprise:


Approach: In this project we will determine the problems pedestrians face when crossing streets where autonomous vehicles drive and the other way around. Then we will look at numerous stakeholders and possible solutions. After that, questionnaires/interviews will be held with stakeholders to determine the needs of a system that offers a solution to the defined problem. After this, a design for our solution will be made and a prototype will show some of the working principles that need to be proven in order to give credibility to the final design.


Define the problem. Start with literature research; what has been done and how has it been done, what can work. Can we also use the available research in our project? Improvements? Define User, Society and Enterprise. Define the needs, get needs from users (by questionnaire for example). Design based on these needs. Create Prot(H)ot(H)ype. Reflect on the prototype. Improvements on prototype Future research, what can still be done on this project (which falls outside of the scope of this course) (Team motto #BoostTheTeamSpirit): Goan mee die waggie (als ie oew zie)


Deliverables We will write our findings in a report style on the wiki. We would like to deliver a prototype near the end of this project.


Who will do what

For the first part of the project we will work together as much as possible so everybody has the same basis. In a later stage of the project we will split the work a little bit more. Since we have a student from software science, he will take the lead in the coding work. The (fietsenmakers) will take the lead in the hardware creation.

Problem description: Tim Driessen USE aspects: Jorik Mols, Jeroen van Meurs State of the art research: Rivelino Wattimena, Lisanne Willems, Tim Driessen

Creating a questionaire Creating own ideas/mockups Testing mockups

Coaching Questions Group 16