Changes between Version 40 and Version 41 of DEVELOPMENT_OVERVIEW


Ignore:
Timestamp:
11/27/08 12:58:56 (16 years ago)
Author:
kyli
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DEVELOPMENT_OVERVIEW

    v40 v41  
    5757Generally speaking, every task must first be analyzed, then a design must be made, and finally the design is implemented. If the task is a coding one, its implementation is tested. After each phase, a review is made. The tasks, sorted by iterations, can be looked at [http://asteasolutions.net:7080/sophie2/roadmap]. The exact task states and much more are described and regularly updated at [wiki:PROCESS]. This document is fundamental, so read it carefully. [[BR]] 
    5858Every state of a task is important. However, here are the existing recomendations for performing various actions: 
    59  * Analyzing: [wiki:PLATFORM_STANDARDS_ANALYSIS how to write good analysis]. 
     59 * Analyzing: [wiki:PLATFORM_STANDARDS_ANALYSIS how to write good analysis]. Please note, that when you create an analysis, the wiki page you write it in most probably won't exist. If you are logged in the Trac, you will be asked whether to use a page template. You should use TaskPageTemplate. 
    6060 * Coding: [wiki:CODE_TASKS_REQUIREMENTS code tasks requirements], [wiki:CODE_SMELLS code smells](bad code examples), [wiki:LOGGING logging]. [wiki:JAVADOC_CONVENTIONS Javadoc] should also be here. 
    6161 * Testing: [wiki:TESTING auto tests](unit / system), [wiki:PLATFORM_STANDARDS_MANUAL_TESTS_R0 manual tests]. [[BR]]