We used a solution before erwin called ProForma, but that was a long time ago. It did not have a web front-end so it was really just a client-server piece. Because it didn't have the web front-end, the information we put in there was not very widely used at all.

We switched to erwin it had a web front-end and it was a little more robust. ProForma was easier to use out-of-the-box, but it was not as flexible as erwin. And, at the time that we bought it, the Evolve feature was new. That's what I was looking for. One of my business goals was to publish the enterprise architecture information to as large of an audience as possible, and to have it usable, because people are not going to read a 12-page document about that. But they are likely to do a quick search, look at a couple of web pages, and download that. erwin afforded us that capability and that's what we took advantage of.

We used ProVision. We switched to erwin because The Department of Defense wanted us to switch to it. They wanted something with better support of The Department of Defense architecture framework. ProVision did not have that. Erwin has very capable and validated support of the DoDAF.

We previously used MEGA HOPEX. We switched for two main reasons:

1. The cost. 
2. The complexity of media texts which was making it really difficult to maintain and share with other architects. 

In the end, MEGA HOPEX was really powerful tool. However, if you're not spending your days on it, you can quickly lose how to do things on it. 

We used the erwin Data Modeler tool in the past, before we went to the EA tool. We went with EA to perform enterprise architecture and systems architecture work in a modeling solution. That's the driving reason to use these kinds of high-end tools.

We have used another enterprise architecture product before. In comparison, erwin has the best features for interface, graphics, and integration with third-party applications.

We used Word documents in a SharePoint library so it wasn't a very easy-to-use system. We went with erwin because we liked the flexibility of being able to create the objects with the attributes and relationships that fit our organization. We also liked the usability that the Evolve product provides as a front-end interface that could be used on desktops and mobile devices.

No.

We previously used a data modeling product called Silverrun. We switched because most of our customers were using Erwin and because Erwin did a better job of staying current with most popular RDBMS for reverse and forward engineering.

Our software architects had a different tool that they were using. We were hoping to show that Evolve was more robust and see if we couldn't encourage them to use our tool rather than theirs.

We didn't previously use a different solution.

I've used several other Modeling tool (Embarcadero an System Architect).

No.