svn commit: r13074 - trunk/documentation/manual/argomanual.xml
| Newsgroups | gmane.comp.lang.uml.argouml.cvs |
|---|---|
| Message-ID | <[email protected]> |
Author: mvw
Date: 2007-07-15 01:19:07-0700
New Revision: 13074
Modified:
trunk/documentation/manual/argomanual.xml
Log:
Worked out a TODO in CrTooManyClasses: implemented the right intention of this critic.
Modified: trunk/documentation/manual/argomanual.xml
Url: http://argouml.tigris.org/source/browse/argouml/trunk/documentation/manual/argomanual.xml?view=diff&rev=13074&p1=trunk/documentation/manual/argomanual.xml&p2=trunk/documentation/manual/argomanual.xml&r1=13073&r2=13074
==============================================================================
--- trunk/documentation/manual/argomanual.xml (original)
+++ trunk/documentation/manual/argomanual.xml 2007-07-15 01:19:07-0700
@@ -16902,12 +16902,15 @@
<sect2 id="critics.CrTooManyClasses">
- <title>Reduce Classes in diagram <diagram></title>
+ <title>Reduce Classes in namespace <namespace></title>
- <para>Suggestion to improve readability by having fewer
- classes on a diagram. If one class diagram has too many
- classes it may become very difficult for humans to
- understand. Defining an understandable set of class diagrams
+ <para>Suggestion to improve understandability by having fewer
+ classes in one namespace. If one namespace
+ (such as the model, a package, or a class)
+ has too many classes
+ it may become very difficult for humans to
+ understand. Defining an understandable set of
+ namespaces
is an important part of your design.</para>
<para>The Wizard of this critic allows setting of the treshold,