如何在类图中表示第三个库 [英] how to represent 3rd library in class diagram

问题描述

我正在为我的Android应用设计一个类图。我打算在我的应用程序中使用一些第三个库。

无论如何在我的类图上代表那些库

I am designing a class diagram for my Android app. I intent to use some 3rd libraries to my app.
Is there anyway to represent those libraries on my class diagram

推荐答案

的概念类和静态图的其他元素（类，关系等）与组件的分类（第三方或非第三方）无关。它没有任何区别。在部署图上，您可以以某种方式描述它;它影响了一些开发计划，等等。



但是你知道你绘制所有这些线的方式与开发几乎没有关系吗？这不是科学上的根本。这只是一种帮助您自我组织，执行分析，验证，用作文档，实现参考，需求文档等的方法。



这个就像使用一些共同的语言，通用语言，每个人都会理解的东西，不再是。考虑UML和类似标准或尝试将架构，设计和技术文档形式化为真实科学，这是一个通常的错误，这是一些数学推测和证明的结果。事实上，在所有这些结构中存在很多任意性，仅仅反映了当这些标准/规范出现时许多作者的心态和实际经验。将所有这些问题册封是危险的。

-SA

The notion of class and other element of static diagrams (classes, relationships and the like) has nothing to do with classification of components (3rd-party or not). It just makes no difference. On deployment diagrams, you can depict it somehow; it effects some development plans, and so on.

But to you understand that the way you draw all those lines is barely related to the development? It is not something scientifically fundamental. This is only a way to help you to organize yourself, perform analysis, validation, use as a documentation, reference for implementation, requirement document, and so on.

This is like using some common language, lingua franca, something everyone would understand, no more. It's a pretty usual mistake to consider UML and similar standards or attempts to formalize architecture, design and technical documentation as real science, a result of some mathematical speculations and proof. As a matter of fact, there is a lot of arbitrariness in all those constructs, merely reflecting the state of mind and real experience of many authors of the time when these standards/norms were emerging. It would be dangerous to canonize all this matter.

—SA

这篇关于如何在类图中表示第三个库的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！