Version 2 (modified by deyan, 17 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
Input the three unplanned tasks. Arrange the reports and specificate their situation. Fix dates of the milestones. Structure to write a final report.
Task requirements
The sub-tasks for this revision are:
- Add unplanned tasks
- BASE_MODEL_FRAME_CONTENT_R0
- CORE_MVC_BASE_R0
- BOOK_WINDOW_R0 to the Iteration page.
Consider how to add them - by adding new revisions to the wbs or editing the page. Note that changing revisions will probably cause more issues.
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
Log
(Link the log of the task here)