如何绘制应用程序功能图?

发布于 2025-01-03 14:13:10 字数 253 浏览 1 评论 0原文

我试图找到一些好的读物来澄清这一点,但我无法找到它(或者也许我只是不知道如何正确搜索它)。

我试图找到的是,考虑到您有一个应用程序:

  • 与数据库交互;
  • 与大型机交互;
  • 与外部提供商互动;
  • 等等...

绘制在功能视图中而不是在更技术的视图中表示这一点的图表的最佳方法是什么?什么样的书籍、文章、网站可以帮助我更清楚地了解我应该遵循哪种方法?

提前致谢。

I'm trying to find some good reads to clarify this but I'm unable to find it (or maybe I just don't know how to search this properly).

What I'm trying to find is, considering that you have an application that:

  • interacts with a db;
  • interacts with Mainframe;
  • interacts with external providers;
  • etc...

What is the best approach to draw a diagram that represents this in a functional view rather then in a more techinical view? What kind of books, articles, websites can help me to get a clearer understanding of which approach should I follow?

Thanks in advance.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

情绪 2025-01-10 14:13:10

好吧,

你应该问自己的第一件事:

为什么我要画或想画一个关于这个的图表?

也许你的答案是:

了解这些元素之间的重要/有意义的沟通。

那么我们可以说:

哦,也许序列图可能有帮助......

购买可能是你的答案是:

哦,我担心系统组件的拓扑。那些东西怎么
将被部署?

那么我们可以说:

哦,也许部署图会帮助你......画一个。

所以取决于“上下文”......

UML 图不会解决你的问题。它们帮助您了解系统中棘手和困难的部分,并通过可视化建模思考替代解决方案。

模特不是“自慰”活动。这就像“群交”。当你和别人一起做的时候你会得到最大的好处...

所以主要问题不是画哪个图...主要问题是:

您遇到了什么问题?您想与谁一起寻找解决方案?绘制图表会给您带来什么好处?

对于 UML,我明确建议 Larman 的书:Applying UML and Patterns :检查亚马逊

最后,如果 UML 不符合您的目的,请具有创造性和务实性...使用文本描述,甚至创建您的“自己的”视觉建模:-) 或做任何对你有帮助的东西...

Well,

First thing that you should ask yourself:

Why I am drawing or want to draw a diagram about this?

Maybe you answer is :

To understand important/significiant communication between those elements.

Then we can say:

Oh maybe sequence diagram may help...

Buy may be you answer is:

Oh I am worry about topology of system components. How those things
will be deployed?

Then we can say that:

Oh, may be deployment diagram will help you...Draw one.

So depends on "context"...

UML diagrams will not solve your problems. They help you to understand tricky and hard part of your system and think about alternative solutions by visual modeling.

Modeling is not "self masturbating" activity. It is like "group sex". You will get most benefit when you do with others...

So the main problem is not to draw which diagram... The main problem is:

What kind of problem you have? With whom you wanto to find solution? What kind of benefit may you get from drawing a diagram?

For UML i definelty suggest Larman book: Applying UML and Patterns :Check at amazon

And lastly, if UML does not fit your purpose, be creative and pragmatic...Use textual desription or even create your "own" visual modeling :-) or do anthing which help you...

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文