question for software architects....

[unformed 0]

In a few weeks I'm going to be in charge of redesigning our software architecture as the current system is completely jacked.

I have a bunch of ideas on how to go about doing it ... however, i would like to have a formal set of diagrams to 1) make it completely defined, and 2) make it easier to look at, understand, and explain.

I know that UML is often used to explain the class and structure diagram, however, from using UML myself it seems to make things even more complicated.

I'm wondering if anybody out there has used any diagramming/mapping software that they could recommend.....

This ad space for sale.

[bob.dino 1]

UML contains everything and the kitchen sink, so you can make things far too complex. Stick to a simple subset of the available tools and your life will be a lot easier.

I haven't used any UML modelling tools in best part of a decade, so I'm the wrong person to give advice on that. Besides, Rational Rose 4.0 sucked.

[JohnRich 4]

Quote

I'm wondering if anybody out there has used any diagramming/mapping software that they could recommend...

Attached.

[StreetScooby 5]

System Architect is pretty good. I like to use their leveled data flow diagrams. You can run several "validation checks" to make sure the data flows balance correctly (i.e., data in = data out). Plus, it forces you to come up with a reasonable vocabulary before you start coding (...which is the essence of good software)

We are all engines of karma

[riddler 0]

Quote

from using UML myself it seems to make things even more complicated.

Doesn't that describe pretty much every software methodology?

Is your application data-centric, object-centric or user-centric? Erwin, Rational or Paradigm are the standards.

Trapped on the surface of a sphere. XKCD