Enterprise Architecture Mind Maps


I’m a big fan of mind maps for their simplified communication style. So when I stumbled across these interesting Enterprise Architecture Mind Maps I had to share.

Take a look if you use a Mind Mapping tool. It could be a good way for you to communicate the EA space to your customers.



0 thoughts on “Enterprise Architecture Mind Maps”

  1. I use the Freemind tool for mindmapping. Simple and easy to use, publishes HTML and PDF output when needed.
    One thing we with it is take an EA Repository “IT components” report listing the content of our repository (using a simple layers & categories model to organize it) as an XML file, do an XSLT transform to Freemind “.mm” format, then load it in Freemind and publish as HTML on an intranet website. It’s a nice way to visualize the repository, and if you use the Freemind client you can hack away stuff you don’t want and add freeform content (missing items, notes, etc.) when doing analysis or asking questions.
    I also use Freemind to quickly build an ad-hoc model, re-organize it, then transfer it to a formal modeling tool or repository, depending on the task at hand. I think I can use it for interviewing folks, too, in order to quickly capture their thoughts with at least some structure. I saw a video presented by the makers of the SmartDraw diagramming tool and they recommend using mindmaps to create your meeting agendas, and as you discuss each topic you capture the notes in the tool. I plan to try this with Freemind.
    A colleague of mine prefers more formal modeling tools/languages, like UML, because it’s richer, you can have many relationships instead of the rigid hierarchy, etc. I agree with him, but most tools that do UML or similar are somewhat slow to use, and often require or lead to “arts & crafts” where you waste time moving things around, resizing, re-coloring. etc. Even PowerPoint leads to the same thing. And with mindmaps I’m not overly concerned about duplicating elements – it’s usually something that’s easy to consolidate and dela with later. Doing a mindmap first just makes things so much faster, and you’re more likely to actually end up with a usable and relatively complete model, even if ad-hoc, than a “pretty” or incomplete yet correct model.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s