blocks|key|2767388|text|从一般意义上说，没有您“需要”遵循的顺序，也没有任何图表是强制性的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2767389|有一些以UML为中心的方法(如其他地方提到的RUP、FDD、ICONIX+)，这些方法都是有序的，应该生成哪些图表。|2767390|所以，你写的问题的答案是：|2767391|如果您正在使用一种特定的方法--和严格地坚持它--那么它会告诉您什么时候产生什么。|unordered-list-item|offset|length|style|BOLD|2767392|否则就什么都没有了。|2767393|如果您正在尝试采用基于UML的开发方法，那么我建议您查看各种方法并决定使用哪种方法--这将回答您的问题。|2767394|然而，.覆盖了所有这些：是一组工具。在有用的时候使用它们，不要为了进程的缘故而成为进程的奴隶。|2767395|hth。|2767396|entityMap^0|0|0|0|G|1|0|0|0|3|1|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Z|8|@$I|10|J|11|K|L]]|9|@]|A|$]]|$1|M|3|N|5|H|7|12|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|13|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|14|8|@$I|15|J|16|K|L]]|9|@]|A|$]]|$1|S|3|T|5|6|7|17|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|V|$]]

In the general sense there is no sequence you "need" to follow and no diagram is mandatory.

There are UML-centric methodologies (e.g. RUP, FDD, ICONIX as mentioned elsewhere) that prescibe an ordering and which diagrams should be produced. 

So the answer to your question as written is:

<ul>
<li>If you're using a specific methodology - and sticking rigorously to it - then it will tell you what to produce when.</li>
<li>Otherwise there is none.</li>
</ul>

If you're trying to adopt a UML-based development approach then I'd suggest you look at the various methodologies and decide which to use - which will answer your question.

However. Overriding all of that: UML is a set of tools. Use them as and when useful, and don't be a slave to process for process' sake. 

hth.

blocks|key|3125493|text|用例图、类图、对象图、状态图、顺序图、协作图、活动图、部署图、组件图|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3125494|供参考，请参阅以下链接|3125495|http://www.globalshiksha.com/What-is-the-sequence-of-UML-diagrams-in-project-/ugc/4151036607101480|offset|length|3125496|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|2Q|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

Use case diagram, Class diagram, Object diagram, State diagram, Sequence diagram, Collaboration diagram, Activity diagram, Deployment diagram, Component diagram

for reference use below link

<a href="http://www.globalshiksha.com/What-is-the-sequence-of-UML-diagrams-in-project-/ugc/4151036607101480" rel="nofollow">http://www.globalshiksha.com/What-is-the-sequence-of-UML-diagrams-in-project-/ugc/4151036607101480</a>

blocks|key|2767503|text|没有什么比“基于UML的开发方法”更好的了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2767504|UML只是一个符号。这不是指导你的“过程”：|2767505|Role+--->+Activity+--->+Artifact|code-block|syntax|javascript|2767506|如果您想要这样的指南，您可以查看。或下载更多轻型威格特开放版本的OpenUP+downloads.php|offset|length|2767507|​|2767508|📷|atomic|2767509|2767510|但是没有一个软件过程“像”去买衣服。所有的过程都应该根据你的项目的具体需要量身定做。否则“过程”只会扼杀你的软件项目。Sfinnie是绝对正确的。|style|BOLD|2767511|在他的书“Larman(应用UML和模式:面向对象的分析和设计以及迭代开发的介绍)中，以一种轻量级的方式将Rup应用于Uml。|2767512|这里简要介绍了他使用Uml+(process.html)的方式。|2767513|2767514|2767515|2767516|小心不死被UML发烧！死于UML发热|2767517|entityMap|0|LINK|mutability|MUTABLE|url|http://www.eclipse.org/epf/downloads/configurations/pubconfig_downloads.php|1|IMAGE|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/f562cd9a1921a0690075b711c6e0dc04.png|imageAlt|2|http://www.objectsbydesign.com/books/larman_process.html|3|https://developer.qcloudimg.com/http-save/yehe-900000/1fe1f26a48bcec3398aafed0ab1931c5.png|4|http://0-queue.acm.org.millennium.lib.cyut.edu.tw/detail.cfm?id=984495^0|0|0|0|13|D|0|0|0|0|1|1|0|0|0|I|1N|D|0|0|F|C|2|0|0|0|1|3|0|0|0|A|B|7|4|0^^$0|@$1|2|3|4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1R|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|1S|8|@]|9|@$K|1T|L|1U|1|1V]]|A|$]]|$1|M|3|N|5|6|7|1W|8|@]|9|@]|A|$]]|$1|O|3|P|5|Q|7|1X|8|@]|9|@$K|1Y|L|1Z|1|20]]|A|$]]|$1|R|3|N|5|6|7|21|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|22|8|@$K|23|L|24|U|V]|$K|25|L|26|U|V]]|9|@]|A|$]]|$1|W|3|X|5|6|7|27|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|6|7|28|8|@]|9|@$K|29|L|2A|1|2B]]|A|$]]|$1|10|3|N|5|6|7|2C|8|@]|9|@]|A|$]]|$1|11|3|P|5|Q|7|2D|8|@]|9|@$K|2E|L|2F|1|2G]]|A|$]]|$1|12|3|N|5|6|7|2H|8|@]|9|@]|A|$]]|$1|13|3|14|5|6|7|2I|8|@$K|2J|L|2K|U|V]]|9|@$K|2L|L|2M|1|2N]]|A|$]]|$1|15|3|-4|5|6|7|2O|8|@]|9|@]|A|$]]]|16|$17|$5|18|19|1A|A|$1B|1C]]|1D|$5|1E|19|1F|A|$1G|1H|1I|-4]]|1J|$5|18|19|1A|A|$1B|1K]]|1L|$5|1E|19|1F|A|$1G|1M|1I|-4]]|1N|$5|18|19|1A|A|$1B|1O]]]]

There is nothing like "UML-based development approach ". 

UML is just a notation. It is not a "process" which guide you:

<pre><code>Role ---&gt; Activity ---&gt; Artifact
</code></pre>

If you want such a guide you can look Rational Unified Process. Or more light weigt open version OpenUP
<a href="http://www.eclipse.org/epf/downloads/configurations/pubconfig_downloads.php" rel="nofollow noreferrer">http://www.eclipse.org/epf/downloads/configurations/pubconfig_downloads.php</a> can be downloaded

<img src="https://i.stack.imgur.com/sgpK3.png" alt="enter image description here">

But none of the software process are "like" go and buy clothes. All process should be tailored for your project specific needs. Otherwise "process" will just kill your software project.Sfinnie
is absolutely right.

In his book Larman(Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development) apply Rup with Uml in a light weight way.

Here is a short decription of his way of using Uml (<a href="http://www.objectsbydesign.com/books/larman_process.html" rel="nofollow noreferrer">http://www.objectsbydesign.com/books/larman_process.html</a>)

<img src="https://i.stack.imgur.com/03kZA.png" alt="enter image description here">

Be carefull DO NOT DEAD BY UML FEVER!!! 
<a href="http://0-queue.acm.org.millennium.lib.cyut.edu.tw/detail.cfm?id=984495" rel="nofollow noreferrer">Death by UML Fever</a>

blocks|key|2767321|text|您的顺序看起来是对的，但是我不确定是否有一个强制性的序列来创建一个项目的UML图。当它适合你的时候，你应该能够充分利用它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2767322|如果您想要在如何使用UML上建立一个结构，那么您应该了解一下各种软件建模过程。我使用了相当多的一个是ICONIX过程，http://www.informit.com/articles/article.aspx?p=167902。这是一个基于用例的轻量级过程。|offset|length|2767323|entityMap|0|LINK|mutability|MUTABLE|url|http://www.informit.com/articles/article.aspx?p=167902^0|0|1N|1I|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Your ordering looks about right, bu I'm not sure if there is a mandatory sequence for creating UML diagrams for a project. You should really be able to dip in an out of UML when it suits you.

If you want to put a structure on how you use UML, you should have a look into the various software modelling processes that are out there. One that I have used quite a bit is the ICONIX process, <a href="http://www.informit.com/articles/article.aspx?p=167902" rel="nofollow">http://www.informit.com/articles/article.aspx?p=167902</a>. This is a light weight process based on use cases.

blocks|key|3125715|text|在IT项目中，我们基于UML图创建所谓的项目图。在大多数使用UML图的项目中(Choi，H.，Yeom，K.：一种使用架构的4%2B1视图模型进行软件体系结构评估的方法)。见:第九届亚太软件工程会议，第286-293页。IEEE，2002)，(Kennaley+M.：3%2B1+View+of+Architecture+(在3D中)：4%2B1视点框架的扩展。在第七届IEEE/IFIP工作会议上，第299-302页。IEEE+Com-Com，2008)，用例图是在软件开发开始时开发的，用来描述基于软件的系统的主要功能。然后创建类图来显示系统的结构，并建立状态机图来显示系统元素的行为(Issa+A.，Abu+Rub+F.A.：使用业务流程模型执行软件开发项目的早期可行性研究，2007年7月2日至4日在英国伦敦举行的世界工程师大会2007年第一卷WCE，2007年7月2日至4日)，(Dijkman+R.M.，Joosten+S.M.：从业务过程模型中提取用例图的算法，第6次软件工程和应用国际会议(SEA)，美国加利福尼亚州安纳海姆，美国，Acta出版社，第679至684页，2002年)。随后，可以使用活动或序列图来验证其他图的一致性。这些图还使用可视化场景，即用例实现图。但是在我的UML项目中，首先我创建了基于活动UML图的上下文图。上下文关系图包含一个主要过程、几个输入事件和几个输出产品或服务。然后我创建分解图，接下来可以构建无缺陷的用例图。现在，对于每个用例，我首先根据活动图准备用例实现图。我从每个用例实现图中导出:类、状态和系统使用用例图。接下来，我可以创建一个基于系统用例图的序列图，以显示IT系统的内部行为和结构。最后，我创建组件图(基于序列图)和部署图(基于组件图)。Stanisław+Jerzy+Niepostyn，project-media.pl|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3125716|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In IT projects we create so-call project diagrams based on UML diagrams. In the majority of projects using UML diagrams (Choi, H., Yeom, K.: An Approach to Software Architecture Evaluation with the 4+1 View Model of Architecture. In: Ninth Asia-Pacific Software Engineering Conference, pp. 286—293. IEEE Computer Society, 2002), (Kennaley M.: The 3+1 Views of Architecture (in 3D): An Amplification of the 4+1 View-point Framework. In Seventh Working IEEE/IFIP Conference, pp. 299—302. IEEE Com-puter Society, 2008), use case diagrams are developed at the beginning of software development to describe the main functions of the software-based system. Then class diagrams are created to show the structure of the system, and state machine diagrams are built to show the behaviour of system’s elements (Issa A., Abu Rub F.A.: Performing Early Feasibility Studies of Software Development Projects Using Business Process Models, Proceedings of the World Congress on Engineer-ing 2007 Vol I WCE 2007, July 2 - 4, 2007, London, U.K.), (Dijkman R.M., Joosten S.M.: An Algorithm to Derive Use Case Diagrams from Business Process Models, 6th International Conference on Software Engineering and Applications (SEA), Anaheim, CA, USA, Acta Press, pp. 679-684, 2002). Subsequently activity or sequence diagram can be used in order to verify consistency of other diagrams. These diagrams are also using visualizing scenarios i.e. – use case realization diagrams.
But in my UML projects first I create context diagram based on activity UML diagram. Context diagram contains one main process, a few events on input, and a few products or services on output.
Then I create decomposition diagram, which next enable to build busioness use case diagram. 
Now, for each use case, I first prepare use case realisation diagram based on activity diagram. 
From each use case realisation diagram I derive: class, state, and system uses case diagrams.
Next I may create a sequence diagram based on the system use case diagram to show intrnal behaviour and structure of IT system. In the end I create component diagram (based on the sequence diagram), and deployment diagram (based on the component diagram).
Stanisław Jerzy Niepostyn, project-media.pl

What are the sequence that i need to follow when creating UML diagrams

Can you number it and show it as mandatory?

In my thought its should be like below:

<ol>
<li>Use Case (mandatory)</li>
<li>Sequence (mandatory) </li>
<li>Activity </li>
<li>state</li>
<li>Collaboration</li>
<li>Class (mandatory)</li>
</ol>

Please correct if i m wrong !

Sequence of UML diagrams

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

创建UML图时需要遵循的顺序是什么？你能给它编号并显示它是强制性的吗？在我看来，应该是这样的：用例(强制)顺序(强制性)活动状态协作类别(强制性)如果我错了，请改正！

问UML图序列
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UML图序列EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问UML图序列
EN