sgpem2dman.texi: added the anomaly classes in the subsection about anomaly resolution.

git-svn-id: svn://svn.gna.org/svn/sgpemv2/trunk@377 3ecf2c5c-341e-0410-92b4-d18e462d057c

doc/sgpem2dman.texi

@@ -97,6 +97,10 @@ Free Documentation License''.
 
 @table @strong
 
+@item 2006, February 21st, @r{--- Djina Verbanac}
+Added anomaly classes in the subsection 
+anomaly solving process.
+
 @item 2006, February 7th, @r{--- Matteo Settenvini}
 Added subsection about the anomaly solving process.
 Fixed C++ code conventions about how to document classes,
@@ -428,15 +432,40 @@ This field describes the impact of a bug.
      Request for enhancement
      @end table
 
+
+@item Anomaly Class
+This field contains the name of the class to which the anomaly belongs to.
+There is no need to describe the function of this classes, because as you can see the
+names are self explanatory. 
+
+     @table @sample
+     @item Extra (superfluous)
+     @item Missing
+     @item Ambiguous
+     @item Inefficient
+     @item Improvement needed
+     @item Not conforming to standards
+     @item Risk-prone
+     not wrong but there are known, safer, alternative methods
+     @item Incorrect
+     @item Not implementable
+     @item Safety
+     @item Not adequately documented
+     @end table
+
+
 @item Reporter
 Name and email of the person who discovered the anomaly
 
 @item Date of Identification
 Timestamp at which the anomaly was identified
 
-@item Product type and version
+@item Milestone
-Product (with version number) affected by the anomaly (e.g., architecture, 
+The milestone affected by the anomaly (e.g., m0.1)
-design, code, documentation, @dots{}).
+
+@item Document
+Document (with version number) affected by the anomaly (e.g., Tecnical Specification, 
+Product Definition, code, documentation, @dots{}).
 
 @item Status
 Please choose one and only one of the following states.