New software to use Design Patterns

[Josh28]

Hi

We are a group of two chaps just out of undergrad, we created
a software to automate the use of Design Patterns. We have put it up
at Source Forge--http://dpatoolkit.sourceforge.net/
The software has been designed using the .NET framework and
coded in C#.

The patterns can be stored as plug-ins in XML, adding any
number of attributes like Intent, Behavior and the like... Class
diagrams can be drawn to illustrate it further.

The class diagram for your entire design can be created and
edited in our toolkit.

Furthermore there are added on tools like reverse engineering,
code generators and an algorithm(anti-pattern) to eleminate cyclic
redundancy for inheritance.

Please do download it here and post your reviews to us.
http://dpatoolkit.sourceforge.net/


Thanks
The DPT group

 

[Nick Malik]

Hi Josh28,

I downloaded the tool.

It's an interesting start. However, I would hesitate to apply the term
"usability" to this tool.

a) Two patterns are defined, with no text associated with them. There are
23 patterns in the GoF book that you reference, at least 10 of them I would
consider to be essential, foundational, and necessary knowledge. Dozens
more have been identified in other works, some of which you reference in
your manual. Do you think you can provide some patterns for us to use or do
you expect us to define them all?
b) I read the "manual" (If you can call a set of diagrams and about eight
paragraphs of text a manual). At least it told me how to use the GUI. It
was necessary because, without it, it would never have occured to me to say
"Tools->Merge Design Pattern" in order to add a design pattern to the
current display.
c) You provided plug-ins for composite and builder, so I tried that. I got
both patterns (one on top of the other). I decided that I wanted my
Composite abstract class to inherit from the Builder abstract class, so I
added an inherit link. Good... except that the concrete classes that
inherit from the Composite abstract class did not get the methods of the
Builder class... Clearly I will have to implement these methods now that I
have added the inheritance link!
d) Deciding that I didn't want to keep that inheritance link, I tried to
delete it. No can do. I cannot select it. I cannot delete it. At that
point, I gave up. I cannot use a visual designer that will not allow me the
very basic ability to undo a mistake.

Your tool is a good start, in its way. I encourage you to keep trying.
However, what you have here is about 10% useful.

If you want to compare your tool with one that works, from a UML standpoint,
download a free trial of Sparx Enterprise Architect. While that tool does
not do the "design pattern" bits, it does the UML stuff correctly. You can
get a good feel for the kinds of functions that would be necessary if you
want your tool to be integrated with a UML designer.

I am a big supporter of design patterns. I really do want you to do well.
However, you will need to do more to make this app both useful and usable if
you want it to be considered valuable enough to download and use.

Keep going forward, guys. Great Start!

--- Nick Malik
Applications Architect
http://weblogs.asp.net/nickmalik