| 48 | == For [wiki:PLATFORM_STANDARDS_ANALYSIS] == |
| 49 | The [wiki:PLATFORM_STANDARDS_ANALYSIS] page will have the following structure: |
| 50 | {{{ |
| 51 | |_How to write analyses |
| 52 | |__General information |
| 53 | |__Task types |
| 54 | |___Coding task |
| 55 | |___Bug fix |
| 56 | |___Document |
| 57 | |___Setup |
| 58 | |___Maintenance |
| 59 | |__Examples |
| 60 | |__Coding tasks approach |
| 61 | |__Reviewing |
| 62 | |___Scores |
| 63 | |___Super review |
| 64 | |_Comments |
| 65 | }}} |
| 66 | |
| 67 | These sections will contain: |
| 68 | * General information - a brief description of the structure of the analysis and what each of its sections should contain (applying to all task kinds). |
| 69 | * Task types - for each task type there will be a list of what each section of the analysis should contain (split into required, recommended, optional). |
| 70 | * Examples - several examples of good and bad analyses with brief explanations of their pro and cons. |
| 71 | * Coding tasks approach - a list of things to have a look at when analyzing coding tasks (for example, the WBS file, the task index, etc.). |
| 72 | * Reviewing - rules for reviewing, scoring and requesting a super review - when a task should fail and when not. |
| 73 | * Comments - everyone that has some opinion on the standards should describe it here. |
| 74 | |
| 75 | Everyone has been asked to give his opinion in the Comments section. During the implementation these comments will be considered and integrated into the wiki page. |
| 76 | |
| 77 | |