Changes between Version 46 and Version 47 of PLATFORM_STANDARDS_GENERAL

Timestamp:

09/25/08 13:57:54 (17 years ago)

Author:

Tanya

Comment:

--

PLATFORM_STANDARDS_GENERAL

@@ -10 +10 @@
   * Description - Bug fix type tasks are part of Unplanned tasks. These tasks consist of different kinds of unwanted application behavior - lack of functionality, wrong functionality, different errors. Bug tasks should be presented as "BUG_TASK_NAME"
   * 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
-  * 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.
+  * Design - Design of bug fixes is similar to Coding tasks' design, but should also answer the questions 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.
   * 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.
   * Testing - In testing should be described how bug task will be tested, here should be linked trac tickets, auto tests, test cases.