Work description » History » Version 1
BASTIDE, Paul, 02/02/2016 02:02 PM
| 1 | 1 | BASTIDE, Paul | h1. Work description |
|---|---|---|---|
| 2 | 1 | BASTIDE, Paul | |
| 3 | 1 | BASTIDE, Paul | p. In the beginning of the project, to organize our work, we are going to evaluate which tasks are awaiting us in order to fulfill our objective. |
| 4 | 1 | BASTIDE, Paul | |
| 5 | 1 | BASTIDE, Paul | p. By inspiring ourselves of the realization of former fellow students, plus our experience in other previous project, we have been able to identify five main tasks to be tackled: |
| 6 | 1 | BASTIDE, Paul | * Discover and get acquainted with the Cubesat and its environment |
| 7 | 1 | BASTIDE, Paul | * To define the mission we are going to work on |
| 8 | 1 | BASTIDE, Paul | * To develop the above mission |
| 9 | 1 | BASTIDE, Paul | * To do series of tests and correct any issues |
| 10 | 1 | BASTIDE, Paul | * Write a detailed report while corresponding with all the concerned people. |
| 11 | 1 | BASTIDE, Paul | |
| 12 | 1 | BASTIDE, Paul | |
| 13 | 1 | BASTIDE, Paul | p. After that we tried to analyze what would be the list of tasks in each of the main work tasks: |
| 14 | 1 | BASTIDE, Paul | # Cubesat discovery: |
| 15 | 1 | BASTIDE, Paul | ** Study of past projects + literature research on Cubesats |
| 16 | 1 | BASTIDE, Paul | ** Install needed software (cf COLIN Tony and DUHAUTOIS Brice project) |
| 17 | 1 | BASTIDE, Paul | ** Redo basic tests on the hardware to get acquainted with it (Past year project) |
| 18 | 1 | BASTIDE, Paul | ** Redo basic programming to get acquainted with the softwares |
| 19 | 1 | BASTIDE, Paul | # Mission definition |
| 20 | 1 | BASTIDE, Paul | ** Analyze past missions, from Telecom Bretagne and other sources |
| 21 | 1 | BASTIDE, Paul | ** Define several possible mission objectives |
| 22 | 1 | BASTIDE, Paul | *** Run them through with our project coordinator : Laurent FRANCK, head of the SatCom lab |
| 23 | 1 | BASTIDE, Paul | ** Analyze mission requirements, software and hardware wise |
| 24 | 1 | BASTIDE, Paul | ** Define success of mission requirements |
| 25 | 1 | BASTIDE, Paul | ** Imagine several testing scenarii to test the above requirements |
| 26 | 1 | BASTIDE, Paul | # Mission development |
| 27 | 1 | BASTIDE, Paul | ** Make a list of all needed equipment, recover them if not present in the lab |
| 28 | 1 | BASTIDE, Paul | ** Make a list of needed functions (“tasks”) required to make the software part work |
| 29 | 1 | BASTIDE, Paul | ** Program |
| 30 | 1 | BASTIDE, Paul | ** Make a prototype and upload the program on it |
| 31 | 1 | BASTIDE, Paul | # Mission testing |
| 32 | 1 | BASTIDE, Paul | ** Run defined test scenarii |
| 33 | 1 | BASTIDE, Paul | ** Analyze the results |
| 34 | 1 | BASTIDE, Paul | ** Do the necessary correction and imagine improvements to the system |
| 35 | 1 | BASTIDE, Paul | # Write report: task to be done in parallel to all the others. |
| 36 | 1 | BASTIDE, Paul | |
| 37 | 1 | BASTIDE, Paul | The following graph shows an estimation of the task sequence, and which tasks should and may be done simultaneously. |