Version 1 (modified by sriggins, 16 years ago) (diff) |
---|
Analysis
(The purpose of the analysis is to give as much as possible of the needed information for designing and implementing the task.)
Overview
(The analysis of the first revision of each task should contain a brief overview of the whole task. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)
Task requirements
(Necessary requirements that the task must fulfill.)
Task result
(The Analysis should contain strict requirements about the end product of the task (for example the result must be source code, the result must be google doc, etc.))
Implementation idea
(It is advisable to include some rough implementations ideas.)
Related
(Here you can add related tasks that could be useful or helpful.)
How to demo
(In this section you must add instructions for the demo of the task.)
Design
Implementation
(Implementation results should be described and linked here (from the wiki or the repository))
Testing
Comments
open resources for reading/writing get a list of book templates find resources for the application login files
related to plugin and platform structure some resources should be shared between plugins every plugin has a distrib directory
should work without having everything assembled, or assembled