Difference between revisions of "Project 2014-2015-CannonBall/Scrum"
Jump to navigation
Jump to search
| Line 55: | Line 55: | ||
|- |
|- |
||
! scope="row" | 1. The researcher must be able to consult in real time the car's information to make changes if needed. |
! scope="row" | 1. The researcher must be able to consult in real time the car's information to make changes if needed. |
||
| − | | |
+ | | Broadcast the messages with a publish/subscribe protocol |
| 13 |
| 13 |
||
| 1 week |
| 1 week |
||
| Line 62: | Line 62: | ||
| |
| |
||
| − | | |
+ | | Create a Node.js server that will serve the html page to the client |
| 21 |
| 21 |
||
| 1 week |
| 1 week |
||
| Line 69: | Line 69: | ||
| |
| |
||
| − | | |
+ | | Store the car's data in a database |
| 13 |
| 13 |
||
| 1 week |
| 1 week |
||
| Line 76: | Line 76: | ||
| |
| |
||
| − | | |
+ | | Car's data are showed on the html page |
| 21 |
| 21 |
||
| 1 week |
| 1 week |
||
| Line 89: | Line 89: | ||
|- |
|- |
||
| − | | |
+ | | AISheep : facilitates the QRCode-Action matching : |
| − | | |
+ | | Make generic actions for car mouvements |
| 21 |
| 21 |
||
| 1 week |
| 1 week |
||
| Line 97: | Line 97: | ||
| |
| |
||
| − | | |
+ | | Make a grammar syntax for the user and a its parser |
| 13 |
| 13 |
||
| 1 week |
| 1 week |
||
| Line 103: | Line 103: | ||
|- |
|- |
||
| − | | |
+ | | AIRabbit : the car follow a specific QRcode : |
| − | | |
+ | | QRcode recognition |
| 34 |
| 34 |
||
| 1 week |
| 1 week |
||
| Line 111: | Line 111: | ||
| |
| |
||
| − | | |
+ | | Localize the marker in space |
| 21 |
| 21 |
||
| 2 weeks |
| 2 weeks |
||
| Line 118: | Line 118: | ||
| |
| |
||
| − | | |
+ | | Move in the marker direction |
| 21 |
| 21 |
||
| 2 weeks |
| 2 weeks |
||
| Line 124: | Line 124: | ||
|- |
|- |
||
| − | | |
+ | | AICannonBall : the car moves in a QRcode circuit |
| − | | |
+ | | QRcode recognition and interpretation |
| 34 |
| 34 |
||
| 2 weeks |
| 2 weeks |
||
| Line 132: | Line 132: | ||
| |
| |
||
| − | | |
+ | | Avoid the QRcode |
| 21 |
| 21 |
||
| 2 weeks |
| 2 weeks |
||
| Line 139: | Line 139: | ||
! scope="row" | 3. The researcher needs a car simulator to avoid material constraint |
! scope="row" | 3. The researcher needs a car simulator to avoid material constraint |
||
| − | | |
+ | | Make a simulator |
| 21 |
| 21 |
||
| 2 weeks |
| 2 weeks |
||
| Line 146: | Line 146: | ||
| |
| |
||
| − | | |
+ | | Give instructions to the simulator |
| 21 |
| 21 |
||
| 2 weeks |
| 2 weeks |
||
| Line 153: | Line 153: | ||
| |
| |
||
| − | | |
+ | | The simulator reproduce exactly the comportment of the car (real interpretation) |
| 21 |
| 21 |
||
| 1 week |
| 1 week |
||
| Line 160: | Line 160: | ||
| |
| |
||
| − | | |
+ | | Choose a wise graphic library |
| 13 |
| 13 |
||
| 1 week |
| 1 week |
||
| Line 167: | Line 167: | ||
| |
| |
||
| − | | |
+ | | Get the data from the mosquitto broker |
| 13 |
| 13 |
||
| 1 week |
| 1 week |
||
Revision as of 15:39, 10 March 2015
Project Presentation
User stories
1. The researcher must be able to consult in real time the car's information to make changes if needed.
- Broadcast the messages with a publish/subscribe protocol
- Create a Node.js server that will serve the html page to the client
- Store the car's data in a database
- Car's data are showed on the html page
2. The researchers needs several game mode to verify the good behavior of the car (Control Algorithm).
- AISheep : facilitates the QRCode-Action matching :
- Make generic actions for car mouvements
- Make a grammar syntax for the user and a its parser
- AIRabbit : the car follow a specific QRcode :
- QRcode recognition
- Localize the marker in space
- Move in the marker direction
- AICannonBall : the car moves in a QRcode circuit
- QRcode recognition and interpretation
- Avoid the QRcode
3. The researcher needs a car simulator to avoid material constraint
- Make a simulator
- Give instructions to the simulator
- The simulator reproduce exactly the comportment of the car (real interpretation)
- Choose a wise graphic library
- Get the data from the mosquitto broker
- Documentation : facilitate the comprehension and use of the piece of software
- make a documentation of all the actions that are programmed
The developer have to optimize the processing speed to provide a better product experience.
The RICM must master the different technologies to be able to do the project.
The RICM want the car works in order to start the project.
The RICM need to change the Arduino board with a STM32 (more equipped with sensors) to improve the precision of movement
The user should access the web interface through a Rasberry pi Wifi router
The RICM need to develop a car simulator for algorithms testing purposes
| User story | Tasks | Priority | Time | Actors |
|---|---|---|---|---|
| 1. The researcher must be able to consult in real time the car's information to make changes if needed. | Broadcast the messages with a publish/subscribe protocol | 13 | 1 week | |
| Create a Node.js server that will serve the html page to the client | 21 | 1 week | ||
| Store the car's data in a database | 13 | 1 week | ||
| Car's data are showed on the html page | 21 | 1 week | ||
| 2. The researchers needs several game mode to verify the good behavior of the car (Control Algorithm). | ||||
| AISheep : facilitates the QRCode-Action matching : | Make generic actions for car mouvements | 21 | 1 week | |
| Make a grammar syntax for the user and a its parser | 13 | 1 week | ||
| AIRabbit : the car follow a specific QRcode : | QRcode recognition | 34 | 1 week | |
| Localize the marker in space | 21 | 2 weeks | ||
| Move in the marker direction | 21 | 2 weeks | ||
| AICannonBall : the car moves in a QRcode circuit | QRcode recognition and interpretation | 34 | 2 weeks | |
| Avoid the QRcode | 21 | 2 weeks | ||
| 3. The researcher needs a car simulator to avoid material constraint | Make a simulator | 21 | 2 weeks | |
| Give instructions to the simulator | 21 | 2 weeks | ||
| The simulator reproduce exactly the comportment of the car (real interpretation) | 21 | 1 week | ||
| Choose a wise graphic library | 13 | 1 week | ||
| Get the data from the mosquitto broker | 13 | 1 week |
Product backlog
| User story | Priority | Time | Actors |
|---|---|---|---|
| The RICM want the car works in order to start the project. ( 6 ) | 34 | 1 week | |
| The RICM must master the different technologies to be able to do the project. ( 4 ) | 34 | all time | all |
| The researcher must be able to consult in real time the car's information to make changes if needed. ( 5 ) | 21 | 2 weeks | |
| The developer have to optimize the processing speed to provide a better product experience. ( 2 ) | 21 | 1 week | |
| The RICM need to change the Arduino board with a STM32 (more equipped with sensors) to improve the precision of movement ( 7 ) | 21 | 2 weeks | |
| The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 ) | 13 | 3 weeks | |
| The RICM need to develop a car simulator for algorithms testing purposes ( 9 ) | 13 | 3 weeks | |
| The researcher must be able to change the vehicle mode to realize different tests. ( 3 ) | 8 | 3 weeks | |
| The user should access the web interface through a Rasberry pi Wifi router ( 8 ) | 8 | 1 week |
Sprint 1
We need to do the tasks 2, 5 and 6
End Sprint 1
Tasks done : 6 and 5
Problems :
Task 2 : problem with the speed of processing the images.
The frame rate is very slow. The car is moving slowly.
Sprint 2
We need to do the tasks 1, 3 and 7.
We add also the task 2 because this one was not finished in the last sprint.
Task 3 is already working, so we add some changes on this task : The developper can add specific orders to the car with the help of qrCode to realize different tests.
Sprint 3
We need to do the tasks 8 and 9.