svn commit: r14183 - trunk/www/googlessoc2008.html

Author: mvw
Date: 2008-03-09 01:38:30-0800
New Revision: 14183

Modified:
   trunk/www/googlessoc2008.html

Log:
My proposals.

Modified: trunk/www/googlessoc2008.html
Url: http://argouml.tigris.org/source/browse/argouml/trunk/www/googlessoc2008.html?view=diff&rev=14183&p1=trunk/www/googlessoc2008.html&p2=trunk/www/googlessoc2008.html&r1=14182&r2=14183
==============================================================================
--- trunk/www/googlessoc2008.html	(original)
+++ trunk/www/googlessoc2008.html	2008-03-09 01:38:30-0800
@@ -60,6 +60,9 @@
 </div>
 * End Suggestion Template* -->
 
+
+<!-- BEGIN of proposals -->
+
 <div class="h3">
 <h3>Module Loader Eclipse-style</h3>
 <p>
@@ -198,6 +201,90 @@
 
 
 
+<div class="h3">
+<h3>Improve a subsystem of your choice by solving existing issues</h3>
+<p>
+The issues database contains many <i>bugs</i> 
+and <i>enhancement requests</i>.
+Go to the query page at 
+<a href="http://argouml.tigris.org/issues/query.cgi?">Issue tracking query</a>,
+and select a subsystem from the list below.
+</p>
+<p>
+The task for the student is to solve 
+as much of these issues 
+within one subsystem
+as (s)he can.
+</p>
+
+<p> These are acceptable subsystems:</p>
+<ul>
+    <li>Class Diagram</li>
+    <li>CodeGeneration and ReverseEngineering</li>
+    <li>Collaboration Diagram</li>
+    <li>Cpp module</li>
+    <li>Critics</li>
+    <li>Csharp module</li>
+    <li>Deployment Diagram</li>
+    <li>Diagrams</li>
+    <li>Explorer</li>
+    <li>GUI</li>
+    <li>Model</li>
+    <li>Model/MDR</li>
+    <li>Module loader</li>
+    <li>Notation</li>
+    <li>OCL and Constraints</li>
+    <li>Other</li>
+    <li>Persistence</li>
+    <li>PHP module</li>
+    <li>Property Panels</li>
+    <li>Sequence Diagram</li>
+    <li>State and Activity Diagram</li>
+    <li>Usecase Diagram</li>
+</ul>
+
+<p>
+Beware: This may seem less interesting than
+adding one big new feature to ArgoUML, 
+but has the big advantage that 
+the work is broken in many small parts, 
+each of which are usefull to solve on its own.
+No pressure for deadlines, 
+no disappointment if a project remains unfinished!
+</p>
+<p>
+Developer contact (at least for most subsystems): 
+Michiel van der Wulp.
+</p>
+</div>
+
+
+
+<div class="h3">
+<h3>Create "Critics" for all UML well-formedness rules</h3>
+<p>
+Critics are ArgoUML's system of warnings, 
+i.e. when you break a rule of UML, then a warning will be generated,
+much like warnings and errors used for source code correctness and style.
+</p>
+<p>
+The UML contains the so-called "Well-formedness rules" (WFR),
+written in OCL,
+which specify constraints to the creation of model-elements.
+</p>
+<p>
+ArgoUML currently contains an outdated set of critics, 
+from the days we supported UML 1.3. 
+These need to be updated to the UML 1.4 standard, and completed. 
+</p>
+<p>
+Developer contact: Michiel van der Wulp.
+</p>
+</div>
+
+
+
+<!-- END of proposals -->
 </div> <!-- h2 -->