| 29 | | }}} |
| 30 | | * Document - |
| 31 | | {{{ |
| 32 | | Design should point which tools will be used, how the document will be created. Depending on specific task, these tasks may be designed by developer or qa. |
| 33 | | * Required auxiliary tools |
| 34 | | * Basic content of the document, a sentence for every fundamental thing. These will be expanded in Implementation section. |
| 35 | | * Useful external links |
| 36 | | * Image/Diagram requirements - content, file types, file sizes, position, etc. |
| 37 | | }}} |
| | 29 | |
| | 30 | * Document - Analysis of documents tasks should point the aim of this document. |
| | 31 | * Overview - Overview of specific revision should point what will be done in this revision. |
| | 32 | * Requirements - Requirements to the documents that will be the result |
| | 33 | * What sections should they contain |
| | 34 | * Are these internal or external documents. |
| | 35 | * Optional - who has to read these documents and in what period. |
| | 36 | * Is it an important document. |
| | 37 | * Task result - Should point revision target documents - wiki pages, diagrams, etc. |
| | 38 | * Implementation idea - You may research related examples and share them in this section. |
| | 39 | * Related - Here should be listed related tasks that might be useful. You should link previous revisions of this task. You may list useful external links too. |
| | 40 | * How to demo - Link the document and give idea about highlighting parts of the implementation. |
