简体   繁体   English

系统序列图和交互图(UP)

[英]System Sequence and interaction diagrams (UP)

I can't really figure this out. 我真的无法弄清楚。 I'm reading a book about object oriented analysis and design (and UML) where UP metholodogy is being applied. 我正在读一本关于应用了UP方法的面向对象分析和设计(和UML)的书。 I came across a question: If you make a system sequence diagram (SSD) do you need to create an interaction diagram for every call in that SSD then? 我碰到一个问题:如果您创建系统序列图(SSD),那么是否需要为该SSD中的每个调用创建一个交互图?

According to me, I believe you should if it would be of value, but I can't truly relate it to Unified Process. 据我说,我认为您应该具有它的价值,但是我不能真正将它与Unified Process联系起来。

http://en.wikipedia.org/wiki/System_sequence_diagram http://en.wikipedia.org/wiki/System_sequence_diagram

The UP is a good process but you should not overweigh it. UP是一个很好的过程,但是您不应该过多考虑。 Take those parts that make sense and start using them. 选择那些有意义的部分并开始使用它们。 I once started using ICONIX which is much more lightweight and helped me to get up and running much faster than RUP (Rational UP). 我曾经开始使用ICONIX,它比RUP(Rational UP)轻巧得多,并帮助我更快地启动和运行。

To answer you specific question: no, you don't need to create interactions for each tidbit. 要回答您的特定问题:不,您不需要为每个花絮创建交互。 The purpose of a model it to simplify reality, not to describe it in more detail than reality itself. 模型的目的是简化现实,而不是比现实本身更详细地描述它。 So you may shorten the story wherever it's obvious. 因此,您可以在明显的地方缩短故事。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM