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:
If you're using a specific methodology - and sticking rigorously to it - then it will tell you what to produce when.
Otherwise there is none.
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.
Use case diagram, Class diagram, Object diagram, State diagram, Sequence diagram, Collaboration diagram, Activity diagram, Deployment diagram, Component diagram
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.
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, http://www.informit.com/articles/article.aspx?p=167902. This is a light weight process based on use cases.
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
发布评论
评论（5）
一般来说，没有“需要”遵循的顺序，也没有强制的图表。
有一些以 UML 为中心的方法（例如其他地方提到的 RUP、FDD、ICONIX）规定了顺序以及应该生成哪些图表。
因此，您的问题的答案是：
如果您尝试采用基于 UML 的开发方法，那么我建议您查看各种方法并决定使用哪种方法 - 这将回答您的问题。
但是。 重写所有这些：UML 是一组工具。在有用的时候使用它们，不要为了过程而成为过程的奴隶。
嗯。
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:
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.
用例图、类图、对象图、状态图、序列图、协作图、活动图、部署图、组件图
供参考使用，链接如下
http://www.globalshiksha.com/What-is-the-sequence-of-UML-diagrams-in-project-/ugc/4151036607101480
Use case diagram, Class diagram, Object diagram, State diagram, Sequence diagram, Collaboration diagram, Activity diagram, Deployment diagram, Component diagram
for reference use below link
http://www.globalshiksha.com/What-is-the-sequence-of-UML-diagrams-in-project-/ugc/4151036607101480
没有什么比“基于 UML 的开发方法”更好的了。
UML只是一种符号。它不是一个指导您的“流程”：
如果您需要这样的指导，您可以查看 Rational Unified Process。或者更轻量级的开放版本OpenUP
http://www.eclipse.org/epf/downloads/configurations/pubconfig_downloads。 php可以下载
但是没有一个软件进程“喜欢”去买衣服。所有流程都应根据您项目的具体需求量身定制。否则“进程”只会杀死你的软件项目。Sfinnie
完全正确。
在他的 Larman（应用 UML 和模式：面向对象分析、设计和迭代开发简介）一书中，以轻量级方式应用 Rup 和 Uml。
以下是他使用 Uml 的方式的简短描述 (http://www.objectsbydesign.com/ books/larman_process.html)
小心不要死于 UML 热！！！
UML 热病致死
There is nothing like "UML-based development approach ".
UML is just a notation. It is not a "process" which guide you:
If you want such a guide you can look Rational Unified Process. Or more light weigt open version OpenUP
http://www.eclipse.org/epf/downloads/configurations/pubconfig_downloads.php can be downloaded
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 (http://www.objectsbydesign.com/books/larman_process.html)
Be carefull DO NOT DEAD BY UML FEVER!!!
Death by UML Fever
您的顺序看起来很正确，但我不确定为项目创建 UML 图是否有强制顺序。当 UML 适合您时，您确实应该能够使用它。
如果您想了解如何使用 UML，您应该了解一下现有的各种软件建模过程。我经常使用的一个是 ICONIX 流程，http://www. informit.com/articles/article.aspx?p=167902。这是一个基于用例的轻量级过程。
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, http://www.informit.com/articles/article.aspx?p=167902. This is a light weight process based on use cases.
在 IT 项目中，我们基于 UML 图创建所谓的项目图。在大多数使用 UML 图的项目中（Choi, H., Yeom, K.：使用 4+1 架构视图模型进行软件架构评估的方法。见：第九届亚太软件工程会议，第 286-293 页） . IEEE 计算机协会，2002 年），（Kennaley M.：建筑的 3+1 视图（3D）：4+1 视点框架的放大。第七届工作 IEEE/IFIP 会议，第 299—302 页。IEEE 计算机协会，2008 年），用例图是在软件开发之初开发的，用于描述基于软件的系统的主要功能。然后创建类图来显示系统的结构，并构建状态机图来显示系统元素的行为（Issa A.，Abu Rub FA：使用业务流程模型执行软件开发项目的早期可行性研究，Proceedings of 2007 年世界工程大会 Vol I WCE 2007，2007 年 7 月 2 - 4 日，英国伦敦），（Dijkman RM，Joosten SM：从业务流程模型中导出用例图的算法，第六届软件工程和应用国际会议 (SEA)，美国加利福尼亚州阿纳海姆，Acta Press，第 679-684 页，2002 年）。随后可以使用活动图或序列图来验证其他图的一致性。这些图还使用可视化场景，即用例实现图。
但在我的 UML 项目中，我首先根据活动 UML 图创建上下文图。上下文图包含一个主要流程、一些输入事件以及一些输出产品或服务。
然后我创建分解图，接下来可以构建业务用例图。
现在，对于每个用例，我首先根据活动图准备用例实现图。
我从每个用例实现图中得出：类、状态和系统用例图。
接下来我可能会根据系统用例图创建一个序列图来展示IT系统的内部行为和结构。最后，我创建了组件图（基于序列图）和部署图（基于组件图）。
Stanisław Jerzy Niepostyn，project-media.pl
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