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."
"It's important to create standard templates — Erwin is good at that — and you can customize them. You can create a standard template so that your models have the same look and feel. And then, anyone using the tool is using the same font and the same general layout. erwin's very good at helping enforce that."
"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."
"Another feature of erwin is that it can help you enforce your naming standards. It has little modules that you can set up and, as you're building the data model, it's ensuring that they conform to the naming standards that you've developed."
"The visual data models for helping to overcome data source complexity and enabling understanding and collaboration around maintenance and usage are excellent. A picture speaks 1,000 words. Seeing a picture that shows you how the data relates to each other helps you better understand what the data is and how to use it. Pairing that information with a dictionary, which has the definitions of the tables and columns or the entities and attributes, ensures that the users understand what the data is so that they can use it best and most successfully."
"The solution is good for organizing the data and the scripting part is very powerful. It's easy to create technical scripts for models."
"It's a safeguard for me because I'm always concerned that somebody is free handing it and will forget a key coming from the parent. The migrating keys are a great feature. Identifying relationships, non-identifying relationships, and being visually right there to understand the differences are great features. erwin is key to being able to visually understand whatever the customer is requesting. They'll give you words on a paper, but once they can actually view it as a picture, it really comes to life. The data comes to life to where they understand exactly what they're asking for."
"The technical support is very good."
"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 most valuable feature is the ability to quickly build multiple layers within the organizational and business process environments, as well as in the SysML product environments, and converting to files that can be accessed by clients who do not have a system and a teamwork server access."
"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."
"There is a lot of documentation available on the Internet to understand its functionality."
"I think one of the key things is the plugins for integration with requirements management tools like Doors"
"The solution's reporting side needs to be improved."
"We are planning to move, in 2021, into their server version, where multiple data modelers can work at the same time and share their models. It has become a pain point to merge the models from individual desktops and get them into a single data model, when multiple data modelers are working on a particular project. It becomes a nightmare for the senior data modeler to bring them together, especially when it comes to recreating them when you want to merge them."
"I would like to see improved reporting and, potentially, dashboards built on top of that. Right now, it's a little manual. More automated reporting and dashboard views would help because currently you have to push things out to a spreadsheet, or to HTML, and there aren't many other options that I know of. I would like to be able to produce graphs and additional things right in the tool, instead of having to export the data somewhere else."
"One of the things I've been talking to the erwin team about through the years is that every data model should have the ability to be multi-language... When I was working at Honda, it became very difficult to work with the Japanese teams using just one model. You can have two models, one in English and one in Japanese, but that means you have to keep the updates back and forth, and that always increases the risk of something not being updated."
"The modeling product itself is far and above anything else that I've seen on the market. There are certain inconsistencies when it comes to keeping up with other platforms' databases in the reverse-engineering process. It should also support more database platforms."
"I would like the solution to be less rigid in terms of its theory."
"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."
"erwin is not as robust as a data warehousing project I've been on in the past."
"There are some technical features that you have to study and do research on to be able to understand."
"The cost of upgrading the product should be lower."
"When I am working with my Mac and I right-click to copy and paste, it doesn't work."
"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."
"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."
"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."
"I would like to see the ability to deploy live business process models and capture real-time data (without the need for another product tool) so you don't have to be dependent on other products for this functionality."
"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."
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, Lucidchart, Visio and MEGA HOPEX, whereas No Magic MagicDraw is most compared with Sparx Systems Enterprise Architect, Visio, Visual Paradigm, Lucidchart and ARIS BPA. 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.