erwin Data Modeler

We currently use erwin Data Modeler on a very small scale. We use it to standardize record abbreviations and field names.

We are a big organization that supports multiple applications. We use erwin Data Modeler for database model design before it can actually make to the database.
We build ER diagrams out of requirement documents and then use these ER diagrams to discuss in meetings with functional and DBA teams. Once the design is approved, we further use erwin Data Modeler to make both logical and physical data models, include triggers and constraints in the model, and forward engineer deployment scripts for the DBA team.
erwin Data Modeler has greatly helped us maintain a SDLC for database changes and version control.

We are using erwin Data Modeler for initial design, development and deployment phases. We use it to design ER diagrams for our new databases or incorporate change requests into existing. We then forward engineer deployment scripts for erwin directly and deploy it to various database environments. This has helped us version control and release control in our database environments. It is also easier to discuss with functional team by presenting them with ER diagram block instead of talking to them in database language.

We are using erwin Data Modeler now for the ERD diagram design. We then provide the ERD to end-users or developers so they can make utilize it while designing their applications. We are also using it for some SQL Server change management. For example, when end-users request table changes, we then reverse engineer the existing DB or table, make the change, and then have erwin Data Modeler generate an Alter script that we can reuse once promoted to Production.

Erwin was used as a true enterprise data modeling tool, largely by a team of data architects and modelers, to ensure consistent modeling across the corporation. As a large organization it helped address the needs of multiple developers often needing to work within the same model at the same time. It also provided centralization an assured developers were working with the correct version of the model.