Comments

Database, Database Engine and VMWare are all software so I would model them as Appilcation System Types or if you're talking about installed instances Application System.

Servers and Virtual Servers I would model as Hardware Component Types or at the instance level as Hradware Components. I know that technically speaking the Virtual Server is not hardware but it is acting as hasrdware and therefore I think this is the best fit from a modeling perspective. 

We are talking about a ‘virtual application’ when a client receives in a window a data stream from a physical or virtual server. From a modeling point of view, it makes no difference if this application is virtual (from another server) or physical (e.g. on our local computer). I would handle both situations in the same way.

The situation is slightly different when it comes to a ‘virtual server’. You can model the virtual server in the same way as a physical server with one exception - a virtual server has no hardware component. Instead of modeling a hardware component for a virtual server, you should connect the virtual server to a physical server on which the virtual server application runs.

Hope it helps.

Thank you for your comments, they were helpful for me :)

Im going to follow your recommendations, thank you !

Hi,

I read the answers to my cuestions and I agree with them, but, what about a DBMS (MySQL for example) and the databases contained inside the self DBMS. I mean, we need to diagram a instance of some DBMS and diagram the database contained inside them, how can we diagram the relation between them? and whats the object that we should use to diagram a database (for example a customer database?

Regards