air - User contributions [en]

Project 2014-2015-CannonBall/Scrum

2015-03-10T13:49:06Z

Hugo.Rodrigues-Pereira-Anselmo:

=Project Presentation=
[http://air.imag.fr/index.php/CannonBall_de_voitures_autonomes CannonBall]

=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

=Product backlog=
{|class="wikitable alternance"
|-
!scope="col" width="40%"| User story
!scope="col"| Tasks
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
! 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
| 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
|
|-

! scope="row" | 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
|
|-

! scope="row" | 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
|
|-

|}

=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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-10T13:43:21Z

Hugo.Rodrigues-Pereira-Anselmo: /* User stories */

=Project Presentation=
[http://air.imag.fr/index.php/CannonBall_de_voitures_autonomes CannonBall]

=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

{|class="wikitable alternance"
|-
!scope="col" width="40%"| User story
!scope="col"| Tasks
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
! 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
| 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
|
|-

! scope="row" | 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
|
|-

! scope="row" | 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=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-10T13:41:32Z

Hugo.Rodrigues-Pereira-Anselmo: /* User stories */

=Project Presentation=
[http://air.imag.fr/index.php/CannonBall_de_voitures_autonomes CannonBall]

=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

{|class="wikitable alternance"
|-
!scope="col" width="40%"| User story
!scope="col"| Tasks
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
! 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
| 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
|
|-

! scope="row" | 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
|
|-

! scope="row" | 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=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-10T13:41:07Z

Hugo.Rodrigues-Pereira-Anselmo: /* User stories */

=Project Presentation=
[http://air.imag.fr/index.php/CannonBall_de_voitures_autonomes CannonBall]

=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

{|class="wikitable alternance"
|-
!scope="col" width="40%"| User story
!scope="col"| Tasks
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
! 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
| 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
|
|-

! scope="row" | 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
|
|-

! scope="row" | 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=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-10T13:39:04Z

Hugo.Rodrigues-Pereira-Anselmo:

=Project Presentation=
[http://air.imag.fr/index.php/CannonBall_de_voitures_autonomes CannonBall]

=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

{|class="wikitable alternance"
|-
!scope="col" width="40%"| User story
!scope="col"| Tasks
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
! 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
| 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
|
|-

! scope="row" | 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
|
|-

! scope="row" | 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=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-10T13:37:04Z

Hugo.Rodrigues-Pereira-Anselmo:

=Project Presentation=
[http://air.imag.fr/index.php/CannonBall_de_voitures_autonomes CannonBall]

=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

{|class="wikitable alternance"
|-
!scope="col" width="40%"| User story
!scope="col"| Tasks
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
! 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
| 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
|
|-

! scope="row" | 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
|
|-

! scope="row" | 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=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-10T13:21:59Z

Hugo.Rodrigues-Pereira-Anselmo:

=Project Presentation=
[http://air.imag.fr/index.php/CannonBall_de_voitures_autonomes CannonBall]

=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

{|class="wikitable alternance"
|-
!scope="col"| User story ||width="40%"
!scope="col"| Tasks
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
! 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
| 34
| 4 weeks
|
|-

|
| * Create a Node.js server that will serve the html page to the client
| 34
| 4 weeks
|
|-

|
| * Store the car's data in a database
| 34
| 4 weeks
|
|-

|
| * Car's data are showed on the html page
| 34
| 4 weeks
|
|-

! scope="row" | 2. The researchers needs several game mode to verify the good behavior of the car (Control Algorithm).
|
| 34
| 4 weeks
|
|-

| * AISheep : facilitates the QRCode-Action matching :
| ** Make generic actions for car mouvements
| 34
| 4 weeks
|
|-

|
| ** Make a grammar syntax for the user and a its parser
| 34
| 4 weeks
|
|-

| * AIRabbit : the car follow a specific QRcode :
| ** QRcode recognition
| 34
| 4 weeks
|
|-

|
| ** Localize the marker in space
| 34
| 4 weeks
|
|-

|
| ** Move in the marker direction
| 34
| 4 weeks
|
|-

| * AICannonBall : the car moves in a QRcode circuit
| ** QRcode recognition and interpretation
| 34
| 4 weeks
|
|-

|
| ** Avoid the QRcode
| 34
| 4 weeks
|
|-
|}

{| class="wikitable alternance centre"
|+ Titre
|----
! !! scope="col" | Titre col. A !! scope="col" | Titre col. B !! scope="col" | Titre col. C
|----
! scope="row" | Titre ligne 1
| Donnée 1A || Donnée 1B || Donnée 1C
|----
! scope="row" | Titre ligne 2
| Donnée 2A || Donnée 2B || Donnée 2C
|----
! scope="row" | Titre ligne 3
| Donnée 3A || Donnée 3B || Donnée 3C
|}

=Product backlog=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-10T13:12:47Z

Hugo.Rodrigues-Pereira-Anselmo:

=Project Presentation=
[http://air.imag.fr/index.php/CannonBall_de_voitures_autonomes CannonBall]

=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

{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Tasks
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
! scope="row" | 1. The researcher must be able to consult in real time the car's information to make changes if needed. ||width="25%"
| * Broadcast the messages with a publish/subscribe protocol
| 34
| 4 weeks
|
|-

|
| * Create a Node.js server that will serve the html page to the client
| 34
| 4 weeks
|
|-

|
| * Store the car's data in a database
| 34
| 4 weeks
|
|-

|
| * Car's data are showed on the html page
| 34
| 4 weeks
|
|-
|}

{| class="wikitable alternance centre"
|+ Titre
|----
! !! scope="col" | Titre col. A !! scope="col" | Titre col. B !! scope="col" | Titre col. C
|----
! scope="row" | Titre ligne 1
| Donnée 1A || Donnée 1B || Donnée 1C
|----
! scope="row" | Titre ligne 2
| Donnée 2A || Donnée 2B || Donnée 2C
|----
! scope="row" | Titre ligne 3
| Donnée 3A || Donnée 3B || Donnée 3C
|}

=Product backlog=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T19:21:43Z

Hugo.Rodrigues-Pereira-Anselmo: /* Sprint 2 */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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 researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-

| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=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 and 3.

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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:43:34Z

Hugo.Rodrigues-Pereira-Anselmo: /* End Sprint 1 */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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 researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-

| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=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 5.

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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:41:14Z

Hugo.Rodrigues-Pereira-Anselmo: /* Sprint 2 */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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 researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-

| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=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 5.

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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:40:31Z

Hugo.Rodrigues-Pereira-Anselmo: /* Sprint 2 */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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 researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-

| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=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 5
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.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:38:01Z

Hugo.Rodrigues-Pereira-Anselmo: /* Product backlog */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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 researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-

| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=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 5

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:37:26Z

Hugo.Rodrigues-Pereira-Anselmo: /* Product backlog */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
|
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| 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 researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-

| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=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 5

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:36:19Z

Hugo.Rodrigues-Pereira-Anselmo: /* Product backlog */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
|
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
!scope="row"
| The RICM want the car works in order to start the project. ( 6 )
| 34
| 1 week
|
|-
!scope="row"
| The RICM must master the different technologies to be able to do the project. ( 4 )
| 34
| all time
| all
|-
!scope="row"
| The researcher must be able to consult in real time the car's information to make changes if needed. ( 5 )
| 21
| 2 weeks
|
|-
!scope="row"
| The developer have to optimize the processing speed to provide a better product experience. ( 2 )
| 21
| 1 week
|
|-
!scope="row"
| The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-
!scope="row"
| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=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 5

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:35:59Z

Hugo.Rodrigues-Pereira-Anselmo: /* End Sprint 1 */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
|
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
!scope="row"| 1
| The RICM want the car works in order to start the project. ( 6 )
| 34
| 1 week
|
|-
!scope="row"| 2
| The RICM must master the different technologies to be able to do the project. ( 4 )
| 34
| all time
| all
|-
!scope="row"| 3
| The researcher must be able to consult in real time the car's information to make changes if needed. ( 5 )
| 21
| 2 weeks
|
|-
!scope="row"| 4
| The developer have to optimize the processing speed to provide a better product experience. ( 2 )
| 21
| 1 week
|
|-
!scope="row"| 5
| The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-
!scope="row"| 6
| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=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 5

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:34:32Z

Hugo.Rodrigues-Pereira-Anselmo:

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
|
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
!scope="row"| 1
| The RICM want the car works in order to start the project. ( 6 )
| 34
| 1 week
|
|-
!scope="row"| 2
| The RICM must master the different technologies to be able to do the project. ( 4 )
| 34
| all time
| all
|-
!scope="row"| 3
| The researcher must be able to consult in real time the car's information to make changes if needed. ( 5 )
| 21
| 2 weeks
|
|-
!scope="row"| 4
| The developer have to optimize the processing speed to provide a better product experience. ( 2 )
| 21
| 1 week
|
|-
!scope="row"| 5
| The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-
!scope="row"| 6
| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=Sprint 1=
We need to do the tasks 2, 5 and 6

=End Sprint 1=
Tasks done :
1 and 3

Problems :
Task 5 : 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 5

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:33:40Z

Hugo.Rodrigues-Pereira-Anselmo:

=User stories=

1. The RICM want the car works in order to start the project.

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). 

=Product backlog=
{|class="wikitable alternance"
|-
|
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
!scope="row"| 1
| The RICM want the car works in order to start the project. ( 6 )
| 34
| 1 week
|
|-
!scope="row"| 2
| The RICM must master the different technologies to be able to do the project. ( 4 )
| 34
| all time
| all
|-
!scope="row"| 3
| The researcher must be able to consult in real time the car's information to make changes if needed. ( 5 )
| 21
| 2 weeks
|
|-
!scope="row"| 4
| The developer have to optimize the processing speed to provide a better product experience. ( 2 )
| 21
| 1 week
|
|-
!scope="row"| 5
| The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-
!scope="row"| 6
| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=Sprint 1=
We need to do the tasks 2, 5 and 6

=End Sprint 1=
Tasks done :
1 and 3

Problems :
Task 5 : 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 5

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:31:55Z

Hugo.Rodrigues-Pereira-Anselmo: /* First Sprint */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
|
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
!scope="row"| 1
| The RICM want the car works in order to start the project. ( 6 )
| 34
| 1 week
|
|-
!scope="row"| 2
| The RICM must master the different technologies to be able to do the project. ( 4 )
| 34
| all time
| all
|-
!scope="row"| 3
| The researcher must be able to consult in real time the car's information to make changes if needed. ( 5 )
| 21
| 2 weeks
|
|-
!scope="row"| 4
| The developer have to optimize the processing speed to provide a better product experience. ( 2 )
| 21
| 1 week
|
|-
!scope="row"| 5
| The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-
!scope="row"| 6
| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=Sprint 1=
We need to do the tasks 1, 3 and 5

=End Sprint 1=
Tasks done :
1 and 3

Problems :
Task 5 : problem with the speed of processing the images.

The frame rate is very slow. The car is moving slowly.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:31:33Z

Hugo.Rodrigues-Pereira-Anselmo: /* End Sprint 1 */

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
|
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
!scope="row"| 1
| The RICM want the car works in order to start the project. ( 6 )
| 34
| 1 week
|
|-
!scope="row"| 2
| The RICM must master the different technologies to be able to do the project. ( 4 )
| 34
| all time
| all
|-
!scope="row"| 3
| The researcher must be able to consult in real time the car's information to make changes if needed. ( 5 )
| 21
| 2 weeks
|
|-
!scope="row"| 4
| The developer have to optimize the processing speed to provide a better product experience. ( 2 )
| 21
| 1 week
|
|-
!scope="row"| 5
| The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-
!scope="row"| 6
| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=First Sprint=
We need to do the tasks 1, 3 and 5

=End Sprint 1=
Tasks done :
1 and 3

Problems :
Task 5 : problem with the speed of processing the images.

The frame rate is very slow. The car is moving slowly.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/Scrum

2015-03-08T17:28:33Z

Hugo.Rodrigues-Pereira-Anselmo:

=User stories=

1. The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm).

2. The developer have to optimize the processing speed to provide a better product experience.

3. The researcher must be able to change the vehicle mode to realize different tests.

4. The RICM must master the different technologies to be able to do the project.

5. The researcher must be able to consult in real time the car's information to make changes if needed.

6. The RICM want the car works in order to start the project. 

=Product backlog=
{|class="wikitable alternance"
|-
|
!scope="col"| User story
!scope="col"| Priority
!scope="col"| Time
!scope="col"| Actors
|-
!scope="row"| 1
| The RICM want the car works in order to start the project. ( 6 )
| 34
| 1 week
|
|-
!scope="row"| 2
| The RICM must master the different technologies to be able to do the project. ( 4 )
| 34
| all time
| all
|-
!scope="row"| 3
| The researcher must be able to consult in real time the car's information to make changes if needed. ( 5 )
| 21
| 2 weeks
|
|-
!scope="row"| 4
| The developer have to optimize the processing speed to provide a better product experience. ( 2 )
| 21
| 1 week
|
|-
!scope="row"| 5
| The researcher must be able to send a line of instruction for verify the good behavior of the car (Control Algorithm). ( 1 )
| 13
|
|
|-
!scope="row"| 6
| The researcher must be able to change the vehicle mode to realize different tests. ( 3 )
| 8
| 3 weeks
|
|-
|}

=First Sprint=
We need to do the tasks 1, 3 and 5

=End Sprint 1=
Tasks done :
1 and 3
Problems :
Task 5 : problem with the speed of processing the images.
The frame rate is very slow. The car is moving slowly.

=Waffle=
[https://waffle.io/malek0512/2014_2015_ricm4_cannon_ball here]

Project 2014-2015-CannonBall/SRS

2015-02-02T13:25:39Z

Hugo.Rodrigues-Pereira-Anselmo:

The document provides a template of the '''Software Requirements Specification''' (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

The purpose of this document is to present the requirements of the project CannonBall, which are functional or not. But also quality standards and project risks.

==1.2 Scope of the product==

This project is an important part of the engineering course RICM4.

==1.3 Definitions, acronyms and abbreviations==

We will have to use specific terms like :
* OpenCV : this is a library which implements processing algorithms and image recognition
* Mosquitto : this is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model
* Arduino : this is an open-source electronics platform based on easy-to-use hardware and software.
* Servomotor : this is a rotary actuator that allows for precise control of angular position, velocity and acceleration

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=

The main goal of this project is to take over and improve our predecessors' work to allow better feedback when using the automatic car created under the CannonBall project.

==2.1 Product perspective==

Our project will enable a detailed feedback on the car and driving conditions.

==2.2 Product functions==

* Automatic car
* Restitution and analysis
* Capture and display of a video stream

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture (Car)

'''Source''': Tablette, WebCam, Arduino (tablet, webcam, arduino)

'''Outputs''': Tablette (tablet)

'''Destination''': Ce projet est destiné a être présenté lors de concours (This project is intended to be presented at contest)

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

'''Functionnal requirements''' :

* Doit remonter la voiture (reassembling of the car)
* Peut faire passer le code des Ensimag sur un support linux (modify the code to be compatible with linux)
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map) (perfect the different modes)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information (improve the use of mosquitto for better feedback)

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
(Embedded: The equipment used must be small to be integrated in the car)
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture
(Powerful: the material used must be efficient to be adapted to the speed of the car)

'''Pre-condition''':
* Réussir la récupération du code existant (Recover of existing code)
* Comprendre du code existant (Understand of existing code)
* Réussir à remonter la voiture (Successfully rebuilt the car)

'''Post-condition''':
* Faire un retour d'information pour calibrer la voiture
(Make a feedback to calibrate the car)

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus.

=5. Appendices=
=6. Index=

UML page :
* http://air.imag.fr/index.php/Project_2014-2015-CannonBall/UML

Project 2014-2015-CannonBall/UML

2015-02-02T13:24:53Z

Hugo.Rodrigues-Pereira-Anselmo:

This page provide the UML part of the project CannonBall.

You can access to the main page by clicking here :
* http://air.imag.fr/index.php?title=Project_2014-2015-CannonBall/SRS

Project 2014-2015-CannonBall/UML

2015-02-02T13:24:34Z

Hugo.Rodrigues-Pereira-Anselmo:

This page provide the UML part of the project CannonBall.

You can access to the main page by clicking here:
* http://air.imag.fr/index.php?title=Project_2014-2015-CannonBall/SRS

Project 2014-2015-CannonBall/UML

2015-02-02T13:23:50Z

Hugo.Rodrigues-Pereira-Anselmo: Created page with "This page provide the UML part of the project CannonBall. You can access to the main page by clicking here: [http://air.imag.fr/index.php?title=Project_2014-2015-CannonBall/SRS]"

This page provide the UML part of the project CannonBall.
You can access to the main page by clicking here:
[http://air.imag.fr/index.php?title=Project_2014-2015-CannonBall/SRS]

Project 2014-2015-CannonBall/SRS

2015-02-02T13:03:08Z

Hugo.Rodrigues-Pereira-Anselmo:

Project 2014-2015-CannonBall/SRS

2015-01-27T13:06:51Z

Hugo.Rodrigues-Pereira-Anselmo: /* 3.1 Requirement X.Y.Z (in Structured Natural Language) */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

L'objectif de ce document est de présenter les exigences du projet CannonBall, quelles soient fonctionnelle ou non fonctionelles. Mais également les critères de qualité et les risques du projet.

The purpose of this document is to present the requirements of the project CannonBall, which are functional or not. But also quality standards and project risks.

==1.2 Scope of the product==

Ce projet est une part importante de la formation d'ingénieur RICM4.

This project is an important part of the engineering course RICM4.

==1.3 Definitions, acronyms and abbreviations==

Nous devrons utiliser des termes spécifiques comme :
* OpenCV (C'est une librairie implémentant des algorithmes de traitement et de reconnaissance d'image)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

We will have to use specific terms like :
* OpenCV (A library who implements processing algorithms and image recognition)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=
Le but principal de ce projet est de reprendre et d'améliorer les projets de l'année dernière pour permettre un meilleur retour d'information lors de l'utilisation de la voiture automatique créé dans le cadre du projet CannonBall.

The main goal of the project is to take back and improve last year's projects to allow better feedback when using the automatic car created under the CannonBall project.

==2.1 Product perspective==

Notre projet doit permettre un retour d'information détaillé sur la voiture et les conditions de conduite.

Our project will enable a detailed feedback on the car and driving conditions.

==2.2 Product functions==

* Voiture automatique
* Restitution et analyse des données
* Capture et affichage d'un flux vidéo

* Automatic car
* Restitution and analysis
* Capture and display of a video stream

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture (Car)

'''Source''': Tablette, WebCam, Arduino (tablet, webcam, arduino)

'''Outputs''': Tablette (tablet)

'''Destination''': Ce projet est destiné a être présenté lors de concours (This project is intended to be presented at contest)

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

Fonctionnelles :

* Doit remonter la voiture (reassembling of the car)
* Peut faire passer le code des Ensimag sur un support linux (modify the code to be compatible with linux)
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map) (perfect the different modes)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information (improve the use of mosquitto for better feedback)

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
(Embedded: The equipment used must be small to be integrated in the car)
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture
(Powerful: the material used must be efficient to be adapted to the speed of the car)

'''Pre-condition''':
* Réussir la récupération du code existant (Recover of existing code)
* Comprendre du code existant (Understand of existing code)
* Réussir à remonter la voiture (Successfully rebuilt the car)

'''Post-condition''':
* Faire un retour d'information pour calibrer la voiture
(Make a feedback to calibrate the car)

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus

=5. Appendices=
=6. Index=

Project 2014-2015-CannonBall/SRS

2015-01-27T10:51:42Z

Hugo.Rodrigues-Pereira-Anselmo: /* 2.2 Product functions */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

L'objectif de ce document est de présenter les exigences du projet CannonBall, quelles soient fonctionnelle ou non fonctionelles. Mais également les critères de qualité et les risques du projet.

The purpose of this document is to present the requirements of the project CannonBall, which are functional or not. But also quality standards and project risks.

==1.2 Scope of the product==

Ce projet est une part importante de la formation d'ingénieur RICM4.

This project is an important part of the engineering course RICM4.

==1.3 Definitions, acronyms and abbreviations==

Nous devrons utiliser des termes spécifiques comme :
* OpenCV (C'est une librairie implémentant des algorithmes de traitement et de reconnaissance d'image)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

We will have to use specific terms like :
* OpenCV (A library who implements processing algorithms and image recognition)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=
Le but principal de ce projet est de reprendre et d'améliorer les projets de l'année dernière pour permettre un meilleur retour d'information lors de l'utilisation de la voiture automatique créé dans le cadre du projet CannonBall.

The main goal of the project is to take back and improve last year's projects to allow better feedback when using the automatic car created under the CannonBall project.

==2.1 Product perspective==

Notre projet doit permettre un retour d'information détaillé sur la voiture et les conditions de conduite.

Our project will enable a detailed feedback on the car and driving conditions.

==2.2 Product functions==

* Voiture automatique
* Restitution et analyse des données
* Capture et affichage d'un flux vidéo

* Automatic car
* Restitution and analysis
* Capture and display of a video stream

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture

'''Source''': Tablette, WebCam, Arduino

'''Outputs''': Tablette

'''Destination''': Ce projet est destiné a être présenté lors de concours

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

Fonctionnelles :

* Doit remonter la voiture
* Peut faire passer le code des Ensimag sur un support linux
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture

'''Pre-condition''':
* Réussir la récupération du code existant
* Comprendre du code existant
* Réussir à remontrer la voiture et donc faire preuve d'une grande prudence lors du montage

'''Post-condition''':
* Faire un retour d'information pour recalibrer la voiture

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus

=5. Appendices=
=6. Index=

Project 2014-2015-CannonBall/SRS

2015-01-27T10:40:48Z

Hugo.Rodrigues-Pereira-Anselmo: /* 2. General description */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

L'objectif de ce document est de présenter les exigences du projet CannonBall, quelles soient fonctionnelle ou non fonctionelles. Mais également les critères de qualité et les risques du projet.

The purpose of this document is to present the requirements of the project CannonBall, which are functional or not. But also quality standards and project risks.

==1.2 Scope of the product==

Ce projet est une part importante de la formation d'ingénieur RICM4.

This project is an important part of the engineering course RICM4.

==1.3 Definitions, acronyms and abbreviations==

Nous devrons utiliser des termes spécifiques comme :
* OpenCV (C'est une librairie implémentant des algorithmes de traitement et de reconnaissance d'image)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

We will have to use specific terms like :
* OpenCV (A library who implements processing algorithms and image recognition)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=
Le but principal de ce projet est de reprendre et d'améliorer les projets de l'année dernière pour permettre un meilleur retour d'information lors de l'utilisation de la voiture automatique créé dans le cadre du projet CannonBall.

The main goal of the project is to take back and improve last year's projects to allow better feedback when using the automatic car created under the CannonBall project.

==2.1 Product perspective==

Notre projet doit permettre un retour d'information détaillé sur la voiture et les conditions de conduite.

Our project will enable a detailed feedback on the car and driving conditions.

==2.2 Product functions==

* Voiture automatique
* Restitution et analyse des données
* Capture et affichage d'un flux vidéo

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture

'''Source''': Tablette, WebCam, Arduino

'''Outputs''': Tablette

'''Destination''': Ce projet est destiné a être présenté lors de concours

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

Fonctionnelles :

* Doit remonter la voiture
* Peut faire passer le code des Ensimag sur un support linux
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture

'''Pre-condition''':
* Réussir la récupération du code existant
* Comprendre du code existant
* Réussir à remontrer la voiture et donc faire preuve d'une grande prudence lors du montage

'''Post-condition''':
* Faire un retour d'information pour recalibrer la voiture

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus

=5. Appendices=
=6. Index=

Project 2014-2015-CannonBall/SRS

2015-01-27T10:35:17Z

Hugo.Rodrigues-Pereira-Anselmo: /* 1.3 Definitions, acronyms and abbreviations */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

L'objectif de ce document est de présenter les exigences du projet CannonBall, quelles soient fonctionnelle ou non fonctionelles. Mais également les critères de qualité et les risques du projet.

The purpose of this document is to present the requirements of the project CannonBall, which are functional or not. But also quality standards and project risks.

==1.2 Scope of the product==

Ce projet est une part importante de la formation d'ingénieur RICM4.

This project is an important part of the engineering course RICM4.

==1.3 Definitions, acronyms and abbreviations==

Nous devrons utiliser des termes spécifiques comme :
* OpenCV (C'est une librairie implémentant des algorithmes de traitement et de reconnaissance d'image)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

We will have to use specific terms like :
* OpenCV (A library who implements processing algorithms and image recognition)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=
Le but principal de ce projet est de reprendre et d'améliorer les projets de l'année dernière pour permettre un meilleur retour d'information lors de l'utilisation de la voiture automatique créé dans le cadre du projet CannonBall
==2.1 Product perspective==

Notre projet doit permettre un retour d'information détaillé sur la voiture et les conditions de conduite.

==2.2 Product functions==

* Voiture automatique
* Restitution et analyse des données
* Capture et affichage d'un flux vidéo

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture

'''Source''': Tablette, WebCam, Arduino

'''Outputs''': Tablette

'''Destination''': Ce projet est destiné a être présenté lors de concours

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

Fonctionnelles :

* Doit remonter la voiture
* Peut faire passer le code des Ensimag sur un support linux
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture

'''Pre-condition''':
* Réussir la récupération du code existant
* Comprendre du code existant
* Réussir à remontrer la voiture et donc faire preuve d'une grande prudence lors du montage

'''Post-condition''':
* Faire un retour d'information pour recalibrer la voiture

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus

=5. Appendices=
=6. Index=

Project 2014-2015-CannonBall/SRS

2015-01-27T10:31:17Z

Hugo.Rodrigues-Pereira-Anselmo: /* 1.2 Scope of the product */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

L'objectif de ce document est de présenter les exigences du projet CannonBall, quelles soient fonctionnelle ou non fonctionelles. Mais également les critères de qualité et les risques du projet.

The purpose of this document is to present the requirements of the project CannonBall, which are functional or not. But also quality standards and project risks.

==1.2 Scope of the product==

Ce projet est une part importante de la formation d'ingénieur RICM4.

This project is an important part of the engineering course RICM4.

==1.3 Definitions, acronyms and abbreviations==

Nous devrons utiliser des termes spécifiques comme :
* OpenCV (C'est une librairie implémentant des algorithmes de traitement et de reconnaissance d'image)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=
Le but principal de ce projet est de reprendre et d'améliorer les projets de l'année dernière pour permettre un meilleur retour d'information lors de l'utilisation de la voiture automatique créé dans le cadre du projet CannonBall
==2.1 Product perspective==

Notre projet doit permettre un retour d'information détaillé sur la voiture et les conditions de conduite.

==2.2 Product functions==

* Voiture automatique
* Restitution et analyse des données
* Capture et affichage d'un flux vidéo

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture

'''Source''': Tablette, WebCam, Arduino

'''Outputs''': Tablette

'''Destination''': Ce projet est destiné a être présenté lors de concours

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

Fonctionnelles :

* Doit remonter la voiture
* Peut faire passer le code des Ensimag sur un support linux
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture

'''Pre-condition''':
* Réussir la récupération du code existant
* Comprendre du code existant
* Réussir à remontrer la voiture et donc faire preuve d'une grande prudence lors du montage

'''Post-condition''':
* Faire un retour d'information pour recalibrer la voiture

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus

=5. Appendices=
=6. Index=

Project 2014-2015-CannonBall/SRS

2015-01-27T10:29:39Z

Hugo.Rodrigues-Pereira-Anselmo: /* 1.2 Scope of the product */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

L'objectif de ce document est de présenter les exigences du projet CannonBall, quelles soient fonctionnelle ou non fonctionelles. Mais également les critères de qualité et les risques du projet.

The purpose of this document is to present the requirements of the project CannonBall, which are functional or not. But also quality standards and project risks.

==1.2 Scope of the product==

Ce projet est une part importante de la formation d'ingénieur RICM4.
This project is an important part of the engineering course RICM4.

==1.3 Definitions, acronyms and abbreviations==

Nous devrons utiliser des termes spécifiques comme :
* OpenCV (C'est une librairie implémentant des algorithmes de traitement et de reconnaissance d'image)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=
Le but principal de ce projet est de reprendre et d'améliorer les projets de l'année dernière pour permettre un meilleur retour d'information lors de l'utilisation de la voiture automatique créé dans le cadre du projet CannonBall
==2.1 Product perspective==

Notre projet doit permettre un retour d'information détaillé sur la voiture et les conditions de conduite.

==2.2 Product functions==

* Voiture automatique
* Restitution et analyse des données
* Capture et affichage d'un flux vidéo

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture

'''Source''': Tablette, WebCam, Arduino

'''Outputs''': Tablette

'''Destination''': Ce projet est destiné a être présenté lors de concours

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

Fonctionnelles :

* Doit remonter la voiture
* Peut faire passer le code des Ensimag sur un support linux
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture

'''Pre-condition''':
* Réussir la récupération du code existant
* Comprendre du code existant
* Réussir à remontrer la voiture et donc faire preuve d'une grande prudence lors du montage

'''Post-condition''':
* Faire un retour d'information pour recalibrer la voiture

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus

=5. Appendices=
=6. Index=

Project 2014-2015-CannonBall/SRS

2015-01-27T10:25:31Z

Hugo.Rodrigues-Pereira-Anselmo: /* 1.1 Purpose of the requirements document */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

L'objectif de ce document est de présenter les exigences du projet CannonBall, quelles soient fonctionnelle ou non fonctionelles. Mais également les critères de qualité et les risques du projet.

The purpose of this document is to present the requirements of the project CannonBall, which are functional or not. But also quality standards and project risks.

==1.2 Scope of the product==

Ce projet est une part importante de la formation d'ingénieur RICM4.

==1.3 Definitions, acronyms and abbreviations==

Nous devrons utiliser des termes spécifiques comme :
* OpenCV (C'est une librairie implémentant des algorithmes de traitement et de reconnaissance d'image)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=
Le but principal de ce projet est de reprendre et d'améliorer les projets de l'année dernière pour permettre un meilleur retour d'information lors de l'utilisation de la voiture automatique créé dans le cadre du projet CannonBall
==2.1 Product perspective==

Notre projet doit permettre un retour d'information détaillé sur la voiture et les conditions de conduite.

==2.2 Product functions==

* Voiture automatique
* Restitution et analyse des données
* Capture et affichage d'un flux vidéo

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture

'''Source''': Tablette, WebCam, Arduino

'''Outputs''': Tablette

'''Destination''': Ce projet est destiné a être présenté lors de concours

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

Fonctionnelles :

* Doit remonter la voiture
* Peut faire passer le code des Ensimag sur un support linux
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture

'''Pre-condition''':
* Réussir la récupération du code existant
* Comprendre du code existant
* Réussir à remontrer la voiture et donc faire preuve d'une grande prudence lors du montage

'''Post-condition''':
* Faire un retour d'information pour recalibrer la voiture

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus

=5. Appendices=
=6. Index=

Project 2014-2015-CannonBall/SRS

2015-01-27T10:24:33Z

Hugo.Rodrigues-Pereira-Anselmo: /* 1.1 Purpose of the requirements document */

The document provides a template of the Software Requirements Specification (SRS). It is inspired of the IEEE/ANSI 830-1998 Standard.

'''Read first:'''
* http://www.cs.st-andrews.ac.uk/~ifs/Books/SE9/Presentations/PPTX/Ch4.pptx
* http://en.wikipedia.org/wiki/Software_requirements_specification
* [http://www.cse.msu.edu/~chengb/RE-491/Papers/IEEE-SRS-practice.pdf IEEE Recommended Practice for Software Requirements Specifications IEEE Std 830-1998]

{|class="wikitable alternance"
|+ Document History
|-
|
!scope="col"| Version
!scope="col"| Date
!scope="col"| Authors
!scope="col"| Description
!scope="col"| Validator
!scope="col"| Validation Date
|-
!scope="row" |
| 0.1.0
| janvier 2015
| LE JEAN Alexandre, MAMMAR Malek, PELLOUX-PRAYER Ophélie, RODRIGUES Hugo
| TBC
| TBC
| TBC

|}

=1. Introduction=
==1.1 Purpose of the requirements document==

L'objectif de ce document est de présenter les exigences du projet CannonBall, quelles soient fonctionnelle ou non fonctionelles, les critères de qualité et les risques du projet.

The purpose of this document is to present the requirements of the project CannonBall, working or not, quality standards and project risks.

==1.2 Scope of the product==

Ce projet est une part importante de la formation d'ingénieur RICM4.

==1.3 Definitions, acronyms and abbreviations==

Nous devrons utiliser des termes spécifiques comme :
* OpenCV (C'est une librairie implémentant des algorithmes de traitement et de reconnaissance d'image)
* Mosquitto (That is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport protocol versions 3.1 and 3.1.1. MQTT provides a lightweight method of carrying out messaging using a publish/subscribe model)
* Arduino (That is an open-source electronics platform based on easy-to-use hardware and software.)
* Servo-Moteur

==1.4 References==

This project is based on the work of :

'''From january 13th 2014 to march 2nd 2014''' : Jules Legros and Benoit Perruche from Polytech'Grenoble. [http://air.imag.fr/index.php/Proj-2013-2014-Cannonball-de-Voitures-Autonomes Link Wiki Air]

'''From may 26th 2014 to june 16th 2014''' : Thibaut Coutelou, Benjamin Mugnier and Guillaume Perrin from Ensimag. [http://fablab.ensimag.fr/index.php/Cannonball_de_voitures_RC/FicheSuivi Link]

==1.5 Overview of the remainder of the document==
=2. General description=
Le but principal de ce projet est de reprendre et d'améliorer les projets de l'année dernière pour permettre un meilleur retour d'information lors de l'utilisation de la voiture automatique créé dans le cadre du projet CannonBall
==2.1 Product perspective==

Notre projet doit permettre un retour d'information détaillé sur la voiture et les conditions de conduite.

==2.2 Product functions==

* Voiture automatique
* Restitution et analyse des données
* Capture et affichage d'un flux vidéo

==2.3 User characteristics==

There are two type of user :
* Searcher
* Geek

==2.4 General constraints==
==2.5 Assumptions and dependencies==

=3.Specific requirements, covering functional, non-functional and interface requirements=
* document external interfaces,
* describe system functionality and performance
* specify logical database requirements,
* design constraints,
* emergent system properties and quality characteristics.

==3.1 Requirement X.Y.Z (in Structured Natural Language)==
'''Function''':

'''Description''':

'''Inputs''': Voiture

'''Source''': Tablette, WebCam, Arduino

'''Outputs''': Tablette

'''Destination''': Ce projet est destiné a être présenté lors de concours

'''Action''':
* Natural language sentences (with MUST, MAY, SHALL)
* Graphical Notations : UML Sequence w/o collaboration diagrams, Process maps, Task Analysis (HTA, CTT)
* Mathematical Notations
* Tabular notations for several (condition --> action) tuples

Fonctionnelles :

* Doit remonter la voiture
* Peut faire passer le code des Ensimag sur un support linux
* Doit perfectionner les diffrérents modes (Rabbit, CannonBall, Map)
* Doit améliorer l'utilisation du mosquitto pour permettre un meilleur retour d'information

'''Non functional requirements''':
* Embarqué : le matériel utilisé doit être petit pour pouvoir être intégré dans la voiture
* Performant : le matériel utilisé doit être performant pour être adapté à la vitesse de la voiture

'''Pre-condition''':
* Réussir la récupération du code existant
* Comprendre du code existant
* Réussir à remontrer la voiture et donc faire preuve d'une grande prudence lors du montage

'''Post-condition''':
* Faire un retour d'information pour recalibrer la voiture

'''Side-effects''':

=4. Product evolution=

On pourrait, dans un objectif futur, mettre en place l'utilisation d'un oculus

=5. Appendices=
=6. Index=