We provide the following solutions and extensions in PowerDesigner:
Both for modeling larger areas and modeling in a team, it is always beneficial to set the modeling rules. Although writing down these rules in a Word document is a step in the right direction, it does not guarantee compliance with these rules and practices in all models and by all team members. We will help you to incorporate your own specific rules, requirements, and procedures directly into the PowerDesigner environment:
Everybody has slightly different needs and expectations regarding what purpose each dictionary should serve. We can design optimal implementation in PowerDesigner, the linkage to other models, and the most efficient way to keep the dictionary up to date.
It is quite rare to start from scratch. Frequently, there are pre-existing more or less structured metadata about tables, columns, processes, and classes, their mutual dependencies, comments, etc. We will help you import these metadata from various sources, starting from excel, through DB data to migration from other CASE tools.
Working in teams creates certain pitfalls such as conflicts over the models. Although PD allows detection of these conflicts, it is usually better to avoid them altogether. A special PowerDesigner extension enables doing so by locking individual objects and thus the users can be confident that their modeling will be 100% non-conflict.
Upgrading PowerDesigner models may reveal a variety of problems in the models (either caused by a bug or user errors) resulting in damage or even loss of valuable information contained in the models. Thanks to our service, we can guarantee 100% conservation of all critical information in the models even after the upgrade.
PowerDesigner extension, which allows you to capture more accurately the history of changes done, for example, on tables in data models. These records can be then easily searched through or sorted. It will allow you to answer questions such as: "How and when was the XY business requirement implemented?" How many objects have the user ABC modified in the last two months? How many requirements were implemented this week?"
Do you need to understand the structure of some legacy database in your company? Is the vendor deploying a new primary system and you need to know its structure to extract the data for the data warehousing purposes? Is there a merger with another company that does not have such high standards for documentation or does it develop a data warehouse without any documentation? Let us carry out reverse engineering of these systems for you, display logical model areas on separate diagrams, import all required metadata directly from DB. It may be a matter of a few hours or a few days tops.
Data models of primary systems can be easily extended in PowerDesigner by another skill. The evidence of personal and sensitive data will be significantly easier, and given that GDPR needs to be addressed with respect to processes in your company, PowerDesigner offers the possibility of process modeling and its very close connections to data models.
Do you have DB that is not supported by PowerDesigner and you would like to document its structure? Or even use PowerDesigner for the DB development? PowerDesigner allows you to develop a so-called definition file that will allow you to do so.
Do you need to edit a large number of objects in bulk? For example, adding unified comments for all audit columns in your models? Or do you necessarily have to unify the name conventions of all objects according to new business standards? Did you find an error that has been propagated into many models historically (e.g., by copying objects)? Take advantage of our experience and get the right remedy in the most effective way possible.
If you have a lot of additional work associated with your modeling, this point is probably exactly for you. Sometimes, PowerDesigner may be used for tasks that are quite far from standard modeling. Several examples of already implemented projects: