CASE Tools: A Comparative Analysis

by Ahlyzik M

When implementing a database, one must have the proper tools to design the structure in accordance with best practices. To do so, CASE tools must be used as a guide for developers to properly implement the database. Currently, there are a number of CASE tools in the marketplace, but the ones mentioned in the article were Oracle, Erwin and Microsoft Visio. Each CASE tool has a variety of features that vary in range. For example, the Erwin Modeler has a price tag of just under four thousand dollars but is meant to be used in a professional environment rather than an economic environment. On the other hand, Microsoft’s Visio is fairly cheaper than Erwin or Oracle because the main features of Visio are drawing tools, whereas the other two have the ability to generate code and be used in a production environment. These CASE tools can be used to create great designs, but one must stay within best practices and be trained in order to prevent bad designs. Ultimately the author of the article chose Visio as the best ones to use because of its feature set and its price point.


This article is related to this weeks curriculum because the topic being covered is a comparative analysis between different CASE tools. What I found intriguing about the article is the variation between the different CASE tools. I find it amazing how much the price of the tool can increase simply because of more features. What I like most about the Erwin modeler is the fact that it can generate code for the user when they are implementing a database and creating all of the entities and relationships. This both increases productivity and workflow for a Database Administrator which will then decrease the amount of time it takes to implement a database so there will not be a large amount of downtime for the business.

In my personal use, I found that Visio is quite a versatile program when it comes to designing software as well as building floor plans. Recently, I was an intern at a bank and I had to design and document the process flow of a particular task. I ended up using Visio as it was easy to use and the design elements were easy to use. In addition, I used Vision when taking a class in entrepreneurship because I had to design the floor plan of the mock business that we were creating. The interface is fairly straight-forward with Vision and I agree with the author of the article when he states that this is the best option for the value and versatility. The other two, Oracle and ERwrin are more geared towards an enterprise environment where more customization is needed. Now I will be using Erwin community edition in this class so I will have the opportunity to used to software and see what the differences are.


Callan, Steve (2005, August 10) Making the case for CASE Tools. Database Journal. Retrieved October 1, 2011, from


One thought on “CASE Tools: A Comparative Analysis

  • October 2, 2011 at 5:41 pm

    Personally, I like to use Visio more than the other two CASE tools when I am working with a small database. Visio tends to be simpler to use and more straight forward for an average consumer to use. It’s a great tool for diagramming all sorts of structures. When it comes to a big database though, Erwin will be better since it copes better with large numbers of tables.

Comments are closed.