

If you think it’s making your life harder, then you need a little training to focus on the items you will use and more importantly, how to get the tool to work for you to reuse objects between modelers and minimize repeated tasks. PowerDesigner is designed to make your job easier. Your first reaction is probably “Wow, what does all this mean and how/why would I use all these different features?”. You say “Great!” and launch this new tool. The goal here is to streamline the process and documentation of data, application development and enterprise architects while connecting all components together so you can answer these important impact questions. PD utilizes a common user interface and link and sync technology to connect all the metadata into a complete view. Meet PowerDesigner, affectionately known as PD.

Evaluating the consequences to minor and major changes is a massive undertaking since some of your documentation (if you have any at all) is in Visio, some is in MS Word and the rest is spread out between the tool of choice in each department. Documentation regarding the data, the systems and applications is so disconnected throughout the organization, it’s virtually impossible to identify the complete view. Can you tell them the real world cost and consequences of this change? For most people the answer is no. Maybe someone from upper management decides you’re going to convert all your applications to Java to simplify the support and technology requirements of the organization. This open ended question strikes fear into thousands of analysts, dbas and developers every year.

Does this sound familiar? Management calls and says “Can you tell me if we drop this column on the Customer table, what will happen?”.
