Changes between Version 6 and Version 7 of PLATFORM_STANDARDS_DESIGN_R1

Timestamp:

01/25/09 22:34:27 (16 years ago)

Author:

boyan

Comment:

--

PLATFORM_STANDARDS_DESIGN_R1

@@ -25 +25 @@
 == How to demo ==
 Show refactored [wiki:PLATFORM_STANDARDS_DESIGN]
+
 = Design =
-
 The [wiki:PLATFORM_STANDARDS_DESIGN] page will be restructured as follows:
 {{{
@@ -33 +33 @@
 |__Task kinds
 |___Coding task
-|____Coding task subkinds
+|____A sample approach
 |___Bug fix
 |___Document
@@ -39 +39 @@
 |___Maintenance
 |__Examples
-|__Coding tasks approach
-|___UML Diagrams
-|___Unit tests
 |__Reviewing
-|___Scores
-|___Super review
 |_Comments
 }}}
@@ -50 +45 @@
 These sections will contain:
  * General information - a brief description of what the design should contain (applying to all task kinds).
- * Task types - for each task type there will be a list of what is required, recommended or optional.
- * Examples - several examples of good and bad designs with brief explanations of their pro and cons.
- * Coding tasks approach - a list of useful tools and brief instructions for their usage - how to make good UML diagrams, how to quickly write good unit tests.
-  * This is a separate section because most of the tasks are coding tasks and their designs are quite difficult and really important.
+ * Task types - for each task type there will be a list of requirements for the design content.
+  * for coding tasks - a list of links about UML & diagrams, test-driven development and automatic testing.
+ * Examples - several examples of good designs.
  * Reviewing - rules for reviewing, scoring and requesting a super review - when a task should fail and when not.
  * Comments - everyone that has some opinion on the standards should describe it here.
@@ -59 +53 @@
 Everyone has been asked to give his opinion in the Comments section. During the implementation these comments will be considered and integrated into the wiki page. The existing requirements will be reviewed and new will be added where necessary.
 
+Everything that is listed in the Task types section is required (there will be no recommended and optional sections as stated in the analysis). Instead, the Reviewing section should state how to score a design and what is required/recommended. The reason is that these things are common for all task kinds.
+
 = Implementation =
-^(Implementation results should be described and linked here (from the wiki or the repository))^
+^(Implementation results should be described and linked here (from the wiki or the repository))
+
 = Testing =
+
 = Comments =
 ^(Write comments for this or later revisions here.)