We performed a comparison between erwin Data Modeler by Quest and No Magic MagicDraw based on real PeerSpot user reviews.
Find out in this report how the two Business Process Design solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."What has been useful, I have been able to reverse engineer our existing data models to document explicitly referential integrity relationships, primary/foreign keys in the model, and create ERDs that are subject area-based which our clients can use when working with our databases. The reality is that our databases are not explicitly documented in the DDL with primary/foreign key relationships. You can't look at the DDL and explicitly understand the primary/foreign key relationships that exist between our tables, so the referential integrity is not easily understood. erwin has allowed me to explicitly document that and create ERDs. This has made it easier for our clients to consume our databases for their own purposes."
"The product lets us import different types of models from various databases."
"The most valuable feature is the physical or visual representation of the database, showing the tables, the columns, the foreign keys, and the ability to generate DDL, so you can physically implement databases."
"It is a scalable solution...The technical support team is fine."
"I have worked with erwin Data Modeler for quite some time and familiarity is its most valuable feature."
"We use the macros with naming standards patterns, domains, datatypes, and some common attributes. As far as other automations, a feature of the Bulk Editor is mass updates. When it sees something is nonstandard or inaccurate, it will export the better data out. Then, I can easily see which entities and attributes are not inline or standard. I can easily make changes to what was uploaded to the Bulk Editor. When taking on a new project, it can save you about a half a day on a big project across an entire team."
"The ability to collaborate between different members across the organization is the most valuable feature. It gives us the ability to work on the same model, regardless of where we are physically."
"It reduces monthly savings by hundreds of thousands of dollars. Think about a company like Costco and all of the points of sale systems in Costco, all of the systems, the applications, but if all the applications in Costco all had their own data model, trying to integrate those, upgrade them and manage their different versions of the same model throughout the store, is an absolute nightmare. It's phenomenally expensive. This helps reduce that cost significantly. I'm talking on the orders of hundreds of thousands of dollars."
"I think one of the key things is the plugins for integration with requirements management tools like Doors"
"I would rate MagicDraw a nine out of ten because of the price. Enterprise Architect has a lot of bugs and MagicDraw is a lot more accurate and flexible. It's a level better."
"When you look at it, No Magic is an all-encompassing tool. You can use it for business architecture design. You can use it for deploying an ERP system across your enterprise. However, it was initially designed and developed for model-based systems engineering. That's the systems engineering required to either produce an IP system or product. It takes away the mounds of paper and puts it into a model. It enables you to generate significant savings by modeling that new product or that system before you ever start developing a prototype."
"I like the traceability feature. Whoever is working with the product would be sure of the things that could be affected if they decided to affect one of the other companies. For example, let's say that an engineer starts a new project optimization problem by adjusting the thickness of metal sheets. However, the engineers only see a reduced number of affections, but when we use the requirement traceability, they can see the whole picture. That's the main aspect that we were promoting with this tool."
"It is very user-friendly, and the customer service is really good."
"The technical support is very good."
"The most valuable features are the visibility, standard compliance, and interface."
"The most valuable feature is the amount of flexibility that one has to model, which is great for an individual."
"The erwin ETL functionality has room for improvement when it comes to mapping databases with a classic entity-relationship model to a data warehouse model."
"I would like to see the reporting capabilities be more dynamic and more inclusive of information. The API is very sparsely understood by people across the user community."
"I still use Visio for conceptual modeling, and that's mainly because it is easier to change things, and you can relax some of the rules. DM's eventual target is a database, which means you actually have to dot all the Is and cross all the Ts, but in a conceptual model, you don't often know what you're working with. So, that's probably a constraint with erwin. They have made it a lot easier, and they've done a lot, but there is probably still room for improvement in terms of the ease of presentation back to the business. I'm comparing it with something like Visio where you can change colors on a box, change the text color and that sort of stuff, and change the lines. Such things are a whole lot easier in Visio, but once you get a theme organized in erwin, you can apply that theme to all of the objects. So, it becomes easier, but you do have to set up that theme."
"I love the product. I love the ability to get into the code, make it automated, and make it do what I want. I would like to see them put some kind of governance over the ability to make changes to the mart tables with the API, so that instead of just using the modeler's rights to a table -- it has a separate set of rights for API access. That would give us the ability to put governance around API applications. Right now a person with erwin and Excel/VBA has the ability to make changes to models with the API if they also have rights to make changes to the model from erwin. It's a risk."
"The reverse engineering in Oracle Databases needs improvement, as there are issues."
"In terms of new features, it would be great to have a cloud base. We should be able to put it on the cloud for better collaboration and data models sharing."
"erwin generally fails to successfully reverse engineer our Oracle Databases into erwin data models. The way that they are engineered on our side, the syntax is correct from an Oracle perspective, but it seems to be very difficult for erwin to interpret. What I end up doing is using Oracle Data Modeler to reverse engineer into the Oracle data model, then forward engineer the DDL into an Oracle syntax, and importing that DDL into erwin in order to successfully bring in most of the information from our physical data models. That is a bit of a challenge."
"Complete Compare is set up only to compare properties that are of interest to us, but some of the differences cannot be brought over from one version of the model to another. This is despite the fact that we are clicking to bring objects from one place to another. Therefore, it's hard to tell at times if Complete Compare is working as intended without having to manually go into the details and check everything. If it could be redesigned to a degree where it is easier to use when we bring things over from one site to another and be sure that it's been done correctly, that would be nice to have. We would probably use the tool more often if the Complete Compare were easier to use."
"The licenses are expensive compared to similar tools. At the moment, the user is open to using MagicDraw if it's 15% more than other solutions. If it were to cost any more, they wouldn't use it."
"It's very focused on specific modern languages and it doesn't do necessarily general systems software engineering with diagrams. They should expand the diagram types for the languages."
"There's lots of documentation. They process multiples of guides. They've got all kinds of guides and documentation out there, but it's kind of hard to find. There are a lot of videos. You can go to YouTube and find videos on how it's been used in different ways, but it just kind of scratches the surface."
"The UI UX of the tool is not really user-friendly and needs to be completely reformed."
"It would be better if the User Interface were updated. At the moment, it's a classic environment. It reminds me of the old Windows interface, for example, Windows 95. It would be better to make it more user-friendly. It would also be better if it could integrate with SAP solutions. It isn't easy to find experts in the field. It's hard to find people around the globe that have the necessary skills and expertise to manage this solution. For example, in our case, we needed someone with refrigeration knowledge that also knew how to use the tool, and that was a challenge. We also had issues relating to erasing. Sometimes, it kept it in the background and didn't erase it at all. We had to review the entire list to ensure that the item was deleted."
"For the next releases, I would like to have them import requirements from other sources. They could make it very easy to do that because there are a lot requirements management tools like DOORS, D-O-O-R-S, Dynamic Object Oriented Management. A lot of folks use DOORS to create a requirement. For those requirements you allocate them to a component in the architecture and a verification method for that requirement. It would be good if we could import those into MagicDraw as components so you don't have to manually do these things."
"One potential area for improvement is the recommendation feature. At times, we face challenges in locating specific features, and we have to reach out for assistance in finding the information we need."
"They don't really support code engineering, and that's why we have to move to Enterprise Architect. MagicDraw is stuck at C++03 standards, whereas most C++ programs today want to use the latest definition of the C++ standards. We were at C++11, and we wanted to do code engineering with C++11 or 17, but they didn't support it. That pushed us into a different tool, which is Sparx Enterprise Architect."
erwin Data Modeler by Quest is ranked 9th in Business Process Design with 37 reviews while No Magic MagicDraw is ranked 10th in Business Process Design with 17 reviews. erwin Data Modeler by Quest is rated 8.6, while No Magic MagicDraw is rated 8.2. The top reviewer of erwin Data Modeler by Quest writes "The product lets users import different types of models, but it is expensive, and the interface must be improved". On the other hand, the top reviewer of No Magic MagicDraw writes "Pretty easy to use and versatile, but doesn't support code engineering and can be overly complicated at times". erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Visio, Lucidchart and MEGA HOPEX, whereas No Magic MagicDraw is most compared with Sparx Systems Enterprise Architect, Visio, Visual Paradigm, Lucidchart and IBM System Architect. See our No Magic MagicDraw vs. erwin Data Modeler by Quest report.
See our list of best Business Process Design vendors.
We monitor all Business Process Design reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.