Another valuable feature is being able to rearrange the model so that we can display it to users. What is most valuable?īeing able to point it to a database and then pull the metadata is a valuable feature. You generate it, and then you can use it. This means that you don't have to touch anything physical. So, if you have to re-key something, no matter how careful you are, you're going to misspell things, which would cause problems down the track, whereas if you make a mistake in DM, there is only one place you have to go and fix it, and then, you would regenerate the downstream stuff. For example, I saw the word conceptual model misspelled today. It certainly improves accuracy for the generation of target databases because you're only putting information in one spot. It would probably take three or four times longer without the tool. In terms of time-saving, if you had to write it all out by hand, it would take weeks. It is a really good repository of all that sort of information, and then you just push a button, and it generates the other end. You can store all sorts of information within the model itself. You can put in your indexes, and you can put in expected size changes. There are so many parameters you can put on the physical side. You put in the information at one spot, and it flows out from there.
#Visio for mac current seats code#
Its ability to generate database code from a model for a wide array of data sources cuts development time. You don't have to re-key things. If we didn't have the tool, we wouldn't have that visibility and wouldn't have been able to recognize that sort of situation.
They could go and see what wasn't theirs and should be someone else's. We had a point where two stewards were looking at the models, and one of them said, "I think that one that you've got over there is actually mine." The other one said, "I think you're right." So, we actually moved an entity from one subject area to another because now they had the ability to see what was in their subject area. For each steward, you could say, "Well, this is your domain over here." Once they had that, they could understand what you were talking about. So, it improved communication. With the tool, it was a lot easier because you could show a steward how this is his or her domain. In my previous company, when we had 1,000 tables, 6,000 columns, and 14 subject areas, trying to explain to people in the organization was difficult. Without the tool, it would have been impossible. So, having all of it on one platform to be able to tell one story makes it not as fragmented as components have been in the past. We want to bring different erwin components together and tell a business user story. So, it becomes easier, but you do have to set up that theme." 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. 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. 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. So, that's probably a constraint with erwin. 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.
0 kommentar(er)
