If you were talking to someone whose organization is considering SAP PowerDesigner, what would you say?
How would you rate it and why? Any other tips or advice?
I definitely recommend it, but you still need to do a proof of concept first because it fits into quite a complex set of tasks that companies will be doing. The main purpose is you actually know what you're letting in for and how much work you may or may not have to do to get it to work the way you want because you can customize it. In the next release, I would like to see better support for NoSQL databases. I would rate SAP PowerDesigner an eight out of ten.
We don't have a business relationship with SAP. We prefer to keep our relationship independent and have no direct relationships with them at the moment. It's certainly a good strategy to migrate to this solution from another tool, but I wouldn't recommend anyone start using it by trying out a trial-and-error strategy. An organization must think first about the migration strategy if they already have a tool and want to migrate before they start. A trial and error approach will waste a lot of time. I'd rate the solution eight out of ten. It's easy to use and you can get good pictures out of it.
Before deploying PowerDesigner, do not underestimate the initial analysis of WHAT will be modeled, as well as HOW and BY WHOM. Are your users prepared well enough for the transition to PD (training, potential changes in the modeling process, ...)? My advice for anybody implementing this solution is not to deploy PowerDesigner fully by yourself. Allow an experienced vendor consultant to explain all of the features and possibilities of the tool to you, and then just decide what and how you want or need to use.
I would rate this solution a nine out of ten.