| 51 | | {{{ |
| 52 | | Design explains what should be done for meeting the requirements, links to tools that will be used, algorithms, diagrams and whatever is needed for an easy implementation. Depending on specific task, these tasks may be designed by developer or qa. |
| 53 | | * If script are needed, design and link them |
| 54 | | * Link any used tools for maintaining appliances/files. |
| 55 | | A good design doesn't leave any questions about implementation - when it's read, implementation should be trivial. Parts of the design may be pointed as implementation. |
| 56 | | |
| 57 | | Use the design section [wiki:PageTemplates/TaskPageTemplate#Design] of the Task Page Template. |
| 58 | | }}} |
| | 52 | * Overview - explains what should be revised in a sentence |
| | 53 | * Requirements |
| | 54 | * Are there impediments related to this maintenance in the backlog |
| | 55 | * What are the steps that are recreated each maintenance |
| | 56 | * Log requirements |
| | 57 | * Task result |
| | 58 | * In most common case the result is a maintained appliance/tool. |
| | 59 | * and/or setup, backup scripts. |
| | 60 | * Implementation idea - Couple of sentences about implementation. |
| | 61 | * Related - Here should be listed related tasks that might be useful for solving this task. You should also list previous revisions and setup of this tool/appliance. External links may be useful too. |
| | 62 | * How to demo - Give instructions about presenting the results depending on task requirements. |
