Changes between Version 1 and Version 2 of PLATFORM_STANDARDS_ANALYSIS


Ignore:
Timestamp:
10/13/08 17:52:51 (17 years ago)
Author:
deyan
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PLATFORM_STANDARDS_ANALYSIS

    v1 v2  
    1616  * Implementation methods, suggested algorithms, etc. 
    1717  * UML diagrams (class diagrams) where needed 
    18   * Initial tests (Test Driven Development, Research Tests etc.)}} 
    19  * Bug Fix - 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. These tasks should be designed by a developer. 
     18  * Initial tests (Test Driven Development, Research Tests etc. 
     19)}} 
     20 * Bug Fix -  
     21{{{ 
     22Design 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. These tasks should be designed by a developer. 
    2023  * In which module did the bug appear 
    2124  * In which part of the code did the bug appear 
    … …  
    2427  * UML diagrams (class diagrams) where needed 
    2528  * Initial tests 
    26  * Document - Design should point which tools will be used, how the document will be created. Depending on specific task, these tasks may be designed by developer or qa. 
     29}}} 
     30 * Document -  
     31{{{ 
     32Design should point which tools will be used, how the document will be created. Depending on specific task, these tasks may be designed by developer or qa. 
    2733  * Required auxiliary tools 
    2834  * Basic content of the document, a sentence for every fundamental thing. These will be expanded in Implementation section. 
    2935  * Useful external links 
    3036  * Image/Diagram requirements - content, file types, file sizes, position, etc. 
    31  * Setup - Design  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. These tasks should be designed by a developer. 
     37}}} 
     38 * Setup -  
     39{{{ 
     40Design  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. These tasks should be designed by a developer. 
    3241  * Hardware requirements - point specific hardware requirements, limitations if any. 
    3342  * Software requirements - point which of the suitable tools will be installed and configured.   
    34  * Maintenance - Design explains what should be done for meeting the requirements, links to tools that will be used, algorithms, diagrams and whatever is needed for an easy implementation. Depending on specific task, these tasks may be designed by developer or qa. 
     43}}} 
     44 * Maintenance -  
     45{{{Design explains what should be done for meeting the requirements, links to tools that will be used, algorithms, diagrams and whatever is needed for an easy implementation. Depending on specific task, these tasks may be designed by developer or qa. 
    3546  * If script are needed, design and link them 
    3647  * Link any used tools for maintaining appliances/files. 
    3748A good design doesn't leave any questions about implementation - when it's read, implementation should be trivial. Parts of the design may be pointed as implementation. 
     49 
    3850Use the design section [wiki:PageTemplates/TaskPageTemplate#Design] of the Task Page Template. 
     51}}}