I am using just part of SAP PowerDesigner as a tool. This makes it easy to switch and maintain the logical level and then create the DDL for Oracle, MSSQL, MySQL, for DB2, or DB2W. But PowerDesigner, as well as erwin can be sued with many different relational databases. There are over 50 or 60 different tools like SAP PowerDesigner, but most of them are limited to maintaining a few relational databases like Oracle or MSSQL. It doesn't matter which relational database as you can use it for MSSQL, Oracle, Postgres. I would highly recommend this product to be used in each and every application system where you have to design a relational database. This is a main benefit over the other solutions which are more neutral and more stand-alone products. We use quite a lot of SAP modules in our organization, so it's a good fit in a way that we can actually link it to some of our SAP servers and database and just reverse engineer the models. That is one advantage because this is actually the SAP program so it has a good connection with the SAP product. We will try to connect to different data sources to extract information rather than building a model from scratch. Besides the modeling we also do reverse engineering. But from a whole enterprise setup the repositories, the check in, check out of those things into a central repository, are the key reasons we switched.
#Sap powerdesigner viewer how to
The usability of how to model is pretty similar and there's no big difference in terms of the functionalities. That was the main consideration for switching. SAP has the function to be able to establish the repositories, work in teams and then consolidate and present to a larger audience through a web browser. We selected PowerDesigner here because of the repository setup it caters to. In my previous job, the focus was more on the modeling and data modeling as a stand-alone kit. I used to use ER/Studio and Techwin for modeling. There is still a lot of room for improvement on the web portals in terms of the usability and the visual. That would enhance the whole usability and enterprise nature of the modeling tĪdditional features could support other model types which would improve the connectors to the increasing number of software to service packages now that a lot of the applications are moving into the cloud. You could be adopting the industry standard as with made models, UML and other forms of industry enterprise architecture models. Another improvement would be to adopt more industry models, especially from the enterprise architecture dimension.
It would be ideal if there was a more seamless viewing experience of the models. We are customers of SAP and I'm a manager, data architecture.Īlthough the presentation for viewing the models is good, I think it could be better. From my experience with other products, the SAP UI could be improved by enabling simpler navigation, especially for non-technical users. We will likely carry out a review at the end of the year to see whether the current configuration is enough for us or whether we need to expand. For the web portal which allows viewing of the models, all users in our organization have access rights, meaning there are around 100 people that have access.
#Sap powerdesigner viewer license
In terms of modeling, we have large teams of around 50 to 60 people who have the license to show the different kinds of models in terms of system projects. I model a lot of these into centralized repositories, so they can be used by internal staff to view all the models or to see the lineage and navigate through them, viewing the relationship between the models and staff. We have categories of different models and we use this tool. From a dimension perspective it's like a business application with data and infrastructure. We are using the enterprise architect version of the solution, using the repository to create our enterprise models different business models that include process to data models and application architecture models.
0 kommentar(er)
