Planning Group 6

To go back to the mainpage: PRE2017 3 Groep6.

---

Planning

During the first week of the project, every team member dove into locating and reading online articles and other literature that could be relevant for our research, and a clear planning was yet to be made. After having conducted our research, we had a better idea regarding what we wanted to do and accomplisch in the time we have for this project. There are going to be two deliverables; a literature study, and alongside that, a computer model based on existing technology and information.
In order to create our planning, we sat down together and worked through all the available todo's, assigning them to one or more team members in the process.
Also, to ensure that no important requirements are missed, each team member will focus on a specific part of the process to write down requirements for. Below is the detailed planning for the entire team.

Week 1
All:

• Choosing subject
  
• Each team member will find 5 relevant research papers and makes a summary of those articles
  

Week 2

Daan:

• Making minutes.
  
• Answering coaching questions.
  
• Make planning.
  

Bart:

• Make 1 user stories.
  
• Make a page on the wiki for the user stories.
  
• Put the user story on the wikipage
  

Chiel:

• Do research about safety and accidents
  

Patrick:

• Make page for requirement on the wike. Start with writing requirements.
  

Berdine:

• Make a state of the art page.
  
• Combine summary to one story for the state of the art page.
  

Week 3

Berdine:

• Making minutes.
  
• Answering coaching questions.
  
• Make more detailed planning.
  
• Finish state of the art page.
  
• Look for rules an regulation for mobility scooter.
  
• Put requirement that come from rules and regulations on requirement page.
  

Bart:

• Make a second user story.
  
• Make first users story more detailed.
  
• Look for requirement in user stories an put them on the requirement page.
  

Daan:

• Make requirements about how communication between user and system should be set up.
  
• Think about how the system communicates with the user when it needs their assistance.
  
• Think about how the user can ask for external support in case the system crashes or malfunctions.
  

Chiel:

• Make requirement about safety.
  

Patrick:

• Make a fancy chart about the planning.
  
• Make requirement about smart mobility.
  
• Make requirement about physical.
  
• Make requirements about navigation.
  

Week 4
Bart:

• Making minutes.
  
• Answering coaching questions.
  
• Update planning.
  
• Find solution for requirement that have to do with navigation.
  

Daan:

• Find solution for requirements communication between user and system.
  
• Research into sensor fusion.
  

Berdine:

• Find solution for requirement that have to do with rules and regulations.
  

Chiel:

• Find solution for requirement that have to do with safety.
  

Patrick:

• Find solution for requirement that have to do with smart mobility.
  
• Find solution for requirement that have to do with physical.
  

Week 5
Patrick:

• Making minutes.
  
• Answering coaching questions.
  
• Work out important field requirement in detail (Motion planning and/or footpath detection, for example)

Daan:

• Update planning.
  
• Work out a specific sensor fusion in detail (pick the sensors)

Bart:

• Work out important field requirement in detail
• Look for base model to work with in AutoCad

Chiel:

• Work out important field requirement in detail (center of gravity with physical reasoning/calculations, for example)

All:

• Translate solutions to input for model (This is about the solutions each member found for their specific research question)
  
• Ask each other critical questions in order to have an answer ready for the teachers
• Show that our scooter actually does drive safely, by creating testcases with certain velocities, models (pedestrians) and calculating the results

Week 6
Chiel:

• Making minutes.
  
• Answering coaching questions.
  
• Update planning.
  

Berdine:

• Cleaning oud an proofreading wiki.
  

Patrick:

• Fix layout issues with wiki.
  

Daan:

• Make presentation.
  

Bart:

• Make model.
  

Week 7
All:

• Give presentation.
  

Meetings and Notes

Week 1

• 7 February 12.40-13.30 Group meeting without tutors
  

Week 2

• 19 February 10.40-12.00 Meeting with tutors
  
• 19 February 12.00-13.30 Group meeting without tutors
  

Week 3

• 26 February 10.40-12.00 Meeting with tutors
  
• 26 February 12.00-13.30 Group meeting without tutors
  

Week 4

• 5 March 10.40-12.00 Meeting with tutors
  
• 5 March 12.00-13.30 Group meeting without tutors
  

Week 5

• 12 March 10.40-12.00 Meeting with tutors
  
• 12 March 12.00-13.30 Group meeting without tutors
  
• TODO:
  • Per individueel kopje de belangrijkste requirement(s) in DETAIL uitwerken (met feiten, cijfers en berekeningen)
  • Gewenst zwaartepunt berekenen (natuurkundige uitwerking)
    • Modellen maken voor de berekeningen
  • Welke sensorfusie willen we precies gaan doen? Deze in detail uitwerken (geen mankracht om alle sensoren te doen)
    • Voorbeeld: camera + lidar
  • Navigatie requirement kiezen om zorgvuldig uit te werken
    • Voorbeeld: motionplanning en/of detectie voor voetpad(en)
  • Aantonen dat onze scooter wel echt veilig rijdt
    • Dit d.m.v. testcases
  • Onderling kritische vragen stellen om antwoord paraat te hebben bij vraag docent
    • Voorbeeld: hoe draagt deze uitwerking bij aan het einddoel van het project? Wees kritisch en duidelijk

Week 6

• 19 March 09.30-10.40 Group meeting preceding final tutor meeting
  
• 19 March 10.40-12.00 Meeting with tutors
  
• 19 March 12.00-13.30 Group meeting without tutors
  

Week 7

• 26 March final presentation