部署图中的动态加载库如何？
我的部署图中有一个带有Windows执行环境的设备。该应用程序使用了几个动态加载的库，其中一些库与应用程序部署，另一些则将其用于系统本身。
如何在部署图中通常表示动态加载的库？
我当前的理论是我的应用程序在我部署应用程序特定的动态加载库的窗口中获得了自己的执行环境，并在其外部部署了系统库：
已安装的库b，并将LibraryA的V2与应用程序一起部署，从而阴影系统版本。
My deployment diagram has a device with a Windows ExecutionEnvironment in it. The application uses several dynamically loaded libraries, some of which are deployed with the application, others into the system itself.
How are dynamically loaded libraries normally represented in deployment diagrams?
My current theory is my application gets its very own execution environment within the Windows where I deploy my application specific dynamically loaded libraries, and have the system libraries deployed outside it:
For above diagram the system has v1 of libraryA and libraryB installed, and v2 of libraryA is deployed with the application, shadowing the system version.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您的方法完全有道理：
而且：
这完全适用于动态库，其中一个由OS加载的库，并且可以由多个应用程序使用，每个库都在其自己的地址空间中。
一些提示：
«library»和«可执行文件»UML标准配置文件的刻板印象，以更好地区分不同类型的文物。Your approach makes perfectly sense:
Moreover:
This applies perfectly to dynamic libraries, where there is one library loaded by the OS and that may be used by multiple applications, each in its own address space.
Some hints:
«Library»and«Executable»stereotypes of the UML standard profile to better distinguish different kind of artifacts.