Changes between Version 41 and Version 42 of DEVELOPMENT_OVERVIEW

Timestamp:

11/28/08 13:31:14 (16 years ago)

Author:

kyli

Comment:

--

DEVELOPMENT_OVERVIEW

@@ -55 +55 @@
 = 2. The Process =
 This chapter includes the states of each task until it is completed, the rules you have to follow when performing a task, some good/bad examples. The "writing reports" thing is also placed here. [[BR]]
-Generally 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]]
+Generally 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. Also, tasks are several different types. For explanation what the types are, read [wiki: PLATFORM_STANDARDS_GENERAL]. [[BR]]
 Every state of a task is important. However, here are the existing recomendations for performing various actions:
  * 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.