I have 2 thoughts regarding ArgoUML and Design Patterns.
- Would it be possible to document the patterns used in the
ArgoUML source?
By this I mean label them both in the Developer's Cookbook and in
comments of the source code itself.
It may make it easier for new developers to join, as they could simply
take note in ways like "Okay, this component fulfills the [ role ]
in this [ design pattern ]" and then become familiar with the
specifics of the Argo implementation. This would allow familiarizing
to follow General ➝ Specific and take advantage of an individual's
prior knowledge of Best Practices.
- What about a subproject that allows a user to quickly generate
models based off of Design Pattern templates?
For example, there might be a "New from Template…" dialog allowing a
user to create a new Model / Package / Class (depending on need) and
present some quick forms for naming the various components.
This would be another tool to help usability and adaptability, as well
as help to spread Best Practices.
-- Tony | "Zearin"
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
|
- [argouml-dev] Design Patterns Tony | "Zearin"
-
