Changes between Version 7 and Version 8 of PLATFORM_STANDARDS_DESIGN


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

--

Legend:

Unmodified
Added
Removed
Modified

  • PLATFORM_STANDARDS_DESIGN

    v7 v8  
    1010  * UML diagrams (class diagrams) where needed 
    1111  * Initial tests 
    12  * Bug Fix - 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. 
    13   *  
     12 * 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. 
     13  * In which module did the bug appear 
     14  * In which part of the code did the bug appear 
    1415  * Required libraries 
    1516  * Implementation methods, suggested algorithms, etc. 
    … …  
    1718  * Initial tests 
    1819 * Document - Design should point which tools will be used, how the document will be created. 
    19  * Setup - In 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. 
    20  * Design - 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. 
    21  
    22  
    23  * For specification tasks 
    2420  * Required auxiliary tools 
    25   * Exact text requirements - for example how the user should be referred (you, You, the user, he, she, ..), What formatting should be used (here you may link an existing page template.) 
    26   * Image/Diagram requirements - file types, file sizes, position, etc. 
     21  * Basic content of the document, a sentence for every fundamental thing. These will be expanded in Implementation section. 
     22  * Useful external links 
     23  * Image/Diagram requirements - content, file types, file sizes, position, etc. 
     24 * 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. 
     25  * Hardware requirements - point specific hardware requirements, limitations if any 
     26  * Software requirements - point which of the suitable tools will be installed and configured.   
     27 * 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. 
     28  * If script are needed, design and link them 
     29  * Link any used tools for maintaining appliances. 
    2730A 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. 
    2831Use the design section [wiki:PageTemplates/TaskPageTemplate#Design] of the Task Page Template.