Changes between Version 40 and Version 41 of PLATFORM_STANDARDS_GENERAL


Ignore:
Timestamp:
09/25/08 11:07:24 (17 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PLATFORM_STANDARDS_GENERAL

    v40 v41  
    99  * 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. 
    1010  * 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 the wrong code, why it was not suitable). 
     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). 
    1212  * 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. 
    1313 * Document 
     14  * 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. 
     15  * Analysis - Analysis section should contain document requirements (file format, dimensions, formatting), contents requirements. This section should also contain related tasks - tasks that depend on that one, tasks of which this task depends, similar tasks, etc. 
     16  * Design - Design should point which tools will be used, how the document will be created. 
     17  * Implementation - Implementation section as in other tasks should contain link to created documents and explanation how they were done. The results should be presentable in Analysis/How to Demo section. 
    1418 * Setup 
     19  * Description - The result of this tasks are hardware/software setup of different computer appliances that will be used for executing all other tasks. These contain website, wiki, developer platform setup, etc. 
     20  * Analysis - Analysis answers the question what are the requirements for this appliance - hardware and software. For example, some of the community server hardware requirements are space and bandwidth, and software - running web server, security issues. Here should be also listed tasks that depend on that one. 
     21  * Design - In this section should be decided which computer appliance will satisfy the requirements, how it will be set up, what technologies will be used. Give links to websites of software solutions that should be used. 
     22  * Implementation - This section should contain how exactly was this appliance set up. Give links to any setup files or other information in order for the server to be recreated. 
    1523 * Maintenance  
    1624The results of this phase should be described in the Implementation section of the task's current revision page [wiki:PageTemplates/TaskPageTemplate]. Depending on task type, results can be