13 | | * Coding tasks - |
14 | | {{{ |
15 | | Design of these tasks should describe technology that will be used for reaching task's requirement. These tasks should be designed by a developer. |
16 | | * Required libraries |
17 | | * Implementation methods, suggested algorithms, etc. |
18 | | * UML diagrams (class diagrams) where needed |
| 13 | * Coding tasks - Analysis of these tasks should describe the aim of this revision. |
| 14 | * Overview - contains explanation of the task. This explanation should present what will be done from the user point of view, what will be the visible result from the task. |
| 15 | * Requirements - Here should be listed requirements of the result - what is desired functionality, what should this element have, etc. |
| 16 | * Task result - In this section should be listed what is the result of the task. For these tasks it will be code but depending on task may also contain diagrams, graphics, etc |
| 17 | * Implementation idea - Brief overview of implementation methods, suggested algorithms, etc. |
| 18 | * Related - Here should be listed related tasks that might be useful for solving this task. You may also point to previous and next revisions of the same task, useful external links, etc. |
| 19 | * How to demo |
| 20 | |
| 21 | |
| 22 | |