We estimate that one in ten SOAs make unnecessary use of graphs. Graphically, this number looks like this:
Put another way, it also looks like this:
Put yet another way, it also looks like this:
You can see our point. 1 in 10 is a pretty easy concept. While graphs can be useful, they should only be used where they actually add value. In our experience, the usual culprit for unnecessary graphs is SOA software. This software presumes that all SOAs benefit from a pictorial representation – no matter how simple the concept being presented.
Graphs can be useful, but typically only where they allow a person to compare two or more meaningful pieces of information. If they just put in a picture something easily communicated with words, then there is little or no point. Your SOA looks better (and shorter) without them.