We performed a comparison between Bonita and erwin Data Modeler by Quest 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."Process automation with Bonita BPM is really easy."
"Its user-friendliness, along with the availability of comprehensive and clear documentation on the website is the most valuable."
"I find process management and user interface designing the most valuable features."
"Bonita is simple and lightweight and is flexible to integrate with third-party systems. The UI is now flexible, whereas it was previously rigid. Any technology can be used as a frontend, including ReactJS, Angular, and others."
"It is a great product that is powerful in developing applications."
"We use the tool to validate and give access to the users. It is for access management."
"Bonita is user-friendly."
"The most valuable features of Bonita are the connectors, detailed documentation, and web applications. The documentation was useful because it is how I learned how to use it."
"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 generation of DDL saved us having to write the steps by hand. You still had to go in and make some minor modifications to make it deployable to the database system. However, for the data lineage, it is very valuable for tracing our use of data, especially personal confidential data through different systems."
"The most valuable features are being able to visualize the data in the diagrams and transform those diagrams into physical database deployments. These features help, specifically, to integrate the data. When the source data is accumulated and modeled, the target model is in erwin and it helps resolve the data integration patterns that are required to map the data to accommodate a model."
"The fitting model is very intuitive."
"The solution's ability to compare and synchronize data sources with data models is fantastic. We use it for that on a regular basis to make sure that changes haven't been made to the database outside of the modeling process. I can take existing databases and reverse engineer them and understand their structure within 15 minutes. If I didn't have Data Modeler it would take hours. It increases our productivity and helps in understanding our legacy application."
"The data lineage feature is very valuable."
"The modeling portion of the tool is the most valuable. There are some notes, naming standards, and other functions that we use as well. There's a whole boatload of functionality in this thing and we use maybe 10% of it. It seems to be pretty common that not all the functionality is fully utilized. But it's just got gobs and gobs of stuff that you can implement if you so choose to."
"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."
"Installation could be made easier."
"There is a considerable learning curve."
"There could be an improvement in IoT connectivity."
"It is missing some important features that other products have."
"I would like to improve the product's load balancing."
"I have run into a lot of problems because there is not enough documentation."
"Bonita can improve by offering more flexibility. The developer does not receive the code of the application to modify it. Most of the other solutions I have used allow the developers to change or improve the code that is generated."
"The main issue with Bonita is that the workspace crashes sometimes."
"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."
"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."
"It is not a very stable solution. I rate the stability five out of ten."
"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."
"The interface must be improved."
"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 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 would like to see the ability to support more NoSQL platforms more quickly. In addition, enhancing the graphics to render more quickly would be beneficial for any user."
Bonita is ranked 11th in Business Process Design with 27 reviews while erwin Data Modeler by Quest is ranked 9th in Business Process Design with 37 reviews. Bonita is rated 8.2, while erwin Data Modeler by Quest is rated 8.6. The top reviewer of Bonita writes "A simple and lightweight college course automation system with third-party integrations". On the other hand, 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". Bonita is most compared with Camunda, Bizagi, Apache Airflow, IBM BPM and ProcessMaker, whereas erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Visio, Lucidchart and Sparx Systems Enterprise Architect. See our Bonita 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.
