Changes between Version 44 and Version 45 of PLATFORM_STANDARDS_GENERAL


Ignore:
Timestamp:
09/25/08 12:26:35 (17 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PLATFORM_STANDARDS_GENERAL

    v44 v45  
    66  * Design - Design of these tasks should describe technology that will be used for reaching task's requirement. It should contain initial tests, libraries needed, rough algorithm explanation, class diagrams, etc.  
    77  * Implementation - In implementation section of task's revision the results must be linked with explanation what was done during this revision. Explain which part of source you've added/edited and how. The result of your work should be presentable in Analysis/How to Demo section. 
     8  * Testing - In testing should be described how this task will be tested, here should be linked trac tickets, auto tests, test cases. 
    89 * Bug Fix 
    910  * Description - Bug fix type tasks are also referred as "Unplanned tasks". These tasks consist of different kinds of unwanted application behavior - lack of functionality, wrong functionality, different errors. 
    10   * Analysis - Analysis of Bug Fixes should contain exact explanation of what and how happens / not happens (what's wrong). Analysis should answer the question why this bug appears, which part of the code is guilty for the wrong functionality. How to demo should contain steps to recreate to prove that the bug doesn't exist anymore. In this section links to tickets can be very useful 
    11   * Design - Design of bug fixes is similar to Coding tasks' design, but should also answer the question why did this bug appear (what was wrong with the code, why it was not suitable). 
     11  * Analysis - Analysis of Bug Fixes should contain exact explanation of exactly happens / not happens (what's wrong). How to demo should contain steps to recreate to prove that the bug doesn't exist anymore. In this section links to tickets can be very useful 
     12  * Design - Design of bug fixes is similar to Coding tasks' design, but should also answer the questions Analysis should answer the question why does this bug appear, which part of the code is guilty for the wrong functionality (what was wrong with the code, why it was not suitable). Design also contains auto-tests that prove bug wouldn't be presented after implementation. 
    1213  * Implementation - Implementation section should contain link to files where was added/maintained/re factored code, should also describe what was done. The results should be presentable in Analysis/How to Demo section. 
     14  * Testing - In testing should be described how bug task will be tested, here should be linked trac tickets, auto tests, test cases. 
    1315 * Document 
    1416  * Description - Document tasks require different documents as result. In most cases, these documents are auxiliary for other tasks. Commonly, the result of document tasks will be Wiki page, but may also be other document and may consist of text, diagrams, media files, spreadsheets, examples, etc.